podium

MonoCode

50 of 51 criteria have a sourced finding; 0 were also cross-checked by a second agent. Every comparison that includes MonoCode links here for scope, limitations, atomic answers and sources.

Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.

Rubric
0.3 · 51 criteria
Source checks
2026-11-08 to 2026-11-16
Agent cross-checked
0 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Sourced partial

Desktop installers support macOS Apple Silicon/Intel, Linux x64 and Windows x64. Native preview installers are experimental. Source-build instructions exist for an Expo iOS/Android development client. No store-distributed client was established by this pass. Local /operator exposes a product-owned app CLI to opted-in active agent turns. Desktop sessions can be prompted and split side by side; remote desktop views start/steer host sessions with documented feature limits. The phone can read/send/start/stop desktop sessions, but approvals and questions still need desktop attention. The scoped host exposes RPC to native clients and does not serve a standalone browser client.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
9 atomic answers
  • Desktop os [supported] Desktop installers support macOS Apple Silicon/Intel, Linux x64 and Windows x64. Native preview installers are experimental. Sources: monocode:readme.
  • Mobile apps [partial] Source-build instructions exist for an Expo iOS/Android development client. No store-distributed client was established by this pass. Sources: monocode:mobile.
  • Browser [unsupported] The scoped host accepts native authenticated RPC rather than serving a browser UI. Sources: monocode:gap39-access.
  • Mobile browser [unsupported] The companion requires an Expo native module and the host serves RPC rather than a mobile web UI. Sources: monocode:mobile, monocode:gap39-access.
  • Cli [supported] Local /operator exposes a product-owned app CLI to opted-in active agent turns. Sources: monocode:operator.
  • Editor extensions [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no editor extension; searched terms: vscode extension, jetbrains, .vsix. Sources: monocode:m-scan.
  • Task actions [supported] Desktop sessions can be prompted and split side by side; remote desktop views start/steer host sessions with documented feature limits. Sources: monocode:readme, monocode:remote.
  • Notifications [supported] Approval and question notices, macOS Dock badge of sessions needing input, input notifications and session reminders. Sources: monocode:m-notify.
  • Cross device continuity [partial] The phone can read/send/start/stop desktop sessions, but approvals and questions still need desktop attention. Sources: monocode:mobile.

Sources: monocode:readme, monocode:mobile, monocode:operator, monocode:remote, monocode:gap39-access, monocode:m-scan, monocode:m-notify

Sourced partial

Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, omp, fx, Hermes, Antigravity and Devin CLI are listed. MonoCode launches installed provider CLIs and reuses native logins; preview transports vary by provider. MonoCode v0.16.0 documents running installed Antigravity on macOS and Linux and selecting it to send a message after sign-in.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. Antigravity source pass: v0.16.0 (7508feaee84db638fb7a7c146d9f15de5d0f3689). · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
  • Antigravity uses the ACP runtime on macOS/Linux; the released documentation excludes Windows for this provider.
5 atomic answers
  • Harnesses [supported] Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, omp, fx, Hermes, Antigravity and Devin CLI are listed. MonoCode v0.16.0 documents running installed Antigravity on macOS and Linux and selecting it to send a message after sign-in. Sources: monocode:providers, monocode:agy-release-1, monocode:agy-release-2.
  • Model providers [supported] Model choice is per CLI harness: models.list reports providers, models and settings from each installed agent; MonoCode sells no tokens. Sources: monocode:m-agentaccess, monocode:m-harness.
  • Custom adapters [unsupported] Harness IDs are a closed list of eleven; no generic adapter or user-defined harness exists in the pinned release. Sources: monocode:m-harness, monocode:m-scan.
  • Session integration [supported] MonoCode launches installed provider CLIs and reuses native logins; preview transports vary by provider. Sources: monocode:providers, monocode:parity.
  • Mixed harness operation [supported] Orchestration tasks name a harness and model each, allowedHarnesses limits the set, and handoff moves context between harnesses. Sources: monocode:m-orch, monocode:m-orchstate, monocode:m-handoff.

Sources: monocode:providers, monocode:parity, monocode:agy-release-1, monocode:agy-release-2, monocode:m-agentaccess, monocode:m-harness, monocode:m-scan, monocode:m-orch, monocode:m-orchstate, monocode:m-handoff

Sourced partial

README explicitly says existing supported coding-agent subscriptions work; MonoCode does not sell tokens. Mobile account selection reuses desktop Claude/Codex profiles and opens a new conversation when switching an existing chat.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
7 atomic answers
  • Agent subscriptions [supported] README explicitly says existing supported coding-agent subscriptions work; MonoCode does not sell tokens. Sources: monocode:readme.
  • Api accounts [partial] The CLIs use whatever keys they hold; MonoCode adds no key entry, only multiple provider accounts and usage headroom per account. Sources: monocode:m-usage, monocode:m-providers.
  • Vendor credits [unsupported] README states MonoCode does not sell tokens and the tree has no credit or billing code. Sources: monocode:m-readme, monocode:m-scan.
  • Local models [partial] Local models are possible only through harnesses that support them (OpenCode, Pi and others); the app has no local model runtime. Sources: monocode:m-harness.
  • Account switching [supported] Mobile account selection reuses desktop Claude/Codex profiles and opens a new conversation when switching an existing chat. Sources: monocode:mobile.
  • Vendor account requirement [supported] No MonoCode account is needed; at least one agent CLI must be installed and logged in. Sources: monocode:m-readme, monocode:m-providers.
  • Provider restrictions [unsupported] No provider-restriction handling is documented or coded beyond reading usage limits. Sources: monocode:m-scan.

Sources: monocode:readme, monocode:mobile, monocode:m-usage, monocode:m-providers, monocode:m-readme, monocode:m-scan, monocode:m-harness

Sourced partial

Install/authenticate a provider, open a project folder, select an agent and send a message. Experimental SSH connection setup installs/verifies a remote host package, service and per-device credentials.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
7 atomic answers
  • First task setup [supported] Install/authenticate a provider, open a project folder, select an agent and send a message. Sources: monocode:providers.
  • No git [partial] Projects are folders; worktree features need Git, other features do not appear to require it (non-Git checkpoints are listed as remaining work in the native docs). Sources: monocode:m-wt.
  • Local git without remote [supported] Branch and worktree operations are local Git commands and need no remote; PR creation uses gh. Sources: monocode:m-wt, monocode:m-pr.
  • Hosted git [supported] GitHub via gh for pull requests and inbox; GitLab, Azure DevOps, Linear and Jira inbox sources. Sources: monocode:m-pr, monocode:m-inbox.
  • Prerequisite guidance [supported] Providers doc lists install and login commands per CLI; remote doc lists host prerequisites. Sources: monocode:m-providers, monocode:m-remote.
  • Managed cloud setup [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no managed cloud setup; searched terms: cloud sandbox, provision, vendor cloud. Sources: monocode:m-scan.
  • Byo vps onboarding [supported] Experimental SSH connection setup installs/verifies a remote host package, service and per-device credentials. Sources: monocode:remote.

Sources: monocode:providers, monocode:remote, monocode:m-wt, monocode:m-pr, monocode:m-inbox, monocode:m-providers, monocode:m-remote, monocode:m-scan

Sourced partial

Opt-in app CLI offers models.list, sessions.start/list/read/send/stop and note/worktree operations. The local operator CLI acts only during its opted-in active turn; remote host device tokens grant OS-user workspace/provider control. A separate user-runnable MonoCode Host CLI starts/stops the host, manages its service and lists/revokes paired devices.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
8 atomic answers
  • Cli [supported] The MonoCode Host command-line program supports serve/start/status/stop, service install/uninstall and device pairing/listing/revocation. The app-internal /operator interface is a separate surface. Sources: monocode:gap39-host-cli.
  • Api [partial] Local authenticated loopback control CLI for orchestration and /operator actions, plus a host HTTP API used by the desktop and phone; neither is documented as a public stable API. Sources: monocode:m-control, monocode:m-hostauth, monocode:m-agentaccess.
  • Sdk [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no SDK package; searched terms: sdk, npm publish client. Sources: monocode:m-scan.
  • Mcp server [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no MCP server exposing MonoCode; searched terms: mcp server, mcp-server. Sources: monocode:m-scan.
  • Webhooks [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no webhook endpoint or sender (Jira automation polls); searched terms: webhook, openapi. Sources: monocode:m-scan.
  • Operations [supported] Create, list, read, send, stop, archive and delete sessions, draft messages, manage folders and notes from the operator CLI; orchestration CLI adds delegate, steer, review and finish. Sources: monocode:m-agentaccess, monocode:m-orch.
  • Authentication [partial] The local operator CLI acts only during its opted-in active turn; remote host device tokens grant OS-user workspace/provider control. Sources: monocode:operator, monocode:remote.
  • Stability [partial] The remote feature is labelled experimental and unknown CLI fields are rejected; no versioned API stability guarantee is stated. Sources: monocode:m-remote, monocode:m-agentaccess.

Sources: monocode:operator, monocode:remote, monocode:gap39-host-cli, monocode:m-control, monocode:m-hostauth, monocode:m-agentaccess, monocode:m-scan, monocode:m-orch, monocode:m-remote

Sourced partial

MonoCode manages MCP servers and skills for the agent CLIs it runs; MCP use, plugins and tools stay with the underlying harness.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: mcp_client (partial), plugins (unsupported), custom_tools (unsupported), authentication (partial), permission_scope (partial). See each atomic answer for the limit and its evidence.
7 atomic answers
  • Mcp client [partial] MonoCode adds and discovers MCP server config per provider (mcp.rs) and offers /mcp commands; the harness CLI is the MCP client. Sources: monocode:m-mcp.
  • Plugins [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no plugin host (Tauri plugins are only internal); searched terms: plugin api, extension host. Sources: monocode:m-scan.
  • Custom tools [unsupported] No user-defined tool registry in MonoCode; tools are provider tools plus the operator CLI. Sources: monocode:m-scan, monocode:m-agentaccess.
  • Instructions import [supported] Skill discovery reads project and home skill roots and the UI can create skills. Sources: monocode:m-skills.
  • Authentication [partial] Jira uses an unscoped API token, other inbox sources use their tokens; MCP authentication belongs to the provider CLI. Sources: monocode:m-jira, monocode:m-mcp.
  • Permission scope [partial] Jira scoped tokens are explicitly unsupported; MCP permissions are inherited from each provider. Sources: monocode:m-jira.
  • Integration owner [supported] Inbox and operator are product-owned; MCP and skills connections are inherited from the harness. Sources: monocode:m-mcp, monocode:m-skills.

Sources: monocode:m-mcp, monocode:m-scan, monocode:m-agentaccess, monocode:m-skills, monocode:m-jira

Sourced supported

Production uses React/Tauri; experimental native preview uses Rust/GPUI. Mobile is an Expo app with a Rust native QUIC transport module; Expo Go cannot load it.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
4 atomic answers
  • Desktop implementation [supported] Production uses React/Tauri; experimental native preview uses Rust/GPUI. Sources: monocode:readme.
  • Mobile implementation [supported] Mobile is an Expo app with a Rust native QUIC transport module; Expo Go cannot load it. Sources: monocode:mobile.
  • Hybrids [supported] Production app is a Tauri shell with a React web UI and Rust back end; an experimental Rust GPUI app and an Expo phone app also exist. Sources: monocode:m-tauri, monocode:m-mobile.
  • Implementation evidence [supported] Tauri config, Cargo and package.json at the tag; mobile README describes the Expo app. Sources: monocode:m-tauri, monocode:m-mobile.

Sources: monocode:readme, monocode:mobile, monocode:m-tauri, monocode:m-mobile

Planning and context

Sourced partial

Jira inbox includes issue descriptions/comments and starts work with a Jira identifier; it is an external tracker integration. Jira issue-appeared automation polls the inbox after its initial snapshot; it is not a webhook for every created issue.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
9 atomic answers
  • Local creation [partial] Users create sessions, notes and drafts locally; sessions started from inbox items carry the issue identifier. Sources: monocode:m-agentaccess, monocode:m-jira.
  • Prompt intake [supported] Composer prompts start sessions; operator CLI and automations can start sessions with prompts. Sources: monocode:m-agentaccess, monocode:m-auto.
  • External import [supported] Jira inbox includes issue descriptions/comments and starts work with a Jira identifier; it is an external tracker integration. Sources: monocode:jira.
  • Chat git triggers [partial] Jira issue-appeared automation polls the inbox after its initial snapshot; it is not a webhook for every created issue. Sources: monocode:jira.
  • Authoritative tracker [supported] GitHub, Linear, Jira, GitLab or Azure DevOps stay the authoritative tracker; sessions can link to issues and pull requests. Sources: monocode:m-inbox, monocode:m-jira.
  • Stable ids [partial] Linked work items keep repo and number (LinkedWorkItem); sessions have their own IDs. Sources: monocode:m-harness.
  • Sync [partial] Inbox polls the trackers; Jira comments can be posted back; no bidirectional field sync. Sources: monocode:m-jira, monocode:m-inbox.
  • Supported edits [partial] Read issues, read and post comments (Jira doc); status or field edits are not documented. Sources: monocode:m-jira.
  • External roundtrips [supported] Status and field changes require a trip to the tracker. Sources: monocode:m-jira.

Sources: monocode:jira, monocode:m-agentaccess, monocode:m-jira, monocode:m-auto, monocode:m-inbox, monocode:m-harness

Sourced partial

Remote Plan mode creates a reviewable plan card whose Build action continues on the host.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
7 atomic answers
  • Plans [supported] Remote Plan mode creates a reviewable plan card whose Build action continues on the host. Sources: monocode:remote.
  • Acceptance criteria [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no acceptance-criteria field; searched terms: acceptance criteria. Sources: monocode:m-scan.
  • Editors [supported] Plan mode produces a plan card and read-only plan tabs; orchestration proposal cards can be edited before approval. Sources: monocode:m-remote, monocode:m-orch.
  • Revisions [unsupported] No revision history for plans in the inspected models. Sources: monocode:m-scan.
  • Amendment [partial] Lead can message or steer running workers and retry with new files, so scope can change mid-run. Sources: monocode:m-orch.
  • Restart persistence [supported] Orchestration runs commit versioned snapshots and recover interrupted workers on resume. Sources: monocode:m-orchstate.

Sources: monocode:remote, monocode:m-scan, monocode:m-remote, monocode:m-orch, monocode:m-orchstate

Sourced partial

Orchestration runs give a lead agent tasks with dependencies, readiness and states, within one run; there is no epic object.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: epics (partial), hierarchy (partial), state_propagation (partial), task_to_epic (unsupported), identity_retention (partial), workflow_constraints (partial). See each atomic answer for the limit and its evidence.
9 atomic answers
  • Epics [partial] An orchestration run groups tasks under a lead but is not an epic with identity across runs. Sources: monocode:m-orchstate.
  • Hierarchy [partial] Run to task, one level; workers cannot spawn further workers through the control CLI. Sources: monocode:m-orchstate, monocode:m-orch.
  • Blockers [supported] dependsOn lists task IDs; blocked and scope-blocked states exist. Sources: monocode:m-orchstate, monocode:m-orch.
  • Readiness [supported] A queued task is ready only when all dependencies are accepted. Sources: monocode:m-orch.
  • Enforcement [supported] The pump refuses to dispatch until dependencies are accepted and scopes do not overlap. Sources: monocode:m-orch.
  • State propagation [partial] Interrupted and blocked states propagate to affected tasks on pause; accepted state gates dependents. Sources: monocode:m-orchstate, monocode:m-orch.
  • Task to epic [unsupported] A simple session cannot be promoted to an orchestration run; the lead starts the run from a prompt. Sources: monocode:m-scan.
  • Identity retention [partial] Retried tasks keep their worker checkout and task ID with new dispatch IDs. Sources: monocode:m-orchstate.
  • Workflow constraints [partial] Orchestration requires a lead session and approved proposal; ordinary sessions need no workflow. Sources: monocode:m-orch.

Sources: monocode:m-orchstate, monocode:m-orch, monocode:m-scan

Sourced partial

Operator notes.read/write stores project notes with IDs, titles and tags. This is not a verified living spec system. Experimental Monos maintain memory across projects; the native preview still lists runtime/recovery checks as open.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
10 atomic answers
  • Instructions [supported] Provider CLIs read their own repository instruction files; inbox.md instructions ship with the app. Sources: monocode:m-skills.
  • Skills [supported] Skill discovery by project and home scope with creation and picker UI. Sources: monocode:m-skills.
  • Project docs [partial] Operator notes.read/write stores project notes with IDs, titles and tags. This is not a verified living spec system. Sources: monocode:operator.
  • Memory [partial] Experimental Monos maintain memory across projects; the native preview still lists runtime/recovery checks as open. Sources: monocode:readme, monocode:parity.
  • Scope [supported] Skills carry scope and source; Monos keep memory per Mono. Sources: monocode:m-skills.
  • Provenance [partial] Skills show their source path; Mono memory provenance not documented. Sources: monocode:m-skills.
  • Correction [partial] Skills are files the user edits; no memory correction flow was inspected. Sources: monocode:m-skills.
  • Deletion [partial] Skills can be disabled via disabled paths; Mono reset exists (ConfirmReset). Sources: monocode:m-skills.
  • Freshness [unsupported] No stale-context controls. Sources: monocode:m-scan.
  • Takeover continuity [partial] Sessions persist in the local database; remote host sessions persist on the host. Sources: monocode:m-remote.

Sources: monocode:operator, monocode:readme, monocode:parity, monocode:m-skills, monocode:m-scan, monocode:m-remote

Sourced partial

File and project text search exists; no indexed architecture knowledge, citations or review-time enforcement.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: indexing (unsupported), external_knowledge (unsupported), freshness (unsupported), access_scope (unsupported), api_retrieval (unsupported), citations (unsupported), conflict_detection (unsupported), review_enforcement (unsupported). See each atomic answer for the limit and its evidence.
10 atomic answers
  • Indexing [unsupported] No code index or embeddings; the background-work module only bounds optional indexing. Sources: monocode:m-bg, monocode:m-scan.
  • External knowledge [unsupported] No external knowledge connector beyond inbox items. Sources: monocode:m-scan.
  • Multimodal inputs [supported] File and image attachments are supported in the composer. Sources: monocode:m-remote.
  • Freshness [unsupported] No retrieval freshness controls. Sources: monocode:m-scan.
  • Access scope [unsupported] No retrieval access scope. Sources: monocode:m-scan.
  • Api retrieval [unsupported] No API documentation retrieval. Sources: monocode:m-scan.
  • Citations [unsupported] No retrieval citations. Sources: monocode:m-scan.
  • Conflict detection [unsupported] No architecture conflict detection. Sources: monocode:m-scan.
  • Review enforcement [unsupported] No architecture review enforcement. Sources: monocode:m-scan.

Sources: monocode:m-search, monocode:m-bg, monocode:m-scan, monocode:m-remote

Sourced partial

MonoCode keeps sessions, notes and orchestration tasks, and brings issues in from external trackers; it has no native issue tracker.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
17 atomic answers
  • Create [unsupported] No product-owned issue creation/store was found in the scoped task and inbox implementations. Sources: monocode:gap39-tasks.
  • Edit [unsupported] No native issue edit; external issues are read and commented. Sources: monocode:m-jira, monocode:m-scan.
  • Discuss [partial] Inbox discussion panels read and post comments on external items. Sources: monocode:m-jira.
  • Prioritize [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no priority field; searched terms: priority, rank. Sources: monocode:m-scan.
  • Label [unsupported] No native labels (session folders only). Sources: monocode:m-agentaccess.
  • Assign [unsupported] No assignment. Sources: monocode:m-scan.
  • Filter [supported] Inbox filters (InboxFiltersMenu) by source and project. Sources: monocode:m-jira.
  • Archive [supported] Sessions can be archived and restored (sessions.archive). Sources: monocode:m-agentaccess.
  • Reopen [supported] Archived sessions restore. Sources: monocode:m-agentaccess.
  • Project epic views [partial] Project rail and sidebar session folders; no epic view. Sources: monocode:m-agentaccess.
  • Idea parking [supported] Notes and unsent drafts (sessions.draft) park ideas without starting an agent. Sources: monocode:m-agentaccess.
  • Explicit dispatch [supported] A saved draft is sent when the user chooses; orchestration proposals need approval. Sources: monocode:m-agentaccess, monocode:m-orch.
  • Task session separation [unsupported] The todo list belongs to the agent session; external inbox tickets retain external tracker identity. Sources: monocode:gap39-tasks.
  • Metadata [partial] Sessions keep harness, model, worktree and linked work item; tasks keep scope and dependsOn. Sources: monocode:m-orchstate.
  • Durable states [supported] Orchestration tasks and dispatches persist states; sessions persist archived status. Sources: monocode:m-orchstate.
  • External tracker requirement [supported] Inbox issue models use external GitHub, Jira, Linear or Azure DevOps trackers. Sources: monocode:gap39-tasks.

Sources: monocode:gap39-tasks, monocode:m-jira, monocode:m-scan, monocode:m-agentaccess, monocode:m-search, monocode:m-inbox, monocode:m-orch, monocode:m-orchstate

Sourced partial

Agents can read and write sessions and notes through the operator CLI and tasks through the orchestration CLI; there is no shared issue record.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: shared_ids (partial), claim (unsupported), attribution (partial). See each atomic answer for the limit and its evidence.
14 atomic answers

Sources: monocode:m-agentaccess, monocode:m-orch, monocode:m-scan, monocode:m-orchstate, monocode:m-control

Sourced partial

No living product specification system exists in the pinned release.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: persistent_requirements (unsupported), human_edits (partial), agent_edits (partial), revisions (unsupported), approvals (unsupported), implementation_links (unsupported), later_retrieval (unsupported), drift_detection (unsupported), review_integration (unsupported). See each atomic answer for the limit and its evidence.
9 atomic answers
  • Persistent requirements [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no persistent requirements store; searched terms: living spec, requirements, acceptance criteria. Sources: monocode:m-scan.
  • Human edits [partial] Notes can hold specs but are not managed requirements. Sources: monocode:m-agentaccess.
  • Agent edits [partial] Agents can write notes through notes.write; notes are not requirement objects. Sources: monocode:m-agentaccess.
  • Revisions [unsupported] No attributable requirement revisions. Sources: monocode:m-scan.
  • Approvals [unsupported] No spec approval rules. Sources: monocode:m-scan.
  • Later retrieval [unsupported] No automatic spec retrieval. Sources: monocode:m-scan.
  • Drift detection [unsupported] No drift detection. Sources: monocode:m-scan.
  • Review integration [unsupported] No spec consideration in review. Sources: monocode:m-scan.

Sources: monocode:m-scan, monocode:m-agentaccess

Coordination and automation

COORD-01

Parallel work

Sourced partial

README explicitly documents separate Git worktrees for parallel tasks and split sessions.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
5 atomic answers
  • Concurrent sessions [supported] README explicitly documents separate Git worktrees for parallel tasks and split sessions. Sources: monocode:readme.
  • Concurrent tasks [supported] Sessions run concurrently in tabs and split panes; orchestration runs up to four workers. Sources: monocode:m-readme, monocode:m-orch.
  • Quotas [partial] Orchestration maxWorkers is 1-4 per run; no global session quota. Sources: monocode:m-orch.
  • Observed concurrency [partial] Concurrency is bounded and observable in the UI, but no measured concurrency figures are published. Sources: monocode:m-orch.
  • Status visibility [supported] Session list shows busy, needs input and finished states; orchestration shows task states. Sources: monocode:m-orchstate, monocode:m-notify.

Sources: monocode:readme, monocode:m-readme, monocode:m-orch, monocode:m-orchstate, monocode:m-notify

Sourced partial

Delegation assigns tasks to chosen harnesses with scheduling and scope exclusion; there is no multi-user assignment.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: human_assignment (unsupported), claims (unsupported), routing (partial). See each atomic answer for the limit and its evidence.
7 atomic answers
  • Human assignment [unsupported] No human assignment; single local user. Sources: monocode:m-scan.
  • Agent assignment [supported] Lead delegates tasks to workers with harness and model. Sources: monocode:m-orch.
  • Claims [unsupported] No claim mechanism. Sources: monocode:m-scan.
  • Queues [supported] Queued tasks wait for worker slots and dependencies. Sources: monocode:m-orch.
  • Routing [partial] Lead chooses harness and model per task; the app does no automatic routing. Sources: monocode:m-orch.
  • Duplicate prevention [supported] Overlapping file scopes are queued and the approved-proposal prompt says not to delegate duplicates. Sources: monocode:m-orch.
  • Ownership enforcement [supported] Scope violations block the worker; only the active dispatch can settle a task. Sources: monocode:m-orchstate, monocode:m-orch.

Sources: monocode:m-scan, monocode:m-orch, monocode:m-orchstate

Sourced supported

sessions.start accepts provider, model, effort, permission mode and worktree scope. Opted-in Operator can start/read/send/stop other local project sessions through MonoCodes own CLI. sessions.read returns paginated exchanges and sessions.send submits an idle-session follow-up.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
12 atomic answers
  • Roles [supported] Lead and worker roles with a lead CLI. Sources: monocode:m-orch.
  • Model harness effort [supported] sessions.start accepts provider, model, effort, permission mode and worktree scope. Sources: monocode:operator.
  • Messages [supported] message and steer send text to workers; respond and answer reply to approvals and questions. Sources: monocode:m-orch.
  • Results return [supported] Worker results reach the lead automatically when idle and via get and wait. Sources: monocode:m-orch.
  • Cross harness [supported] Tasks pick any allowed harness, so a lead can mix harnesses. Sources: monocode:m-orch, monocode:m-orchstate.
  • Orchestration owner [supported] Opted-in Operator can start/read/send/stop other local project sessions through MonoCodes own CLI. Sources: monocode:operator.
  • Activation [supported] Started from an orchestrator command with an approval card or by /operator. Sources: monocode:m-orch, monocode:m-agentaccess.
  • Authentication [supported] Per-session loopback tokens grant the CLI; credentials sit in the environment. Sources: monocode:m-control, monocode:m-orch.
  • Live progress [supported] Worker sessions are visible live and task states update. Sources: monocode:m-orchstate.
  • Retained results [supported] Task results and dispatches persist in run snapshots. Sources: monocode:m-orchstate.
  • Followup [supported] sessions.read returns paginated exchanges and sessions.send submits an idle-session follow-up. Sources: monocode:operator.
  • Invocation [supported] Lead runs the app CLI, documented by cli --help in its prompt. Sources: monocode:m-orch.

Sources: monocode:operator, monocode:m-orch, monocode:m-orchstate, monocode:m-agentaccess, monocode:m-control

Sourced partial

Experimental Monos can run user-configured scheduled tasks. Native preview scheduler/runtime behavior remains unverified. Jira Issue appeared can start work in a selected local project after inbox polling.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
8 atomic answers
  • Schedules [partial] Experimental Monos can run user-configured scheduled tasks. Native preview scheduler/runtime behavior remains unverified. Sources: monocode:readme, monocode:parity.
  • Events [supported] Jira Issue appeared can start work in a selected local project after inbox polling. Sources: monocode:jira.
  • Recurring tasks [supported] Hourly, daily, weekday and weekly schedules plus Monos habits. Sources: monocode:m-auto, monocode:m-readme.
  • Completion conditions [partial] A run ends with status succeeded, failed, skipped or cancelled; no custom completion conditions. Sources: monocode:m-auto.
  • Scheduler location [supported] Evaluated in the desktop app by a 30 s timer; persistence in the local SQLite database. Sources: monocode:m-autotimer, monocode:m-autors.
  • Overlaps [partial] Runs can reuse a session (reuseSession) or start fresh; skipped status exists for runs that do not start. Sources: monocode:m-auto.
  • Retries [unsupported] No automatic retry policy for failed runs; a failed run records lastRunError. Sources: monocode:m-auto.
  • Client independence [unsupported] The scheduler runs inside the desktop app, so a closed app does not fire runs; missed runs start only within the grace window on next launch. Sources: monocode:m-autotimer, monocode:m-autors.

Sources: monocode:readme, monocode:parity, monocode:jira, monocode:m-auto, monocode:m-readme, monocode:m-autotimer, monocode:m-autors

Sourced partial

sessions.stop cancels the current local turn and pauses queued messages; archive preserves its conversation.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
10 atomic answers
  • Pause [supported] Orchestration runs can be paused (status paused with a reason) and stop pauses queued messages. Sources: monocode:m-orchstate, monocode:m-agentaccess.
  • Stop [supported] sessions.stop cancels the current local turn and pauses queued messages; archive preserves its conversation. Sources: monocode:operator.
  • Resume [supported] Resume continues interrupted workers from their retained checkouts. Sources: monocode:m-orch.
  • Steer [supported] steer redirects a running worker mid-turn without losing its work. Sources: monocode:m-orch.
  • Notifications [supported] Dock badge, approval notices and input notifications. Sources: monocode:m-notify.
  • Pending decisions [supported] needsInput on tasks, approval toasts and the Dock badge count. Sources: monocode:m-orch, monocode:m-notify.
  • Escalation [partial] The lead decides worker approvals and puts genuine user calls in the conversation. Sources: monocode:m-orch.
  • Visible errors [supported] Tasks hold error text, dispatch states include start_unknown and stop_unknown, and runs hold error and pause reason. Sources: monocode:m-orchstate.
  • Chat terminal parity [partial] Chat sessions and terminals are separate surfaces; remote hosts do not offer terminals. Sources: monocode:m-remote.
  • Retained history [supported] Stopped sessions and cancelled tasks retain transcripts. Sources: monocode:m-agentaccess, monocode:m-remote.

Sources: monocode:operator, monocode:m-orchstate, monocode:m-agentaccess, monocode:m-orch, monocode:m-notify, monocode:m-remote

Sourced partial

A session list and orchestration views show agents and task states; no cross-epic fleet board exists.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: fleet_fixture (unsupported), dependencies (partial), workload (partial), navigation_errors (partial), fixture_mode (unsupported). See each atomic answer for the limit and its evidence.
8 atomic answers
  • Fleet fixture [unsupported] No multi-epic view. Sources: monocode:m-scan.
  • Parent child [supported] OrchestrationSidebarAgents lists a lead and its workers. Sources: monocode:m-orchstate.
  • Dependencies [partial] dependsOn exists in the model; the sidebar view of dependencies was not verified. Sources: monocode:m-orchstate.
  • Attention [supported] Needs-input sessions raise the Dock badge and toasts. Sources: monocode:m-notify.
  • History [supported] Project session history and archived sessions. Sources: monocode:m-agentaccess.
  • Workload [partial] Resource-pressure notice shows load; no per-agent workload view. Sources: monocode:m-pressure.
  • Navigation errors [partial] Errors are readable on tasks; direct navigation to a failed task was not verified. Sources: monocode:m-orchstate.
  • Fixture mode [unsupported] No fixture mode. Sources: monocode:m-scan.

Sources: monocode:m-scan, monocode:m-orchstate, monocode:m-notify, monocode:m-agentaccess, monocode:m-pressure

Sourced partial

Quick sessions need no preset; orchestration is optional and visible. Natural-language configuration is available through the /operator and orchestrator commands.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: growing_epic (unsupported), presets (partial), discoverability (partial). See each atomic answer for the limit and its evidence.
10 atomic answers
  • Quick task [supported] Open a folder, pick an agent and send a message. Sources: monocode:m-readme.
  • Growing epic [unsupported] A session cannot be promoted into an orchestration run. Sources: monocode:m-scan.
  • Presets [partial] Automation templates exist; no orchestration presets. Sources: monocode:m-auto.
  • Natural language [supported] /operator requests such as starting two Codex sessions are interpreted by the agent. Sources: monocode:m-agentaccess.
  • Agent configuration [supported] sessions.start and delegate accept provider, model, effort and permission mode. Sources: monocode:m-agentaccess, monocode:m-orch.
  • In run changes [supported] steer, message, retry and cancel change work during a run. Sources: monocode:m-orch.
  • Live roles [supported] Lead and worker roles are visible in the sidebar. Sources: monocode:m-orchstate.
  • Retained relationships [supported] Run snapshots keep lead, tasks, dependencies and dispatches. Sources: monocode:m-orchstate.
  • Discoverability [partial] Slash picker offers /operator; orchestration is reached by a command. Sources: monocode:m-agentaccess.
  • Auth friction [supported] No MonoCode login; the CLI credentials are injected into the lead environment. Sources: monocode:m-orch, monocode:m-control.

Sources: monocode:m-readme, monocode:m-scan, monocode:m-auto, monocode:m-agentaccess, monocode:m-orch, monocode:m-orchstate, monocode:m-control

Execution and reliability

Sourced partial

Installed provider CLIs execute in the chosen local project or worktree. Experimental remote hosts execute agent sessions on Linux/macOS/Windows machines. Quitting desktop closes its SSH forward but does not stop remote host services or agent sessions. The remote machine must remain awake. No MonoCode-managed execution service is implemented in the scoped launch paths.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
12 atomic answers
  • Local [supported] Installed provider CLIs execute in the chosen local project or worktree. Sources: monocode:readme.
  • Byo remote [supported] Experimental remote hosts execute agent sessions on Linux/macOS/Windows machines. Sources: monocode:remote.
  • Self hosted [partial] Remote host can be installed on a machine you own via SSH or manually; it is a self-managed execution host, not a self-hosted control plane. Sources: monocode:m-remote.
  • Managed cloud [unsupported] The product starts local or user-operated remote host processes; no vendor runtime provisioner exists in the scoped launch implementation. Sources: monocode:gap39-process.
  • Hybrid [supported] Local and remote projects coexist in one app. Sources: monocode:m-remote.
  • Provisioning [supported] Settings downloads the matching host package, verifies its checksum and installs a user service over SSH. Sources: monocode:m-remote.
  • Payer [supported] The user owns the machine and pays their own agent subscriptions; MonoCode charges nothing. Sources: monocode:m-readme, monocode:m-remote.
  • Resources [unsupported] Host resources are whatever the user machine has; the app sets none. Sources: monocode:m-remote.
  • Region [unsupported] No region concept; the host is wherever the user runs it. Sources: monocode:m-remote.
  • Expiry [supported] Host has no time limit (Windows scheduled task has none); manual start without systemd is not restarted after reboot. Sources: monocode:m-remote.
  • Client disconnect [supported] Quitting desktop closes its SSH forward but does not stop remote host services or agent sessions. The remote machine must remain awake. Sources: monocode:remote.
  • Other device continuation [supported] The host owns sessions so another paired desktop can connect and see them; the phone also pairs with the desktop. Sources: monocode:m-remote, monocode:m-hostauth.

Sources: monocode:readme, monocode:remote, monocode:gap39-process, monocode:m-remote, monocode:m-readme, monocode:m-hostauth

Sourced partial

Desktop/operator can create and choose Git worktrees for session file separation. The inspected desktop and remote host launch paths use host child processes without per-session containers or VMs.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
12 atomic answers
  • Checkout [supported] Sessions run in the project checkout or a chosen worktree. Sources: monocode:m-readme, monocode:m-wt.
  • Branch [supported] Branch pickers and branch creation; orchestration branches. Sources: monocode:m-wt.
  • Worktree [supported] Desktop/operator can create and choose Git worktrees for session file separation. Sources: monocode:readme, monocode:operator.
  • Container [unsupported] The inspected provider launcher uses ordinary host processes without provisioning a per-session container. Sources: monocode:gap39-process.
  • Vm [unsupported] The inspected provider launcher uses ordinary host processes without provisioning a per-session vm. Sources: monocode:gap39-process.
  • Os sandbox [unsupported] No OS sandbox of its own (no seatbelt, bubblewrap or landlock); safety comes from provider permission modes. Sources: monocode:m-scan, monocode:m-harness.
  • Filesystem [unsupported] Agents run as the user; scope exclusion for orchestration is advisory file scopes. Sources: monocode:m-orch.
  • Process [partial] Provider processes run under lowered priority and the host stops process trees on cancel; no isolation. Sources: monocode:m-bg, monocode:m-remote.
  • Network [unsupported] No network boundary. Sources: monocode:m-scan.
  • Secrets [partial] Orchestration credentials sit in the lead environment; remote host credentials are device tokens with restricted file permissions. Sources: monocode:m-orch, monocode:m-remote.
  • Code separation [supported] Separate Git worktrees per task and isolated worker checkouts in orchestration. Sources: monocode:m-wt, monocode:m-orchstate.
  • Security boundary [unsupported] No security boundary is claimed; remote tokens grant control as the OS user. Sources: monocode:m-remote.

Sources: monocode:readme, monocode:operator, monocode:gap39-process, monocode:m-readme, monocode:m-wt, monocode:m-scan, monocode:m-harness, monocode:m-orch, monocode:m-bg, monocode:m-remote, monocode:m-orchstate

Sourced partial

Remote host restart retains transcripts and marks active turns interrupted; uncertain provider operations are not automatically replayed. Uncertain remote commands retain command IDs; Retry asks for the same receipt to avoid duplicated creation/prompts.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
12 atomic answers
  • Client disconnect [supported] Closing the desktop or losing the SSH tunnel does not stop host sessions. Sources: monocode:m-remote.
  • Worker crash [partial] Interrupted workers are recoverable from retained checkouts; nothing is replayed automatically after a host crash. Sources: monocode:m-remote, monocode:m-orch.
  • Service restart [partial] Remote host restart retains transcripts and marks active turns interrupted; uncertain provider operations are not automatically replayed. Sources: monocode:remote.
  • Expiry [unsupported] No sandbox expiry exists. Sources: monocode:m-remote.
  • Transcript reload [supported] Host snapshots reload the latest persisted transcript on reconnect. Sources: monocode:m-remote.
  • Process reconnect [supported] The desktop reattaches to host sessions over the tunnel. Sources: monocode:m-remote.
  • Task resume [supported] Resume continues interrupted orchestration workers. Sources: monocode:m-orch.
  • State reconstruction [supported] Run snapshots and host SQLite state rebuild sessions. Sources: monocode:m-orchstate, monocode:m-remote.
  • Context loss [partial] Turns running at host crash are marked interrupted, not resumed. Sources: monocode:m-remote.
  • Duplicate actions [supported] Uncertain remote commands retain command IDs; Retry asks for the same receipt to avoid duplicated creation/prompts. Sources: monocode:remote.
  • Manual repair [partial] Users restart the host service or press Reconnect; Update Host for older hosts. Sources: monocode:m-remote.
  • Multi day continuity [partial] Possible on a long-running user machine; replacement compute is a user task. Sources: monocode:m-remote.

Sources: monocode:remote, monocode:m-remote, monocode:m-orch, monocode:m-orchstate

Sourced partial

Matching host archives are checksum verified; missing release artifacts cause an explicit error instead of falling back to latest.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
10 atomic answers
  • Dependencies [unsupported] No dependency installation for worktrees. Sources: monocode:m-scan.
  • Caches [unsupported] No dependency or cache management. Sources: monocode:m-scan.
  • Snapshots [partial] Per-session file checkpoints exist; no environment snapshots. Sources: monocode:m-ckpt.
  • Services [unsupported] No service provisioning. Sources: monocode:m-scan.
  • Ports [unsupported] No workspace port allocation. Sources: monocode:m-scan.
  • Secrets [partial] Credentials are inherited from the user environment; no secret injection feature. Sources: monocode:m-orch.
  • Duplicate installs [unsupported] No duplicate-install handling. Sources: monocode:m-scan.
  • Collisions [unsupported] No collision handling. Sources: monocode:m-scan.
  • Remote setup [supported] Matching host archives are checksum verified; missing release artifacts cause an explicit error instead of falling back to latest. Sources: monocode:remote.
  • Automatic repair [unsupported] No automatic environment repair. Sources: monocode:m-scan.

Sources: monocode:remote, monocode:m-scan, monocode:m-ckpt, monocode:m-orch

Sourced partial

Run limits are limited to orchestration worker counts, usage-limit pauses and provider failure messages; no time, token or spend caps.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: time_limits (unsupported), turn_limits (unsupported), token_limits (unsupported), spend_limits (unsupported), timeouts (partial), retries (partial), enforcement (partial). See each atomic answer for the limit and its evidence.
8 atomic answers
  • Time limits [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no time limit for agent runs; searched terms: timeout, max duration. Sources: monocode:m-scan.
  • Turn limits [unsupported] No turn limit. Sources: monocode:m-scan.
  • Token limits [unsupported] No token limit; context usage is displayed only. Sources: monocode:m-ctx.
  • Spend limits [unsupported] No spend limit. Sources: monocode:m-scan.
  • Timeouts [partial] Host and mobile link have transport timeouts; agent turns have none. Sources: monocode:m-hostauth.
  • Retries [partial] Request-ID retries make mutations idempotent; no automatic agent retry. Sources: monocode:m-agentaccess.
  • Provider failures [supported] usageLimit detection pauses a session and resumes when the limit is due; errors display on tasks. Sources: monocode:m-usage, monocode:m-orchstate.
  • Enforcement [partial] Usage-limit pauses and maxWorkers are enforced; others are not. Sources: monocode:m-orch, monocode:m-usage.

Sources: monocode:m-scan, monocode:m-ctx, monocode:m-hostauth, monocode:m-agentaccess, monocode:m-usage, monocode:m-orchstate, monocode:m-orch

Sourced partial

The app keeps transcripts and task states and shows context usage and account usage windows; it has no trace store, export or per-task statistics.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: logs (partial), traces (unsupported), usage_export (unsupported), task_stats (unsupported), agent_stats (partial), project_stats (unsupported), time_stats (unsupported), performance_method (unsupported), responsiveness (unsupported). See each atomic answer for the limit and its evidence.
13 atomic answers
  • Logs [partial] Host logs live in ~/.monocode-host; transcripts persist per session. Sources: monocode:m-remote.
  • Traces [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no trace store; searched terms: trace, opentelemetry, span. Sources: monocode:m-scan.
  • Failure reasons [supported] Tasks, dispatches and runs carry error text and pause reasons. Sources: monocode:m-orchstate.
  • Usage export [unsupported] No usage export. Sources: monocode:m-scan.
  • Task stats [unsupported] No per-task statistics. Sources: monocode:m-scan.
  • Agent stats [partial] Account usage and headroom per provider account. Sources: monocode:m-usage.
  • Project stats [unsupported] No project statistics. Sources: monocode:m-scan.
  • Time stats [unsupported] No time statistics. Sources: monocode:m-scan.
  • Failure status [supported] failed, blocked, interrupted and start_unknown states. Sources: monocode:m-orchstate.
  • Approval status [supported] Pending approvals show in toasts, Dock badge and needsInput. Sources: monocode:m-notify, monocode:m-orch.
  • Reconnect consistency [supported] Remote views load the latest host snapshot and retained command receipts. Sources: monocode:m-remote.
  • Performance method [unsupported] No in-app performance measurement method; ADEMark is the catalog source. Sources: monocode:m-scan.
  • Responsiveness [unsupported] No responsiveness figures in the repository. Sources: monocode:m-scan.

Sources: monocode:m-remote, monocode:m-scan, monocode:m-orchstate, monocode:m-usage, monocode:m-notify, monocode:m-orch

Sourced partial

No cost tracking: the app shows context tokens and account usage headroom but no per-task spend.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: task_cost (unsupported), session_cost (unsupported), child_cost (unsupported), epic_cost (unsupported), harness_aggregation (unsupported), billed_vs_estimated (unsupported), provider_reconciliation (unsupported), compute_cost (unsupported), refresh_delay (partial), alerts (partial), export (unsupported), drilldown (unsupported). See each atomic answer for the limit and its evidence.
14 atomic answers
  • Task cost [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no per-task cost; searched terms: costUsd, total_cost, billing. Sources: monocode:m-scan.
  • Session cost [unsupported] No session cost. Sources: monocode:m-scan.
  • Child cost [unsupported] No child cost. Sources: monocode:m-scan.
  • Epic cost [unsupported] No epic cost. Sources: monocode:m-scan.
  • Harness aggregation [unsupported] No cross-harness aggregation. Sources: monocode:m-scan.
  • Billed vs estimated [unsupported] No billed or estimated amounts. Sources: monocode:m-scan.
  • Tokens [supported] Context tokens used versus the window per session. Sources: monocode:m-ctx.
  • Subscription allowance [supported] Provider account usage windows and remaining headroom are shown. Sources: monocode:m-usage.
  • Provider reconciliation [unsupported] No reconciliation against provider invoices. Sources: monocode:m-scan.
  • Compute cost [unsupported] No compute charges. Sources: monocode:m-scan.
  • Refresh delay [partial] Usage readers poll on a timer; the interval was not documented. Sources: monocode:m-usage.
  • Alerts [partial] Usage-limit notices and resume; no budget alerts. Sources: monocode:m-usage.
  • Export [unsupported] No export. Sources: monocode:m-scan.
  • Drilldown [unsupported] No cost drill-down. Sources: monocode:m-scan.

Sources: monocode:m-scan, monocode:m-ctx, monocode:m-usage

Sourced partial

Resource awareness exists for the interactive UI: priority lowering, a bounded indexing semaphore, resource-pressure notices and orchestration worker caps.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: cpu_ram (partial), backpressure (partial), host_awareness (partial), check_reuse (unsupported), check_deduplication (unsupported), bounded_tests (unsupported), fairness (unsupported), shared_limits (unsupported). See each atomic answer for the limit and its evidence.
12 atomic answers
  • Concurrency [supported] maxWorkers 1-4 per orchestration run. Sources: monocode:m-orch.
  • Queues [supported] Queued tasks wait on dependencies, scopes and worker slots; messages queue per session. Sources: monocode:m-orch.
  • Cpu ram [partial] Child priority is lowered and pressure is sampled; no CPU or RAM quotas. Sources: monocode:m-bg, monocode:m-pressure.
  • Backpressure [partial] Resource-pressure notice with hysteresis informs the user; it does not throttle agents. Sources: monocode:m-pressure.
  • Host awareness [partial] Samples the local host CPU, memory pressure and stall share. Sources: monocode:m-pressure.
  • Check reuse [unsupported] No check reuse. Sources: monocode:m-scan.
  • Check deduplication [unsupported] No check deduplication. Sources: monocode:m-scan.
  • Bounded tests [unsupported] No test running of its own. Sources: monocode:m-scan.
  • Cancellation [supported] Tasks can be cancelled and runs stopped. Sources: monocode:m-orch.
  • Fairness [unsupported] No fairness policy beyond queue order. Sources: monocode:m-orch.
  • Recovery [supported] Resume continues interrupted workers. Sources: monocode:m-orch.
  • Shared limits [unsupported] Limits are per run, not shared between runs. Sources: monocode:m-orch.

Sources: monocode:m-orch, monocode:m-bg, monocode:m-pressure, monocode:m-scan

Human collaboration and control

Sourced partial

Several paired native clients can access the same host sessions and send turn commands. Shared access is through revocable device credentials under the host OS user, without per-person role or ordering guarantees.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
11 atomic answers
  • Visibility [unsupported] Single-user app; a phone and extra desktops pair to the same owner. Sources: monocode:m-mobile, monocode:m-scan.
  • Discussion [unsupported] No shared discussion. Sources: monocode:m-scan.
  • Comments [partial] Diff comments and tracker comments, not team comments on agent work. Sources: monocode:m-diffcomment, monocode:m-jira.
  • Presence [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no presence; searched terms: presence, crdt, yjs. Sources: monocode:m-scan.
  • Coprompting [unsupported] Each remote device credential controls the host as the OS user; the docs describe no shared co-prompting. Sources: monocode:m-remote.
  • Ordering [partial] The host serializes commands with receipts; this is device ordering, not multi-user. Sources: monocode:m-remote.
  • Conflicts [partial] The docs warn not to edit the same conversation in two apps at once. Sources: monocode:m-remote.
  • Attribution [unsupported] Device credentials are named for the computer, not for people. Sources: monocode:m-remote.
  • Permissions [partial] A device token grants host-user workspace/provider control; this is not a per-user role system. Sources: monocode:remote, monocode:gap39-access.
  • Plan restrictions [unsupported] No plans exist. Sources: monocode:m-scan.
  • Owner online [supported] The host must stay awake and the desktop may disconnect. Sources: monocode:m-remote.

Sources: monocode:gap39-access, monocode:remote, monocode:m-remote, monocode:m-scan, monocode:m-mobile, monocode:m-diffcomment, monocode:m-jira

Sourced partial

The scoped remote host authenticates revocable device bearer tokens and uses the host OS user privileges. It has no organization, project or task roles and no SAML/OIDC SSO implementation.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
9 atomic answers
  • Organization roles [unsupported] The scoped authentication/dispatch code uses device credentials with host-user access, without organization roles. Sources: monocode:gap39-access.
  • Project roles [unsupported] The scoped authentication/dispatch code uses device credentials with host-user access, without project roles. Sources: monocode:gap39-access.
  • Task roles [unsupported] The scoped authentication/dispatch code uses device credentials with host-user access, without task roles. Sources: monocode:gap39-access.
  • Membership [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no membership; searched terms: organization, member, rbac. Sources: monocode:m-scan.
  • Sso [unsupported] The scoped authentication/dispatch code uses device credentials with host-user access, without sso. Sources: monocode:gap39-access.
  • Provisioning [unsupported] No provisioning. Sources: monocode:m-scan.
  • Unauthorized access [supported] Remote host rejects invalid or revoked device bearer tokens. Sources: monocode:m-hostauth.
  • Revocation [supported] Per-device revoke via CLI or Settings. Sources: monocode:m-remote, monocode:m-hostauth.
  • Plan scope [unsupported] No plans. Sources: monocode:m-scan.

Sources: monocode:gap39-access, monocode:m-scan, monocode:m-hostauth, monocode:m-remote

Sourced partial

Provider permissions remain CLI-specific; native Supervised mode does not guarantee approval on every edit. Remote credentials can be explicitly revoked; merely removing a saved desktop connection does not revoke them. A paired mobile device has workspace access; display project selection is not an authorization boundary.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
14 atomic answers
  • Command [partial] Provider permissions remain CLI-specific; native Supervised mode does not guarantee approval on every edit. Sources: monocode:parity.
  • Tool [supported] Tool approvals surface as toasts and needsInput; permission mode chosen per session. Sources: monocode:m-notify, monocode:m-harness.
  • Network [unsupported] No product network approvals. Sources: monocode:m-scan.
  • Secret [unsupported] No secret approvals. Sources: monocode:m-scan.
  • Delivery [partial] PR creation is a user action; no delivery approval gate. Sources: monocode:m-pr.
  • Approver identity [unsupported] No approver identity. Sources: monocode:m-scan.
  • Lifetime [partial] Approvals are per request (provider-dependent). Sources: monocode:m-orch.
  • Allow [supported] Approve a request in the UI or via the lead respond action. Sources: monocode:m-orch.
  • Deny [supported] Decline a request via the same flow. Sources: monocode:m-orch.
  • Revoke [partial] Remote credentials can be explicitly revoked; merely removing a saved desktop connection does not revoke them. Sources: monocode:remote.
  • Tunnels [supported] Remote SSH forward closes when the desktop quits; device credentials persist until revoked. Sources: monocode:m-remote.
  • Defaults [partial] A paired mobile device has workspace access; display project selection is not an authorization boundary. Sources: monocode:mobile.
  • Safer modes [supported] Supervised default mode plus auto-accept-edits, auto and full-access modes. Sources: monocode:m-harness.
  • Enforcement [partial] Enforcement depends on the provider CLI; the docs say Supervised does not guarantee approval for every edit. Sources: monocode:m-harness.

Sources: monocode:parity, monocode:remote, monocode:mobile, monocode:m-notify, monocode:m-harness, monocode:m-scan, monocode:m-pr, monocode:m-orch, monocode:m-remote

Sourced partial

Remote host stores transcripts/snapshots and preserves pending request identity across desktop restarts.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
11 atomic answers
  • Actions [partial] Transcripts record agent actions per session; no multi-user attribution. Sources: monocode:m-remote.
  • Approvals [partial] Approval decisions appear in transcripts. Sources: monocode:m-orch.
  • Edits [supported] Checkpoints record exact file edits per session. Sources: monocode:m-ckpt.
  • Discussion [unsupported] No team discussion. Sources: monocode:m-scan.
  • Decisions [partial] Lead decisions on worker requests appear in the run. Sources: monocode:m-orch.
  • Cross user persistence [unsupported] No multi-user history. Sources: monocode:m-scan.
  • Cross session persistence [supported] Remote host stores transcripts/snapshots and preserves pending request identity across desktop restarts. Sources: monocode:remote.
  • Export [unsupported] No export in the inspected release (native docs list explicit import/export as remaining work). Sources: monocode:m-scan.
  • Mutability [supported] History is local SQLite the user can alter. Sources: monocode:m-remote.
  • Retention [unsupported] No retention policy. Sources: monocode:m-scan.
  • Integrity [unsupported] No integrity protection beyond file permissions. Sources: monocode:m-remote.

Sources: monocode:remote, monocode:m-remote, monocode:m-orch, monocode:m-ckpt, monocode:m-scan

Sourced partial

Review has a Changes panel, working-tree and session diffs, diff comments and a checkpoint undo, but no guided review queue.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: pending_reviews (partial), request_changes (partial), shipping_guidance (partial), effort (unsupported), missed_evidence (unsupported), keyboard (partial), narrow_screen (partial), context_switching (unsupported), roles (unsupported). See each atomic answer for the limit and its evidence.
13 atomic answers
  • Pending reviews [partial] Orchestration review action marks completed tasks accepted; no review inbox. Sources: monocode:m-orch.
  • Change understanding [supported] Session changes diff and working-tree diff views. Sources: monocode:m-ckpt, monocode:m-diffcomment.
  • Evidence navigation [supported] Per-file diffs with navigation and a Git history graph. Sources: monocode:m-ckpt.
  • Comments [supported] Diff comments on lines go back to the agent. Sources: monocode:m-diffcomment.
  • Request changes [partial] Message a worker or add diff comments; no formal request-changes state. Sources: monocode:m-orch, monocode:m-diffcomment.
  • Shipping guidance [partial] PR creation action in Git views. Sources: monocode:m-pr.
  • Effort [unsupported] No review effort model. Sources: monocode:m-scan.
  • Missed evidence [unsupported] No missed-evidence detection. Sources: monocode:m-scan.
  • Keyboard [partial] The diff view navigates changed files or hunks with ArrowUp and ArrowDown (UnifiedDiffView L423-L430); no documented review shortcut set. Sources: monocode:m-diffkeys.
  • Narrow screen [partial] The phone app shows changes and sessions (ChangesView). Sources: monocode:m-mobile.
  • Context switching [unsupported] No review queue. Sources: monocode:m-scan.
  • Roles [unsupported] No reviewer roles. Sources: monocode:m-scan.
  • Retained context [supported] Session transcripts and checkpoints persist. Sources: monocode:m-ckpt.

Sources: monocode:m-orch, monocode:m-ckpt, monocode:m-diffcomment, monocode:m-pr, monocode:m-scan, monocode:m-diffkeys, monocode:m-mobile

Sourced partial

Takeover is limited to the same owner on another paired device; no second-person takeover exists.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: ongoing_takeover (partial), same_task (partial), decisions (partial), artifacts (partial), permissions (partial), ownership (unsupported), attribution (unsupported), context_loss (partial). See each atomic answer for the limit and its evidence.
12 atomic answers
  • Ongoing takeover [partial] Another desktop of the same user can connect to a host with its own device credential. Sources: monocode:m-remote.
  • Same task [partial] Host-owned sessions are shared across paired devices. Sources: monocode:m-remote.
  • Session history [supported] Host persists transcripts. Sources: monocode:m-remote.
  • Decisions [partial] Decisions are in the transcript. Sources: monocode:m-remote.
  • Artifacts [partial] Attachments are copied to the host private data directory. Sources: monocode:m-remote.
  • Permissions [partial] Tokens grant control as the OS user; no per-person permissions. Sources: monocode:m-remote.
  • Runtime context [supported] Runtime context lives on the host, not the desktop. Sources: monocode:m-remote.
  • Owner disconnect [supported] Host sessions continue after the desktop disconnects. Sources: monocode:m-remote.
  • Ownership [unsupported] No ownership transfer feature. Sources: monocode:m-scan.
  • Attribution [unsupported] No person attribution. Sources: monocode:m-remote.
  • Context loss [partial] Local-only features (terminals, skills, operator) are not available remotely. Sources: monocode:m-remote.
  • Harness transfer [supported] Handoff and second-opinion cards move work between harnesses. Sources: monocode:m-handoff.

Sources: monocode:m-remote, monocode:m-scan, monocode:m-handoff

Verification and delivery

Sourced partial

Desktop and remote Changes/Git views display file diffs and history. Remote file/image attachments persist in host private data with 20 MiB per-file limit.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
13 atomic answers
  • Diffs [supported] Desktop and remote Changes/Git views display file diffs and history. Sources: monocode:readme, monocode:remote.
  • Documents [supported] Plan cards and HTML or Markdown artifacts and notes. Sources: monocode:m-remote.
  • Screenshots [supported] Remote file/image attachments persist in host private data with 20 MiB per-file limit. Sources: monocode:remote.
  • Recordings [unsupported] Bounded inspection of v0.16.0 (src, src-tauri/src, host, crates, mobile/src, docs) finds no recording; searched terms: recording, screen capture. Sources: monocode:m-scan.
  • Previews [partial] HTML artifacts render in an artifact panel. Sources: monocode:m-scan.
  • Test outputs [partial] Test output appears in transcripts and terminals only. Sources: monocode:m-scan.
  • Reviewer outputs [partial] Reviewer worker results are retained in the run. Sources: monocode:m-orchstate.
  • Persistence [supported] Artifacts and checkpoints persist in the local store. Sources: monocode:m-ckpt.
  • Child findings [supported] Worker results stay readable after completion. Sources: monocode:m-orchstate.
  • Prompt leakage [unsupported] No artifact export path in the inspected release. Sources: monocode:m-scan.

Sources: monocode:readme, monocode:remote, monocode:m-remote, monocode:m-scan, monocode:m-orchstate, monocode:m-ckpt

Sourced partial

No product-enforced test, lint or CI gate; CI repair starts a session from failing checks and the lead is told to review and validate.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: tests (unsupported), lint (unsupported), types (unsupported), ci (partial), independent_review (partial), spec_checks (unsupported), required_checks (unsupported), failure_blocking (partial), requirement_conflicts (unsupported), configured_policy (unsupported), enforced_policy (partial). See each atomic answer for the limit and its evidence.
11 atomic answers
  • Tests [unsupported] The app runs no tests itself; agents do. Sources: monocode:m-scan.
  • Lint [unsupported] No lint gate. Sources: monocode:m-scan.
  • Types [unsupported] No type gate. Sources: monocode:m-scan.
  • Ci [partial] GitHub check results appear in the inbox and CI repair starts a repair session. Sources: monocode:m-inbox.
  • Independent review [partial] A lead reviews each worker and must accept it before dependents run. Sources: monocode:m-orch.
  • Spec checks [unsupported] No spec checks. Sources: monocode:m-scan.
  • Required checks [unsupported] No required checks. Sources: monocode:m-scan.
  • Failure blocking [partial] A task not accepted blocks dependents; no check failure blocks delivery. Sources: monocode:m-orch.
  • Requirement conflicts [unsupported] No requirement conflict checks. Sources: monocode:m-scan.
  • Configured policy [unsupported] No configurable policy. Sources: monocode:m-scan.
  • Enforced policy [partial] Acceptance gating within orchestration is enforced. Sources: monocode:m-orch.

Sources: monocode:m-scan, monocode:m-inbox, monocode:m-orch

Sourced partial

Remote Git views stage/discard files, commit and push through the host. Remote PR creation uses gh on the host with commit list/diff summary; generated commit messages are not yet available remotely.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
9 atomic answers
  • Branches [supported] Branch picker, create and switch dialogs. Sources: monocode:m-wt.
  • Worktrees [supported] Create, rename and remove worktrees, orchestration worktrees and per-task choice. Sources: monocode:m-wt, monocode:m-agentaccess.
  • Commits [supported] Remote Git views stage/discard files, commit and push through the host. Sources: monocode:remote.
  • Pull requests [partial] Remote PR creation uses gh on the host with commit list/diff summary; generated commit messages are not yet available remotely. Sources: monocode:remote.
  • Comments [partial] Diff comments to the agent and PR comments in the inbox. Sources: monocode:m-diffcomment, monocode:m-inbox.
  • Ci response [supported] CI repair sessions start from failing checks. Sources: monocode:m-inbox.
  • Rebase [unsupported] No rebase operation in the source-control UI. Sources: monocode:m-scan.
  • Conflicts [partial] Worker integration reports applied and already-applied files; no merge-conflict resolution UI. Sources: monocode:m-ckpt.
  • Product state [supported] Sessions link to worktrees, branches and linked pull requests. Sources: monocode:m-wt, monocode:m-harness.

Sources: monocode:remote, monocode:m-wt, monocode:m-agentaccess, monocode:m-diffcomment, monocode:m-inbox, monocode:m-scan, monocode:m-ckpt, monocode:m-harness

Sourced partial

No merge, release or deploy authority features; PR creation uses the user gh login.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: approve (partial), merge (unsupported), release (unsupported), deploy (unsupported), exact_revision (unsupported), authority_enforcement (unsupported). See each atomic answer for the limit and its evidence.
6 atomic answers
  • Approve [partial] Orchestration review accepts a worker task; no merge approval. Sources: monocode:m-orch.
  • Merge [unsupported] No merge button or operation found. Sources: monocode:m-scan.
  • Release [unsupported] No release feature. Sources: monocode:m-scan.
  • Deploy [unsupported] No deploy feature. Sources: monocode:m-scan.
  • Exact revision [unsupported] No revision-bound approval. Sources: monocode:m-scan.
  • Authority enforcement [unsupported] No authority enforcement. Sources: monocode:m-scan.

Sources: monocode:m-orch, monocode:m-scan

Sourced partial

Sessions link to pull requests and checkpoints allow undo; no delivery or deployment evidence chain.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: commit_links (partial), build_links (unsupported), deployment_links (unsupported), delivery_status (partial), retained_evidence (partial), revert (partial), stale_approval_invalidation (unsupported). See each atomic answer for the limit and its evidence.
9 atomic answers
  • Delivery status [partial] PR checks status in the inbox. Sources: monocode:m-inbox.
  • Retained evidence [partial] Checkpoint diffs and transcripts. Sources: monocode:m-ckpt.
  • Rollback [supported] Checkpoint undo restores per-file state. Sources: monocode:m-ckpt.
  • Revert [partial] Checkpoint undo reverts agent edits; no commit revert operation. Sources: monocode:m-ckpt.
  • Stale approval invalidation [unsupported] No approvals bound to revisions to invalidate. Sources: monocode:m-scan.

Sources: monocode:m-wt, monocode:m-pr, monocode:m-harness, monocode:m-scan, monocode:m-inbox, monocode:m-ckpt

Sourced partial

No batch review or delivery queue; review is per session or per orchestration task.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: review_queue (unsupported), summaries (partial), grouping (partial), risk_size_filters (unsupported), findings (partial), artifacts (partial), request_changes (partial), exact_revision_approval (unsupported), dependency_queues (partial), next_actions (unsupported), stale_approval_invalidation (unsupported), check_deduplication (unsupported). See each atomic answer for the limit and its evidence.
12 atomic answers
  • Review queue [unsupported] No queue of completed tasks. Sources: monocode:m-scan.
  • Summaries [partial] Orchestration summaries of runs. Sources: monocode:m-orchstate.
  • Grouping [partial] Sessions group in folders and orchestration runs. Sources: monocode:m-agentaccess.
  • Risk size filters [unsupported] No risk or size filters. Sources: monocode:m-scan.
  • Findings [partial] Worker results are retained. Sources: monocode:m-orchstate.
  • Artifacts [partial] Artifacts per session. Sources: monocode:m-ckpt.
  • Request changes [partial] Message a worker for fixes. Sources: monocode:m-orch.
  • Exact revision approval [unsupported] No exact-revision approval. Sources: monocode:m-scan.
  • Dependency queues [partial] Dependency ordering for workers, not for merges. Sources: monocode:m-orch.
  • Next actions [unsupported] No next-action guidance. Sources: monocode:m-scan.
  • Stale approval invalidation [unsupported] No approvals to invalidate. Sources: monocode:m-scan.
  • Check deduplication [unsupported] No check deduplication. Sources: monocode:m-scan.

Sources: monocode:m-scan, monocode:m-orchstate, monocode:m-agentaccess, monocode:m-ckpt, monocode:m-orch

Ownership, privacy and economics

Sourced partial

MonoCode source is MIT licensed; provider trademarks and notices remain separate.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
6 atomic answers
  • Client license [supported] MonoCode source is MIT licensed; provider trademarks and notices remain separate. Sources: monocode:license.
  • Server license [supported] Remote host and desktop are in the same repository under the MIT licence. Sources: monocode:license, monocode:m-remote.
  • Hosted extensions [unknown] Hosted extensions of the website or download site: a business or hosted-service fact the public repository cannot answer.
  • Source visibility [supported] Full source of desktop, host, native crates and the phone app is public. Sources: monocode:license, monocode:m-tauri.
  • Source revision [supported] Pinned to v0.16.0, commit 7508feaee84d; native preview releases are separate tags. Sources: monocode:m-tauri.
  • Hosted parity [unknown] Parity between the repository and the download host: a business or hosted-service fact the public repository cannot answer.

Sources: monocode:license, monocode:m-remote, monocode:m-tauri

Sourced partial

Desktop and remote host can run from repository source on user-controlled machines. Installed agent providers need their own login; remote hosts reuse the hosts OS-user credentials.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
8 atomic answers
  • Self hosting [supported] Desktop and remote host can run from repository source on user-controlled machines. Sources: monocode:readme, monocode:remote.
  • Vendor dependencies [supported] Installed agent providers need their own login; remote hosts reuse the hosts OS-user credentials. Sources: monocode:providers, monocode:remote.
  • Export [unsupported] No export command; the native docs list explicit import and export as remaining work. Sources: monocode:m-scan.
  • Import [unsupported] No import command for sessions. Sources: monocode:m-scan.
  • Formats [partial] Local SQLite session store and notes; remote host data in ~/.monocode-host. Sources: monocode:m-remote.
  • Cancellation [supported] No account or subscription exists. Sources: monocode:m-readme.
  • Account independence [supported] No MonoCode account is required. Sources: monocode:m-readme.
  • History portability [partial] Data stays in local files that can be copied; no documented migration. Sources: monocode:m-remote.

Sources: monocode:readme, monocode:remote, monocode:providers, monocode:m-scan, monocode:m-remote, monocode:m-readme

Sourced partial

Bounded source inspection found no MonoCode product analytics emitter or telemetry opt-out control in the public app dependencies and implementation. Underlying agent-provider data handling is separate and remains unestablished here.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
15 atomic answers
  • Code data [supported] Code stays on the local machine or the user host. Sources: monocode:m-remote.
  • Prompts [partial] Prompts go to the chosen agent CLI vendor; no MonoCode service receives them. Sources: monocode:m-readme.
  • Credentials [partial] Jira and remote tokens are stored locally with restricted file permissions, not in the OS keychain; provider logins stay with the CLIs. Sources: monocode:m-jira, monocode:m-remote.
  • Logs [supported] Logs and transcripts stay local. Sources: monocode:m-remote.
  • Artifacts [supported] Artifacts stay local. Sources: monocode:m-remote.
  • Retention [partial] No retention limit; data stays until the user deletes it. Sources: monocode:m-remote.
  • Deletion [partial] Sessions can be deleted permanently; Jira disconnect clears cached content. Sources: monocode:m-agentaccess, monocode:m-jira.
  • Training [unknown] Vendor training use is governed by each model provider, not by MonoCode: a business or hosted-service fact the public repository cannot answer.
  • Residency [partial] Data stays on the machines the user chooses; provider residency is outside the repository. Sources: monocode:m-remote.
  • Subprocessors [unknown] Subprocessor list: a business or hosted-service fact the public repository cannot answer.
  • Telemetry disclosure [unsupported] No telemetry is disclosed and no telemetry or analytics client appears in the source. Sources: monocode:m-scan.
  • Telemetry defaults [supported] No product analytics emitter was found in the inspected public application components. Sources: monocode:gap39-privacy-code.
  • Telemetry controls [unsupported] No product telemetry opt-out setting was found in the inspected source. Sources: monocode:gap39-privacy-code.
  • Provider separation [supported] MonoCode does not relay model traffic; each provider CLI sends its own. Sources: monocode:m-readme.

Sources: monocode:gap39-privacy-code, monocode:m-remote, monocode:m-readme, monocode:m-jira, monocode:m-agentaccess, monocode:m-scan

Sourced partial

MonoCode is MIT open source and free to download, with no paid plan found; it runs agents on your own existing agent subscriptions and says it does not sell tokens.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: First-party pricing sources read 2026-11-10 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-10 (12 days old)
Agent cross-check
Not separately cross-checked
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
12 atomic answers
  • Currency [unsupported] No price is published or coded. Sources: monocode:m-scan, monocode:license-nov10.
  • Interval [unsupported] No billing interval. Sources: monocode:m-scan.
  • Seats [unsupported] No seats. Sources: monocode:m-scan.
  • Seat minimum [unsupported] No seat minimum. Sources: monocode:m-scan.
  • Workspace fees [unsupported] No workspace fees. Sources: monocode:m-scan.
  • Included usage [unsupported] No included usage allowance because nothing is sold. Sources: monocode:m-readme.
  • Credits [unsupported] The README says MonoCode does not sell tokens. No credits are mentioned. Sources: monocode:readme-nov10.
  • Trial [unsupported] No trial exists; the app is free. Sources: monocode:m-scan.
  • Overages [unsupported] No overages. Sources: monocode:m-scan.
  • Taxes [unknown] Tax treatment of any future paid plan: a business or hosted-service fact the public repository cannot answer.
  • Model cost [supported] MonoCode uses your existing agent subscriptions and does not sell tokens, so those providers bill for model usage. Sources: monocode:readme-nov10.
  • Compute cost [supported] Compute is the user machine or host at the user cost. Sources: monocode:m-remote.

Sources: monocode:license-nov10, monocode:readme-nov10, monocode:m-readme, monocode:m-providers, monocode:m-scan, monocode:m-remote

Sourced partial

ADE cost is zero for one, two or five developers; model costs belong to their agent subscriptions.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: task_assumptions (unknown), concurrency (unknown), tokens (unknown), variable_cost (unknown), unknown_cost (unknown). See each atomic answer for the limit and its evidence.
11 atomic answers
  • One person [supported] Zero ADE cost; agent subscriptions separate. Sources: monocode:m-readme.
  • Two people [supported] Zero ADE cost per person; no collaboration plan. Sources: monocode:m-readme, monocode:m-scan.
  • Five people [supported] Zero ADE cost per person. Sources: monocode:m-readme, monocode:m-scan.
  • Task assumptions [unknown] No ADE price exists to model; workloads depend on the chosen agent subscriptions.
  • Concurrency [unknown] Concurrency has no ADE price; limits come from agent subscriptions.
  • Tokens [unknown] Tokens are billed by agent vendors, not MonoCode.
  • Compute hours [supported] Compute hours run on the user hardware, free to the ADE. Sources: monocode:m-remote.
  • Fixed cost [supported] Fixed ADE cost is zero. Sources: monocode:m-readme.
  • Variable cost [unknown] Variable cost is agent vendor billing, not known here.
  • Included cost [supported] Nothing is bundled. Sources: monocode:m-readme.
  • Unknown cost [unknown] Agent subscription costs are unknown for this record.

Sources: monocode:m-readme, monocode:m-scan, monocode:m-remote

Sourced partial

The React/Tauri app is production; Rust/GPUI remains experimental preview and uses the same saved database. README links public issues for bug reports without a documented response commitment. Native preview 0.16.0-preview.14 release notes describe current terminal/Git/sign-in changes.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-08 (14 days old)
Agent cross-check
Not separately cross-checked
  • Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
8 atomic answers
  • Release stage [supported] The React/Tauri app is production; Rust/GPUI remains experimental preview and uses the same saved database. Sources: monocode:readme, monocode:parity.
  • Access restrictions [supported] MIT licence with no sign-in; the Rust GPUI preview and remote host are labelled experimental. Sources: monocode:license, monocode:m-remote.
  • Support [partial] README links public issues for bug reports without a documented response commitment. Sources: monocode:readme.
  • Response commitments [unsupported] No response commitments in CONTRIBUTING or SECURITY docs inspected. Sources: monocode:m-scan.
  • Release activity [supported] Native preview 0.16.0-preview.14 release notes describe current terminal/Git/sign-in changes. Sources: monocode:release-notes.
  • Status history [unsupported] No status history in the repository. Sources: monocode:m-scan.
  • Deprecation [unsupported] No deprecation policy. Sources: monocode:m-scan.
  • Export options [unsupported] No export options. Sources: monocode:m-scan.

Sources: monocode:readme, monocode:parity, monocode:release-notes, monocode:license, monocode:m-remote, monocode:m-scan

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Sourced partial

MonoCode is a free MIT-licensed desktop download for macOS, Linux and Windows; no paid plan is shown. Agent usage is billed by the user's own agent subscriptions.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-10 (12 days old)
Agent cross-check
Not separately cross-checked
  • Underlying agent plan limits were not checked. No installed-product test was run.
10 atomic answers

Sources: monocode:b4-license, monocode:b4-install, monocode:m-scan, monocode:m-remote, monocode:m-readme, monocode:m-mobile

Sourced partial

No pricing exists, so no transparency classification applies.

Scope
Surfaces: Production MonoCode React/Tauri desktop, Experimental MonoCode Rust/GPUI preview, Experimental MonoCode remote host, Source-built Expo mobile development client · Version: Repository 164957961717a02ffff91a6c25e1f0ae8007a40e; first-party source pass 2026-11-08. React/Tauri is production; Rust/GPUI is experimental preview. Remote hosts and source-built mobile have distinct restrictions. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • Partial: units (unsupported), included_limits (unsupported), overages (unsupported), compute_markup (unsupported), model_markup (unsupported), minimum_commitment (unsupported), cancellation (unsupported), sales_only_unknowns (unknown), transparency_classification (unknown). See each atomic answer for the limit and its evidence.
9 atomic answers
  • Units [unsupported] No pricing units. Sources: monocode:m-scan.
  • Included limits [unsupported] No included limits. Sources: monocode:m-scan.
  • Overages [unsupported] No overage rates. Sources: monocode:m-scan.
  • Compute markup [unsupported] No compute sold. Sources: monocode:m-scan.
  • Model markup [unsupported] README states tokens are not sold. Sources: monocode:m-readme.
  • Minimum commitment [unsupported] No commitment. Sources: monocode:m-scan.
  • Cancellation [unsupported] No subscription to cancel. Sources: monocode:m-scan.
  • Sales only unknowns [unknown] Whether a sales-only offer exists on the website is not answerable from source.
  • Transparency classification [unknown] Classification needs a priced offering; none is published.

Sources: monocode:m-scan, monocode:m-readme

Sources

monocode:readme

MonoCode README.md

Desktop installers cover macOS, Linux and Windows. MonoCode uses existing coding-agent subscriptions; parallel tabs/worktrees, editing, diff review and /operator are documented. Production is React/Tauri, preview is Rust/GPUI.

Kind
documented
Locator
Install; Get started; Native preview
Source date
Not stated
Retrieved
2026-11-08
monocode:operator

MonoCode docs/agent-access.md

Opt-in /operator gives that active local thread a scoped app CLI. It starts, reads, sends, stops and organizes sessions/worktrees and notes with explicit IDs; uncertain writes retry with identical request IDs.

Kind
documented
Locator
Enable access; CLI actions
Source date
Not stated
Retrieved
2026-11-08
monocode:remote

MonoCode docs/remote-access.md

Remote Linux/macOS/Windows hosts run provider processes independently of the connecting desktop. SSH setup installs a host service and per-device credentials; remote files/Git/PRs work but operator, terminals and most local-only tools are unavailable.

Kind
documented
Locator
SSH setup; Sessions; Manage host; Scope
Source date
Not stated
Retrieved
2026-11-08
monocode:mobile

MonoCode mobile/README.md

The source-built Expo app uses QUIC/mTLS to show desktop projects, send prompts/start/stop turns and view changes. iOS/Android builds require native toolchains; approvals/questions remain on desktop, which must stay awake.

Kind
documented
Locator
Run locally; Pair; Account selection
Source date
Not stated
Retrieved
2026-11-08
monocode:gap39-access

MonoCode host RPC server

The host exposes authenticated RPC using revocable device bearer credentials. All paired devices address the same stored sessions and can issue session/turn commands, without per-user, organization, project or task roles. The server serves RPC, not a browser UI; no SAML/OIDC login is implemented.

Kind
source-inspected
Locator
Request dispatch, lines 180-265; sessions and turns RPC methods
Source date
Not stated
Retrieved
2026-11-13
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
host/server.ts
monocode:m-notify

src/features/notifications/model/dockBadge.ts

Pending approval or question count is pushed to the macOS Dock badge; useInputNotifications announces sessions that need input, and approvalToast builds approval and question notices.

Kind
source-inspected
Locator
syncDockBadge (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/notifications/model/dockBadge.ts
monocode:m-scan

MonoCode repository (bounded inspection)

Searched src, src-tauri/src, host, crates, mobile/src and docs at v0.16.0 for: vscode extension/jetbrains/.vsix, sso/saml/oidc/scim, rbac/organization roles, presence/crdt/yjs, soc 2/iso 27001, stripe/subscription/checkout/billing, openapi/swagger/webhook, docker/bubblewrap/landlock/seatbelt, kanban/epic/milestone, acceptance criteria, living spec/requirements, embedding/vector/rag, costUsd/total_cost, telemetry/posthog/sentry/analytics. No product implementation exists; hits were unrelated UI or test code. No outbound telemetry host appears in the source.

Kind
source-inspected
Locator
whole-tree search (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
.
monocode:providers

MonoCode docs/providers.md

Installed Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi and other named CLIs use their existing native logins. Missing providers are disabled individually with installation hints.

Kind
documented
Locator
Provider setup
Source date
Not stated
Retrieved
2026-11-08
monocode:parity

MonoCode docs/native/parity.md

Preview is experimental, and source presence does not establish parity with production. Native automations/Monos and remote features retain documented verification gaps.

Kind
documented
Locator
Native preview limitations
Source date
Not stated
Retrieved
2026-11-08
monocode:agy-release-1

MonoCode Antigravity support at v0.16.0

MonoCode v0.16.0 documents running installed Antigravity on macOS and Linux and selecting it to send a message after sign-in.

Kind
documented
Locator
docs/providers.md lines 1-23, v0.16.0, commit 7508feaee84db638fb7a7c146d9f15de5d0f3689
Source date
2026-10-19
Retrieved
2026-11-10
monocode:agy-release-2

MonoCode Antigravity support at v0.16.0

MonoCode v0.16.0 documents running installed Antigravity on macOS and Linux and selecting it to send a message after sign-in.

Kind
documented
Locator
docs/remote-access.md lines 13-20, v0.16.0, commit 7508feaee84db638fb7a7c146d9f15de5d0f3689
Source date
2026-10-19
Retrieved
2026-11-10
monocode:m-agentaccess

docs/agent-access.md

The /operator command enables a local app CLI with models.list, sessions.start/list/read/send/draft/stop/archive/delete, folders.list/move and notes.list/read/write actions; unknown fields are rejected and retries reuse a request ID.

Kind
documented
Locator
whole file (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
monocode:m-harness

src/features/sessions/model/session.ts

Closed list of eleven harness IDs and four runtime modes: supervised (default), auto-accept-edits, auto, full-access.

Kind
source-inspected
Locator
HARNESSES, RuntimeMode (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/sessions/model/session.ts
monocode:m-orchstate

src/features/orchestration/model/orchestrationState.ts

Orchestration runs hold a lead, tasks with harness, model, files, scopes, dependsOn, status (queued, running, blocked, interrupted, cancelled, completed, failed), dispatch records and a maxWorkers limit.

Kind
source-inspected
Locator
TaskStatus, OrchestrationTask, OrchestrationRun (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/orchestration/model/orchestrationState.ts
monocode:m-orch

src/features/orchestration/model/orchestration.ts

Lead CLI actions list/get/delegate/message/retry/cancel/wait/review/finish/steer/respond/answer; maxWorkers 1-4; pump starts a queued task only after its dependencies are accepted, no active task has an overlapping file scope and the worker count is below the limit; lead decides worker approvals.

Kind
source-inspected
Locator
control actions, maxWorkers, lead prompt, pump (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/orchestration/model/orchestration.ts
monocode:m-handoff

src/features/sessions/model/handoff.ts

Handoff and second-opinion cards move a conversation recap from one harness to another.

Kind
source-inspected
Locator
HandoffComposerCard (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/sessions/model/handoff.ts
monocode:m-readme

README.md

Runs eleven installed agent CLIs on the user subscriptions, tabs are sessions, separate Git worktrees for parallel tasks, /operator lets an agent open sessions and manage worktrees and notes, Monos keep memory and run scheduled tasks; MonoCode does not sell tokens.

Kind
documented
Locator
intro, Get started (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
monocode:m-providers

docs/providers.md

MonoCode runs the installed agent CLIs and reuses their existing logins; probes each CLI at startup and disables missing ones; install and login commands for eleven providers.

Kind
documented
Locator
whole file (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
monocode:m-usage

src-tauri/src/rate_limits.rs

Reads the Claude account usage windows with the user own OAuth credential; similar usage readers exist for Devin and Pi; the UI shows account headroom and usage-limit resume.

Kind
source-inspected
Locator
OAUTH_USAGE_URL (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/src/rate_limits.rs
monocode:m-remote

docs/remote-access.md

Experimental remote host over an SSH loopback tunnel with per-device tokens and revoke, host service that survives disconnects, supported and unsupported remote features, no OS keychain, and interrupted turns after host crash.

Kind
documented
Locator
whole file (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
monocode:m-wt

src-tauri/src/worktrees.rs

Creates, renames, checks and removes Git worktrees and dedicated orchestration worktrees and branches from the desktop app.

Kind
source-inspected
Locator
worktree create/remove (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/src/worktrees.rs
monocode:m-pr

src-tauri/src/fs.rs

Uses gh to find the current branch pull request, create a pull request and return its URL, and list issues and pull requests for the inbox.

Kind
source-inspected
Locator
PR lookup, create, list (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/src/fs.rs
monocode:m-inbox

src/features/inbox/model/ciRepair.ts

Inbox connects GitHub, Linear, Jira, GitLab and Azure DevOps (model files per source) and a CI repair flow starts a session from failing check evidence.

Kind
source-inspected
Locator
CI repair context (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/inbox/model/ciRepair.ts
monocode:gap39-host-cli

MonoCode Host command-line interface

The user-runnable MonoCode Host CLI serves, starts, checks and stops the agent host, installs/uninstalls its service and manages paired device credentials. Published host archives include a Node runtime and launcher for Windows, macOS and Linux. This is separate from the agent-only /operator app actions.

Kind
source-inspected
Locator
main help and command dispatch, lines 80-108; docs/remote-access.md Manage the host
Source date
Not stated
Retrieved
2026-11-13
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
host/cli.ts
monocode:m-control

src-tauri/src/control.rs

Authenticated loopback transport for the control CLI: per-session tokens, app windows own execution, callers get no arbitrary Tauri commands or database writes.

Kind
source-inspected
Locator
module docs, Grant, ActiveTurn (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/src/control.rs
monocode:m-hostauth

host/server.ts

Remote host requires a 43-character bearer device credential checked against the store before and after reading a request body; credentials can be revoked.

Kind
source-inspected
Locator
bearer auth, devices.revokeSelf (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
host/server.ts
monocode:m-jira

docs/jira.md

Jira Cloud inbox with an unscoped API token: browse issues and comments, post comments, ask or start work; automations poll for new Jira issues; credentials stored locally with owner-only permissions.

Kind
documented
Locator
whole file (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
monocode:m-mcp

src-tauri/src/mcp.rs

Reads and edits MCP server config for providers (including Claude Desktop config), adds one server at a time from JSON and discovers connections for a project; MCP use itself belongs to each provider CLI.

Kind
source-inspected
Locator
mcp_add, mcp_discover (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/src/mcp.rs
monocode:m-skills

src-tauri/src/skills.rs

Discovers skills from project and home skill roots by scope and source (max 5,000, frontmatter capped), with a disabled-path filter, and the UI offers a skill picker and slash commands.

Kind
source-inspected
Locator
list_skills_from (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/src/skills.rs
monocode:m-mobile

src-tauri/src/mobile_access.rs

A paired phone controls the workspace through the owning desktop window over a QUIC link; no arbitrary Tauri commands or direct database writes are exposed.

Kind
source-inspected
Locator
module docs, Device, Config (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/src/mobile_access.rs
monocode:m-tauri

src-tauri/tauri.conf.json

Tauri 2 desktop bundle for all targets (macOS, Linux, Windows); main window minimum 800x520.

Kind
source-inspected
Locator
bundle targets, window (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/tauri.conf.json
monocode:jira

MonoCode docs/jira.md

Jira Cloud inbox browses issues/comments, starts local work with ticket identity and polls issue-appeared automation. It supports unscoped API tokens, not Jira Data Center.

Kind
documented
Locator
Inbox; Automation trigger
Source date
Not stated
Retrieved
2026-11-08
monocode:m-auto

src/features/automations/model/automations.ts

Automations trigger on time (hourly, daily, weekdays, weekly) or GitHub, Linear, Jira, GitLab or Azure DevOps events, run in current checkout, new worktree or existing worktree, with a missed-run grace period and per-run status.

Kind
source-inspected
Locator
AutomationTrigger, Automation (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/automations/model/automations.ts
monocode:m-bg

src-tauri/src/background_work.rs

Lowers CPU and disk priority of agent descendants and bounds optional indexing work with a four-permit semaphore.

Kind
source-inspected
Locator
configure_child, LIMIT (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/src/background_work.rs
monocode:gap39-tasks

MonoCode session task renderer

The displayed task list parses TodoWrite/write_todos/update_todos tool payloads inside agent sessions. The scoped inbox models integrate GitHub, Jira, Linear and Azure DevOps trackers; inspection found no product-owned issue/backlog store distinct from sessions and external tickets.

Kind
source-inspected
Locator
isTaskListToolName; taskListFromToolInput; src/features/inbox/model
Source date
Not stated
Retrieved
2026-11-13
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/sessions/model/taskList.ts
monocode:m-autotimer

src/app/App.tsx

Due automations are evaluated by a 30-second timer in the desktop app window; there is no separate scheduler service.

Kind
source-inspected
Locator
automation evaluate interval (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/app/App.tsx
monocode:m-autors

src-tauri/src/automations.rs

Automations persist in SQLite with at most 20 triggers each; missed-run grace is validated to 0-43,200 minutes and applied when deciding whether a missed run still starts.

Kind
source-inspected
Locator
persistence, validation, grace (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src-tauri/src/automations.rs
monocode:m-pressure

src/features/notifications/model/resourcePressure.ts

Samples CPU percent, memory pressure and stall share with high/low hysteresis to show a resource-pressure notice.

Kind
source-inspected
Locator
ResourceSample, PressureState (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/notifications/model/resourcePressure.ts
monocode:gap39-process

MonoCode host child backend

The scoped host starts installed coding-provider child processes in a local checkout or worktree. Inspection of host providers, child backend and desktop launch paths found no vendor-managed runtime provisioning or per-session container/VM launcher.

Kind
source-inspected
Locator
Provider process launch, lines 330-370; docs/remote-access.md
Source date
Not stated
Retrieved
2026-11-13
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
host/child-backend.ts
monocode:m-ckpt

src/features/sessions/model/checkpoint.ts

Per-session checkpoint records exact before/after diffs per file with an undoable flag and applies or reverts them while guarding changes made outside the session.

Kind
source-inspected
Locator
CheckpointFile, apply result (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/sessions/model/checkpoint.ts
monocode:m-ctx

src/features/sessions/model/contextUsage.ts

Shows context used as a percentage and token counts per session (for example 176K of 256K tokens).

Kind
source-inspected
Locator
context usage label (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/sessions/model/contextUsage.ts
monocode:m-diffcomment

src/features/source-control/model/diffComment.ts

Diff comments are composed on changed lines (DiffCommentComposer) and sent to the agent as feedback.

Kind
source-inspected
Locator
diff comments (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/source-control/model/diffComment.ts
monocode:m-diffkeys

src/features/source-control/ui/UnifiedDiffView.tsx

The unified diff view handles ArrowUp and ArrowDown to move between diff entries.

Kind
source-inspected
Locator
keyboard navigation (hardbeat920/monocode @ 7508feaee84d)
Source date
Not stated
Retrieved
2026-11-16
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
src/features/source-control/ui/UnifiedDiffView.tsx
monocode:license

MonoCode LICENSE

MonoCode repository code is MIT licensed, subject to provider names/logos and notices.

Kind
source-inspected
Locator
MIT grant
Source date
Not stated
Retrieved
2026-11-08
Commit
164957961717a02ffff91a6c25e1f0ae8007a40e
Path
LICENSE
monocode:gap39-privacy-code

MonoCode app dependencies and telemetry inspection

Inspection of the public application dependencies and implementation found no product analytics emitter or telemetry opt-out setting. Provider login and provider network usage remain outside this conclusion; this does not establish a provider privacy policy.

Kind
source-inspected
Locator
package.json; src, src-tauri, crates, host, mobile; search telemetry, PostHog, Sentry, analytics, Mixpanel, Amplitude
Source date
Not stated
Retrieved
2026-11-13
Commit
7508feaee84db638fb7a7c146d9f15de5d0f3689
Path
package.json
monocode:readme-nov10

MonoCode README

Says MonoCode works with your own Claude Code, Codex, Cursor and other subscriptions and does not sell tokens. The license is MIT.

Kind
documented
Locator
Intro paragraph above 'Install'; 'License' section
Source date
Not stated
Retrieved
2026-11-10
monocode:license-nov10

hardbeat920/monocode LICENSE (MIT)

The MIT License lets anyone obtain, use, copy and modify the software free of charge.

Kind
documented
Locator
Permission grant, first paragraph
Source date
Not stated
Retrieved
2026-11-10
monocode:release-notes

MonoCode docs/native/preview-release-notes.md

Native preview release notes cover terminals, sessions, Git views and sign-in fixes; broad real-device parity is not established.

Kind
documented
Locator
Preview 14; Git; Accounts
Source date
Not stated
Retrieved
2026-11-08
monocode:b4-install

MonoCode README: install

MonoCode runs the user's installed, logged-in agent subscriptions and does not sell tokens. Installers for macOS, Linux and Windows are free downloads from GitHub releases and dl.usemono.dev; no price or paid plan is named.

Kind
documented
Locator
README.md lines 15-27 (intro and Install table), commit 7e5a9e3
Source date
Not stated
Retrieved
2026-11-10
monocode:b4-license

MonoCode LICENSE

The repository is under the MIT License.

Kind
documented
Locator
LICENSE lines 1-3, commit 7e5a9e3
Source date
Not stated
Retrieved
2026-11-10

Comparisons with MonoCode

Compare MonoCode with any other product on adecomparison.com.