For AI agents
The studio has two operators: a person, and an agent driving the page through the accessibility tree, a screenshot or script. Everything a person can do, an agent can do the same way.
Read the state
#sigscape-studio-stateis a JSON script tag the shell keeps current: records, tabs, the open tool and its inputs, panels, warnings, and the runner (connected, version, compatible, update).window.sigscapeStudiois the scripting API:help(),state(),commands(),run(id),select(recordId),openTool(capId),addFiles(files).- llms.txt is the same guide as text.
The hooks
| Hook | Where |
|---|---|
| [data-studio="runner-indicator"][data-state] | the footer's runner; ok, attention, problem, empty |
| [data-studio="runner-panel"] | the flyout; its actions are buttons by name |
| [data-studio="runner-update"][data-phase] | the update line; idle, checking, updating, restarting, done, error |
| [data-studio="step"][data-step][data-phase] | a pipeline step and the state of its live or chosen run |
| li[data-run][data-state][aria-current] | a run row; the chosen one carries aria-current |
| [data-studio="export"] | the chain export link |
| [data-record][aria-checked] | a record row in the data panel |
Connect from a script
Open https://sigscape.org/?runner=http://127.0.0.1:PORT&token=TOKEN, the link the daemon prints, and the page is connected. /?tool=tau opens a tool on arrival. The daemon's HTTP API is documented in the reference; its export links are plain URLs with the token as a query parameter.