메뉴
Complete cortextos bus CLI reference - all available commands with examples. Use when you need to look up a bus command, check syntax, or discover available tools.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | bus-reference |
| description | Complete cortextos bus CLI reference - all available commands with examples. Use when you need to look up a bus command, check syntax, or discover available tools. |
| triggers | ["bus","list-tasks","create-task","update-task","complete-task","send-message","check-inbox","log-event","update-heartbeat","create-approval","send-telegram","list-agents","list-skills","read-all-heartbeats","check-stale-tasks","how do I","what command"] |
Every tool you have. Use them or the system cannot see your work.
All commands are available via cortextos bus <command>.
Create a new task in the system. Tasks are visible on the dashboard.
cortextos bus create-task "<title>" --desc "<description>" [--assignee <agent>] [--priority <p>] [--project <name>]
urgent | high | normal | low. Defaults to normalExample:
cortextos bus create-task "Write blog post" --desc "Draft a 500-word post on agent orchestration" --priority normal
Update a task's status. Use this when you START working on something.
cortextos bus update-task "<task_id>" <status>
pending | in_progress | blocked | completedExample:
cortextos bus update-task "task_abc123" in_progress
Mark a task as completed with a result. Use this when DONE, not when starting.
cortextos bus complete-task "<task_id>" --result "<what you produced>"
Example:
cortextos bus complete-task "task_abc123" --result "Deployed landing page to production. URL: https://site.com"
List and filter tasks. Use during every heartbeat to check your queue.
cortextos bus list-tasks [--status S] [--agent A] [--priority P] [--all-orgs]
pending | in_progress | blocked | completedurgent | high | normal | lowExample:
cortextos bus list-tasks --agent $CTX_AGENT_NAME --status pending
Send a message to another agent. They will see it on their next inbox check.
cortextos bus send-message <target_agent> <priority> '<message_body>' [reply_to]
urgent | high | normal | lowExample:
cortextos bus send-message <agent-name> high '{"action":"deploy","repo":"website","branch":"main"}'
Check for incoming messages from other agents. Run this EVERY heartbeat.
cortextos bus check-inbox
Returns a list of messages. Each has an ID you must ACK.
Acknowledge a message. Un-ACK'd messages are re-delivered in 5 minutes.
cortextos bus ack-inbox "<message_id>"
Example:
cortextos bus ack-inbox "msg_xyz789"
Log a structured event. Events are the primary way the dashboard tracks your activity. No events = you look dead. Log aggressively.
cortextos bus log-event <category> <event_name> <severity> --meta '<json_payload>'
action | task | heartbeat | message | approval | error | metric | milestonesession_start, task_completed, deploy_started)info | warning | error | criticalExamples:
cortextos bus log-event heartbeat agent_heartbeat info --meta '{"agent":"'$CTX_AGENT_NAME'"}'
cortextos bus log-event task task_completed info --meta '{"task_id":"task_abc123","summary":"Deployed site"}'
cortextos bus log-event error deploy_failed error --meta '{"repo":"website","error":"build timeout"}'
cortextos bus log-event action research_complete info --meta '{"topic":"competitor analysis","findings":3}'
Update your heartbeat timestamp and status. This is how the system knows you are alive. If you do not call this, the dashboard shows you as DEAD.
cortextos bus update-heartbeat "<current_task_summary>"
Example:
cortextos bus update-heartbeat "WORKING ON: Implementing user auth for the dashboard"
Request human approval before taking a high-stakes action. Required for: external comms, production deploys, data deletion, financial commitments.
cortextos bus create-approval "<title>" <category> "[context]"
external-comms | financial | deployment | data-deletion | otherExample:
cortextos bus create-approval "Send cold outreach to 50 leads" external-comms "Draft email attached in task_abc123. Target list: SaaS founders."
Resolve an approval request (typically called by the system after human responds via Telegram).
cortextos bus update-approval <approval_id> <approved|rejected> "[note]"
Example:
cortextos bus update-approval "appr_123" approved "User approved via Telegram"
Send a message to the user via Telegram. Use for urgent updates, approval requests, and status reports. Do NOT spam. Reserve for things the user actually needs to see.
cortextos bus send-telegram <chat_id> "<message>"
Example:
cortextos bus send-telegram "$CTX_TELEGRAM_CHAT_ID" "Task completed: Landing page deployed to production. URL: https://site.com"
Edit an existing Telegram message (e.g., to update a status message in-place).
cortextos bus edit-message <chat_id> <message_id> "<new_text>" [reply_markup_json]
Answer a Telegram callback query to dismiss button loading state.
cortextos bus answer-callback <callback_query_id> [toast_text]
Discover all agents in the system.
cortextos bus list-agents [--org <org>] [--format json|text] [--status running|all]
List available skills for the current agent.
cortextos bus list-skills [--format text|json]
Aggregate all agent heartbeats into a single JSON object keyed by agent name.
cortextos bus read-all-heartbeats
Find stale tasks: in_progress >2h, pending >24h, stale human tasks, overdue.
cortextos bus check-stale-tasks [--all-orgs]
Check each agent's GOALS.md Updated timestamp. Flags goals older than threshold.
cortextos bus check-goal-staleness [--threshold DAYS] [--json]
Check for stale human-assigned tasks and send reminders.
cortextos bus check-human-tasks
Archive completed tasks older than 7 days.
cortextos bus archive-tasks [--dry-run] [--all-orgs]
Send an urgent signal to another agent's fast-checker (bypasses normal inbox polling).
cortextos bus notify-agent <agent_name> "<message>"
Post a message to the org's Telegram activity channel.
cortextos bus post-activity "<message>"
Create a new experiment proposal. For system-scope, auto-creates an approval.
cortextos bus create-experiment <metric_name> "<hypothesis>" [--surface <path>] [--direction higher|lower] [--window <duration>] [--measurement <cmd>]
Start running a proposed experiment.
cortextos bus run-experiment <experiment_id> [changes_description]
Evaluate a running experiment and decide keep/discard.
cortextos bus evaluate-experiment <experiment_id> <measured_value> [--score <1-10>] [--justification "<text>"]
List experiments with filters.
cortextos bus list-experiments [--agent <name>] [--status <status>] [--metric <name>] [--json]
Collect experiment context for hypothesis generation.
cortextos bus gather-context [--agent <name>] [--metric <name>] [--format json|markdown]
Restart with --continue (preserves conversation history).
cortextos bus self-restart --reason "why"
Kill and relaunch (fresh session, no history).
cortextos bus hard-restart --reason "why"
Automatic daily snapshot of agent workspace changes. Local only, never pushes.
cortextos bus auto-commit [--dry-run]
Check for framework updates from the canonical repo.
cortextos bus check-upstream [--apply]
Browse community catalog for skills, agents, or org templates.
cortextos bus browse-catalog [--type skill|agent|org] [--tag <tag>] [--search <query>]
Install a community catalog item.
cortextos bus install-community-item <item-name> [--dry-run]
Prepare a skill/agent/org for community submission (PII scan + staging).
cortextos bus prepare-submission <type> <source-path> <item-name> [--dry-run]
Submit a prepared item to the community catalog.
cortextos bus submit-community-item <item-name> <item-type> "<description>" [--dry-run]
| I need to... | Command |
|---|---|
| Prove I'm alive | update-heartbeat |
| Check for messages | check-inbox |
| Confirm I read a message | ack-inbox |
| Talk to another agent | send-message |
| Create work | create-task |
| Show progress | update-task |
| Finish work | complete-task |
| See my queue | list-tasks |
| Leave a trail | log-event |
| Ask permission | create-approval |
| Alert the user | send-telegram |
| Edit a Telegram message | edit-message |
| Post to activity channel | post-activity |
| Urgently signal another agent | notify-agent |
| Find all agents | list-agents |
| Find available skills | list-skills |
| Check fleet heartbeats | read-all-heartbeats |
| Find stale tasks | check-stale-tasks |
| Find stale goals | check-goal-staleness |
| Archive old tasks | archive-tasks |
| Run an experiment | create-experiment |
| Restart (keep history) | self-restart |
| Restart (fresh) | hard-restart |
| Snapshot workspace | auto-commit |
| Check for updates | check-upstream |
agent-browser (Rust CLI, npm-installed globally; Chrome auto-downloaded by agent-browser install).claude/skills/agent-browser/SKILL.md — that skill instructs running agent-browser skills get <name> to fetch current per-version command syntax from the CLI itselfagent-browser open https://example.com && agent-browser get title && agent-browser closeagent-browser snapshot (returns a11y tree with refs e1/e2/...) then agent-browser click @e1 / fill @e2 "text" — more reliable than text-search selectors for AI-driven flowsdashboard/ which use Playwright DIRECTLY (not via MCP). agent-browser only replaces the agent-facing browser MCP layer that was previously mcp__plugin_playwright_*. The dashboard's Playwright dependency stayspeekaboopeekaboo image (screenshot), peekaboo list (apps/windows), peekaboo run <script> (automation)peekaboo learn for comprehensive AI agent usage guidegoggog auth credentials + gog auth add-a email@gmail.com to specify which account.-a email@gmail.com or --account email@gmail.com flag-j or --json for structured output-p or --plain for TSV parseable outputgog gmail ls -a YOUR_EMAIL "is:unread" --max 10gog gmail send -a YOUR_EMAIL --to "user@example.com" --subject "Subject" --body "Body"gog calendar ls -a YOUR_EMAIL --max 5gog calendar create -a YOUR_EMAIL --summary "Meeting" --start "2026-03-28T14:00:00" --end "2026-03-28T15:00:00"gog drive ls -a YOUR_EMAIL --max 10Full interactive setup for the agentic CRM personal assistant template. Use at first boot or whenever the user asks to configure/reconfigure the assistant.
Discover, research, and CONNECT the tools a tool-agnostic personal assistant needs — email, calendar, contacts, meeting notes, messaging, CRM. CLI-first, research-driven, verified. Use during setup and whenever a workflow fails because a tool is missing or not authed.
You need to create a new agent, restart a crashed agent, change an agent's model or config, fix a Telegram bot token, troubleshoot why an agent is not responding, enable or disable an agent, spawn an agent for another user, manage PM2 process management, reset crash limits, or do anything that touches an agent's lifecycle, configuration, or credentials. This is the definitive guide for every agent operation in cortextOS.
You need to create a new agent, restart a crashed agent, change an agent's model or config, fix a Telegram bot token, troubleshoot why an agent is not responding, enable or disable an agent, spawn an agent for another user, manage PM2 process management, reset crash limits, or do anything that touches an agent's lifecycle, configuration, or credentials. This is the definitive guide for every agent operation in cortextOS.
You need to create a new agent, restart a crashed agent, change an agent's model or config, fix a Telegram bot token, troubleshoot why an agent is not responding, enable or disable an agent, spawn an agent for another user, manage PM2 process management, reset crash limits, or do anything that touches an agent's lifecycle, configuration, or credentials. This is the definitive guide for every agent operation in cortextOS.
You need to create a new agent, restart a crashed agent, change an agent's model or config, fix a Telegram bot token, troubleshoot why an agent is not responding, enable or disable an agent, spawn an agent for another user, manage PM2 process management, reset crash limits, or do anything that touches an agent's lifecycle, configuration, or credentials. This is the definitive guide for every agent operation in cortextOS.