inline-screen — Claude Code prompt: what it does, how to install
inline-screen — a prompt for Claude Code and ChatGPT that guides agents through handling differential screen updates after UI actions.
Apache-2.0 ★ 9,488 updated 2026-11-16
.claude/commands/inline-screen.mdWhat inline-screen does
The prompt instructs an agent on reading screen responses without redundant observation steps. Action results already supply a screen field listing only newly appeared, removed, or modified elements.
For phone interfaces, the agent processes window-grouped element trees or differential treeChanges. The updated entry provides node paths such as w7/0/2 with updated properties, while removed tracks disappeared paths.
When an element is ambiguous or absent from the list, the prompt directs the agent to request a screenshot or visual location. Re-observation is reserved for moments when the screen continues to transition.
What it helps with
- avoid redundant screen capture calls after UI actions
- parse differential phone UI updates using treeChanges
- track added or removed interface elements by window node paths
- request visual fallbacks when an element target is ambiguous
Example prompts for the agent
- Apply inline-screen guidelines to interpret the mobile UI state
- Process the differential treeChanges update for window w7
- Locate node w7/0/2 or ask for a screenshot if the target is unclear
How to install inline-screen
Manually: put the files in place
.claude/commands/inline-screen.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about inline-screen
How to install inline-screen in Claude Code?
Save the prompt contents into your project file at .claude/commands/inline-screen.md.
What does inline-screen do?
It teaches an agent to read differential screen diffs and mobile UI trees without querying observation tools after every action.
How are phone screen updates formatted under inline-screen?
A full phone screen uses window-grouped tree objects, whereas differential updates pass treeChanges with paths like w7/0/2 under updated and removed.
Source text
inline-screen.md · Apache-2.0
- The result of a screen action already includes the screen after the action (`screen`: only elements that appeared, disappeared or changed are listed; anything not listed is unchanged). You do not need to observe after every action. If the target is missing or ambiguous in the elements, request a screenshot or visual location. Observe again when the screen is still changing. - On phone, a full screen includes `tree` grouped by window. A differential result includes `treeChanges`: `updated` gives a node path and its new properties (or a full subtree when added), and `removed` gives paths that disappeared. Paths follow window ID and child indexes, such as `w7/0/2`.
© wangzan101 · Apache-2.0 · wangzan101/Mika