Archon
Open-source desktop app for Mac, Windows and Linux. Agents run on your computer or on your own server.
Product websitegithub.com Compare with others Missing or wrong data?
- Desktop app
- Mac, Windows and Linux
- Browser
- Yes
- Phone
- Not listed
- Command line
- Yes
- Agents
- Claude Code, Codex, OpenCode and Pi
- Your subscription
- Works with your own plan
- Agents run
- On your computer and on your own server
- Laptop closed
- Keeps going
- Isolation
- Worktree and Container
- Parallel agents
- Yes
- Scheduled runs
- Yes
- Coordinator agent
- Yes
- Built-in issues
- No
- Pull requests
- Yes
- Review screen
- No
- Team
- Roles
- Self-hosting
- Yes
- Licence
- MIT
- Price from
- Free
- How it charges
- No paid plan and bring your own key
- Paid plans from
- Not listed
Receipts
- Checked
- · oldest answer 2026-11-08
- Findings
- 44 published · 36 cross-checked by a second agent · read them all
- Sources
- 51 public pages on 2 sites: github.com, archon.diy
- Screenshot
- github.com, retrieved · self captured · shows appearance, not capability
- Data
- /products/archon.json · .md
- Method
- Same rules for all 103 researched ADEs. How we check · Report wrong data
What it does
Where you use it
Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
Source and scope for Where you use itAgents it runs
Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific. Archon v0.14.0 mentions Antigravity as an OAuth subscription available through Pi. That does not establish running Antigravity as a separate provider plugin.
Source and scope for Agents it runsAccounts and subscriptions
Archon runs existing Claude Code, Codex and Pi accounts. The quickstart asks users to install and sign into Claude Code or Codex before setup.
Source and scope for Accounts and subscriptionsWhere agents run
Archon can run locally or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL. The scoped execution service is operator-hosted, without an Archon-vendor compute backend.
Source and scope for Where agents runHow work is kept apart
Repository runs receive their own Git worktree by default, permitting separate runs against the same repository. Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment. VM/remote labels in the type system do not have shipped provider implementations.
Source and scope for How work is kept apartParallel work
Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
Source and scope for Parallel workScheduled runs
Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
Source and scope for Scheduled runsGit and pull requests
The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
Source and scope for Git and pull requestsLicence and source
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Source and scope for Licence and sourcePrice
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
Source and scope for PriceTyped filters
Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.
| Filter | Value |
|---|---|
| Desktop OS: macOS | Yes |
| Desktop OS: Windows | Yes |
| Desktop OS: Linux | Yes |
| Web client | Yes |
| Phone access: Native iOS | No |
| Phone access: Native Android | No |
| Phone access: Phone browser | Unknown |
| CLI | Yes cross-checked |
| Coding agents: Claude Code | Yes cross-checked |
| Coding agents: Codex | Yes cross-checked |
| Coding agents: Cursor Agent | Unknown |
| Coding agents: Gemini CLI | Unknown |
| Coding agents: OpenCode | Yes cross-checked |
| Coding agents: Pi | Yes cross-checked |
| Coding agents: Grok | Unknown |
| Coding agents: Aider | Unknown |
| Coding agents: Antigravity | Unknown |
| Use my subscription | Yes cross-checked |
| Where agents run: On your computer | Yes |
| Where agents run: On your own server | Yes |
| Where agents run: In the vendor's cloud | No |
| Workspace isolation: Git worktree | Yes |
| Workspace isolation: Container | Yes |
| Workspace isolation: VM or microVM | No |
| Parallel runs | Yes cross-checked |
| Coordinator | Yes cross-checked |
| Native issue tracking | No |
| Unattended triggers | Yes cross-checked |
| Shared prompting | No |
| Team roles | Yes |
| SSO | No |
| Pull request workflow | Yes cross-checked |
| Review interface | No |
| Product license: Apache-2.0 | No. MIT cross-checked |
| Product license: MIT | Yes. MIT cross-checked |
| Product license: GPL-3.0 | No. MIT cross-checked |
| Product license: GPL-3.0-or-later | No. MIT cross-checked |
| Product license: AGPL-3.0 | No. MIT cross-checked |
| Product license: AGPL-3.0-or-later | No. MIT cross-checked |
| Product license: Elastic License 2.0 | No. MIT cross-checked |
| Product license: Custom terms | No. MIT cross-checked |
| Product license: Proprietary | No. MIT cross-checked |
| Self-hosting | Yes cross-checked |
| Telemetry opt-out | Yes cross-checked |
| Free access | Yes cross-checked |
| Starting price: Free | Yes. Free cross-checked |
| Starting price: Up to $20/month | No. Free cross-checked |
| Starting price: $21–40/month | No. Free cross-checked |
| Starting price: $41–100/month | No. Free cross-checked |
| Starting price: Over $100/month | No. Free cross-checked |
| Starting price: Contact for pricing | No. Free cross-checked |
| Pricing model: Free, no paid plan | Yes |
| Pricing model: Free plan | No |
| Pricing model: Subscription | No |
| Pricing model: Per seat | No |
| Pricing model: Usage-based | No |
| Pricing model: Per machine or compute | No |
| Pricing model: Bring your own key | Yes |
| Pricing model: One-time purchase | No |
| Paid plans from: No paid plan | Unknown |
| Paid plans from: $10 or less/month | Unknown |
| Paid plans from: $11–20/month | Unknown |
| Paid plans from: $21–40/month | Unknown |
| Paid plans from: $41–100/month | Unknown |
| Paid plans from: Over $100/month | Unknown |
| Paid plans from: Contact sales | Unknown |
| Lifecycle status: Active | Unknown |
| Lifecycle status: Sunsetting | Unknown |
| Keeps going with laptop closed | Yes |
| Open-source license | Yes. MIT cross-checked |
| Any desktop app | Yes |
| Paid plan up to $20/month | Unknown |
| Paid plan up to $40/month | Unknown |
| Any phone client | Unknown |
Filter receipts
Desktop OS: macOS: Yes
Desktop OS: macOS
Typed value: Yes.
Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
- Browser: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Cli: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Task actions: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Quickstart; Connect a platform
Finding: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
Desktop OS: Windows: Yes
Desktop OS: Windows
Typed value: Yes.
Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
- Browser: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Cli: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Task actions: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Quickstart; Connect a platform
Finding: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
Desktop OS: Linux: Yes
Desktop OS: Linux
Typed value: Yes.
Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
- Browser: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Cli: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Task actions: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Quickstart; Connect a platform
Finding: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
Web client: Yes
Web client
Typed value: Yes.
Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
- Browser: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Cli: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Task actions: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Quickstart; Connect a platform
Finding: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
Phone access: Native iOS: No
Phone access: Native iOS
Typed value: No.
Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
- Mobile apps: Only CLI and browser console clients in the complete scoped distribution/build tree; chat adapters are separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The complete distribution is native CLI installers and a self-hosted web console; no native iOS/Android target is built. Chat adapters are separate Slack/Telegram/GitHub channels. The web console has responsive navigation for smaller viewports.
Phone access: Native Android: No
Phone access: Native Android
Typed value: No.
Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
- Mobile apps: Only CLI and browser console clients in the complete scoped distribution/build tree; chat adapters are separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The complete distribution is native CLI installers and a self-hosted web console; no native iOS/Android target is built. Chat adapters are separate Slack/Telegram/GitHub channels. The web console has responsive navigation for smaller viewports.
CLI: Yes cross-checked
CLI
Typed value: Yes.
Archon exposes a REST API under /api with OpenAPI 3 generation. Solo local authentication is optional; configured web auth requires a session or trusted proxy identity. The CLI controls workflow runs and approvals.
- Cli: Archon exposes a REST API under /api with OpenAPI 3 generation. Solo local authentication is optional; configured web auth requires a session or trusted proxy identity. The CLI controls workflow runs and approvals.
- Api: Archon exposes a REST API under /api with OpenAPI 3 generation. Solo local authentication is optional; configured web auth requires a session or trusted proxy identity. The CLI controls workflow runs and approvals.
- Operations: Archon exposes a REST API under /api with OpenAPI 3 generation. Solo local authentication is optional; configured web auth requires a session or trusted proxy identity. The CLI controls workflow runs and approvals.
- Authentication: Archon exposes a REST API under /api with OpenAPI 3 generation. Solo local authentication is optional; configured web auth requires a session or trusted proxy identity. The CLI controls workflow runs and approvals.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: API Reference; Authentication
Finding: Archon exposes a REST API under /api with OpenAPI 3 generation. Solo local authentication is optional; configured web auth requires a session or trusted proxy identity. The CLI controls workflow runs and approvals.
Coding agents: Claude Code: Yes cross-checked
Coding agents: Claude Code
Typed value: Yes.
Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific. Archon v0.14.0 mentions Antigravity as an OAuth subscription available through Pi. That does not establish running Antigravity as a separate provider plugin.
- Custom adapters: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
- Mixed harness operation: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
- Antigravity harness support remains unknown; a Pi model-login option is not an Antigravity coding-agent integration.
-
Archon: Your agents, your subscriptions; Plugin kinds
Finding: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
Coding agents: Codex: Yes cross-checked
Coding agents: Codex
Typed value: Yes.
Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific. Archon v0.14.0 mentions Antigravity as an OAuth subscription available through Pi. That does not establish running Antigravity as a separate provider plugin.
- Custom adapters: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
- Mixed harness operation: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
- Antigravity harness support remains unknown; a Pi model-login option is not an Antigravity coding-agent integration.
-
Archon: Your agents, your subscriptions; Plugin kinds
Finding: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
Coding agents: OpenCode: Yes cross-checked
Coding agents: OpenCode
Typed value: Yes.
Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific. Archon v0.14.0 mentions Antigravity as an OAuth subscription available through Pi. That does not establish running Antigravity as a separate provider plugin.
- Harnesses: Maintained provider plugins run Claude Code, Codex and Pi. OpenCode and GitHub Copilot providers stay bundled and working in v0.14.0 but are deprecated with no maintainer owner, and in chat they launch headless detached runs. Archon v0.14.0 mentions Antigravity as an OAuth subscription available through Pi. That does not establish running Antigravity as a separate provider plugin.
- Mixed harness operation: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
- Antigravity harness support remains unknown; a Pi model-login option is not an Antigravity coding-agent integration.
-
Archon docs: AI assistants (v0.14.0)
Finding: Archon configures Claude Code, Codex, Pi, OpenCode and GitHub Copilot providers. OpenCode and Copilot are deprecated (no maintainer owner) but stay bundled and keep working; in chat they launch headless detached CLI runs instead of using native tools.
Coding agents: Pi: Yes cross-checked
Coding agents: Pi
Typed value: Yes.
Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific. Archon v0.14.0 mentions Antigravity as an OAuth subscription available through Pi. That does not establish running Antigravity as a separate provider plugin.
- Custom adapters: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
- Mixed harness operation: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
- Antigravity harness support remains unknown; a Pi model-login option is not an Antigravity coding-agent integration.
-
Archon: Your agents, your subscriptions; Plugin kinds
Finding: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
Use my subscription: Yes cross-checked
Use my subscription
Typed value: Yes.
Archon runs existing Claude Code, Codex and Pi accounts. The quickstart asks users to install and sign into Claude Code or Codex before setup.
- Agent subscriptions: Archon runs existing Claude Code, Codex and Pi accounts. The quickstart asks users to install and sign into Claude Code or Codex before setup.
- Provider restrictions: Archon runs existing Claude Code, Codex and Pi accounts. The quickstart asks users to install and sign into Claude Code or Codex before setup.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Your agents, your subscriptions; Quickstart
Finding: Archon runs existing Claude Code, Codex and Pi accounts. The quickstart asks users to install and sign into Claude Code or Codex before setup.
Where agents run: On your computer: Yes
Where agents run: On your computer
Typed value: Yes.
Archon can run locally or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL. The scoped execution service is operator-hosted, without an Archon-vendor compute backend.
- Local: Archon can run locally for development and personal use.
- Byo remote: Archon can be deployed on a user's Docker host or cloud VPS.
- Self hosted: Docker and cloud VPS deployments are self-hosted, with SQLite or PostgreSQL.
- Client disconnect: A server deployment provides always-on, 24/7 operation.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Archon can run locally for development or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL.
Where agents run: On your own server: Yes
Where agents run: On your own server
Typed value: Yes.
Archon can run locally or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL. The scoped execution service is operator-hosted, without an Archon-vendor compute backend.
- Local: Archon can run locally for development and personal use.
- Byo remote: Archon can be deployed on a user's Docker host or cloud VPS.
- Self hosted: Docker and cloud VPS deployments are self-hosted, with SQLite or PostgreSQL.
- Client disconnect: A server deployment provides always-on, 24/7 operation.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Archon can run locally for development or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL.
Where agents run: In the vendor's cloud: No
Where agents run: In the vendor's cloud
Typed value: No.
Archon can run locally or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL. The scoped execution service is operator-hosted, without an Archon-vendor compute backend.
- Managed cloud: Deployment/launcher paths use operator-managed hosts and contain no Archon-vendor execution service.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon packages/isolation/src/index.ts
Finding: The shipped isolation provider factory implements worktree and container backends. vm and remote type labels are reserved, not implemented provider factories. Deployments run on the operator machine, Docker host or cloud VPS; no vendor-managed execution service is implemented.
Workspace isolation: Git worktree: Yes
Workspace isolation: Git worktree
Typed value: Yes.
Repository runs receive their own Git worktree by default, permitting separate runs against the same repository. Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment. VM/remote labels in the type system do not have shipped provider implementations.
- Worktree: Repository runs receive their own Git worktree by default, permitting separate runs against the same repository.
- Container: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
- Filesystem: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
- Process: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
- Secrets: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
- Code separation: Repository runs receive their own Git worktree by default, permitting separate runs against the same repository.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Repository runs receive their own Git worktree by default, permitting separate runs against the same repository.
-
Archon: How it works; Provider support; Security posture
Finding: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
Workspace isolation: Container: Yes
Workspace isolation: Container
Typed value: Yes.
Repository runs receive their own Git worktree by default, permitting separate runs against the same repository. Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment. VM/remote labels in the type system do not have shipped provider implementations.
- Worktree: Repository runs receive their own Git worktree by default, permitting separate runs against the same repository.
- Container: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
- Filesystem: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
- Process: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
- Secrets: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
- Code separation: Repository runs receive their own Git worktree by default, permitting separate runs against the same repository.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Repository runs receive their own Git worktree by default, permitting separate runs against the same repository.
-
Archon: How it works; Provider support; Security posture
Finding: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
Workspace isolation: VM or microVM: No
Workspace isolation: VM or microVM
Typed value: No.
Repository runs receive their own Git worktree by default, permitting separate runs against the same repository. Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment. VM/remote labels in the type system do not have shipped provider implementations.
- Vm: The shipped isolation provider factory supplies worktree/container, with no VM/microVM backend.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon packages/isolation/src/index.ts
Finding: The shipped isolation provider factory implements worktree and container backends. vm and remote type labels are reserved, not implemented provider factories. Deployments run on the operator machine, Docker host or cloud VPS; no vendor-managed execution service is implemented.
Parallel runs: Yes cross-checked
Parallel runs
Typed value: Yes.
Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
- Concurrent sessions: Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
- Concurrent tasks: Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
- Quotas: Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
- Status visibility: Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
Coordinator: Yes cross-checked
Coordinator
Typed value: Yes.
The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
- Roles: The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
- Results return: The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
- Orchestration owner: The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
- Activation: The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
- Retained results: The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
- Invocation: The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Launching a separate governed run
Finding: The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
Native issue tracking: No
Native issue tracking
Typed value: No.
The current TypeScript product runs workflows against external forge issues and stores runs/attention waits. Independent task management belongs to the archived Python product, not this scoped app.
- Task session separation: Current schema and command routes have runs/conversations and external issue references, without independent native issue entities.
- Source inspection covers the scoped release only. Unanswered atomic questions remain unknown; no live scenario was run.
-
Archon packages/core/src/db/bundled-schema.ts
Finding: The current TypeScript application persists projects, conversations, sessions, workflow runs/events, attention waits and isolation environments. Forge integrations use external issue IDs; no standalone native issue/task CRUD model exists. The prior Python task-management product is archived outside this profile scope.
Unattended triggers: Yes cross-checked
Unattended triggers
Typed value: Yes.
Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
- Schedules: Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
- Events: Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
- Scheduler location: Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
- Overlaps: Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
- Client independence: Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Start workflows from schedules and signed webhooks
Finding: Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
Shared prompting: No
Shared prompting
Typed value: No.
Authenticated Web/CLI operator conversations are private to their owner. Another signed-in identity cannot send instructions to that conversation; shared run visibility is not shared prompting.
- Visibility: Run transcripts can be visible to signed-in users, while operator conversation controls remain owner-only.
- Coprompting: The documented owner check rejects another identity for sending, starting a run and reading conversation history.
- Source inspection covers the scoped release only. Unanswered atomic questions remain unknown; no live scenario was run.
-
Archon packages/docs-web/src/content/docs/reference/security.md
Finding: With web authentication or a trusted identity header, operator conversations are private to their owner; other identities cannot read, send or start work in them. Built-in auth uses email/password or proxy/basic/form access; the scoped authentication implementation has no enterprise SAML/OIDC provider configuration.
Team roles: Yes
Team roles
Typed value: Yes.
New identities are members. Operators designate admins; only a run starter or an admin can perform governance actions on that run. Solo installs may leave web auth disabled. Built-in email/password and trusted-proxy identity mechanisms do not include an enterprise SSO integration.
- Organization roles: New identities are members. Operators designate admins; only a run starter or an admin can perform governance actions on that run. Solo installs may leave web auth disabled.
- Membership: New identities are members. Operators designate admins; only a run starter or an admin can perform governance actions on that run. Solo installs may leave web auth disabled.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Users and roles; Who can act on a run
Finding: New identities are members. Operators designate admins; only a run starter or an admin can perform governance actions on that run. Solo installs may leave web auth disabled.
SSO: No
SSO
Typed value: No.
New identities are members. Operators designate admins; only a run starter or an admin can perform governance actions on that run. Solo installs may leave web auth disabled. Built-in email/password and trusted-proxy identity mechanisms do not include an enterprise SSO integration.
- Sso: No enterprise SAML/OIDC login provider in the complete scoped built-in auth configuration/service.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon packages/docs-web/src/content/docs/reference/security.md
Finding: With web authentication or a trusted identity header, operator conversations are private to their owner; other identities cannot read, send or start work in them. Built-in auth uses email/password or proxy/basic/form access; the scoped authentication implementation has no enterprise SAML/OIDC provider configuration.
Pull request workflow: Yes cross-checked
Pull request workflow
Typed value: Yes.
The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
- Branches: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
- Worktrees: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
- Commits: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
- Pull requests: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
- Ci response: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
- Conflicts: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
- Product state: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
Review interface: No
Review interface
Typed value: No.
The console retains workflow events and artifacts, but the scoped product UI has no dedicated proposed-code/diff renderer.
- Diffs: The complete scoped console view tree has artifact/event display but no functional proposed-code diff viewer.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon packages/web/src/App.tsx
Finding: The shipped console routes show chat, workflow runs/events, artifacts and governance decisions. Source view/component inspection finds no proposed-code/diff renderer; the code-like approval preview in experimental components is sample text rather than a working review interface.
Product license: Apache-2.0: No. MIT cross-checked
Product license: Apache-2.0
Typed value: No. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Product license: MIT: Yes. MIT cross-checked
Product license: MIT
Typed value: Yes. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Product license: GPL-3.0: No. MIT cross-checked
Product license: GPL-3.0
Typed value: No. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Product license: GPL-3.0-or-later: No. MIT cross-checked
Product license: GPL-3.0-or-later
Typed value: No. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Product license: AGPL-3.0: No. MIT cross-checked
Product license: AGPL-3.0
Typed value: No. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Product license: AGPL-3.0-or-later: No. MIT cross-checked
Product license: AGPL-3.0-or-later
Typed value: No. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Product license: Elastic License 2.0: No. MIT cross-checked
Product license: Elastic License 2.0
Typed value: No. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Product license: Custom terms: No. MIT cross-checked
Product license: Custom terms
Typed value: No. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Product license: Proprietary: No. MIT cross-checked
Product license: Proprietary
Typed value: No. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Self-hosting: Yes cross-checked
Self-hosting
Typed value: Yes.
Archon is a full self-hosted application on the user machine or server, using SQLite by default or PostgreSQL. CLI, server and web console do not require a separate hosted Archon service.
- Self hosting: Archon is a full self-hosted application on the user machine or server, using SQLite by default or PostgreSQL. CLI, server and web console do not require a separate hosted Archon service.
- Vendor dependencies: Archon is a full self-hosted application on the user machine or server, using SQLite by default or PostgreSQL. CLI, server and web console do not require a separate hosted Archon service.
- Account independence: Archon is a full self-hosted application on the user machine or server, using SQLite by default or PostgreSQL. CLI, server and web console do not require a separate hosted Archon service.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Self-hosted; Quickstart
Finding: Archon is a full self-hosted application on the user machine or server, using SQLite by default or PostgreSQL. CLI, server and web console do not require a separate hosted Archon service.
Telemetry opt-out: Yes cross-checked
Telemetry opt-out
Typed value: Yes.
Archon sends anonymous categorical workflow/platform/provider/outcome and numeric usage events, excluding code and prompts. ARCHON_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1 or disabled POSTHOG_API_KEY turns it off; CI disables it automatically.
- Telemetry disclosure: Archon sends anonymous categorical workflow/platform/provider/outcome and numeric usage events, excluding code and prompts. ARCHON_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1 or disabled POSTHOG_API_KEY turns it off; CI disables it automatically.
- Telemetry defaults: Archon sends anonymous categorical workflow/platform/provider/outcome and numeric usage events, excluding code and prompts. ARCHON_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1 or disabled POSTHOG_API_KEY turns it off; CI disables it automatically.
- Telemetry controls: Archon sends anonymous categorical workflow/platform/provider/outcome and numeric usage events, excluding code and prompts. ARCHON_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1 or disabled POSTHOG_API_KEY turns it off; CI disables it automatically.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Archon sends anonymous categorical workflow/platform/provider/outcome and numeric usage events, excluding code and prompts. ARCHON_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1 or disabled POSTHOG_API_KEY turns it off; CI disables it automatically.
Free access: Yes cross-checked
Free access
Typed value: Yes.
The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Ongoing free: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Self host cost: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
Starting price: Free: Yes. Free cross-checked
Starting price: Free
Typed value: Yes. Free.
The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Ongoing free: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Self host cost: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
Starting price: Up to $20/month: No. Free cross-checked
Starting price: Up to $20/month
Typed value: No. Free.
The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Ongoing free: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Self host cost: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
Starting price: $21–40/month: No. Free cross-checked
Starting price: $21–40/month
Typed value: No. Free.
The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Ongoing free: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Self host cost: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
Starting price: $41–100/month: No. Free cross-checked
Starting price: $41–100/month
Typed value: No. Free.
The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Ongoing free: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Self host cost: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
Starting price: Over $100/month: No. Free cross-checked
Starting price: Over $100/month
Typed value: No. Free.
The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Ongoing free: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Self host cost: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
Starting price: Contact for pricing: No. Free cross-checked
Starting price: Contact for pricing
Typed value: No. Free.
The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Ongoing free: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Self host cost: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
Pricing model: Free, no paid plan: Yes
Pricing model: Free, no paid plan
Typed value: Yes.
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
- Model cost: The source license permits use and distribution free of charge. Provider subscriptions and self-hosted compute are separate user costs; there is no vendor cloud plan price asserted here.
- Compute cost: The source license permits use and distribution free of charge. Provider subscriptions and self-hosted compute are separate user costs; there is no vendor cloud plan price asserted here.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: MIT License; Distribution grant
Finding: The source license permits use and distribution free of charge. Provider subscriptions and self-hosted compute are separate user costs; there is no vendor cloud plan price asserted here.
Pricing model: Free plan: No
Pricing model: Free plan
Typed value: No.
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The current first-party distribution is the MIT source/CLI application to install and self-host. README and installation/provider/deployment docs expose no paid ADE tier. Underlying provider subscriptions/API keys and operator compute are separate; the Pi provider documentation describes reuse of API keys.
Pricing model: Subscription: No
Pricing model: Subscription
Typed value: No.
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The current first-party distribution is the MIT source/CLI application to install and self-host. README and installation/provider/deployment docs expose no paid ADE tier. Underlying provider subscriptions/API keys and operator compute are separate; the Pi provider documentation describes reuse of API keys.
Pricing model: Per seat: No
Pricing model: Per seat
Typed value: No.
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The current first-party distribution is the MIT source/CLI application to install and self-host. README and installation/provider/deployment docs expose no paid ADE tier. Underlying provider subscriptions/API keys and operator compute are separate; the Pi provider documentation describes reuse of API keys.
Pricing model: Usage-based: No
Pricing model: Usage-based
Typed value: No.
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The current first-party distribution is the MIT source/CLI application to install and self-host. README and installation/provider/deployment docs expose no paid ADE tier. Underlying provider subscriptions/API keys and operator compute are separate; the Pi provider documentation describes reuse of API keys.
Pricing model: Per machine or compute: No
Pricing model: Per machine or compute
Typed value: No.
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The current first-party distribution is the MIT source/CLI application to install and self-host. README and installation/provider/deployment docs expose no paid ADE tier. Underlying provider subscriptions/API keys and operator compute are separate; the Pi provider documentation describes reuse of API keys.
Pricing model: Bring your own key: Yes
Pricing model: Bring your own key
Typed value: Yes.
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The current first-party distribution is the MIT source/CLI application to install and self-host. README and installation/provider/deployment docs expose no paid ADE tier. Underlying provider subscriptions/API keys and operator compute are separate; the Pi provider documentation describes reuse of API keys.
Pricing model: One-time purchase: No
Pricing model: One-time purchase
Typed value: No.
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The current first-party distribution is the MIT source/CLI application to install and self-host. README and installation/provider/deployment docs expose no paid ADE tier. Underlying provider subscriptions/API keys and operator compute are separate; the Pi provider documentation describes reuse of API keys.
Keeps going with laptop closed: Yes
Keeps going with laptop closed
Typed value: Yes.
Archon can run locally or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL. The scoped execution service is operator-hosted, without an Archon-vendor compute backend.
- Local: Archon can run locally for development and personal use.
- Byo remote: Archon can be deployed on a user's Docker host or cloud VPS.
- Self hosted: Docker and cloud VPS deployments are self-hosted, with SQLite or PostgreSQL.
- Client disconnect: A server deployment provides always-on, 24/7 operation.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Archon can run locally for development or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL.
Open-source license: Yes. MIT cross-checked
Open-source license
Typed value: Yes. MIT.
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Client license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Server license: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source visibility: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Source revision: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
Any desktop app: Yes
Any desktop app
Typed value: Yes.
Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
- Browser: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Cli: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Task actions: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Quickstart; Connect a platform
Finding: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
All public findings
Findings may summarize a source. They are not presented as verbatim statements.
archon:ACC-01: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
archon:ACC-01
Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs. The scoped release has no native phone application targets.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Quickstart; Connect a platform
Finding: Archon has a product CLI and self-hosted browser console. macOS/Linux and Windows installers are documented, and Slack/Telegram/GitHub adapters are separate conversation channels. Installable CLI platforms do not establish native desktop GUIs.
-
Finding: The complete distribution is native CLI installers and a self-hosted web console; no native iOS/Android target is built. Chat adapters are separate Slack/Telegram/GitHub channels. The web console has responsive navigation for smaller viewports.
archon:ACC-02: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific. Archon v0.14.0 mentions Antigravity as an OAuth subscription available through Pi. That does not establish running Antigravity as a separate provider plugin. cross-checked
archon:ACC-02
Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific. Archon v0.14.0 mentions Antigravity as an OAuth subscription available through Pi. That does not establish running Antigravity as a separate provider plugin.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
- Antigravity harness support remains unknown; a Pi model-login option is not an Antigravity coding-agent integration.
-
Archon: Your agents, your subscriptions; Plugin kinds
Finding: Maintained provider plugins run Claude Code, Codex and Pi using their CLIs/SDKs. Community providers use a published contract; compatibility and workflow capabilities are provider-specific.
-
Archon docs: AI assistants (v0.14.0)
Finding: Archon configures Claude Code, Codex, Pi, OpenCode and GitHub Copilot providers. OpenCode and Copilot are deprecated (no maintainer owner) but stay bundled and keep working; in chat they launch headless detached CLI runs instead of using native tools.
-
Archon Antigravity support at v0.14.0
Finding: Archon v0.14.0 mentions Antigravity as an OAuth subscription available through Pi. That does not establish running Antigravity as a separate provider plugin.
archon:ACC-03: Archon runs existing Claude Code, Codex and Pi accounts. The quickstart asks users to install and sign into Claude Code or Codex before setup. cross-checked
archon:ACC-03
Archon runs existing Claude Code, Codex and Pi accounts. The quickstart asks users to install and sign into Claude Code or Codex before setup.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Your agents, your subscriptions; Quickstart
Finding: Archon runs existing Claude Code, Codex and Pi accounts. The quickstart asks users to install and sign into Claude Code or Codex before setup.
archon:ACC-04: Users install a provider, install Archon and run a named workflow in a git repository. Folder projects can be directories with or without git. cross-checked
archon:ACC-04
Users install a provider, install Archon and run a named workflow in a git repository. Folder projects can be directories with or without git.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Users install and sign in to Claude Code or install Codex, install Archon, then run a named workflow in any git repository.
-
Archon: How it works; Provider support; Security posture
Finding: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
archon:ACC-05: Archon exposes a REST API under /api with OpenAPI 3 generation. Solo local authentication is optional; configured web auth requires a session or trusted proxy identity. The CLI controls workflow runs and approvals. cross-checked
archon:ACC-05
Archon exposes a REST API under /api with OpenAPI 3 generation. Solo local authentication is optional; configured web auth requires a session or trusted proxy identity. The CLI controls workflow runs and approvals.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: API Reference; Authentication
Finding: Archon exposes a REST API under /api with OpenAPI 3 generation. Solo local authentication is optional; configured web auth requires a session or trusted proxy identity. The CLI controls workflow runs and approvals.
archon:ACC-06: Versioned plugins supply workflow packs, agent providers, forges and chat adapters through a published contract and install from GitHub; users can build their own plugins. cross-checked
archon:ACC-06
Versioned plugins supply workflow packs, agent providers, forges and chat adapters through a published contract and install from GitHub; users can build their own plugins.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: A reliable core; Plugin kinds
Finding: Versioned plugins supply workflow packs, agent providers, forges and chat adapters through a published contract and install from GitHub; users can build their own plugins.
archon:PLAN-01: The SDLC pack takes GitHub issues through intake, build and merge queues via the forge plugin. External issues remain the durable intake objects; this is not the archived native RAG/task app. cross-checked
archon:PLAN-01
The SDLC pack takes GitHub issues through intake, build and merge queues via the forge plugin. External issues remain the durable intake objects; this is not the archived native RAG/task app.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The SDLC pack takes GitHub issues through intake, build and merge queues via the forge plugin. External issues remain the durable intake objects; this is not the archived native RAG/task app.
archon:PLAN-02: YAML workflows declare ordered or dependent agent, script, loop, wait and approval nodes, with output contracts and persisted runs. Workflow files can be edited and versioned in the project. cross-checked
archon:PLAN-02
YAML workflows declare ordered or dependent agent, script, loop, wait and approval nodes, with output contracts and persisted runs. Workflow files can be edited and versioned in the project.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: YAML workflows declare ordered or dependent agent, script, loop, wait and approval nodes, with output contracts and persisted runs. Workflow files can be edited and versioned in the project.
archon:PLAN-03: A workflow node can launch separate child runs with their own identity, artifacts, costs and pauses. Dependencies and fan-out govern execution; max_parallel caps concurrent children rather than total work. cross-checked
archon:PLAN-03
A workflow node can launch separate child runs with their own identity, artifacts, costs and pauses. Dependencies and fan-out govern execution; max_parallel caps concurrent children rather than total work.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Separate governed child runs; fan_out
Finding: A workflow node can launch separate child runs with their own identity, artifacts, costs and pauses. Dependencies and fan-out govern execution; max_parallel caps concurrent children rather than total work.
archon:PLAN-04: Archon reuses provider project guidance and stores workflow commands and scripts beside YAML. This does not establish a shared cross-provider semantic memory store. cross-checked
archon:PLAN-04
Archon reuses provider project guidance and stores workflow commands and scripts beside YAML. This does not establish a shared cross-provider semantic memory store.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Your agents; Workflow packs
Finding: Archon reuses provider project guidance and stores workflow commands and scripts beside YAML. This does not establish a shared cross-provider semantic memory store.
archon:PLAN-06: The current TypeScript product runs workflows against external forge issues and stores runs/attention waits. Independent task management belongs to the archived Python product, not this scoped app.
archon:PLAN-06
The current TypeScript product runs workflows against external forge issues and stores runs/attention waits. Independent task management belongs to the archived Python product, not this scoped app.
- Source inspection covers the scoped release only. Unanswered atomic questions remain unknown; no live scenario was run.
-
Archon packages/core/src/db/bundled-schema.ts
Finding: The current TypeScript application persists projects, conversations, sessions, workflow runs/events, attention waits and isolation environments. Forge integrations use external issue IDs; no standalone native issue/task CRUD model exists. The prior Python task-management product is archived outside this profile scope.
archon:PLAN-07: The discoveries workflow reads out-of-task findings and files them as new GitHub issues or attaches them to existing issues through the forge plugin. Native issue object parity is not asserted. cross-checked
archon:PLAN-07
The discoveries workflow reads out-of-task findings and files them as new GitHub issues or attaches them to existing issues through the forge plugin. Native issue object parity is not asserted.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The discoveries workflow reads out-of-task findings and files them as new GitHub issues or attaches them to existing issues through the forge plugin. Native issue object parity is not asserted.
archon:COORD-01: Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable. cross-checked
archon:COORD-01
Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
archon:COORD-02: The build queue claims ready issues; the merge queue processes ready PRs and returns conflicts for rework. The bundled pack binds no triggers by default. cross-checked
archon:COORD-02
The build queue claims ready issues; the merge queue processes ready PRs and returns conflicts for rework. The bundled pack binds no triggers by default.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The build queue claims ready issues; the merge queue processes ready PRs and returns conflicts for rework. The bundled pack binds no triggers by default.
archon:COORD-03: The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records. cross-checked
archon:COORD-03
The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Launching a separate governed run
Finding: The product assistant can invoke workflows and inspect runs; workflow nodes delegate child runs with output returned to their parent, separate artifacts, pauses and cost records.
archon:COORD-04: Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records. cross-checked
archon:COORD-04
Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Start workflows from schedules and signed webhooks
Finding: Native schedules, GitHub events and Standard Webhooks request governed runs with host identity, overlap policy and resource admission. The configured server or detached CLI host starts admitted work and deduplicates shared admission records.
archon:COORD-05: Console actions include approve, reject, resume, cancel and abandon. Optional alerts announce approval/attention waits, completion, failure and cancellation. cross-checked
archon:COORD-05
Console actions include approve, reject, resume, cancel and abandon. Optional alerts announce approval/attention waits, completion, failure and cancellation.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Workflows and runs; Alerts
Finding: Console actions include approve, reject, resume, cancel and abandon. Optional alerts announce approval/attention waits, completion, failure and cancellation.
archon:COORD-06: The console lists runs across projects and exposes per-run event logs, artifacts and graph context; alerts announce approval or attention waits. Workflow fan-out keeps parent and child run records inspectable. Fleet-navigation effort was not measured. cross-checked
archon:COORD-06
The console lists runs across projects and exposes per-run event logs, artifacts and graph context; alerts announce approval or attention waits. Workflow fan-out keeps parent and child run records inspectable. Fleet-navigation effort was not measured.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Workflow fan-out creates concurrent governed child runs and max_parallel limits active children. Parent and child records remain inspectable.
-
Archon: Workflows and runs; Alerts
Finding: Console actions include approve, reject, resume, cancel and abandon. Optional alerts announce approval/attention waits, completion, failure and cancellation.
-
Archon: Console navigation; Workflows and runs
Finding: The console lists runs across projects and exposes per-run event logs, artifacts and graph context when the workflow definition is available. Fleet-navigation effort was not measured.
archon:COORD-07: Users invoke a ready workflow in natural language or edit the YAML graph to combine agent prompts, scripts, waits, loops and child workflows. cross-checked
archon:COORD-07
Users invoke a ready workflow in natural language or edit the YAML graph to combine agent prompts, scripts, waits, loops and child workflows.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Build any factory; Quickstart
Finding: Users invoke a ready workflow in natural language or edit the YAML graph to combine agent prompts, scripts, waits, loops and child workflows.
archon:RUN-01: Archon can run locally or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL. The scoped execution service is operator-hosted, without an Archon-vendor compute backend.
archon:RUN-01
Archon can run locally or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL. The scoped execution service is operator-hosted, without an Archon-vendor compute backend.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Archon can run locally for development or be deployed with Docker or on a cloud VPS for always-on operation, using SQLite by default or PostgreSQL.
-
Archon packages/isolation/src/index.ts
Finding: The shipped isolation provider factory implements worktree and container backends. vm and remote type labels are reserved, not implemented provider factories. Deployments run on the operator machine, Docker host or cloud VPS; no vendor-managed execution service is implemented.
archon:RUN-02: Repository runs receive their own Git worktree by default, permitting separate runs against the same repository. Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment. VM/remote labels in the type system do not have shipped provider implementations.
archon:RUN-02
Repository runs receive their own Git worktree by default, permitting separate runs against the same repository. Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment. VM/remote labels in the type system do not have shipped provider implementations.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Repository runs receive their own Git worktree by default, permitting separate runs against the same repository.
-
Archon: How it works; Provider support; Security posture
Finding: Folder projects optionally run in Docker with read-only project root, overlay writes and approval-gated write-back. Only Claude nodes currently support this container mode; other providers fail before execution. Native overlay fallback uses CAP_SYS_ADMIN and is not hostile-agent containment.
-
Archon packages/isolation/src/index.ts
Finding: The shipped isolation provider factory implements worktree and container backends. vm and remote type labels are reserved, not implemented provider factories. Deployments run on the operator machine, Docker host or cloud VPS; no vendor-managed execution service is implemented.
archon:RUN-03: Normal container pauses stop compute; resume can restart or recreate the container from its persisted upper volume. Missing volumes fail loudly. Web/chat decisions cannot continue container execution; a same-project CLI resume is required. cross-checked
archon:RUN-03
Normal container pauses stop compute; resume can restart or recreate the container from its persisted upper volume. Missing volumes fail loudly. Web/chat decisions cannot continue container execution; a same-project CLI resume is required.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Normal container pauses stop compute; resume can restart or recreate the container from its persisted upper volume. Missing volumes fail loudly. Web/chat decisions cannot continue container execution; a same-project CLI resume is required.
archon:RUN-04: Container runs require Docker and a current runner image containing tools. Artifacts are retained through a dedicated writable bind; stopped containers preserve their upper volume for resume. cross-checked
archon:RUN-04
Container runs require Docker and a current runner image containing tools. Artifacts are retained through a dedicated writable bind; stopped containers preserve their upper volume for resume.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Prerequisites; Running
Finding: Container runs require Docker and a current runner image containing tools. Artifacts are retained through a dedicated writable bind; stopped containers preserve their upper volume for resume.
archon:RUN-05: Optional run budgets enforce work-unit and provider-reported USD spend ceilings before new attempts. In-flight work can overshoot spend, unknown cost fails a spend-capped run, and budgeted nested/loop shapes are rejected if unsupported. cross-checked
archon:RUN-05
Optional run budgets enforce work-unit and provider-reported USD spend ceilings before new attempts. In-flight work can overshoot spend, unknown cost fails a spend-capped run, and budgeted nested/loop shapes are rejected if unsupported.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Run budgets; Retry policy
Finding: Optional run budgets enforce work-unit and provider-reported USD spend ceilings before new attempts. In-flight work can overshoot spend, unknown cost fails a spend-capped run, and budgeted nested/loop shapes are rejected if unsupported.
archon:RUN-06: Run details expose event logs and artifacts; live events show governance state. Documentation describes retry and failure records but no induced worker-failure consistency test was run. cross-checked
archon:RUN-06
Run details expose event logs and artifacts; live events show governance state. Documentation describes retry and failure records but no induced worker-failure consistency test was run.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Run details expose event logs and artifacts; live events show governance state. Documentation describes retry and failure records but no induced worker-failure consistency test was run.
archon:RUN-07: Child run costs roll up into parents without duplicating prior resumed increments; per-run token and provider-cost records persist even for failed fan-out. Unknown provider cost stays unknown. cross-checked
archon:RUN-07
Child run costs roll up into parents without duplicating prior resumed increments; per-run token and provider-cost records persist even for failed fan-out. Unknown provider cost stays unknown.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Cost roll-up; Reading tokens and cost
Finding: Child run costs roll up into parents without duplicating prior resumed increments; per-run token and provider-cost records persist even for failed fan-out. Unknown provider cost stays unknown.
archon:RUN-08: Trigger bindings declare host, shared resource and overlap policy and share admission records. Workflow fan-out adds max_parallel limits. This is not a measured host-load safety test. cross-checked
archon:RUN-08
Trigger bindings declare host, shared resource and overlap policy and share admission records. Workflow fan-out adds max_parallel limits. This is not a measured host-load safety test.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Trigger bindings declare host, shared resource and overlap policy and share admission records. Workflow fan-out adds max_parallel limits. This is not a measured host-load safety test.
archon:TEAM-01: Authenticated Web/CLI operator conversations are private to their owner. Another signed-in identity cannot send instructions to that conversation; shared run visibility is not shared prompting.
archon:TEAM-01
Authenticated Web/CLI operator conversations are private to their owner. Another signed-in identity cannot send instructions to that conversation; shared run visibility is not shared prompting.
- Source inspection covers the scoped release only. Unanswered atomic questions remain unknown; no live scenario was run.
-
Archon packages/docs-web/src/content/docs/reference/security.md
Finding: With web authentication or a trusted identity header, operator conversations are private to their owner; other identities cannot read, send or start work in them. Built-in auth uses email/password or proxy/basic/form access; the scoped authentication implementation has no enterprise SAML/OIDC provider configuration.
archon:TEAM-02: New identities are members. Operators designate admins; only a run starter or an admin can perform governance actions on that run. Solo installs may leave web auth disabled. Built-in email/password and trusted-proxy identity mechanisms do not include an enterprise SSO integration.
archon:TEAM-02
New identities are members. Operators designate admins; only a run starter or an admin can perform governance actions on that run. Solo installs may leave web auth disabled. Built-in email/password and trusted-proxy identity mechanisms do not include an enterprise SSO integration.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Users and roles; Who can act on a run
Finding: New identities are members. Operators designate admins; only a run starter or an admin can perform governance actions on that run. Solo installs may leave web auth disabled.
-
Archon packages/docs-web/src/content/docs/reference/security.md
Finding: With web authentication or a trusted identity header, operator conversations are private to their owner; other identities cannot read, send or start work in them. Built-in auth uses email/password or proxy/basic/form access; the scoped authentication implementation has no enterprise SAML/OIDC provider configuration.
archon:TEAM-03: Workflow approval gates pause for explicit approve or reject decisions, can rework on rejection and record decisions in the run. Broader shell policy remains provider-specific. cross-checked
archon:TEAM-03
Workflow approval gates pause for explicit approve or reject decisions, can rework on rejection and record decisions in the run. Broader shell policy remains provider-specific.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Workflow approval gates pause for explicit approve or reject decisions, can rework on rejection and record decisions in the run. Broader shell policy remains provider-specific.
archon:TEAM-04: Each run retains an event log, transcript and cost in the user database. The docs call this an audit trail; immutable retention and tamper resistance were not independently established. cross-checked
archon:TEAM-04
Each run retains an event log, transcript and cost in the user database. The docs call this an audit trail; immutable retention and tamper resistance were not independently established.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Each run retains an event log, transcript and cost in the user database. The docs call this an audit trail; immutable retention and tamper resistance were not independently established.
archon:TEAM-05: Operators open run details with event logs and artifacts and approve, reject, resume, cancel or abandon runs from the console, with optional alerts for approval waits. Approving a container run from the Web UI records the decision but the run must be resumed from the CLI. No timed review fixture was run. cross-checked
archon:TEAM-05
Operators open run details with event logs and artifacts and approve, reject, resume, cancel or abandon runs from the console, with optional alerts for approval waits. Approving a container run from the Web UI records the decision but the run must be resumed from the CLI. No timed review fixture was run.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Workflows and runs; Alerts
Finding: Console actions include approve, reject, resume, cancel and abandon. Optional alerts announce approval/attention waits, completion, failure and cancellation.
-
Finding: Normal container pauses stop compute; resume can restart or recreate the container from its persisted upper volume. Missing volumes fail loudly. Web/chat decisions cannot continue container execution; a same-project CLI resume is required.
-
Finding: Operators launch workflows, follow live events, open run details with event logs and artifacts, and approve, reject, resume, cancel or abandon runs from the console. No timed review fixture was run.
archon:SHIP-01: The console retains workflow events and artifacts, but the scoped product UI has no dedicated proposed-code/diff renderer.
archon:SHIP-01
The console retains workflow events and artifacts, but the scoped product UI has no dedicated proposed-code/diff renderer.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Run details retain artifacts and an event log, linked to the run identity. Graph context depends on an accessible workflow definition.
-
Archon packages/web/src/App.tsx
Finding: The shipped console routes show chat, workflow runs/events, artifacts and governance decisions. Source view/component inspection finds no proposed-code/diff renderer; the code-like approval preview in experimental components is sample text rather than a working review interface.
archon:SHIP-02: The SDLC build queue plans, implements, reviews through specialist lenses and fixes findings; its merge gate checks verdict, head-commit CI and non-red base branch. These are documented pack policies, not observed passing fixtures. cross-checked
archon:SHIP-02
The SDLC build queue plans, implements, reviews through specialist lenses and fixes findings; its merge gate checks verdict, head-commit CI and non-red base branch. These are documented pack policies, not observed passing fixtures.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The SDLC build queue plans, implements, reviews through specialist lenses and fixes findings; its merge gate checks verdict, head-commit CI and non-red base branch. These are documented pack policies, not observed passing fixtures.
archon:SHIP-03: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge. cross-checked
archon:SHIP-03
The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The forge-backed SDLC pack opens PRs, waits for CI and sends conflicting PRs back through build work before merge.
archon:SHIP-04: The merge queue checks a ready review and CI against the head commit and base health before merging. Open review threads are judged by the queue; configured repository policy remains relevant. cross-checked
archon:SHIP-04
The merge queue checks a ready review and CI against the head commit and base health before merging. Open review threads are judged by the queue; configured repository policy remains relevant.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: The merge queue lands it
Finding: The merge queue checks a ready review and CI against the head commit and base health before merging. Open review threads are judged by the queue; configured repository policy remains relevant.
archon:SHIP-05: SDLC output links the issue and pull request with a ready-review result and exact-head merge checks. A rollback or stale-approval mutation test was not performed. cross-checked
archon:SHIP-05
SDLC output links the issue and pull request with a ready-review result and exact-head merge checks. A rollback or stale-approval mutation test was not performed.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: SDLC output links the issue and pull request with a ready-review result and exact-head merge checks. A rollback or stale-approval mutation test was not performed.
archon:SHIP-06: Build and merge queues coordinate ready issues and PRs, review verdicts, CI and conflict rework. This is a documented queue, not a measured six-task human review scenario. cross-checked
archon:SHIP-06
Build and merge queues coordinate ready issues and PRs, review verdicts, CI and conflict rework. This is a documented queue, not a measured six-task human review scenario.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Build and merge queues coordinate ready issues and PRs, review verdicts, CI and conflict rework. This is a documented queue, not a measured six-task human review scenario.
archon:OWN-01: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope. cross-checked
archon:OWN-01
Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Current Archon application source is MIT licensed at the pinned revision. The old Python product is preserved on an archive branch and is not the profile scope.
archon:OWN-02: Archon is a full self-hosted application on the user machine or server, using SQLite by default or PostgreSQL. CLI, server and web console do not require a separate hosted Archon service. cross-checked
archon:OWN-02
Archon is a full self-hosted application on the user machine or server, using SQLite by default or PostgreSQL. CLI, server and web console do not require a separate hosted Archon service.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: Self-hosted; Quickstart
Finding: Archon is a full self-hosted application on the user machine or server, using SQLite by default or PostgreSQL. CLI, server and web console do not require a separate hosted Archon service.
archon:OWN-03: Archon sends anonymous categorical workflow/platform/provider/outcome and numeric usage events, excluding code and prompts. ARCHON_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1 or disabled POSTHOG_API_KEY turns it off; CI disables it automatically. cross-checked
archon:OWN-03
Archon sends anonymous categorical workflow/platform/provider/outcome and numeric usage events, excluding code and prompts. ARCHON_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1 or disabled POSTHOG_API_KEY turns it off; CI disables it automatically.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: Archon sends anonymous categorical workflow/platform/provider/outcome and numeric usage events, excluding code and prompts. ARCHON_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1 or disabled POSTHOG_API_KEY turns it off; CI disables it automatically.
archon:OWN-04: The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
archon:OWN-04
The current core Archon application is free MIT software to install and self-host, with no paid ADE tier in the checked first-party offering. Coding-agent subscriptions/API keys and operator compute are paid separately.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Archon: MIT License; Distribution grant
Finding: The source license permits use and distribution free of charge. Provider subscriptions and self-hosted compute are separate user costs; there is no vendor cloud plan price asserted here.
-
Finding: The current first-party distribution is the MIT source/CLI application to install and self-host. README and installation/provider/deployment docs expose no paid ADE tier. Underlying provider subscriptions/API keys and operator compute are separate; the Pi provider documentation describes reuse of API keys.
archon:OWN-06: The repository released v0.14.0 on November 7. Open issue topics include console navigation URLs, effective model throughput, scheduled-run PATH and review blockers. These are issue reports, not verified failures. cross-checked
archon:OWN-06
The repository released v0.14.0 on November 7. Open issue topics include console navigation URLs, effective model throughput, scheduled-run PATH and review blockers. These are issue reports, not verified failures.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The repository released v0.14.0 on November 7. Open issue topics include console navigation URLs, effective model throughput, scheduled-run PATH and review blockers. These are issue reports, not verified failures.
archon:OWN-08: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate. cross-checked
archon:OWN-08
The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.
- Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
-
Finding: The core app is available as free MIT software to install and self-host; paid model and own-compute costs remain separate.