Assistants

Paste the brief and a shot list comes back

Turning a client’s three paragraphs into forty numbered set-ups is the part of this job that is typing. Connect Latentshoot to Claude or ChatGPT and it becomes one conversation, on a shoot that then behaves exactly as it does in the app.

Start free What a shot list holds

The connector is not a paid feature. Your plan limits apply to it the same way they apply to the app.

Connecting

One address, and nothing else to configure

In Claude or ChatGPT, add a connector and give it this address:

https://latentshoot.com/mcp

There is no key to copy. The assistant reads what it needs from that address, registers itself, and sends you to Latentshoot to sign in and approve it — so the moment you decide whether to trust it, you are looking at your own account and your own team name rather than at a settings box.

The approval screen shows two things about the application asking: the name it gives for itself, and the address your approval is sent back to. The name is a claim anybody can make. The address was registered in advance, and a request naming one that does not match it character for character never reaches this screen.

You approve one of two permissions, or both: reading your shoots, and changing them. A connection belongs to the team, everybody on it can see that the connection exists and who approved it, and anybody who can edit can end it. Ending one takes effect on the assistant’s next request.

What changes and what does not

A model writes the shot list, and nothing after it

Latentshoot rests on one arrangement: the shot list is the only thing anybody maintains, and the running order, the daylight band, the gear list and the call sheet are computed from it. Connecting an assistant does not change that. It puts something good at prose in front of the one document that is prose, and leaves the arithmetic where it was.

So an assistant can write forty set-ups from a brief, put them in the order you would shoot them, and give each one a duration. It cannot tell you the day wraps at 18:40 — it asks Latentshoot, which works that out from the sequence and the unit call, and reads the answer back. Ask the same question in the app and on the connector and you get the same number, because it is the same function answering.

That is also why there is no way to write a start time through the connector, and never will be. A slot’s time is derived, so the thing to change is the order. How the schedule and the daylight work.

In practice

Four things it is actually good at

Turning a brief into a shot list. Paste the client’s email and say which shoot it belongs to. What comes back is groups in shooting order, set-ups under them, and a duration on every one — with the must-haves marked.

Asking how long a day comes to. The running order reads back as a column of times, with the company moves inserted where the location changes and any conflict named. It is the fastest way to find out that a plan is ninety minutes over before anybody has booked a model.

Planning around the light. The golden hour for that place and that date, computed from the coordinates rather than fetched from a service — then the shots asking for it pinned to it, with the rest of the day arranged around them.

Writing up a day that has been shot. Planned against actual, per group, from what on-set mode recorded. Those same actual durations are what a new shot’s estimate is learned from — the median of what that size of set-up has really taken you.

The whole surface

Everything an assistant can do, in full

This is the complete list. It is read from the same file the server answers with, so a tool added to Latentshoot appears here without anybody rewriting the page. Nothing in it deletes.

Finding

Search the team's workReads: Find shoots, shots, clients, contacts and moodboard references by words in them.
Read one recordReads: Read one record in full, by the id `search` returned.

The shoot

List shootsReads: Every shoot this team has, newest first, with its client, its status and its dates.
Read a shootReads: One shoot in full: its days, its groups in order, its locations, who is on it, and every shot with its specification.
Start a shootChanges: Start a new shoot.
Change a shootChanges: Rename a shoot, move it to another client, change its status or rewrite its notes.

The shot list

List shotsReads: The shot list, in shot-number order, filtered however you need it.
Add shotsChanges: Add shots to a shoot, in one call.
Change a shotChanges: Change one shot.

The day

Add or change a shoot dayChanges: Put a date on the shoot, or change one already there.
Read the running orderReads: The day as it will actually run: every set-up in sequence with the time it starts and ends, the company moves inserted where the location changes, the slack before an anchored shot, and any conflict — a shot anchored to a time the day can no longer reach, a day running past midnight.
Work out what to dropReads: When a shoot day has run over — a set-up pinned to a time the day now reaches late, usually golden hour, or a wrap well past the planned one — work out two or three ways to get the time back, and what each does to the pin and to the wrap.
Set the running orderChanges: Replace a day's running order with the sequence you give.
Anchor a shot to a timeChanges: Pin one set-up to a time of day — the golden-hour shot the whole afternoon is built around.
Read the lightReads: Sunrise, sunset, both golden hours, both blue hours and the civil twilights for a place and a date, on the shoot's own clock.

Documents

Read the call sheetReads: The call sheet for a day, assembled rather than written: unit call, each person's own call time, the location with its access notes, parking, permit and nearest hospital, the running order, the light, and anything that conflicts.
Read the gear listReads: What the shot list asks for — bodies, glass and lighting, counted, each line saying which shots put it there — checked against the kit the team owns.
Read the wrap reportReads: What a day was planned to take against what it took, per group and overall, once shots have been captured.

