claude_codex_bridge

Send a request to a CCB agent with `ask`.

Send a request to a CCB agent with `ask`.

Send a request to a CCB agent with `ask`.

Send a request to a CCB agent with `ask`.

Delegate work or request information from another CCB-managed agent using ask. Use when the user asks Grok to ask, delegate to, hand off to, consult, or send work to a named CCB agent, or when project memory requires CCB collaboration.

Send a request to a CCB agent with `ask`.

Proves that a managed Claude session can discover a seeded plugin.

Produce one revision-fenced Planner backfill proposal for either a Detailer replan or task-set closure, with compact Frontdesk status evidence.

Verify one coder node against the assigned execution contract and return pass, rework, blocked, or non-converged evidence.

Submit one node result to the assigned Reviewer and finish only after a bounded pass/rework chain.

Execute one scoped implementation or investigation item and return evidence without changing workflow authority.

Convert user conversation into macro workflow requests and present curated clarification or final artifacts.

Draft task-scoped detail artifacts and a detail packet as reply content for script-owned workflow import.

Clear conversation context for one or more mounted CCB agents using ccb clear. Use when the user invokes /ccb-clear, $ccb-clear, or $ccb_clear, or asks Grok to clear or reset CCB agent context without restarting agents or deleting project state.

Select one route and return one adaptive one-to-four-workgroup bundle candidate as reply-only evidence.

Draft CCB workflow task packets, readiness recommendations, and candidate clarification questions without mutating authoritative state.

Verify integrated round evidence and return a machine-readable round result for script import.

Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state, or GitHub Actions release/test status.

Private built-in CCB configuration skill for agentroles.ccb_self. Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs. Use only inside ccb_self; non-self agents should delegate CCB config changes to ccb_self.

Historical reference for script-owned dynamic-agent lifecycle actions. Do not use from provider sessions.

Historical reference for script-owned loop capacity requests. Do not use from provider sessions.

Verify one CCB worker node and reject hidden fallback, degradation, scope shrinkage, or missing evidence.

Compress planner candidate questions into a compact frontdesk-facing clarification batch and normalize answers back to planner.

Review planner task packets for readiness without rewriting authoritative task state.

Verify a CCB execution round and produce a machine-readable round result artifact.

Execute one bounded CCB work item and report evidence without changing workflow authority.

Diagnose and recover CCB communication and reply delivery stalls. Use when a user reports a missing CCB_REPLY, stuck ask, agent stuck busy/delivering, queued work behind an active job, cancelled/incomplete reply, empty artifact, callback not continuing, duplicate retry after success, or a CCB mailbox/communication backend that appears stuck.

Diagnose and repair CCB ask/job/message/reply/artifact/callback lineage. Use for missing replies, incomplete artifacts, pending callbacks, retry/resubmit/ack decisions, reply delivery problems, or work-chain resume advice.

Diagnose CCB runtime, mounted daemon graph, tmux namespace and panes, provider context, queue/inbox/trace, replies/artifacts, config drift, and storage boundaries. Use when the user asks what is broken, which agent is stuck, whether CCB is mounted, why a reply did not arrive, or what to check first.

Recover CCB agents, panes, mounts, provider contexts, API/provider failures, config reload aftermath, clear operations, and guarded single-agent restarts. Use when the user asks to fix, recover, restart if safe, clear context, reload, remount, or keep work going after provider/API failure.

Clear CCB managed agent conversation context with `ccb clear`. Use when the user writes `$ccb-clear`, `$ccb_clear`, or asks to clear/reset one or more CCB agent contexts without restarting or deleting project state.

Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next state; resume work from TODO/handoff state; move resolved questions into decisions; promote ideas into formal plan artifacts; or keep plan documents and file-structure planning internally consistent without making this project-specific.