Stats
Actions
Tags
From maniple
Checks status of all active workers via list_workers and logs, categorizes as ACTIVE/READY/COMPLETED/STUCK, and reports in markdown table with summary and attention needed.
How this command is triggered — by the user, by Claude, or both
Slash command
/maniple:check-workersThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Check Workers Check status of all active workers and report in a consistent format. ## Process 1. Call `list_workers` to get all managed sessions 2. For workers needing investigation, call `read_worker_logs` to understand their state 3. Determine status based on `is_idle`, `status`, and log content ## Output Format Report status in this exact format: ## Status Determination - **ACTIVE**: `is_idle: false` — worker is currently processing - **READY**: `is_idle: true` with no prior assignment or work completed — waiting for instructions - **COMPLETED**: `is_idle: true` and worker lo...
Check status of all active workers and report in a consistent format.
list_workers to get all managed sessionsread_worker_logs to understand their stateis_idle, status, and log contentReport status in this exact format:
## Worker Status Report
| Worker | Type | Status | Issue/Task | Duration | Notes |
|--------|------|--------|-----------|----------|-------|
| Groucho | claude | ACTIVE | cic-xyz | 12m | Working on feature |
| Harpo | codex | READY | - | 5m | Idle, no assignment |
| Chico | claude | COMPLETED | cic-abc | 8m | Logs indicate task done |
| Zeppo | codex | STUCK | cic-def | 20m | BLOCKED: needs API key |
### Summary
- Active: X workers (currently working)
- Completed: Y workers (believe they're done)
- Ready: Z workers (idle, awaiting task)
- Stuck: W workers (blocked or unclear)
### Attention Needed
- Zeppo: Reported blocker - needs coordinator input
is_idle: false — worker is currently processingis_idle: true with no prior assignment or work completed — waiting for instructionsis_idle: true and worker logs indicate the worker believes it has completed its taskis_idle: true but logs show the worker is blocked or status is otherwise unclearTo distinguish COMPLETED from STUCK, use read_worker_logs to check the worker's final messages for completion language vs. blocker language.
Codex workers (agent_type: "codex") explicitly end responses with "COMPLETED" or "BLOCKED: " — check for these markers in their logs.
discover_workers if the user believes there should be some workerscoordinator_badge in list_workers outputnpx claudepluginhub martian-engineering/maniple --plugin maniple/statusSummarizes active swarm coordination state: workers, progress, messages, reservations, active cells, and task list if agent teams active.
/statusChecks status of background sessions and workflows. Specify optional session_id or list all. Supports --verbose and --json flags.
/swarm-statusDisplays compact overview of agent swarm: total agents (active/idle) with examples and statuses/tasks, plus tasks summarized by status (pending, in-progress, completed, failed, blocked). Prompts to join if needed.
/gm-statusChecks the current state of operations by querying daemon status, listing tasks, and agent sessions, then produces a concise summary report.
/statusDisplays current egregore state: work item progress table, pipeline position, token budget, session counts, and recent decision log tail.
/statusDisplays status of tasks in the orchestration system, including summaries, distributions, detailed views, timelines, and velocity reports with filters for date, status, agent, priority, and type.