ONCUE / GUIDE
Sessions
A session is the durable thread around a task. The browser shows it; a remote sandbox does the execution.
Start with a clear request
Choose the repository and supported model, then describe the desired change. Include relevant constraints, acceptance criteria, and the checks that should be run.
OnCue coordinates the session and its remote workspace. Startup can fail independently of the task itself—for example, if compute or repository access is unavailable.
Follow and steer
Read the conversation and expand tool activity when you need detail. Current source includes structured agent questions and permission modes; answer prompts and add context when a decision needs your input.
The command-output surface is read-only. It should not be treated as an interactive terminal.
Leave, stop, and resume
Leaving the browser does not move execution back onto your device. Session state is managed outside the tab. Stopping work and resuming work are explicit lifecycle actions, subject to the actual run state and sandbox limits.
Persistent conversation history does not mean a sandbox runs forever. Inspect the session state when returning, and do not assume an interrupted run completed successfully.
Understand the result
Review changed files, checks, and warnings together. A verified state means the required recorded checks passed for the relevant revision. It does not establish that all behavior is correct or that every possible check ran.
If a run fails, keep the useful evidence and determine whether the failure came from setup, execution, or verification before retrying.