
manage-run
Use when: User wants to INSPECT, MONITOR, START, APPROVE, or CONTROL Archon workflow RUNS in the current project — driven through the archon CLI over bash. Triggers (inspect): "what's running", "list runs", "show recent runs", "run status", "did the review pass", "check run ", "show me run ", "what happened in that run". Triggers (control): "approve the plan", "approve run ", "reject that run", "cancel that run", "abandon run ", "resume run ", "continue that run". Triggers (start): "start in the background", "kick off detached". Capability: Drives archon workflow runs/get/status/run --detach/approve/reject/cancel/abandon/resume with machine-readable --json output, scoped to the current project by cwd. NOT for: Authoring workflows/commands, or Archon setup/config — use the broader archon skill.
- Installs
- 154
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/coleam00/archon --skill manage-run- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads manage-run automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Manage Archon Runs
A focused skill for managing workflow runs through the archon CLI. It assumes
Archon is already installed and you are working inside the project repo — the
current directory scopes every command to that project automatically. For authoring
workflows, setup, or config, use the broader archon skill instead.
Recent runs (live)
!archon workflow runs --limit 10 2>&1 || echo "Archon CLI not installed. (This skill needs the archon CLI on PATH.)"
How output works
- Add
--jsonto any command for a single clean JSON object on stdout (logs are suppressed automatically in--jsonmode). Prefer--jsonwhen you will parse the result. - Without
--jsonyou get human-readable text. Diagnostics/warnings always go to stderr. - The current directory (cwd) determines which project's runs you see. Run from the repo.
Verbs
| Goal | Command |
|---|---|
| List recent runs (all statuses, this project) | archon workflow runs --json |
| List across all projects | archon workflow runs --all --json |
| Filter by status / cap rows | archon workflow runs --status running --limit 50 --json |
| Show one run (status, error) | archon workflow get <run-id> --json |
| One run with per-node detail | archon workflow get <run-id> --verbose --json |
| Active runs only (running/paused) | archon workflow status --json |
| Start a run, non-blocking | archon workflow run <workflow> "<message>" --detach |
| Approve a paused gate | archon workflow approve <run-id> "looks good" --json |
| Accept & complete a loop gate with a completed condition | archon workflow approve <run-id> --json (NO comment) |
| Reject a paused gate | archon workflow reject <run-id> "fix X first" --json |
Actively stop a running CLI --detach run | archon workflow cancel <run-id> --json |
| Mark a paused or verified-orphan run cancelled without stopping host work | archon workflow abandon <run-id> --json |
Patterns
Monitor a run to completion
archon workflow runs --json # find the run id
archon workflow get <run-id> --json # poll status: running | completed | failed | paused
A run is finished when status is completed, failed, or cancelled.
Start work without blocking
archon workflow run archon-assist "Investigate the flaky test" --detach
# returns immediately; the run then appears in `archon workflow runs`
--detach runs the workflow in a background child. The parent can't print the new
run id (it's created in the child) — find it with archon workflow runs. If the run
never appears, check the child log path printed by the command (or the logPath
field in --detach --json).
Console UI note: a detached run appears in the web console's Workflow dock (the dock lists runs by project) and updates live — even though it executes in a separate process. A server-side poller tails the workflow-event table and replays new rows to the console's live feed (on PostgreSQL a
NOTIFYtrigger pushes them within the same second; on SQLite the poller picks them up on its short interval). No refresh is needed.
Approve or reject a paused run (two steps)
--json approve/reject/resume record the decision (the run becomes resumable) but
do not execute the workflow — execution streams output that would corrupt the JSON.
So:
archon workflow approve <run-id> "ship it" --json # records the approval (resumable: true)
archon workflow resume <run-id> # execute it — run this as a BACKGROUND task
archon workflow get <run-id> --json # poll until completed/failed
If you only need to record a gate decision and don't need to drive the resulting
cancel-or-rework path forward, the --json step alone is enough. To approve and continue
in one blocking call, drop --json: archon workflow approve <run-id> "ship it"
auto-resumes (run it as a background task).
Interactive-loop gates: no comment = accept & complete
When a paused interactive loop gate met any declared completion condition
(archon workflow get <run-id> --json → .metadata.approval.completionSignaled is
true), approving with no comment accepts the completion — on resume the node
finalizes from the already-computed output with no re-run. Approving with a
comment runs another iteration using it as feedback. Read the gate state first, then
choose deliberately:
archon workflow get <run-id> --json | jq .metadata.approval.completionSignaled
archon workflow approve <run-id> --json # accept & complete (finalize, no re-run)
archon workflow approve <run-id> "redo X" --json # run another iteration with feedback
(In project-scoped chat, the manage_run tool's approve action mirrors this: no
message — or accept: true — finalizes; a message iterates.)
Reference
For the full flag list and JSON shapes of each verb: read references/commands.md.
FAQ
What does the manage-run skill do?
Use when: User wants to INSPECT, MONITOR, START, APPROVE, or CONTROL Archon workflow RUNS in the current project — driven through the archon CLI over bash. Triggers (inspect): "what's running", "list runs", "show recent runs", "run status", "did the review pass", "check run ", "show me run ", "what happened in that run". Triggers (control): "approve the plan", "approve run ", "reject that run", "cancel that run", "abandon run ", "resume run ", "continue that run". Triggers (start): "start in the background", "kick off detached". Capability: Drives archon workflow runs/get/status/run --detach/approve/reject/cancel/abandon/resume with machine-readable --json output, scoped to the current project by cwd. NOT for: Authoring workflows/commands, or Archon setup/config — use the broader archon skill.
How do I install manage-run?
Run npx skills add https://github.com/coleam00/archon --skill manage-run in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/manage-run/ (personal) or .claude/skills/manage-run/ (project).
Which AI agents can use manage-run?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is manage-run safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains manage-run?
It is published by coleam00 in coleam00/archon. It has 154 recorded installs.
More from coleam00/archon
playwright-cli
coleam00/archon
Automate browser interactions, test web pages and work with Playwright tests.
triage
coleam00/archon
Triage GitHub issues by applying type, effort, priority, and area labels. Runs in an isolated context to avoid polluting the main conversation with issue details. Delegates to a specialized triage agent with label validation hooks.
docker-extend
coleam00/archon
Use when: User wants to extend Docker with custom tools, personalize the Docker environment, or set up user-specific Docker customization. Triggers: 'extend docker', 'docker-extend', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'docker user setup', 'install tools in docker'. Does: Interactively sets up Dockerfile.user and docker-compose.override.yml so users can add personal tools to their Docker environment without affecting maintainer files or committing user-specific config to git.
rulecheck
coleam00/archon
Autonomous rule adherence checker. Scans the codebase for rule violations, fixes the highest-impact ones in an isolated worktree, runs full validation, creates a PR. Uses memory to track progress across runs.
test-release
coleam00/archon
Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。