People and places

Add locationsChanges: Add places to a shoot.
Cast people onto a shootChanges: Put people on a shoot.
Read the address bookReads: The team's clients and contacts — the library that outlives any one shoot.
Put references on the moodboardChanges: Paste addresses onto a shoot's moodboard.

Sharing

Create a client share linkChanges: Mint a read-only link to parts of a shoot, for a client or the crew.
List a shoot's galleriesReads: The galleries on one shoot, with how many photographs each holds, how many of those sit in sets hidden from the client, how many pictures guests have selected, and whether the gallery is a draft, published or hidden.
Read what the client choseReads: What each guest selected in a gallery, named as the client's page names it — the filename, and the version's name where they chose an edited version rather than the frame as delivered — with any note they left, and how many frames and selects fall against each set-up.

In the browser

The same tools, in the tab you already have open

Some browsers now let a page hand its own tools to the assistant built into them, through the Web Model Context API. Latentshoot registers the whole list above on every screen of the app, so an assistant in that browser can work on the shoot you are looking at without a connector being added at all. It runs in the session you are already signed in with, so an assistant there can do what you can do, and a read-only member is handed the reading tools alone.

Two tools exist only there, because a connector has no screen to read or to open.

Read what is on screen: What the photographer is looking at in Latentshoot right now: the screen they are on, the shoot it belongs to, and whether their role on the team permits changes.
Open a screen: Move the photographer to another screen of a shoot — the shot list, the running order, the call sheet, the moodboard, people and places, sharing, the gallery, or on-set mode.

The screens it can open are the ones you can: the moodboard, the shot list, people and places, the running order, the call sheet, sharing, the gallery, and on-set mode.

The answers are the same either way. A tool called from the browser is run by the same code the connector runs, on the same shoot data, so the running order an assistant reads in a tab is the running order the Schedule screen draws.

Where it stops

What it will not do

It does not delete. There is no tool for removing a shot, a shoot, a day or a person. An assistant adds work and revises it; taking work away is done in Latentshoot, where you can see what else points at the thing you are about to lose.

It does not find you references. It can put addresses on a moodboard — and each one is fetched by Latentshoot, so a page that is one photograph arrives as the photograph with the photographer’s name on it. But it will not go looking for pictures, and an address it guessed at usually lands as a card saying very little. Searching the photograph libraries is a job for the moodboard, where you can see what you are choosing. More on the moodboard.

It does not get round anything. A read-only member stays read-only. The plan limits are enforced where they always were, at write time, so a second active shoot on the free plan is refused with the same sentence the app gives. What each plan includes.

It is not on set. On-set mode is a phone in a pocket with no signal, and it is built for that: the taps queue locally and go out when the signal comes back. A connector needs a connection. How on-set mode works.

Common questions

Which assistants does this work with?

Anything that speaks the Model Context Protocol, which includes Claude and ChatGPT and a growing number of editors and desktop tools. There is one address to add and no key to copy: the assistant discovers everything else and sends you to Latentshoot to approve it, in your own account.

Can an assistant see shoots I have not asked it about?

Yes. A connection is approved for your whole team, the same way your own sign-in is, so an assistant can list every shoot the team has. It cannot see anything the person who approved it could not see, and you can end the connection under Account at any moment — it stops working on its next request rather than at the end of an hour.

Can it delete my work?

No. There is no tool for deleting a shot, a shoot, a day or a person, on purpose. An assistant adds work and revises it; removing work is done in Latentshoot, where you can see what else points at the thing you are about to lose.

Does it invent the schedule?

No. The running order, the daylight band, the gear list and the call sheet are computed by Latentshoot from the shot list, and an assistant reads them back — it is the same arithmetic the Schedule screen runs, not a second opinion about it. What an assistant may change is the order of the day and the shots pinned to golden hour.

What does it cost?

Nothing beyond your plan. The connector is not a paid feature and the plan limits apply to it exactly as they apply to the app: the free plan still keeps one active shoot, and a shoot beyond that is refused with an explanation rather than a silent failure.

Do I have to add the connector to use this in my browser?

No. Where the browser itself supports the Web Model Context API, the Latentshoot tab hands the assistant in it the same tools, and they run in the session you are already signed in with. The connector is for an assistant that is not in the browser — Claude on your desktop, or a research turn in ChatGPT that starts without a tab open.

Can somebody on my team who is read-only connect one?

They can connect one that reads. The approval screen narrows a request from a read-only member so that permission to make changes is not granted, and the assistant is told it cannot write rather than finding out when a change is refused.

Start with the shot list

Make an account, add the address above to Claude or ChatGPT, and paste in a brief you already have. Free covers one active shoot for as long as you want it.

Start free Everything in Latentshoot