Claude
The Claude panel runs Claude Code, an AI assistant, beside the canvas. You ask in plain words, Claude changes the project, and you watch the canvas.
Open the Claude panel
The panel opens on the right side of the window. It shows Claude Code in a terminal: a text window for a command-line program.
The first time you start Starlight, the panel is already open, large. Later, Starlight remembers your layout.
- Press ⌃` / Ctrl+`: hold ⌃ / Ctrl and press the backtick key. This works from anywhere: a text field, a dialog, the help, the terminal.
- Wait until Claude Code starts in the terminal. The terminal already has the keys, so you can type at once.
⌃` / Ctrl+` goes to Claude. What it does depends on where the keys are:
| When | What ⌃` / Ctrl+` does |
|---|---|
| The panel is closed | Opens the panel. The keys go to Claude's prompt. |
| The panel is open, and the keys are somewhere else | Puts the keys in Claude's prompt. The panel stays open. |
| The keys are already in the terminal | Closes the panel. Claude keeps running. |
| A dialog is open | Closes the dialog first (as Esc does), then goes to Claude. A question that needs an answer stays open. |
Window › Claude, the palette's toggle claude and the canvas menu's toggle claude do the same.
Other ways to open or close the panel:
- Window › Claude;
- toggle claude panel in the command palette;
- right-click an empty part of the canvas, then pick toggle claude.
What Claude needs:
- Claude Code on this computer (the
claudeprogram). The panel uses it with your own sign-in and settings. You set up nothing in Starlight. - A Claude sign-in. If Claude Code is not signed in, it asks you in the terminal. Follow its steps.
- The internet, for the AI model. The link between Claude and Starlight stays on this computer (The MCP tools).
- Claude Code is not installed, or does not start? See When Claude does not start.
Good to know:
- Claude keeps working while the panel is closed. Open the panel again to see what it did.
- Move or dock the panel like any other (Float, dock and pin).
- The terminal follows Starlight's light or dark look. Claude Code draws its own colours: type
/themein the terminal to match them. - Each kind of text has its own shade of grey. Your words and Claude's answers are the strongest. Tool calls are one step softer. Tool results, thinking and status lines are softer again. Errors and changed lines keep their colours.
- A bare `, without ⌃ / Ctrl, does not open the panel. It makes the panel you work in fill the window (Make a panel fill the window). In the terminal, it types a backtick.
- Your keyboard has no ` key, or ⌃` / Ctrl+` does not open the panel? Use Window › Claude or the command palette.
Ask Claude for a change
Tell Claude what you want, in plain words, and watch the canvas.
- Click in the Claude panel.
- Type your request, for example: make the opener's gradient sweep slower, or a 4 s logo loop on STAGE.
- Press ⏎ / Enter.
- Answer Claude in the terminal when it asks something. It may ask before it uses a tool (Permissions and spending).
- Watch the canvas. Claude changes the scene file, and the canvas updates.
Or send it from the command palette, from anywhere:
- Press / or ⌘K / Ctrl+K, and type your request.
- Press ⏎ / Enter on ask Claude: … (or ⌘⏎ / Ctrl+Enter). Your words go to the tab in front. For a new tab, press ⇧⌘⏎ / Ctrl+Shift+Enter.
- The panel opens if it is closed. A line at the top of the window says sent to Claude · tab 2, or why your words wait.
Starlight adds the scene, the selection and the playhead to your words (Compose a change with Claude).
After each change, Claude renders the surface: it draws the final picture of that LED output. Then it looks at the picture. Only then does it say the job is finished.
Claude can also:
- Make AI images and video, always with a price quote first.
- Set up stages, and focus the canvas on one surface.
- Time a scene to a song, with its beats, sections and drops (the big moments).
- Export scenes and the reel (several scenes in one video, see Export).
- Publish to Glimpse, when you ask.
- Add a new effect or node type. It works at once. After a restart of Starlight, you must trust it.
- Read the app's log when something failed.
- Make a new project. You open it yourself.
The full list, with an example for each: The MCP tools.
Talk to Claude
You can speak to Claude instead of typing. Claude Code does this itself: it sends what you say to Anthropic, which turns it into text. It costs nothing extra, and it does not count toward your Claude limits. It needs the claude.ai sign-in that the panel already uses. It does not work with an API key.
- Click in the Claude panel, after the prompt.
- Type
/voiceand press ⏎. Claude Code remembers this. - Hold Space and talk. Let go to stop. Your words appear in the prompt. Press ⏎ to send them.
- The first time, your computer asks if Starlight may use the microphone. Click Allow. On Windows, also check Settings › Privacy & security › Microphone › Let desktop apps access your microphone.
To start and stop with a tap instead of holding Space, type /voice tap. To turn it off, type /voice off.
Undo Claude's change
Every change Claude makes is saved as a version, so you can always go back. In the v list, each of Claude's versions has a short line that says what Claude changed (What each version says).
- Ask Claude: undo that. Claude restores the version from before its change.
- Or click v at the top right and pick an earlier version (Save and go back to a version).
- Or press ⌘Z / Ctrl+Z in the scene that Claude changed.
While a scene is open, Claude edits the live scene. Claude sees the scene as it is on your canvas, with your unsaved edits. Claude's change goes into the open scene, and Starlight saves it as a version. No bar asks you.
- Your unsaved edits are kept. They are saved together with Claude's change.
- Claude's change is one undo step. The first ⌘Z / Ctrl+Z undoes Claude's change and keeps your edits. The notice says, for example,
undid: Claude: write sceneorundid: Claude: fit logo to N (cover). - Did you change the scene after Claude read it? Then Claude's change is refused, and nothing changes. Claude reads the scene again and tries again. So Claude never writes over your newest edits.
- This is also true for a scene that has unsaved edits but is not open (Unsaved edits when you switch).
Another program changed a scene. For example, Dropbox synced a scene from another computer, or Claude restored an old version. Then these rules apply.
- Claude's change is one undo step of its own, for each scene it changed. The first ⌘Z / Ctrl+Z undoes Claude's change and keeps your edits. The notice says
undid: external edit. - The next ⌘Z / Ctrl+Z undoes your own last edit. ⇧⌘Z / Ctrl+Shift+Z brings Claude's change back.
- After ⌘Z / Ctrl+Z, the scene is unsaved. Claude's version stays in Versions until you save over it.
- Did Claude change another scene? Then your unsaved edits on the open scene stay as they are.
Another program changed the scene you are editing. If you have unsaved edits in it, nothing is replaced. A bar asks you first, for example: Another program changed "02-walls" on disk — checkpoint 3f9a1c2 — while you have unsaved changes. If you have no unsaved edits, the scene reloads at once, and no bar asks.
- Reload takes the other version. Your edits go on the undo list, so ⌘Z / Ctrl+Z brings them back.
- Keep mine keeps your edits. Claude's version stays in Versions. ⌘S / Ctrl+S saves your edits over it.
- If Claude deleted or renamed the scene, the bar says so. Keep mine keeps the scene open, and ⌘S / Ctrl+S writes it back.
- While the bar waits, Starlight also keeps your edits as a recovery draft.
Another program changed a scene that has unsaved edits, but is not open. You left that scene before you saved it (Unsaved edits when you switch). Your edits are kept. A bar asks you, for example: Another artist (Dropbox sync) changed "02-walls" on disk. It has unsaved changes here.
- Reload takes the other version. Your edits go on that scene's undo list: open the scene and press ⌘Z / Ctrl+Z to bring them back. They also stay in its recovery draft.
- Keep mine keeps your edits. When you save that scene, your version replaces the other one. The other version stays in Versions.
- If the other program deleted or renamed that scene, its unsaved edits leave the app, but they stay in its recovery draft. A warning says so.
- There is no Compare button yet. To see the other version, open v (Versions).
Make an effect with Claude
Ask Claude for a new effect, for example: a heat haze that wobbles slowly. Claude makes it as an effect module: a small shader saved as data in the project's effects/ folder. It is not code, so it needs no trust prompt.
- Claude makes the effect's folder and writes its shaders.
- Claude checks it. The check compiles it for both graphics systems (WebGPU and WebGL), makes sure that both draw the same picture, makes sure that very wide surfaces export with no seam, and times it on your graphics card.
- Claude looks at pictures of it, and changes it until the check passes.
- Then use it like a built-in effect: add it to a layer, and change its settings or animate them in the properties.
- The heavy badge. The check measures how long the effect takes. If the effects on a layer need more than half of each frame, the layer shows a small heavy badge in the node graph and in its properties. Point at the badge to see how many milliseconds it needs. When the red frame rate shows, its hover names the heavy effect (The red frame rate).
- The time is measured on this computer. Another computer can be faster or slower.
- If the graphics card stops during a check, that version of the effect is switched off on this computer. A line under the canvas says so. Ask Claude to change the effect, and check it again.
- Only a person can publish an effect to the team. Claude cannot.
Point Claude at what you mean
A reference tells Claude exactly which layer, surface, scene or moment you mean.
- Select the layers on the canvas or in the graph, or move the playhead (the marker of the current time).
- Right-click in the Claude panel.
- Pick a reference (see the table). Starlight types it into the prompt, at the cursor.
- Finish your sentence and press ⏎ / Enter. Nothing is sent before that.
| Menu item | What it types |
|---|---|
| reference the selection | Each selected layer or node: its id, its name in the graph, and its place in the scene. For example [node text-1x9k3a text "TOUCHDOWN" at comps.td-stack.0]. With several selected, the item says reference the 3 selected. |
| reference the scene and surface | The scene and its surface, for example [scene 02-walls] [surface N]. |
| reference the playhead | The time in the loop, for example [t=1.250s of 4.000s, frame 37 @30fps]. |
| reference what is here | All of them together: the scene, the surface, the playhead and the selection. |
| reference the selected generation | The job selected in the Generations panel. With several jobs selected, the item says reference the 3 selected generations and types them all, in the order of the list (Select several jobs). Shows only when a job is selected. See below. |
- A selected surface, comp, clock or effect has its own short form:
[surface N],[comp td-stack],[clock pulse],[effect glow on node … at ….effects.0]. - Which surface: the selected surface, or else every surface that shows the selected layers. With nothing selected, it names all the scene's surfaces.
- Grey text next to each item shows what it will type. You cannot pick an item when there is nothing to reference, or when no chat is running.
- Selecting layers never types anything by itself. To take a reference out, select its words in the prompt and delete them.
- Drag and drop: drag a generation job, an asset tile, or files from Finder or File Explorer onto the Claude panel. The panel shows a dashed border. Drop, and Starlight types the reference. A job looks like
[generation gmvje06cr-6560fe#0 "VIP section…" · Magnific One · image · assets/vip.png].#0is the job's first result. An asset is[asset assets/crowd.mp4]. A file is its path: short when it is in the project, in quotes when it has spaces. - A job's right-click menu has mention in Claude too. It opens the Claude panel and types the job's reference. With several jobs selected, it says mention 3 in Claude and types all of them.
- Starlight never presses ⏎ / Enter for you. The reference goes into the prompt at once, also while Claude is working: finish your sentence and send it, and Claude reads it after its current step. If Claude is asking you a question, the reference waits until you answer. A notice says so.
The rest of the menu:
- The menu's title is the front tab's name. It adds · not running when that chat has stopped.
- clear the prompt empties the prompt, like Esc twice. Claude keeps your text in its history: press ↑ to get it back.
- While Claude works, clear the prompt deletes the text letter by letter. It does not press Esc, so Claude keeps working.
- If the prompt does not clear, a notice says so. Then press ⌃C / Ctrl+C in the terminal.
- copy copies the text that you selected in the terminal. It shows only when text is selected.
- paste into the prompt pastes the clipboard. Text with several lines goes in as one paste, and it is not sent.
- new chat, resume an earlier chat…, restart this chat and close this chat: see Work in tabs and Resume an earlier chat. When the chat has stopped, restart this chat says start it again.
- The full menu: Claude menu.
Work in tabs
Each tab is a separate chat (a Claude Code session) with its own conversation.
- Click + to start a new chat.
- Click a tab to bring it to the front.
- To rename a tab, double-click it. Or right-click it and pick rename…. Type a name (up to 40 characters) and press ⏎ / Enter, or press Esc to cancel. A click outside the name also keeps it.
- Drag a tab along the tab strip to change the order. To move it further, hold it at the left or right end of the strip: the strip scrolls. Move nearer the end (or past it) to scroll faster. Press Esc to stop and put the tab back.
- Click × on a tab to end that chat.
- A new tab is called claude 1, claude 2 and so on. Then it shows the title that Claude gives the chat.
- A name that you type replaces Claude's title. Clear the name to go back to Claude's title.
- ↻ restarts the front tab, with the same conversation. Use it when a chat has stopped (○ before its name) or does not respond.
- Right-click a tab for its own menu: new chat, resume an earlier chat…, then rename…, restart this chat and close this chat. The last three act on that tab, also when it is not in front (Claude tab menu).
- When a chat stops, the terminal says
[claude exited; ↻ starts it again with the same conversation]. - Closing the last tab opens a new one. A project can have up to 50 tabs.
- With many tabs, scroll the tab strip with the mouse wheel.
- Tabs belong to the project. Another project shows its own tabs. To bring a chat from another project, open a copy of it (Resume an earlier chat).
- When you open this project again, even after a restart, its tabs come back with their conversations.
- After
/clearor/resumein a tab, the tab keeps the new conversation. That conversation comes back after a restart. The conversation from before/clearis in resume an earlier chat…. - A tab that comes back starts Claude only when you first bring it to the front.
Resume an earlier chat
Open an earlier chat of this project again and continue where it stopped.
- Right-click in the Claude panel.
- Pick resume an earlier chat…. A list opens, called earlier chats in this project.
- Pick a chat from the list. Each one shows its first message and when it was last used.
The chat opens in a new tab and continues where it stopped.
- The time is short: 14:05 (today), yesterday 14:05, oct 18 (this year) or oct 18 2025.
- The list shows the 12 newest chats that no tab has open. A chat where nobody typed anything is not listed.
- With no earlier chats, the list says no earlier chats in this project. At the end, new chat starts a fresh chat instead.
- If no open tab has a conversation yet, but the project has earlier chats, + shows this list first. This helps when a project's saved tabs were lost.
- For an older chat, type
/resumein a tab. This is Claude Code's own list. - In a shared project, the list shows only the chats on this computer.
Chats from your other projects. The same list also shows chats from your other recent projects. Use this to bring a chat from one project into another.
- Open the project where you want to work.
- Right-click in the Claude panel, or on a tab, and pick resume an earlier chat….
- Look under earlier chats in other projects · opens a copy here. Each chat shows its first message, then its project's name and when it was last used. For example: Bolts Arena · 14:05.
- Pick a chat. A copy of it opens in a new tab, with the whole conversation.
- The copy works in the project that is open now. Claude knows which project the chat came from, and which project is open now.
- Claude can still read files in the other project's folder, and copy them into this project.
- Claude can also change the other project without opening it: its scenes, and scenes or files copied from this project into it. Starlight checks each change the same way as in the open project, and puts it in the other project's own version history. It does not change a scene that another artist is editing, or a scene that has unsaved edits on this computer: open that project first. Claude cannot render the other project; open it to see the changes.
- The chat in the other project does not change. The copy and the chat in the other project go separate ways from then on.
- The copy stays in its tab. ↻ and the next start of Starlight continue the copy, not the chat in the other project.
- The terminal's first line says where the copy came from.
- The list shows up to 12 chats from your other recent projects together, newest first. A chat that a tab here is already a copy of is not listed. Use that tab.
- Starlight remembers where a project's chats are when you open the project on this computer. A recent project that you have not opened since you updated Starlight can be missing from the list for about a minute after a project opens. Then it is listed.
- If the chat in the other project is gone from this computer, the tab says so. Close the tab.
Keys in the terminal
After you click in the terminal, your typing goes to Claude. Starlight's one-key shortcuts (letters, Space, the arrows, Delete) do not work there. Most of its ⌘ / Ctrl shortcuts still work. These keys help:
| Key | What it does |
|---|---|
| ⌃` / Ctrl+` | Closes the panel. Claude keeps running. |
| ⇧Esc / Shift+Esc | Gives the keys back to the canvas. The panel stays open. |
| ⌘S / Ctrl+S, ⌥⌘S / Ctrl+Alt+S | Save the open scene, or save all scenes. These keys never go to Claude. |
| ⌘PageDown / Ctrl+PageDown, ⌘PageUp / Ctrl+PageUp | Open the next or the previous scene. |
| Every other ⌘ key (Mac) | Starlight's, for example ⌘K, ⌘/, ⌘,, ⌘F and ⌘E. Only ⌘C, ⌘V, ⌘X and ⌘A stay in the terminal. |
| ⌃ + a letter (Mac) | Claude's. ⌃C, ⌃R, ⌃K and the others are Claude Code's own keys. |
| Ctrl+K, Ctrl+/, Ctrl+,, F11 (Windows) | Starlight's: the command palette (both keys), Settings and full screen. Every other Ctrl + letter is Claude's, for example Ctrl+R, Ctrl+L and Ctrl+O. |
| Alt, F10 (Windows) | Claude's. They do not go to the menu bar while the keys are in the terminal. |
| Esc | Claude's own key: it stops what Claude is doing. |
| ⇧⏎ / Shift+Enter | A new line in the prompt, without sending it. |
| ⌘C / Ctrl+C | Copies the selected text. On Windows, with nothing selected, Ctrl+C stops Claude. Ctrl+Shift+C always copies. |
| ⌘V / Ctrl+V | Pastes. On Windows Ctrl+Shift+V pastes too. |
| ⌃V (Mac) | Claude Code's own key: it pastes an image from the clipboard. |
| ⌥-drag / Shift-drag | Selects text when a plain drag does not select it. |
- A click outside the panel also gives the keys back to Starlight.
- A right-click opens the Claude menu. The text you selected stays selected.
- On Windows, Alt and a letter goes to Claude. It does not open a menu.
- The terminal keeps the last 5000 lines. Scroll up with the mouse wheel.
- All Claude panel keys: Keyboard & mouse.
What Claude knows about Starlight
Starlight gives every chat a guide to the app, so Claude works the same way in every project.
- The Starlight plugin comes with the app and loads in every chat. Its skills (short guides for Claude) are in the table.
- The project's own notes are
CLAUDE.mdin the project folder, and any skills in.claude/skills/. Claude reads them too. - Put what is special about this job in
CLAUDE.md: the venue, the client, the content. Starlight writes a firstCLAUDE.mdin every new project. - Help › Reveal Skills Folder in Finder (on Windows, Help › Show Skills Folder in Explorer) opens the project's
.claude/skillsfolder. - The project's notes and the plugin may disagree about how the app works. Then Claude follows the plugin.
- Type
/skillsin a tab to list the skills that Claude has.
| Skill | What it teaches Claude |
|---|---|
starlight:mcp | The Starlight tools, how to change a scene, how to check the picture, undo, and money |
starlight:scene-yaml | The scene file: every node kind, clocks, effects and stages |
starlight:add-extension | How to add a new effect or node type |
starlight:project-memory | Read the brief first, and record your direction as you give it |
starlight:make-loop | How to make a clip loop with no visible jump |
starlight:led-venue-craft | Good LED content: native pixels, loops, surfaces and corners, seams, cost and delivery |
starlight:sports-venue-craft | Sports venues only: ribbons, energy and team colours |
If the plugin is missing, the terminal's first line says [starlight: the Starlight plugin was not found, so its skills are not loaded in this chat]. Claude can still work. It then uses the notes that get_project gives about each node type and effect.
The brief
The brief is the project's list of what the artists asked for: direction, decisions, likes and dislikes, per scene.
Claude keeps it for you. When you give direction or feedback, Claude adds one short point, in your words (the brief_add tool). At the start of every chat, and before it plans a change, Claude reads the whole brief (brief_read). So the next chat, yours or another artist's, starts from what was decided.
Add to the brief:
- Tell Claude what you want, like or dislike, for example: the pink is too strong, keep it blue.
- Claude records the point. The app adds the date, the time, your name and the open scene.
- For a point about the whole project, say so: for the whole project, …. For another scene, name it: for 03-finale, ….
A point looks like this: - 14:32 · 02-walls · direction: slower gradient sweep, an 8 s loop, not 4 s.
Read the brief:
- Ask Claude, for example: what is in the brief? or what did we decide for 02-walls?
- Or open the files yourself, in
context/direction/in the project folder. To open the folder, choose File › Reveal Project in Finder (Windows: File › Show Project in Explorer).
- For one scene, Claude reads that scene's points and the points for the whole project.
- There is one file per artist and computer,
<artist>@<machine>.md, so two artists never write the same file. - Your name is the artist name in Settings › Project. If it is empty, Starlight uses your computer's user name.
- Each point has a kind: direction (what you want, the default), decision, like, dislike or note.
- You can add lines to your file by hand. Claude reads them as notes.
- The brief is a summary. The full chats are in
context/sessions/(Where chats are logged). - Going back to an earlier version never removes points from the brief.
- In a shared project, a file that is still downloading from Dropbox is skipped. Claude is told which file.
Where chats are logged
Every chat is saved in the project as a file you can read, so nothing is lost.
- Each chat goes to
context/sessions/while it runs, a few seconds behind. The file name has the date, your name and the chat, for example2026-10-20_rosco_dfb550b2.md. - It has your words exactly, Claude's replies, and one line for each thing Claude did, for example wrote scene 05-gradients.
- It leaves out Claude's thinking and the raw output of the tools.
- Starlight removes secrets, such as API keys, before it writes.
- ⌘K compose requests go there too, in one file per day. So do Claude Code sessions that you run yourself in the project folder.
- The app writes these files. Do not edit them.
- Details: What the project remembers.
Permissions and spending
Claude asks before it acts, and it cannot spend more than you allow.
- Claude asks first. Claude Code asks in the terminal before it uses a tool, runs a command or edits a file. It does not ask again for what you allowed before.
- Your answers are kept in
.claude/settings.local.json, in the folder where Claude runs. This file is never part of a version. - In a shared project, Claude runs in a folder on this computer. So your answers never go to the other artists.
- Money is quoted first. Before a generation, Claude shows you the price and waits for your yes.
- One job can never cost more than Settings › Generation › MCP cap: $20 by default. Set it to 0 to stop Claude spending. Bigger jobs go through the Generations panel.
- Jobs with no price. Some models have no price, so the cap cannot check them. Claude tells you the cost is unknown and starts the job only if you say yes. Check your provider's dashboard for what it cost.
- When Claude cancels a job, Starlight stops following it at once. A job that the service already accepted may still finish and cost money.
- Your grades: Claude reads your grades before it makes new versions. It changes a grade only when you ask.
- Shared projects: Claude cannot write a scene that another artist has locked (it shows a padlock). The same rule applies to you.
- Glimpse: Claude publishes a look only when you ask (Publish to Glimpse). It replaces another person's look only when you ask for that too.
The MCP tools
Claude works on Starlight through MCP: a local connection that gives Claude a set of Starlight tools. The tables show what you can ask for.
- Starlight runs this MCP server inside the app, on this computer only (127.0.0.1, port 4150 or the next free port).
- The connection works offline. Claude itself needs the internet for the AI model.
- There are 37 tools. You do not need their names: ask in plain words. The terminal shows each tool's name when Claude uses it.
- The tools work only while the project is open in Starlight. Tools that render a picture or export need the app window open too.
Scenes and layers
| Ask Claude to… | For example | Tool |
|---|---|---|
| Look at the project: the surfaces, the brand, the scenes, every node type and effect | What surfaces and scenes does this project have? | get_project |
| Read a scene | How is 02-walls built? | read_scene |
| Change a scene: layers, text, colours, motion, effects | Make the opener's gradient sweep slower. | write_scene |
| Make a new scene | Make a scene 05-outro with the logo on every surface. | create_scene |
| Show a scene on the canvas, as a click in the scene list does | Open 05-outro. | open_scene |
| Rename or delete a scene | Rename 03-test to 03-finale. | rename_scene · delete_scene |
| Rename a composition, everywhere it is used | Rename the comp panorama to skyline. | rename_comp |
| Put layers into a comp with a frame, or give a comp a frame | Pre-comp the logo and the title into a 21:9 comp. | precomp · set_comp_frame |
| Show a framed comp as the AI model will get it, and save it as an asset | Show me the hero comp's frame. | render_comp_still |
| Scale a layer to fit a surface (Scale to Fit) | Fit the plate on E1 to the surface height. | fit_layer |
| Make a clip loop (Make a clip loop) | Make the cloud clip loop. | make_loop |
| Make a layer follow something in a video: tracking data from After Effects, Mocha or a CSV file, or a rectangle Claude tracks in the clip itself. The motion lands as per frame lanes (keyframes) | Track the phone screen in shot1 from frame 40, and pin the UI card to it. | import_track · track_region |
Look at one surface at one moment (a small preview; a part of it at full size; or save the full-size file in renders/) | Show me the N surface at 2 seconds. | render_still |
| Look at every surface at one moment, on one picture | Show me the whole room at 2 seconds. | render_surfaces |
| Measure a colour exactly, or compare a surface with a plate frame by frame. Nothing is saved in the project. A still and these checks show the colour of a best export. | What colour is the patch on N at 2 seconds? / Does the N surface match the plate? | probe_pixels · diff_against |
| Go back to the version before its change | Undo that. | restore_checkpoint |
| Run a change through ⌘K compose | Use compose: a 4 s logo loop on STAGE. | compose_run |
- Claude checks a scene before it writes it. If the check finds an error, nothing is written.
- Claude never deletes the last scene. A generation that costs money waits for your yes.
The brief
| Ask Claude to… | For example | Tool |
|---|---|---|
| Record what you want, like or dislike | Keep it blue. The pink is too strong. | brief_add |
| Tell you what was decided | What did we decide for 02-walls? | brief_read |
Stages and the view
| Ask Claude to… | For example | Tool |
|---|---|---|
| List or read the stages of a scene | Which stages does 04-hero have? | stage_list · stage_read |
| Block out a shot in 3D: shapes, figures, a lens | Make a stage: a presenter on a riser, 35 mm lens, 21:9. | stage_write |
| Delete a stage | Delete the hero-walk stage. | stage_delete |
| Capture the stage's grey layout (free) | Capture hero-walk and show me. | stage_capture |
| Show only one surface or comp in the window, or open a stage in the Stage panel | Focus on the STAGE surface. / Show all surfaces again. / Open the hero-walk stage. | canvas_focus |
- A capture uses the saved scene. Save your own stage edits first.
- Focus changes only what the window shows. Renders, exports and Glimpse always use every surface (Focus).
Generations
| Ask Claude to… | For example | Tool |
|---|---|---|
| List the AI models, with their settings and prices | Which video models can make a 10 s clip? | gen_models |
| Get a price, then make an image or a video | Make a night-sky plate for the N surface. Quote first. | gen_create |
| Upscale a picture to a surface's full size, in tiles, and check the seams | Upscale the panorama to 24640×1600 and check the seams. | gen_create · tiles_check |
| Follow jobs, or stop one | How is the Kling job doing? / Cancel it. | gen_list · gen_status · gen_cancel |
Bring a finished result into assets/, with or without its background | Import the second result, with the background cut out. | gen_import |
| Grade results, or act on your grades | Mark that one NG: garbled text. / Redo everything marked soft. | gen_grade · gen_list |
- Claude gets a quote first. It starts a job only after your yes, within the MCP cap (Permissions and spending).
- Cutting out the background is a paid job of its own, so it is quoted too.
- Results stay in
generations/until they are imported (Where results go). - The grades are circled, select, hold, soft, NG and ref (Grade results).
Assets and music
| Ask Claude to… | For example | Tool |
|---|---|---|
Prepare videos that were copied into assets/ by hand (ingest) | Ingest the clips in assets/walls. | assets_ingest |
| Read a song: tempo, beats, sections, drops and the climax | Time this scene to anthem.mp3. Cut on the drop. | music_map |
Export
| Ask Claude to… | For example | Tool |
|---|---|---|
| List the export formats that this computer can make | Which formats can I export here? | export_formats |
| Export a scene: every surface, at full size | Export 02-walls as ProRes, two loops. | export_scene |
| Export several scenes as one export: each scene's own files, nothing joined | Export 01-intro, 02-walls and 03-drop in HEVC. | export_scenes |
| Export the reel: every scene, one file per surface | Export the reel in HEVC. | export_reel |
| Cancel the export that runs now. The monitor then reads export canceled, not export failed. | Stop the export. | cancel_export |
Exports go to renders/ (Export).
Glimpse
| Ask Claude to… | For example | Tool |
|---|---|---|
| Check the Glimpse site, and list its looks | Is Glimpse connected? Which looks are there? | glimpse_status · glimpse_list |
| Publish a scene as a look: the team and the client see it | Publish 02-walls to Glimpse. Do a dry run first. | glimpse_publish |
| Download a look's media into the project | Pull the "Opener v3" look into assets. | glimpse_pull |
- Claude does a dry run first. It shows the look's name, its surfaces and their sizes, and nothing is uploaded.
- A publish uses the saved scene: save first. It exports every surface first, so six surfaces can take about 10 minutes.
Project and extensions
| Ask Claude to… | For example | Tool |
|---|---|---|
| Make a new project. Claude asks you how you will work on it first. You open it yourself (Make a new project) | Make a project "Halcyon Arena" with the surfaces of this one, just me. | create_project |
| Add a new effect or node type (Extensions) | Make an LED scan-line effect. | scaffold_extension |
Logs
| Ask Claude to… | For example | Tool |
|---|---|---|
| Read the app's diagnostics log after a problem. It never leaves this computer | The export failed. Check the log. | get_logs |
Claude calls read_scene, edits the whole scene, then calls write_scene. In a big scene it can send one comp (write_comp) or one layer (write_node) instead. The rest of the scene stays as you have it, your unsaved edits included. An error means nothing was written. Claude fixes the place it names and tries again. Next, it calls render_still and looks at the picture.
If the picture got worse, Claude calls restore_checkpoint. A scene can be valid and still look bad: the picture decides, not the YAML.
Use Claude Code from your own terminal
Any Claude Code session can work on the open project, not only the panel. The panel does these steps for you.
- Open the project in Starlight. Starlight writes
.mcp.jsoninto the project folder. It holds the server's address and the project's access token (a secret code). - In a terminal, go to the project folder, or any folder inside it.
- Start
claude. For the app's own guidance, add--plugin-dirand the plugin folder (below). - If Claude Code asks, approve the
starlightserver. - The
starlighttools are now ready. Ask Claude as you would in the panel.
- The plugin folder on a Mac:
/Applications/Starlight.app/Contents/Resources/claude-plugin. On Windows: theresources\claude-pluginfolder besideStarlight.exe. - The access token is also in
.starlight/mcp-token. Starlight keeps both files out of the version history. Do not share them. - These sessions are logged in
context/sessions/too (Where chats are logged). - No
starlighttools? Starlight is not running with that project. Open the project, and the tools appear. - Opening another project moves the server to that project.
- Error 401, "missing or stale Starlight MCP token"? The session belongs to another project, or the access token changed. Reconnect in
/mcp, or start the session again. - Shared project (Dropbox):
.mcp.jsonand the access token are not in the shared folder. They are in this computer's folder for the project. To open that folder, click the folder button on the mode row in Settings › Project. - So, for a shared project, start
claude --mcp-config "<that folder>/.mcp.json".
When Claude does not start or cannot change the project
The panel and the terminal tell you what is wrong. Find the message here.
| You see | What to do |
|---|---|
| Claude Code is not installed | Click Install Claude Code. Starlight runs Anthropic’s installer for you; it goes in your user folder and needs no administrator password. The panel shows the installer’s last lines while it works, then Claude starts and asks you to sign in. To install it yourself instead, click copy next to an install command, run it in a terminal (Mac: Terminal, Windows: PowerShell), then click retry. |
| The command palette: Claude Code is not installed on this computer | ask Claude sends your words to this panel, so it needs Claude Code too. Install it as in the row above. Your words stay in the bar: press ⏎ / Enter again. |
| Claude could not start | Read the reason under the title. Fix it, then click retry. |
[starlight: the app’s MCP server is not running, so this chat cannot drive the project] | Claude can talk, but it cannot change the project. Quit Starlight and start it again. Then click ↻. |
[starlight: the Starlight plugin was not found, so its skills are not loaded in this chat] | Claude works without the app's guide (What Claude knows). Install Starlight again to get the plugin back. |
○ before a tab's name, and [claude exited …] in the terminal | That chat stopped. Click ↻ to start it again, with the same conversation. |
| Claude Code asks you to sign in | Follow its steps in the terminal. |
| Claude says a scene is read-only | Another artist has locked it (Lock a scene). |
| A job is over the MCP spend cap | Raise MCP cap in Settings › Generation, or start the job in the Generations panel. |
- The install commands are
curl -fsSL https://claude.ai/install.sh | bash(Mac) orirm https://claude.ai/install.ps1 | iex(Windows).npm install -g @anthropic-ai/claude-codeworks on both. - Starlight looks for
claudein the folders that your terminal searches (your PATH). It also looks in~/.local/bin, in Homebrew and in npm's global folder. retry looks again. - To send the details to support, use Help › Troubleshooting › Export Diagnostics… (Diagnostics).
Glimpse
Glimpse shows your scene in the real LED room, in 3D and live. Use it to check how the work looks in the room. Make your changes on the canvas.
Settings
Settings holds your API keys, spend limits, the project's name and folder, the media cache, light or dark mode, the graphics chip, and the logs. Press ⌘, / Ctrl+, to open it.