Task workflow
A task is a conversation with a coding agent in its own container. You choose the repositories and starting branches, then follow the work until you are ready to push the result.
Create a task
- Select one or more repositories from your configured root.
- Choose a starting branch for each repository. caic adopts an available local branch with an upstream, or creates a task branch from your selection.
- Choose a harness and model. Available models depend on the installed harness and its credentials.
- Enter a concrete prompt and send it.
Use Settings to choose the default runtime, image, CPU settings, caches, and host mounts. Each task keeps the runtime it was created with. Sudo needs Docker; rootless Podman does not support it.
The agent edits repository copies inside the container. Your host checkout stays separate. Multi-repository tasks share one conversation and container.
Follow and steer the work
The transcript streams agent text and tool calls. Expand a tool call to inspect its arguments and result. Native subagent and background-command cards show the activity the harness reports, including outcomes when available. The task header lists Loaded skills for the current context. The list resets after context compaction or a clear, while earlier loads stay linked in the transcript. Expand a past session to review its previous skills. Its info dialog reports the session's context compaction.


Follow the agent while it runs. When a task waits for another message or asks a structured question, respond to continue. A message you send while the agent works is queued and delivered after the current turn; later messages append to the same queued prompt. Choose Edit, or press Arrow Up in an empty composer, to move the queued prompt back into the composer. Agents can also render interactive widgets in the conversation.




When an agent presents a plan, review it before continuing.


Task cards show running background commands, subagents, and watches as icons beside the model, and a failed turn's error while the task waits.


Agent links to generated images and files open in a document pane beside the conversation. Prompt images appear as thumbnails and open in the same pane. caic serves them from the task log, so they survive reloads. The conversation stays mounted while you read, and app-viewport full screen hides the surrounding chrome. caic previews Markdown with relative links and images, PDFs, audio, video, bounded text, and CAD models: STL, STEP or STP, compressed STEP, and 3MF with filament colors and printing plates where the file provides them. Mermaid diagrams render inline in Markdown. Other files offer a raw download. On mobile, the task and document use separate views. These files depend on the task's retained runtime, so save artifacts you need before purging it.
Review and push
Open a repository's changes from the task card or task view. Check commit history, missing upstream commits, and file diffs. Expand individual files to read their changes.


Choose the appropriate push action to send a task branch to its remote, or squash-push the changes to the default branch. caic scans for common secrets before pushing; treat this as a safety net, not a guarantee. When the repository has a pre-push hook, caic runs it inside the task container against the commit being pushed, and a rejection stops the push. The task timeline shows each push as one entry with the hook's output; cancel a running push from that entry. A multi-repository push can succeed for some repositories and fail for others. Inspect the result before retrying.
GitHub and GitLab integration provide pull request or merge request creation and CI monitoring. Check your forge setup before enabling automatic CI repair or PR creation in Settings.
Inspect usage and resources
Open task statistics to see token usage, cost, tool timing, sampled container resources, and the task's configured CPU ceiling when the runtime reports it. Task CPU usage stays aggregate because the runtime stream has no per-CPU breakdown, and an explicit ceiling excludes inherited cgroup limits and process affinity. The process view shows running processes in a continuous tree.
The account menu's Monitoring page groups three sections. Usage shows cross-task daily trends with range and subject filters. System shows live whole-machine CPU, memory, network, and filesystem history, including per-CPU meters and any sampling error. Metrics lists server operation measurements with counts, percentiles, and observed ranges. Whole-machine health also appears in the header as always-visible CPU and memory icons. Green means below 80%, orange means 80% or more, red means 90% or more, and gray means a sampling error or disconnected updates. The icons open Monitoring > System.








When host CPU or memory is under pressure, the task list colors the tasks that contribute most to it.
Provider cards show available quota information. Support and freshness vary by provider; an unknown balance does not mean unlimited capacity.
Work from your phone
The web app adapts to mobile browsers. Open a task to read results, send a message, or review changes. Connect the separate Go Mode app for native capabilities.


Keyboard navigation
Press ? or F1 to open the shortcut reference. Arrow keys navigate task cards, Page Up and Page Down switch tasks, and Tab moves between task controls and the composer. Press F4 to toggle voice mode.
When work stops unexpectedly or reaches a quota limit, use Recovery and handoffs.