Related pages
- Where your code runs: the sandbox and what survives it.
- Context and permissions: what the provider permits versus what you approve.
- Issue properties reference: every value each issue property accepts.
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
What to check when a session, issue view, document, artifact, or connection does not behave.
| Symptom | Check |
|---|---|
| A session is waiting | The conversation and the right rail for a pending tool approval or a question. Approvals sit in the right rail until you answer them. |
| An issue is missing from What’s next | Its status: What’s next holds committed work only - Review, In progress, and Planned. Backlog is not in it. Then check the view’s active filters. |
| A document does not look saved | The Saved indicator, then reopen the document from the tree. |
| An artifact is missing | Whether the session actually produced a durable output: chat answers register nothing. Durable outputs appear under Work, then Artifacts. |
| An app is not available | Capabilities, then Apps: the connection state, and the provider authorization behind it. |
| Work vanished after a run ended | The sandbox is ephemeral and resets between sessions, on crash or timeout, or when another agent works in the same space. Work that was never pushed does not survive any of those. |
| A connector action keeps pausing | That is the approval checkpoint working. Read the card: Allow once while you are learning the workflow, Always allow for a tool you trust. |