Chat, context and shortcuts
Send requests, select project context, use commands and restore conversations.
On this page
Send your first request
Open the intended project, confirm its name in the Agent dock and select a ready model. Describe a bounded task, the relevant objects and the desired outcome. For inspection, explicitly say not to edit files.
Type into the composer and press Enter to send. Shift+Enter inserts a line break. While a command or context suggestion is open, Enter selects that suggestion rather than immediately submitting the whole message. During input-method composition, finish choosing the composed text first.
Expected result: your message appears, followed by activity for that turn and the eventual response. Tool progress is not a final answer. Expand tool groups to inspect the operations and their results.
Add project context
Type @ in the composer to search authorized project references. Select the relevant file or supported object and check its readable reference before sending. Remove a reference you no longer want included. Names alone are not proof that a reference is current; after renaming or moving a file, select it again if it is marked stale.
Provide the smallest useful context. Do not attach credentials, unrelated customer projects or whole directories merely to resolve an error. The Agent's working candidate is project-bound.
Commands and keyboard use
Type / to open the command suggestions. Filter by typing, use Up/Down to move, Enter to select and Escape to dismiss. /help lists the controls supported by the installed version.
| Command | Purpose |
|---|---|
/status |
Inspect project, service, model, run and sandbox status. |
/new |
Start a fresh conversation. |
/resume |
Find and restore a project conversation. |
/model |
Choose the model, thinking level and API access. |
/permissions |
Inspect the conversation's permission boundary. |
/plan |
Draft a native Plan for an objective. |
/review |
Open isolated-candidate change review. |
/compact |
Request supported Codex context compaction, retaining project history. |
/branch |
Fork a finished conversation; approvals do not transfer. |
Commands needing an active run or provider are not equivalent to local interface commands. A disabled action should explain its prerequisite. Do not repeatedly invoke an unsupported action.
Stop, follow up and restore
Use Stop to interrupt active work. Wait for cancellation or the terminal result before assuming tools have stopped. Cancellation does not automatically discard an existing candidate or apply its changes.
You can draft a follow-up while work is active. A draft, an explicitly queued message and live steering are different states: check the queue's status rather than assuming typed text has been sent. Review pending follow-ups before leaving the application.
Use Chats or /resume to reopen a conversation in the same project. Use the conversation tabs to keep separate work distinct. Each run's candidate and approvals remain its own; two tabs do not safely merge engineering changes automatically.
When something looks wrong
A duplicate response, endless working indicator or disconnected service is not proof that a task completed. Inspect /status, retain the run identifier and restore the existing conversation before starting another modifying request. Do not reset history as a first troubleshooting step. For uncertain changes, open review and compare the actual revision.