Docs

Troubleshooting

Each entry below starts from a symptom you can see in Consoles and ends with the action that resolves it.

A connected agent does not appear in Sessions#

Confirm that you connected the correct project from Sessions → Connect agent and used a supported agent: Codex or Claude Code. Then check the activation step for that agent:

  • In Codex, open /hooks and review and trust the installed hooks. Reload an existing task if it was open before setup.
  • In Claude Code, restart the project session after installation.

Then run a new normal turn with a harmless, non-sensitive tool action, as described in Connect an agent. If the real event still does not appear, revoke the connection and create a fresh capture configuration for the same project rather than reusing an expired credential.

Some of the conversation is missing#

Consoles can only display supported events emitted by the agent, and it does not reconstruct the rest. Codex assistant text arrives after a turn completes; hidden reasoning, earlier conversation history, uninstrumented actions, unsupported event types, external file contents, and truncated payloads never arrive. Use a Markdown or MDX file in the workbook to preserve a decision that must survive outside the emitted record. Sessions lists what capture does and does not include.

I expected a session to create a workbook#

It will not. Sessions and workbooks are independent. Create a workbook from Workbooks, then explicitly link the relevant session when you want a shared handoff. See Sessions.

My workbook has no running compute#

This is expected after creation: a new workbook does not start paid CPU or GPU compute. Select or attach the runtime you need and explicitly start it, then run the cell again. Viewing saved files and results does not start compute.

A job cannot find a package, command, or model#

Review the selected runtime and recipe requirements. The displayed CPU/Linux capability is not a contract for a specific distribution or a preinstalled package list. Put repeatable setup commands in the workbook configuration, save needed files in the workbook, and start the runtime again. ComfyUI models are not bundled; add the models your workflow requires.

A result is missing after compute stops#

Only saved workbook files and retained run outputs are available after a stop. Live process state, memory, and files that were never saved are gone. Check the run record for a retention warning or error, then save or declare the required outputs before stopping the runtime. A file path mentioned in a session is only a reference until its bytes are uploaded, imported, or written to the workbook.

I cannot open an app such as ComfyUI#

Opening an app link only reaches a server that is already running. Start the associated compute job, wait until the server is listening, and keep that job running. Then use the workbook's authenticated app link. If the job failed, inspect its logs before retrying.

The agent can see or do more than expected#

Review the connection and scopes you granted. Capture credentials can upload events but cannot read workbooks or execute compute. MCP access is separate and can be limited to reading, writing, execution, recordings, or broader workbook management. Disconnect or revoke a connection from Consoles when it is no longer needed.

A large upload failed#

Hosted storage currently accepts files up to 256 MiB and workbooks up to 2 GiB across 1,000 files, including run archives. Use an explicit HTTPS import when appropriate. Resumable uploads are planned but are not available yet, so retry the completed upload or choose a smaller input.

Not available at launch#

Cross-account invitations and sharing, a public named-action API, and resumable uploads are not available at launch. Keep collaborators and handoffs within the access flows currently shown by Consoles.