You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tasks: Documentation for pause/resume lifecycle #1271
Scope: Create comprehensive documentation for task pause/resume lifecycle feature.
Changes:
AI agent compatibility matrix: Document which AI agents support session persistence, what context is lost without it, requirements for full support
Persistent storage requirements guide: Document why persistent storage is needed, required paths (AgentAPI state file, AI agent session dirs like .claude/), minimum storage recommendations, troubleshooting missing storage
Task lifecycle user guide: Document how pause/resume works (automatic pause, manual pause, resume), what gets preserved, viewing logs while paused
Registry module README updates: Document how the AgentAPI module handles shutdown scripts, state file paths, and the new variables (state_file_path, pid_file_path, enable_state_persistence)
Provider shutdown timeout configuration: Document how different providers may have different timeouts for allowing workspace agents to gracefully shut down, and how this will affect task snapshotting. Consider mentioning infra-based timeouts as well (e.g. Kubernetes)
## Pausing and Resuming Tasks
You can pause and resume tasks directly from the Tasks table. Pausing a task
stops the underlying workspace, freeing up compute resources while preserving
task state. This is useful for long-running tasks you want to pause during
periods of inactivity.
Resuming a task restarts the workspace, which takes time while it starts up
and the agent reconnects.
## Task States
When a task stops running, the UI shows a status message along with a preview
of the last 30 AI chat messages. Messages are labeled `[user]` or `[agent]` so
you can quickly see the conversation context.
- **Paused** — The task was stopped manually or by an autostop timeout. Click
**Resume** to continue, or **Edit prompt** to adjust the task before
resuming.
- **Failed** — The workspace build failed. A link to the full build logs is
provided for troubleshooting.
If a log snapshot was captured when the task paused, a timestamp is shown
indicating when it was taken. If no snapshot is available, resume the task to
view logs.
Activity
EhabY commentedon Feb 4, 2026
Docs to add to the
tasks.mdfile for coder/coder#21728EhabY commentedon Feb 17, 2026
More docs to add to the
tasks.mdfile for coder/coder#22063