The dashboard's System area shows what Crew is doing to the machine, how much work the host can admit, and what sessions consume on disk.
The Tasks view lists active sessions, subagents, scheduled work, Task Runner steps, and workflow calls with their current state and resource use. Use it to find a session holding memory, distinguish queued work from running work, or confirm that the host is idle before a heavy step.
Accepted background work is recorded in the durable task queue. Queued subagents, Task Runner steps, and workflow calls survive a Gateway restart and return to scheduling when the host can admit them.
The Services tab reports Gateway components and the capacity currently in force. The subagent limit shown here reflects available host memory and CPU — it can be lower than the configured maximum when headroom is tight. The resource_status tool exposes the same operational view to an agent so it can choose a narrower path before starting a large fan-out or build.
Crew applies one aggregate ceiling across concurrent agents. When memory becomes critically low, scheduled work defers and new work remains queued or is refused according to the caller's contract, rather than pushing the host into sustained memory pressure. The header shows the current posture.
Configure aggregate limits with resource_limits.max_total_memory_mb and resource_limits.max_total_processes in config.json.
Crew records a redacted event trail for each chat by default. The Crew log panel folds that trail into Status, Usage, Timeline, Tools, and Approvals. Authorized agents can read their own unit and the sessions they dispatched through the Crew log tools.
The session work ledger uses this log to preserve a compact goal, phase, next step, rejected approaches, and artifact pointers across context compaction. Conductor work and Issue Radar use the same durable record.
Set KIROCREW_CREW_LOG=0 before starting the Gateway to disable recording for the whole process. Ledger writes then refuse instead of falling back to an unaudited store. Deleting or trashing a conversation removes its Crew log with it, and Storage counts both together.
The Storage screen reports transcript, attachment, and per-session disk use. Move a session to trash to reclaim it from active storage, restore it when needed, or empty trash to free the bytes permanently. Idle sessions are labeled as idle rather than counted as active work.
System & storage