Diagnose one active CCB-managed agent by checking runtime status, job history, and provider or API logs. Use authoritative records to investigate failures, apply a limited supported repair, and check the same evidence again.
Diagnose a named CCB managed agent using runtime, job-lineage, and provider evidence.
Review the instructions the agent will receive before you install.
Diagnose exactly one current mounted agent. Start with CCB authority:
command ccb ping "$AGENT"
command ccb ps
command ccb queue --detail "$AGENT"
command ccb pend --inbox --detail "$AGENT"
Use ccb trace for a current lineage id and ccb doctor logs for provider/API
evidence. For DSH, the pane is only the managed host process/log surface: pane
text is not prompt, reply, or completion authority. Native authority is the
exact DSH session/RPC event history and turn/end reason recorded by CCB.
Do not read credentials, mutate tmux directly, restart all agents, or submit a GitHub issue without showing a redacted proposal and receiving explicit authorization. Apply only a bounded supported repair, then re-check the same runtime and lineage evidence.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Send work requests to another connected CCB agent with ask. Choose options according to whether the current task depends on the result or the work is independent, with terminal results routed through the existing request chain.
Send questions or hand off work to another agent managed by CCB. Choose whether you need a short answer, a summary, or preserved full text, and distinguish independent tasks from tasks that require a reply.
Delegate work or ask questions through CCB agents, choosing whether you need a brief answer, a preserved full response, or no success report. Select request options according to task dependencies and whether exact input must be retained.
Submit implemented and verified work to its assigned Reviewer, the agent responsible for checking it. Follow a bounded review and repair process, and report completion only after approval, or return a blocked or rework outcome.
Execute one clearly scoped CCB task assigned by an orchestrator, the agent coordinating the workflow. Report a single outcome alongside changed files, commands, verification evidence, and unresolved blockers while leaving workflow authority unchanged.
Carry out one clearly scoped implementation or investigation task, verify the work where possible, and submit evidence to the assigned reviewer. Reports changed paths, verification results, and blockers while preserving controller authority.