Skip to main content

​
Terminal

The Terminal panel opens a shell in the agent’s container. It is the agent’s own machine: its workspace, its files, its installed OpenClaw.
The agent must be running. A stopped agent has no container to attach to, and the panel says so rather than failing on connect.
This is also how you reach the workspace. The panel has no file manager — the workspace is a directory on the agent’s volume, and a shell reads and writes it the way a shell does.
A shell in the container can break the agent. The workspace survives a redeploy; a badly edited config or a deleted binary is fixed by redeploying, which replaces the container and leaves the volume alone.

​
Logs

The Logs panel streams what the agent’s process is writing, with refresh and export. It is the first place to look when an agent starts and then stops, or answers nothing. Logs come from the running container. An agent that never started has none, and the failure notice on its page is what carries the reason instead — see Start, stop and status.
Last modified on August 31, 2026