podium

Harness by Autonomous

49 of 51 criteria have a sourced finding; 49 were also cross-checked by a second agent. Every comparison that includes Harness by Autonomous 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-13
Agent cross-checked
49 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Agent cross-checked partial

Desktop installers cover macOS 12+ (Apple Silicon + Intel), Linux x64/ARM64 and Windows x64/ARM64 with self-update. The same Flutter app runs in the browser (workspace front door, browser pairing, hn view links) and as installed iOS/Android phone apps (live App Store listing; Play builds plus store redirect). The harness CLI, hn TUI and MCP stdio server cover terminal use. Approvals and waiting lists surface in-app, on phones via push/local notices, and on the device. Agents keep working with clients closed and continue from another window, phone or browser.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • No Harness editor extension exists in the checked sources. Mobile-browser use of the web app and desktop OS-level push beyond the phone path are not established.
9 atomic answers

Sources: harness-by-autonomous:release, harness-by-autonomous:desktopdl, harness-by-autonomous:webapp, harness-by-autonomous:mobile, harness-by-autonomous:appstore, harness-by-autonomous:tui, harness-by-autonomous:cli, harness-by-autonomous:notify, harness-by-autonomous:app

Agent cross-checked partial

Fourteen named engines run under their own vendor logins, followed via transcripts plus vendor hooks/plugins Harness installs; it never wraps an agent. Local models run through Grid, Ollama, MLX-LM and vLLM, and any pane can retarget to an Autonomous Grid relay. Tabs freely mix engines and machines. No custom engine-adapter mechanism exists.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • No custom engine adapters or unlisted engines are established; Grid relay billing terms are not stated.
5 atomic answers
  • Harnesses [supported] Claude Code, Codex, Cursor, OpenCode, Pi, Hermes, Command Code, Devin, Muse Code, Amp, Kilo, Grok Build, Antigravity and GitHub Copilot, each with binary, follow-method, resume and auto-approve flags. Sources: harness-by-autonomous:engines.
  • Model providers [supported] Vendor-native logins stay in ~/.claude, ~/.codex, etc.; local open-weight models via Grid, Ollama, MLX-LM and vLLM; per-pane Retarget to an Autonomous Grid relay (tmux >= 3.2). Sources: harness-by-autonomous:engines, harness-by-autonomous:readme.
  • Custom adapters [unsupported] The supported-engine table is a fixed list of 14; bounded search found no custom-engine or adapter mechanism (terms: custom engine, adapter, BYO engine, plugin engine). Sources: harness-by-autonomous:negsearch, harness-by-autonomous:engines.
  • Session integration [supported] Harness reads the transcript each agent already writes and installs the vendor's own hooks or plugin to learn turn boundaries; credentials never move into Harness. Sources: harness-by-autonomous:engines.
  • Mixed harness operation [supported] One tab holds any mix of machines and engines side by side (four-agent/three-machine and machine-link recordings; app: tabs hold panes from any mix of machines). Sources: harness-by-autonomous:readme, harness-by-autonomous:app.

Sources: harness-by-autonomous:engines, harness-by-autonomous:readme, harness-by-autonomous:gridstore, harness-by-autonomous:app

Agent cross-checked partial

Agent work runs on the user's own engine subscriptions and API-style logins; Harness sells no credits and states no vendor-credit route. Local models and the Grid relay are supported routes. A different account signs in with login --force (one active account). No Harness account or token purchase is needed for local harnesses.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Vendor credit sales, multi-account switching and provider-specific restrictions beyond engine support are not established.
7 atomic answers

Sources: harness-by-autonomous:engines, harness-by-autonomous:readme, harness-by-autonomous:cli, harness-by-autonomous:mcp, harness-by-autonomous:gridstore, harness-by-autonomous:negsearch

Agent cross-checked partial

Download, install, sign in, link machines with a password, then New Harness (machine, folder, engine, advanced). Any folder starts a harness (plain cwd supported; worktrees optional); GitHub URLs clone; per-machine Node 20+ and tmux, macOS 12+ / Ubuntu 22.04+ stated. Headless Linux servers onboard with install.sh. No managed-cloud setup exists.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Managed-cloud setup does not exist; hosted-Git providers beyond clone-a-URL and no-Git edge cases beyond plain-cwd support are not separately established.
7 atomic answers

Sources: harness-by-autonomous:readme, harness-by-autonomous:app, harness-by-autonomous:cli, harness-by-autonomous:desktopdl, harness-by-autonomous:capacity

Agent cross-checked partial

A product CLI (harness + hn + harness mcp), a credentialed loopback REST/WebSocket API with named agent/session operations, the same tools as an MCP stdio server and machine-scoped MCP servers cover automation. No public SDK or webhooks exist. The loopback protocol carries a version field; no published stability policy was found.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • SDK, webhooks and a published API stability policy do not exist in the checked sources.
8 atomic answers
  • Cli [supported] harness CLI: login/start/stop/status/update, dsh, machines, swarm reads, link/remote, devices, grid, tui, mcp, logs export; hn TUI; JSON/NDJSON flags; managed auto-updates. Sources: harness-by-autonomous:cli, harness-by-autonomous:tui.
  • Api [supported] Loopback REST (127.0.0.1:18473) and WebSocket (machine_select, request ids) with agents_list/create/restart/retarget/delete/read/send/question_response/message/cancel/terminal_open plus fs/engines/usage reads; backend REST serves the web/phone clients. Sources: harness-by-autonomous:cli, harness-by-autonomous:webapp.
  • Sdk [unsupported] No public SDK package or directory exists (bounded: repo tree search for sdk; only the CLI, harness-mcp npm and loopback API). Sources: harness-by-autonomous:negsearch.
  • Mcp server [supported] Product-owned MCP: harness mcp stdio server (whoami/list/search/machines/start/wait/read/close; agents touch only their own harnesses) plus pair mcp serving the same tools; npm @autonomous-ai/harness-mcp. Sources: harness-by-autonomous:mcp, harness-by-autonomous:mcpserver, harness-by-autonomous:cli.
  • Webhooks [unsupported] No webhook subscription or delivery exists (bounded search: webhook finds only prose false positives); GitHub App subscribes to no events. Sources: harness-by-autonomous:negsearch.
  • Operations [supported] Create, inspect (list/read/brief/search), steer (send/talk/type/answer), pause/resume, stop/close and retarget across machines from CLI, API, MCP and agent verbs. Sources: harness-by-autonomous:cli, harness-by-autonomous:agentcli, harness-by-autonomous:mcp.
  • Authentication [supported] Loopback calls show the daemon's local credential (0600 hook-credential file) else 401; pair writes need per-launch tokens; backend uses account sessions with Google/Apple/QR sign-in. Sources: harness-by-autonomous:cli, harness-by-autonomous:security.
  • Stability [unknown] Harness's checked sources did not establish this atomic requirement. The loopback handshake carries localProtocolVersion 1 and the provider protocol versions changes additively, but no published stability or deprecation policy for the automation API was found.

Sources: harness-by-autonomous:cli, harness-by-autonomous:mcp, harness-by-autonomous:mcpserver, harness-by-autonomous:mcpclient, harness-by-autonomous:negsearch

Agent cross-checked partial

Machine-scoped MCP servers attach to every agent a machine starts (per-engine/per-project scoping, product-managed); Claude/Codex/Cursor plugins install a Harness skill plus the MCP server; domain harnesses (harness.json folders) bring instructions, tools and viewers; repo conventions (AGENTS.md, agents/<name>.md) feed sessions. Engine-native logins stay inherited from the underlying harness.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Skill-deletion/correction flows and permission scope beyond MCP scoping plus engine modes are not established.
7 atomic answers

Sources: harness-by-autonomous:mcpclient, harness-by-autonomous:plugin, harness-by-autonomous:readme, harness-by-autonomous:app, harness-by-autonomous:engines

Agent cross-checked partial

Desktop and phone apps are Flutter (desktop targets macOS/Linux/Windows/web; mobile targets Android/iOS); the TUI and installer are Rust; daemon and CLI are managed Node. No Electron shell is used.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Hybrid classification beyond Flutter-plus-native-shells and renderer details are not established.
4 atomic answers

Sources: harness-by-autonomous:clients, harness-by-autonomous:readme, harness-by-autonomous:tui, harness-by-autonomous:naming

Planning and context

Agent cross-checked partial

Local creation (New Harness form, prompts, 1:1 chats) and GitHub-URL cloning are product paths; agents work tasks through Swarm commands. The authoritative tracker is split by design: Swarm tasks for work, GitHub for code and pull requests. Task numbers are stable; PR state is read back and verdicts/merges posted out; issues are not synced. People cannot post in channels or task chats.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
official-integration
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Issue import, GitHub event triggers, person-side task creation/editing and channel posting by people do not exist.
9 atomic answers

Sources: harness-by-autonomous:app, harness-by-autonomous:cli, harness-by-autonomous:agentcli, harness-by-autonomous:swarmv4, harness-by-autonomous:merge, harness-by-autonomous:verdict

Agent cross-checked partial

Swarm tasks are durable server-side goals with chats, sizes, priorities and dependency numbers, linked to the pull requests that close them and surviving restarts. Goal text is writable and messages editable; goal-edit history, explicit acceptance criteria and in-run amendment rules are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Acceptance criteria, revision history of goals and in-run amendment rules are not established.
7 atomic answers
  • Plans [supported] Tasks live in Swarm as a goal plus a chat, kept server-side across restarts and client disconnects. Sources: harness-by-autonomous:swarmv4.
  • Acceptance criteria [unknown] Harness's checked sources did not establish this atomic requirement. No acceptance-criteria construct distinct from sizes, priorities and land rules was found.
  • Editors [partial] Goal write verb plus message edits exist; editor permission rules are not established. Sources: harness-by-autonomous:agentcli.
  • Revisions [partial] Chat history is retained and reviewable; goal revision history is not established. Sources: harness-by-autonomous:swarmv4.
  • Amendment [unknown] Harness's checked sources did not establish this atomic requirement. Whether a goal can be amended while its work runs, and by whom, is not established.
  • Restart persistence [supported] Server-side tasks and chats survive app restarts, machine disconnects and roster lapses (Lead never stopped). Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:retention.

Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:crew, harness-by-autonomous:agentcli, harness-by-autonomous:shipping

Agent cross-checked partial

Swarm projects hold flat task lists with sizes, priorities, dependency numbers and claim limits; ordering is enforced at merge time (lands-after) and by the ready-to-land rule. No epic or parent/child hierarchy exists, and growing a task into an epic is not a construct. No rigid preselected workflow is required.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Epics, deeper hierarchy, state propagation and identity-retention-across-growth are not established. Task-to-epic and workflow-constraint subanswers record absence, not hidden features.
9 atomic answers
  • Epics [unsupported] No epic entity exists; projects hold flat tasks with workgroups/lists (bounded: searched epic, parent/child, subtask entities in cli/src and backend/src). Sources: harness-by-autonomous:negsearch, harness-by-autonomous:swarmv4.
  • Hierarchy [unsupported] No parent/child task depth exists; agent work lists are flat queues with sizes and priorities. Sources: harness-by-autonomous:negsearch, harness-by-autonomous:crew.
  • Blockers [partial] Task ordering (comes after) and PR lands-after ordering are recorded and enforced at merge; UI-level blocker display is not established. Sources: harness-by-autonomous:crew, harness-by-autonomous:merge.
  • Readiness [supported] Readiness is explicit: the ready-to-land rule (non-writer READ-OK, no HOLD, green checks, mergeable, ordered). Sources: harness-by-autonomous:merge.
  • Enforcement [supported] The merge rule is code run on every pass (30s interval, 100-per-page up to 3 pages); only ready PRs land, on a train. Sources: harness-by-autonomous:merge.
  • State propagation [unknown] Harness's checked sources did not establish this atomic requirement. State propagation beyond merge ordering and told-on-PR notes is not established.
  • Task to epic [unsupported] With no epic construct, task-to-epic growth does not exist. Sources: harness-by-autonomous:negsearch.
  • Identity retention [unknown] Harness's checked sources did not establish this atomic requirement. Whether a task keeps identity, discussion and outputs while its scope grows is not established.
  • Workflow constraints [unsupported] No rigid preselected workflow is required: Cmd-N/Cmd-S free-form creation plus PM dispatch; constraints recorded are resource gates and land rules. Sources: harness-by-autonomous:app, harness-by-autonomous:capacity, harness-by-autonomous:merge.

Sources: harness-by-autonomous:crew, harness-by-autonomous:merge, harness-by-autonomous:swarmv4, harness-by-autonomous:negsearch

Agent cross-checked partial

Repo AGENTS.md plus per-agent files, DSH instructions and installed skills feed sessions; the Memories agent aggregates every engine's memory dirs with the Harness session index, cited by agent and project, with search. Correction, deletion and freshness controls for memory are not established; takeover continues through SessionStart re-reads and handoff files.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Memory correction/deletion/freshness controls and project-doc lifecycle rules are not established.
10 atomic answers
  • Instructions [supported] Repo AGENTS.md (goal, ownership, read-agents-first) plus agents/<name>.md per-agent rules, written and pushed by agents; DSH folders bring craft instructions. Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:readme.
  • Skills [supported] Store skills install into sessions (SKILL.md format); the v4 product removed its own built-in swarm skills, manuals and launch text. Sources: harness-by-autonomous:plugin, harness-by-autonomous:swarmv4.
  • Project docs [partial] Kept review ZIPs, reference PDFs and session artifacts persist per project; a managed project-doc lifecycle is not established. Sources: harness-by-autonomous:handson, harness-by-autonomous:shipping.
  • Memory [supported] Memories aggregates Claude/Codex/Grok/Hermes memory dirs with a year of Harness session index; Recall searches both; opening changes nothing. Sources: harness-by-autonomous:memory.
  • Scope [supported] Memories scope by engine and project; per-engine homes (incl. Codex profiles) keep sessions apart; machine MCP entries scope per engine/project. Sources: harness-by-autonomous:memory, harness-by-autonomous:app, harness-by-autonomous:mcpclient.
  • Provenance [supported] Beliefs cite the memories and messages behind them with agent and project attribution; verdicts and commits are signed/named. Sources: harness-by-autonomous:memory, harness-by-autonomous:verdict.
  • Correction [unknown] Harness's checked sources did not establish this atomic requirement. Memory correction flows (lifting a belief to read it is read-only) are not established.
  • Deletion [unknown] Harness's checked sources did not establish this atomic requirement. Memory deletion controls are not established.
  • Freshness [unknown] Harness's checked sources did not establish this atomic requirement. Staleness controls for instructions, skills and memories are not established.
  • Takeover continuity [supported] Sessions re-read root AGENTS.md after compaction (SessionStart hook); handoff files carry requests, answers, git state and tool calls to the next engine or agent with secrets redacted. Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:cli.

Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:readme, harness-by-autonomous:plugin, harness-by-autonomous:memory, harness-by-autonomous:cli

Agent cross-checked partial

Product-level search covers every past and live conversation on a machine; codebase awareness itself is engine-side. Voice input, image paste and craft viewers give multimodal inputs. No product code index exists; retrieval, citation, conflict-detection and enforcement details beyond merge gates are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • A product codebase index, external-knowledge retrieval, citation/conflict machinery and retrieval-time enforcement are not established.
10 atomic answers
  • Indexing [unsupported] No product codebase or repository index exists (bounded: searched index, embeddings, catalogue constructs in cli/src and backend/src). Sources: harness-by-autonomous:negsearch.
  • External knowledge [unknown] Harness's checked sources did not establish this atomic requirement. External knowledge retrieval beyond engines and viewers is not established.
  • Multimodal inputs [supported] Voice input on phone and device, image paste in phone terminal, media previews in 128 KiB chunks, and craft viewers (PDF, 3D, traces, games, video). Sources: harness-by-autonomous:mobile, harness-by-autonomous:readme, harness-by-autonomous:handson, harness-by-autonomous:cli.
  • Freshness [unknown] Harness's checked sources did not establish this atomic requirement. Source freshness for retrieval is not established.
  • Access scope [unknown] Harness's checked sources did not establish this atomic requirement. Retrieval access scope beyond server-enforced project reads is not established.
  • Api retrieval [unknown] Harness's checked sources did not establish this atomic requirement. API-shaped retrieval with stated contracts beyond agent_read_file chunks is not established.
  • Citations [unknown] Harness's checked sources did not establish this atomic requirement. Citation machinery for retrieved context is not established.
  • Conflict detection [unknown] Harness's checked sources did not establish this atomic requirement. Conflict detection across retrieved sources is not established.
  • Review enforcement [partial] At delivery, non-writer reads plus green checks are enforced before merge; retrieval-time enforcement is not established. Sources: harness-by-autonomous:merge.

Sources: harness-by-autonomous:mcp, harness-by-autonomous:readme, harness-by-autonomous:mobile, harness-by-autonomous:handson, harness-by-autonomous:merge, harness-by-autonomous:negsearch

Agent cross-checked partial

Swarm keeps persistent tasks (goal+chat) with sizes, priorities, claim limits, dependency numbers, durable open/closed/not-planned states and PM dispatch without accept/decline; tasks and harness sessions are distinct entities. Edits, search, filters, archive and reopen are only partly established, and idea parking was removed in v4. GitHub remains required for code and PRs.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Idea parking was removed; archive/reopen, task search/filter and person-side direct edits are not established.
17 atomic answers
  • Create [partial] Task creation exists via the PM/backend task commands; person-side direct creation outside Cmd-N/Cmd-S flows is not established. Sources: harness-by-autonomous:swarmv4.
  • Edit [partial] Goal write and message edits exist; task field edit rules are not established. Sources: harness-by-autonomous:agentcli.
  • Discuss [supported] Channel, per-task chats, thread replies and 1:1 agent chats carry discussion; people read, agents post. Sources: harness-by-autonomous:swarmv4.
  • Prioritize [supported] p0/p1/p2 weights plus taskPriority handling order what ships first. Sources: harness-by-autonomous:crew.
  • Label [partial] builder: labels tag team PRs; task-level label taxonomy is not established. Sources: harness-by-autonomous:crew.
  • Assign [supported] The PM assigns tasks to agents; agents take the next on their list; Switch PM moves the role. Sources: harness-by-autonomous:swarmv4.
  • Filter [unknown] Harness's checked sources did not establish this atomic requirement. Task filtering beyond picker filters is not established.
  • Archive [unknown] Harness's checked sources did not establish this atomic requirement. Archive distinct from project deletion is not established.
  • Reopen [unknown] Harness's checked sources did not establish this atomic requirement. Task reopen flows are not established.
  • Project epic views [partial] Swarm view groups projects, channel, task chats and coordinator/agent rows; epic views do not exist (no epics). Sources: harness-by-autonomous:swarmv4.
  • Idea parking [unsupported] The people's proposal form and backlog were explicitly removed in Swarm v4; saving an idea without starting an agent is not a construct. Sources: harness-by-autonomous:swarmv4.
  • Explicit dispatch [supported] No accept/decline: the PM assigns, agents take the next when free, and Swarm tells the PM when a list drops below 3. Sources: harness-by-autonomous:swarmv4.
  • Task session separation [supported] Tasks (goals+chats with states) are distinct from harness sessions (engine runs in tmux panes). Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:app.
  • Metadata [supported] Sizes with minutes/ram/disk/spend, priorities, dependency numbers, claim limits and stable numbers. Sources: harness-by-autonomous:crew.
  • Durable states [supported] Open, closed and closed-as-not-planned states with per-task lists kept at least 3 deep. Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:crew.
  • External tracker requirement [partial] GitHub remains required for code and pull requests; issue tracking itself moved into Swarm. Sources: harness-by-autonomous:product, harness-by-autonomous:merge.

Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:crew, harness-by-autonomous:agentcli, harness-by-autonomous:product, harness-by-autonomous:merge

Agent cross-checked partial

Agents share stable task numbers and agent ids; read/create/update run through documented super-tab verbs, the MCP server and the loopback API; take claims with a limit of 4; results return as posted replies, recaps and cost lines; humans watch with attribution in product views; permissions scope agents to their own sessions and server-enforced reads. Task children, agent-side reassignment and conflict handling are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Agent-side task creation/assignment, child tasks and conflict handling are not established.
14 atomic answers

Sources: harness-by-autonomous:agentcli, harness-by-autonomous:mcp, harness-by-autonomous:mcpserver, harness-by-autonomous:cli, harness-by-autonomous:swarmv4, harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:crew, harness-by-autonomous:tasktokens

Agent cross-checked unsupported

No living product-specification construct exists: no persistent cross-task requirements with human/agent revisions, approvals, implementation links, retrieval, drift detection or review integration. Goals are per-task briefs, AGENTS.md files are instructions, and Memories is a memory store; none is a versioned spec.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Every subanswer records absence from bounded inspection, not a hidden feature.
9 atomic answers

Sources: harness-by-autonomous:negsearch, harness-by-autonomous:swarmv4, harness-by-autonomous:memory

Coordination and automation

COORD-01

Parallel work

Agent cross-checked partial

Sessions run concurrently across panes, tabs and machines with working/waiting/idle/failed/stopped states visible in every client; start requirements gate memory, disk and tools (no CPU cap, no count quotas); agent work lists keep at least 3 deep with quota waits and offer queues. Concurrency is documented, not hands-on tested.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Count quotas, CPU caps and hands-on concurrency verification are absent; status beyond documented states is not claimed.
5 atomic answers

Sources: harness-by-autonomous:app, harness-by-autonomous:cli, harness-by-autonomous:capacity, harness-by-autonomous:crew, harness-by-autonomous:readme

Agent cross-checked partial

The PM agent assigns tasks to agents and agents claim from ordered lists (limit 4) with quota waits and decline reasons; routing prefers the agent that can ship soonest on a machine with memory, disk and tools; ownership is enforced by the identity rule (an agent runs only under its own person's login) with server-enforced reads. Human-to-human assignment does not exist.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Duplicate-work prevention is partial (claim limits, single merger, hot-file warnings) and human assignment is absent by design.
7 atomic answers

Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:crew, harness-by-autonomous:capacity, harness-by-autonomous:agentcli, harness-by-autonomous:swarmapi

Agent cross-checked partial

The PM/coordinator slot is product-designated (Cmd-S creates the coordinator; Switch PM moves it) with shipped delegation tools: task assignment, @sender message injection, verdicts, and merge-by-rule, plus Agent Messages tab-to-tab send (experiment, off by default). Live states, retained replies/recaps/handoffs and follow-up via resume round it out; agent-to-agent reassignment is not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Tab-to-tab Agent Messages is an off-by-default experiment; agent-to-agent reassignment and role display details are not established.
12 atomic answers

Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:agentcli, harness-by-autonomous:merge, harness-by-autonomous:cli, harness-by-autonomous:verdict, harness-by-autonomous:readme, harness-by-autonomous:mcp

Agent cross-checked unsupported

No unattended triggers exist: no schedules, event triggers, recurring tasks, completion conditions, scheduler, overlap handling or retries. Timers in-tree are internal poll/backoff only. Single-shot and conversational initiation is the whole model; Grid-brand schedules belong to the separate Grid product.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Every subanswer records a bounded no-find at the pinned release, not a hidden feature.
8 atomic answers

Sources: harness-by-autonomous:negsearch, harness-by-autonomous:cli, harness-by-autonomous:app

Agent cross-checked partial

Pause, stop, resume, steer (prompts, talk, type), wait-list and pending-decision surfacing, failure reasons and retained transcripts/handoffs are product paths across desktop, phone, device, CLI and API. Escalation beyond waits and the exact chat/terminal parity edge are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Escalation routing and full chat/terminal parity are not established.
10 atomic answers

Sources: harness-by-autonomous:cli, harness-by-autonomous:app, harness-by-autonomous:notify, harness-by-autonomous:agentcli, harness-by-autonomous:mobile, harness-by-autonomous:readme

Agent cross-checked partial

The Swarm view (channel plus task chats beside coordinator/agent rows), harness swarm CLI reads, roster machine stats and told/pushed attention signals cover fleet visibility; merge ordering and workload gating are enforced in code. Grouping, history navigation and navigation-error coverage are only partly established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Dependency/attention display details, history navigation and full error coverage are not established.
8 atomic answers

Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:cli, harness-by-autonomous:capacity, harness-by-autonomous:merge, harness-by-autonomous:notify, harness-by-autonomous:mobile

Agent cross-checked partial

Cmd-N/Cmd-S free-form creation, natural-language PM direction with voice, per-agent engine/model/profile/permission configuration, in-run engine changes with handoffs and Grid retargets, retained task/PR/verdict links, and Cmd-P/docs/agents-page discoverability with frictionless Google/Apple/QR sign-in. Epic growth and mandatory presets do not exist.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Epic growth, mandatory presets and live-role display details are not established.
10 atomic answers

Sources: harness-by-autonomous:app, harness-by-autonomous:swarmv4, harness-by-autonomous:tui, harness-by-autonomous:cli, harness-by-autonomous:crew, harness-by-autonomous:merge, harness-by-autonomous:plugin, harness-by-autonomous:keyboard, harness-by-autonomous:security, harness-by-autonomous:webapp

Execution and reliability

Agent cross-checked partial

Local execution plus your own linked machines (password-linked, SSH-free) over E2EE relay/WebRTC/TURN, mixed in one tab; the backend, daemon and relay are open source with container files. No Harness-operated compute exists. Agents keep working with clients closed and resume from another window, phone or browser.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Vendor-cloud execution does not exist; region, expiry and compute-size disclosures are not established.
12 atomic answers

Sources: harness-by-autonomous:readme, harness-by-autonomous:cli, harness-by-autonomous:app, harness-by-autonomous:mobile, harness-by-autonomous:webapp, harness-by-autonomous:negsearch

Agent cross-checked partial

Each harness gets its own branch and git worktree with its own tmux pane/process; secrets travel in the tmux environment (never argv/files) with 0600 credentials and redacted handoffs. No container, VM or OS-sandbox isolation exists, and hostile-code containment is not claimed.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Container/VM/OS-sandbox isolation and hostile-code containment do not exist; network policy details are not established.
12 atomic answers

Sources: harness-by-autonomous:readme, harness-by-autonomous:cli, harness-by-autonomous:app, harness-by-autonomous:negsearch, harness-by-autonomous:security

Agent cross-checked partial

Client disconnects, app restarts and machine-offline stretches are designed-for: agents keep running, tabs/state reattach, engines resume where supported, handoff files bridge engine changes in degraded modes, and multi-week Swarm operation is on record. Daemon-crash, backend-restart and duplicate-action details are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Crash/restart reconstruction, duplicate-action freedom and manual-repair breadth are not established.
12 atomic answers
  • Client disconnect [supported] Agents keep working; phones poll every 15s and swarm reads/writes work while machines are offline. Sources: harness-by-autonomous:readme, harness-by-autonomous:mobile.
  • Worker crash [unknown] Harness's checked sources did not establish this atomic requirement. Daemon/worker crash recovery beyond tmux persistence is not established.
  • Service restart [unknown] Harness's checked sources did not establish this atomic requirement. Backend restart behavior is not established.
  • Expiry [partial] No sandbox TTL truncates runs; unconfirmed local roster lapses after 7 days while Leads never lapse. Sources: harness-by-autonomous:retention.
  • Transcript reload [supported] Engine transcripts reload with --resume/--session plus product recaps and pair read_harness recaps. Sources: harness-by-autonomous:engines, harness-by-autonomous:cli.
  • Process reconnect [partial] Daemon-owned harness-* tmux sessions reattach on app restart via remembered tabs; crash re-adoption is not established. Sources: harness-by-autonomous:cli, harness-by-autonomous:app.
  • Task resume [supported] Resume Harness, same-pane restart with the same id, stopped-row resume on phones, take-next semantics. Sources: harness-by-autonomous:app, harness-by-autonomous:mobile, harness-by-autonomous:swarmv4.
  • State reconstruction [partial] Handoff files reconstruct requests/answers/git/tool state in normal and degraded modes; full state rebuild is not established. Sources: harness-by-autonomous:cli.
  • Context loss [partial] Fork inheritance limits (5 links, same folder, cycle stops) and degraded handoff replies bound what can be lost. Sources: harness-by-autonomous:cli.
  • Duplicate actions [partial] Retry paths keep one operation id (phone commands, write retries); universal idempotency is not established. Sources: harness-by-autonomous:mobile.
  • Manual repair [partial] harness start --repair re-verifies the managed Node runtime; task-level repair is manual via resume/restart. Sources: harness-by-autonomous:cli.
  • Multi day continuity [supported] Multi-week Swarm operation is on record (lampOS 26 Oct-4 Nov, 122-193 changes/day) with leads that never lapse. Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:retention.

Sources: harness-by-autonomous:readme, harness-by-autonomous:app, harness-by-autonomous:cli, harness-by-autonomous:mobile, harness-by-autonomous:swarmv4, harness-by-autonomous:retention, harness-by-autonomous:engines

Agent cross-checked partial

The daemon installs engines on first launch and per-machine Node/tmux/sqlite prerequisites are documented; loopback port, per-engine homes and 0600 credentials are fixed; remote setup is one install.sh plus link; --repair exists. Caches, services, ports-collision handling, secret injection and install dedupe are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Dependency setup covers engines only; caches, services, ports, secret injection and dedupe are not established.
10 atomic answers
  • Dependencies [partial] Daemon probes and installs engines on first launch; project stacks (node_modules, toolchains) stay user-managed. Sources: harness-by-autonomous:app, harness-by-autonomous:cli.
  • Caches [unknown] Harness's checked sources did not establish this atomic requirement. Cache handling across workspaces is not established.
  • Snapshots [unknown] Harness's checked sources did not establish this atomic requirement. Environment snapshots distinct from Hub session snapshots are not established.
  • Services [unknown] Harness's checked sources did not establish this atomic requirement. Local service dependencies (DBs, ports) are user-managed without product mediation.
  • Ports [partial] Loopback is fixed at 127.0.0.1:18473; remote paths ride WebRTC/TURN; collision handling is not established. Sources: harness-by-autonomous:cli.
  • Secrets [partial] Per-engine homes, 0600 hook credentials and redacted handoffs; injection of project secrets is not established. Sources: harness-by-autonomous:cli, harness-by-autonomous:engines.
  • Duplicate installs [unknown] Harness's checked sources did not establish this atomic requirement. Cross-workspace install deduplication is not established.
  • Collisions [unknown] Harness's checked sources did not establish this atomic requirement. Port/service collision handling between workspaces is not established.
  • Remote setup [supported] install.sh plus login/password-link sets up headless Linux remotes with managed Node and tmux. Sources: harness-by-autonomous:readme, harness-by-autonomous:cli, harness-by-autonomous:desktopdl.
  • Automatic repair [partial] harness start --repair re-verifies the managed runtime; broader auto-repair is not established. Sources: harness-by-autonomous:cli.

Sources: harness-by-autonomous:app, harness-by-autonomous:cli, harness-by-autonomous:readme, harness-by-autonomous:desktopdl, harness-by-autonomous:negsearch

Agent cross-checked partial

No product-side time, turn, token or spend limits exist; token visibility comes from usage windows and ledgers while enforcement stays provider-side (subscription modes) or rule-side (pair dial, merge gates). Provider exits surface as failed states with reasons for manual resume/restart.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • No product-enforced run limits exist; timeout/retry configurability and provider-failure recovery are manual.
8 atomic answers
  • Time limits [unsupported] No product time limits exist. Sources: harness-by-autonomous:negsearch.
  • Turn limits [unsupported] No product turn limits exist. Sources: harness-by-autonomous:negsearch.
  • Token limits [partial] No product token caps; vendor subscription windows are surfaced and enforced provider-side. Sources: harness-by-autonomous:app.
  • Spend limits [unsupported] No spend limits exist (usage is never priced by Harness). Sources: harness-by-autonomous:negsearch, harness-by-autonomous:tasktokens.
  • Timeouts [unknown] Harness's checked sources did not establish this atomic requirement. User-facing timeout configuration is not established (internal relay/merge intervals only).
  • Retries [unknown] Harness's checked sources did not establish this atomic requirement. User-facing retry configuration is not established.
  • Provider failures [partial] Engine exits become failed states with reasons and told notes; recovery is manual resume/restart. Sources: harness-by-autonomous:cli, harness-by-autonomous:merge.
  • Enforcement [unknown] Harness's checked sources did not establish this atomic requirement. With no product-side limits, enforcement semantics are moot and unstated.

Sources: harness-by-autonomous:negsearch, harness-by-autonomous:app, harness-by-autonomous:cli, harness-by-autonomous:merge, harness-by-autonomous:engines

Agent cross-checked partial

Transcripts, scrollback, device history, journaled automation and one-command log export give logs; start-failure reasons, told-on-PR notes and sha-bound verdicts give failure/approval truth; per-task token rows, scoreboards and usage windows/ledgers give statistics with a documented benchmark method. Traces, usage export and reconnect-consistency details are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Traces do not exist; usage export, time-based stats and reconnect-consistency details are not established.
13 atomic answers

Sources: harness-by-autonomous:cli, harness-by-autonomous:app, harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:tasktokens, harness-by-autonomous:swarmapi, harness-by-autonomous:crew, harness-by-autonomous:readme

Agent cross-checked partial

Per-task token counts with hand-reviewed USD list prices post cost lines on landed PRs; per-provider ledgers and subscription windows show allowances; refresh is per minute. Billed charges never exist (BYO subscriptions, never priced), and compute cost, alerts, export and drilldown are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Billed amounts never exist; compute cost, budget alerts, export and drilldown are not established.
14 atomic answers
  • Task cost [supported] Per-task token rows with USD list-price math post cost lines on landed PRs (estimates from API list prices). Sources: harness-by-autonomous:tasktokens, harness-by-autonomous:costs.
  • Session cost [partial] Per-conversation counts feed the same rows; session-scoped cost views are not established. Sources: harness-by-autonomous:tasktokens.
  • Child cost [unknown] Harness's checked sources did not establish this atomic requirement. Child-scoped cost aggregation is not established.
  • Epic cost [unknown] Harness's checked sources did not establish this atomic requirement. No epics exist to cost.
  • Harness aggregation [partial] Counts aggregate per model across tasks/repos; harness-level rollups are not established. Sources: harness-by-autonomous:tasktokens.
  • Billed vs estimated [supported] Estimates only: Harness never bills; spend stays provider-side on your subscriptions. Sources: harness-by-autonomous:tasktokens, harness-by-autonomous:app.
  • Tokens [supported] Input/output/cacheRead/cacheWrite counted per model per task from transcripts and DBs. Sources: harness-by-autonomous:tasktokens, harness-by-autonomous:swarmapi.
  • Subscription allowance [supported] Each engine's subscription usage window is shown and refreshed every minute. Sources: harness-by-autonomous:app.
  • Provider reconciliation [unknown] Harness's checked sources did not establish this atomic requirement. Provider-bill reconciliation is not established.
  • Compute cost [unknown] Harness's checked sources did not establish this atomic requirement. Compute cost is your own hardware; no product accounting exists.
  • Refresh delay [supported] Usage windows refresh every minute. Sources: harness-by-autonomous:app.
  • Alerts [unknown] Harness's checked sources did not establish this atomic requirement. Budget or usage alerts are not established.
  • Export [unknown] Harness's checked sources did not establish this atomic requirement. Cost/usage export is not established.
  • Drilldown [unknown] Harness's checked sources did not establish this atomic requirement. Cost drilldown views are not established.

Sources: harness-by-autonomous:tasktokens, harness-by-autonomous:costs, harness-by-autonomous:swarmapi, harness-by-autonomous:app, harness-by-autonomous:cli

Agent cross-checked partial

Starts gate on probed memory/disk/tools with quota flags; agent lists, offer queues, quota waits and the merge train queue work; trains combine checks and hot-file warnings serialize risky landings. CPU has no cap, and backpressure, bounded-test, fairness-beyond-priority and recovery details are only partly established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • CPU caps, backpressure semantics, bounded-test rules and recovery policies are not established.
12 atomic answers

Sources: harness-by-autonomous:capacity, harness-by-autonomous:crew, harness-by-autonomous:merge, harness-by-autonomous:swarmv4

Human collaboration and control

Agent cross-checked partial

Members share visibility into Swarm work (channel reads, watch/join, told notes) with discussion across channels, task chats, threads and 1:1 agent chats; people comment via GitHub and CLI verdicts since channels are agents-only for posting. Simultaneous co-steering, presence, ordering and plan-tiering do not exist; async progress never needs the owner online.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Co-prompting, presence, ordering/conflict handling and plan restrictions do not exist.
11 atomic answers

Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:mobile, harness-by-autonomous:notify, harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:product, harness-by-autonomous:readme

Agent cross-checked partial

Project-scoped roles (Lead, PM, members, readers/writers) carry documented rules with server enforcement, revocation and unauthorized-access refusals; sign-in is Google/Apple/QR only with no org SSO, SCIM provisioning or organization roles.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Organization roles, org SSO/SAML/SCIM, provisioning and plan-scoped controls do not exist.
9 atomic answers

Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:verdict, harness-by-autonomous:retention, harness-by-autonomous:cli, harness-by-autonomous:security, harness-by-autonomous:negsearch

Agent cross-checked partial

Command approvals ride engine permission modes with phone-side approve/answer, pair autonomy dials (watch/suggest/act-within-rules) and per-launch tokens; the dial and the merge rule permanently refuse push/force/delete/deploy/publish/drop/merge approvals while READ-OK-gated merges still land. Network/secret/tunnel specifics and approval lifetimes are only partly established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Network and secret approval specifics, approval lifetimes and temporary tunnels are not established.
14 atomic answers

Sources: harness-by-autonomous:engines, harness-by-autonomous:cli, harness-by-autonomous:notify, harness-by-autonomous:merge, harness-by-autonomous:app, harness-by-autonomous:security

Agent cross-checked partial

Device add/remove history, journaled automation, co-authored commits, signed verdicts and retained chats/decisions give attributed cross-user, cross-session history with message edits and goal writes; project deletion removes its messages. Chat export, edit rules, retention windows and integrity details beyond signed device logs and sha-bound verdicts are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Export, edit rules, retention windows and tamper-evidence breadth are not established.
11 atomic answers

Sources: harness-by-autonomous:security, harness-by-autonomous:cli, harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:swarmv4, harness-by-autonomous:agentcli

Agent cross-checked partial

Wait lists, Needs-you badges and PR groupings locate pending reviews; recaps, transcripts, task/PR links and Hub outputs navigate evidence; READ-OK/HOLD plus told notes carry comments, change requests and shipping guidance; task sizes estimate effort; full keyboard remap and the phone app cover narrow screens; context persists across switching.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Unified evidence navigation, missed-evidence handling, reviewer-role display and cross-epic switching cost are not established.
13 atomic answers

Sources: harness-by-autonomous:app, harness-by-autonomous:notify, harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:cli, harness-by-autonomous:tasktokens, harness-by-autonomous:crew, harness-by-autonomous:keyboard, harness-by-autonomous:mobile, harness-by-autonomous:swarmv4, harness-by-autonomous:handson

Agent cross-checked partial

A colleague cannot take over a live session (identity rule: an agent runs only under its own person's login), so takeover is by handoff: sealed handoff files with degraded modes, Switch PM ownership transfer, co-authored attribution and continued work after disconnect. Runtime-context transfer limits and decision/artifacts edge details are partial.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Live same-session takeover is forbidden by rule; runtime transfer and context completeness are partial.
12 atomic answers

Sources: harness-by-autonomous:swarmv4, harness-by-autonomous:cli, harness-by-autonomous:merge, harness-by-autonomous:mobile

Verification and delivery

Agent cross-checked partial

Typst review ZIPs, viewer captures, Hub portable snapshots with a public gallery, PR-side verdict/merge/cost notes, retained transcripts/handoffs/chats and redacted, never-prompt-carrying handoffs cover artifacts; media previews stream in chunks. Product code-diff galleries, recordings, test-output retention and chat export are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Code-diff galleries, session recordings, test-output retention and chat export are not established.
13 atomic answers

Sources: harness-by-autonomous:handson, harness-by-autonomous:webapp, harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:tasktokens, harness-by-autonomous:cli, harness-by-autonomous:swarmv4, harness-by-autonomous:mcp

Agent cross-checked partial

Delivery runs on enforced gates: every check green plus a non-writer READ-OK with no standing HOLD on the exact head, or no merge. The rule, its train and its told notes are product code; spec conformance gates do not exist (no specs), and check suites themselves are the projects' own.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
official-integration
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Spec gates do not exist; check suites are project-defined, product-enforced.
11 atomic answers

Sources: harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:negsearch

Agent cross-checked partial

Branch-per-harness and worktree-per-harness are the product model; agents commit and open PRs with the person's login; Harness posts verdicts, merges and told notes, reads CI state, detects conflicts/behind states and links tasks to PRs. Rebase execution and full product-state depth are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
official-integration
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Product-executed rebase and unified product-state depth are not established.
9 atomic answers

Sources: harness-by-autonomous:readme, harness-by-autonomous:cli, harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:crew, harness-by-autonomous:shipping

Agent cross-checked partial

Merges are product-executed by rule (train, exact head, person's login) with sha-bound approvals and HOLD vetoes; agents can never merge. Releases and production deploys are not product paths, and pair automation permanently refuses deploy-type approvals.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
official-integration
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Release and deployment authority do not exist as product paths.
6 atomic answers

Sources: harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:cli, harness-by-autonomous:negsearch

Agent cross-checked partial

Task-PR co-authored links, cost lines and merge notes give completion evidence with sha-bound approvals that die on new heads; revert titles count against PRs. Build/deployment links, rollback and product build-link depth are not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
official-integration
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Build/deployment linkage, rollback execution and stale-approval edge beyond sha rebinding are not established.
9 atomic answers

Sources: harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:shipping, harness-by-autonomous:tasktokens, harness-by-autonomous:crew, harness-by-autonomous:cli

Agent cross-checked partial

The merge train is a dependency-aware delivery queue (lands-after ordering, combined checks, per-head notes, retry-backoff reads) with sha-bound approvals, HOLD change requests, size/effort signals and hot-file warnings; human batch-review UI depth (summaries, grouping, artifact navigation) is not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Human batch-review UI (summaries, grouping, artifact navigation, next-action queues) is not established.
12 atomic answers

Sources: harness-by-autonomous:merge, harness-by-autonomous:verdict, harness-by-autonomous:crew, harness-by-autonomous:tasktokens, harness-by-autonomous:cli, harness-by-autonomous:swarmapi

Ownership, privacy and economics

Agent cross-checked partial

The whole repo (app, CLI, daemon, relay, backend, device, store) is MIT-licensed public source at the pinned tag; upstream tools keep their own licenses. Hosted backend/relay parity is not established from the outside, and the GitHub App/extension packaging is configuration, not a license exception.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Hosted parity and per-component license exceptions are not established.
6 atomic answers

Sources: harness-by-autonomous:license, harness-by-autonomous:readme, harness-by-autonomous:naming, harness-by-autonomous:repometa

Agent cross-checked partial

Everything runs on your machines with no account for local work; the MIT sources include backend containers for self-hosting the account/relay side, and Hub snapshots, log export and on-disk transcripts port out while hub/import and repo cloning port in. Account deletion is by email; history portability from the backend is not established.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Backend-side history portability and fine-grained export (chats) are not established.
8 atomic answers

Sources: harness-by-autonomous:readme, harness-by-autonomous:mcp, harness-by-autonomous:license, harness-by-autonomous:webapp, harness-by-autonomous:cli, harness-by-autonomous:privacy, harness-by-autonomous:security

Agent cross-checked partial

Code and prompts stay E2EE-sealed with keys the relay never holds; credentials live in tmux env/0600 files with redacted handoffs; push goes through Apple/Google and transport over Cloudflare. Training use of Harness data, retention windows, residency, subprocessors beyond those named and telemetry controls are not disclosed.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Training, retention, residency, full subprocessor list and telemetry controls are undisclosed business/hosted facts.
15 atomic answers
  • Code data [supported] Code crosses machines as E2EE ciphertext (ChaCha20-Poly1305, X25519, pinned Ed25519); the relay forwards bytes it cannot read. Sources: harness-by-autonomous:readme.
  • Prompts [partial] Same sealed terminal/relay path for prompts; handoff replies never carry prompt text. Sources: harness-by-autonomous:readme, harness-by-autonomous:cli.
  • Credentials [supported] Grid keys in tmux env never argv/file; 0600 hook credentials; QR-approval and key-log visibility rules. Sources: harness-by-autonomous:engines, harness-by-autonomous:cli, harness-by-autonomous:security.
  • Logs [partial] File logs on devices/phones, 7-day export; log contents/retention policy otherwise unstated. Sources: harness-by-autonomous:mobile, harness-by-autonomous:cli.
  • Artifacts [partial] Artifacts persist per project/machine; artifact access policy beyond project reads is not established. Sources: harness-by-autonomous:swarmv4.
  • Retention [unknown] Harness's checked sources did not establish this atomic requirement. Retention windows are generic policy language, not Harness-data schedules.
  • Deletion [partial] Account deletion by email; project deletion removes its messages; per-record deletion is not established. Sources: harness-by-autonomous:privacy, harness-by-autonomous:swarmv4.
  • Training [unknown] Harness's checked sources did not establish this atomic requirement. No statement on training models with Harness agent/code data was found (the only training line covers support calls).
  • Residency [unknown] Harness's checked sources did not establish this atomic requirement. Data residency is not disclosed beyond Cloudflare-edge TURN routing.
  • Subprocessors [partial] Named: Apple APNs and Google FCM for push, Cloudflare TURN; a full subprocessor list is not disclosed. Sources: harness-by-autonomous:notify, harness-by-autonomous:readme.
  • Telemetry disclosure [unknown] Harness's checked sources did not establish this atomic requirement. No telemetry disclosure was found in product docs or policy.
  • Telemetry defaults [unknown] Harness's checked sources did not establish this atomic requirement. Telemetry defaults are not disclosed.
  • Telemetry controls [unknown] Harness's checked sources did not establish this atomic requirement. A documented telemetry control was not found (privacy policy alone is insufficient).
  • Provider separation [supported] Harness-vendor data and model-provider data stay apart: engine logins/keys never move into Harness; Grid asks the Harness backend only who holds a session. Sources: harness-by-autonomous:engines, harness-by-autonomous:security.

Sources: harness-by-autonomous:readme, harness-by-autonomous:cli, harness-by-autonomous:engines, harness-by-autonomous:notify, harness-by-autonomous:privacy, harness-by-autonomous:security

Agent cross-checked partial

Harness software is MIT open source and free to download with no paid plan found; agents run on your own existing subscriptions and Harness sells no tokens. No priced dimensions (currency, intervals, seats, usage, overages, taxes) are stated; hardware devices are priced separately ($129/$299) outside ADE billing.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Priced dimensions are absent because no paid software plan exists in the checked sources; no purchase or billing test was run.
12 atomic answers
  • Currency [unknown] No first-party source states currency for a paid software plan. The store prices hardware in USD; no ADE billing exists. Checked download page, site, README/LICENSE/releases.
  • Interval [unknown] No first-party source states a billing interval; no subscription exists.
  • Seats [unknown] No first-party source states seats; membership is per account without tiers.
  • Seat minimum [unknown] No first-party source states a seat minimum.
  • Workspace fees [unknown] No first-party source states workspace fees.
  • Included usage [unknown] No first-party source states included usage; use is unlimited local execution.
  • Credits [unsupported] No credits are sold or mentioned; agent spend is provider-side. Sources: harness-by-autonomous:negsearch, harness-by-autonomous:gridstore.
  • Trial [unknown] No trial is stated; the product itself is free.
  • Overages [unknown] No first-party source states overages.
  • Taxes [unknown] No first-party source states taxes treatment.
  • Model cost [supported] Agent cost is your own existing subscriptions or API-style logins, handled provider-side; Harness shows estimates, never bills. Sources: harness-by-autonomous:engines, harness-by-autonomous:tasktokens.
  • Compute cost [unknown] No first-party source states compute cost; execution is on user machines.

Sources: harness-by-autonomous:license, harness-by-autonomous:desktopdl, harness-by-autonomous:site, harness-by-autonomous:readme, harness-by-autonomous:engines

Agent cross-checked partial

One, two or five developers run the free download on their own machines with their own engine subscriptions; no fixed/variable product charges exist, so scenarios carry only BYO provider/compute unknowns. No workload, concurrency, token or compute-hour assumptions are published by the vendor.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Vendor-published workload assumptions do not exist; provider-side costs stay unknown. No invented average task cost is used.
11 atomic answers
  • One person [partial] One developer: $0 product cost on their own machine; provider subscription unknown. Sources: harness-by-autonomous:license, harness-by-autonomous:desktopdl.
  • Two people [partial] Two developers collaborating in a Swarm: $0 product cost; provider subscriptions unknown. Sources: harness-by-autonomous:license, harness-by-autonomous:swarmv4.
  • Five people [partial] Five developers: $0 product cost; provider subscriptions and own hardware unknown. Sources: harness-by-autonomous:license, harness-by-autonomous:swarmv4.
  • Task assumptions [unknown] Harness's checked sources did not establish this atomic requirement. No vendor task/concurrency/token/compute-hour assumptions are published.
  • Concurrency [unknown] Harness's checked sources did not establish this atomic requirement. No vendor concurrency assumptions are published (lists keep 3 deep by rule, not priced).
  • Tokens [unknown] Harness's checked sources did not establish this atomic requirement. No vendor token assumptions are published; per-task counts are measured, not priced.
  • Compute hours [unknown] Harness's checked sources did not establish this atomic requirement. No vendor compute-hour assumptions are published.
  • Fixed cost [supported] Fixed product cost is $0 (MIT download; optional hardware aside). Sources: harness-by-autonomous:license, harness-by-autonomous:site.
  • Variable cost [supported] Variable product cost is $0; only BYO provider/compute spend varies. Sources: harness-by-autonomous:license, harness-by-autonomous:engines.
  • Included cost [supported] Everything product-side is included at $0. Sources: harness-by-autonomous:license.
  • Unknown cost [supported] Unknown: provider subscriptions/API spend and own-hardware cost. Sources: harness-by-autonomous:engines.

Sources: harness-by-autonomous:license, harness-by-autonomous:desktopdl, harness-by-autonomous:readme, harness-by-autonomous:engines, harness-by-autonomous:tasktokens

Agent cross-checked partial

Desktop 1.4.49 and CLI 0.6.56 shipped 2026-11-13 on a near-daily cadence with public downloads and auto-update; the provider-protocol changelog runs additive/breaking revisions with deprecation service; support is GitHub issues plus site chat/community with no stated commitments; no status page or history was found; removed Swarm v2 surfaces answer empty for 30 days.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Support commitments, status history and full deprecation/export coverage are not established.
8 atomic answers

Sources: harness-by-autonomous:release, harness-by-autonomous:releases, harness-by-autonomous:desktopdl, harness-by-autonomous:protocol, harness-by-autonomous:site, harness-by-autonomous:swarmv4

No sourced public finding not-published

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

Agent cross-checked partial

The MIT desktop download is a free, ongoing tier for macOS, Windows and Linux with no paid plan, card or evaluation purchase; local harnesses need no account. Trial, credits-trial and paid-evaluation questions do not apply to a free product and are answered negatively; provider-side subscription limits still apply to agent work.

Scope
Surfaces: Harness desktop app (Flutter: macOS, Windows, Linux), Harness web workspace (Flutter web at harness.autonomous.ai), Harness phone app (Flutter: iOS, Android), Harness CLI + daemon + hn TUI (macOS, Linux, Windows launcher), Harness device (ESP32-S3 companion display, USB-linked) · Version: Pinned release v1.4.49_desktop (commit edd86652117e1adf469aaaa761963295f071e156, 2026-11-13); CLI v0.6.56 and backend release from the same repo; first-party source pass 2026-11-13. Desktop/web/mobile share one Flutter codebase; daemon+CLI are managed Node; hn TUI and installer are Rust. · 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
2026-11-13
  • Provider-side subscription limits still apply. No purchase test was run.
10 atomic answers

Sources: harness-by-autonomous:license, harness-by-autonomous:desktopdl, harness-by-autonomous:mcp, harness-by-autonomous:engines, harness-by-autonomous:swarmv4, harness-by-autonomous:releases

No sourced public finding not-published

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

Sources

harness-by-autonomous:readme

Harness README (pinned release)

One command center over agents on many machines: 14 named engines plus seven more; per-machine daemon in tmux; worktree per harness; E2EE relay holding no keys; CLI+harness skill install; local models via Grid/Ollama/MLX-LM/vLLM; 49 store harnesses; open-source MIT app/CLI/daemon/relay/device in this repo.

Kind
documented
Locator
Every agent side by side; Every machine side by side; End-to-end encrypted; Get started; Beyond code; Harness device; store catalog
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:app

The app (pinned release)

Harness = one engine session in one tmux pane; tabs mix machines; app state remembered in state.json. Models menu shows each engine's subscription usage window refreshed 1/min; Settings Usage is a token ledger from Claude/Codex transcripts and OpenCode DB, off per provider until switched on. Amber ring + titlebar bell + Shift-Cmd-I waiting list. Machines link with per-machine password; All-machines shared desk.

Kind
documented
Locator
Sessions; Panes and layouts; Attention, models, usage; Machines
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:cli

The daemon and CLI (pinned release)

harness login/start/stop/status/update, dsh, machines, swarm list/status/machines/agents/starts, link, remote, devices, grid login/env, tui, logs export. Daemon loopback REST+WS (127.0.0.1:18473, X-Harness-Local credential, localProtocolVersion 1) with agents_list/agent_create/agent_restart/agent_retarget/agent_delete/read/send/cancel/terminal_open and more; serves no web page and never a transcript. pair verbs answer/send/stop/pause/resume gated by per-launch token plus autonomy dial (watch/suggest/act-on-key/act-within-rules) that never approves push/force/delete/deploy/publish/drop/merge. pair mcp serves the same tools over stdio.

Kind
documented
Locator
Command table; Automation; pair verbs; autonomy dial; mcp
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:desktopdl

Desktop download page

Desktop app for macOS (12+, arm64+Intel dmg, Apple-signed/notarized), Windows and Linux (x64/ARM64); terminal install.sh path for macOS and Ubuntu 22.04+; CLI-only path for servers; self-updates. Retrieved 2026-11-13.

Kind
documented
Locator
Title; macOS 12+ requirement; mac/Windows/Linux downloads; install.sh
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:release

Harness Desktop 1.4.49 release

v1.4.49_desktop published 2026-11-13 lists every desktop build: macOS arm64 dmg, macOS Intel dmg, Linux x64 + arm64 AppImages, Windows installer (x64+ARM64) and Windows x64/ARM64 zips. Already-running copies self-update.

Kind
documented
Locator
Downloads table; self-update note
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:mobile

Harness phone app (pinned release)

Flutter iOS/Android viewer: one harness at a time; reads/sends/start/stop; voice input; approvals; 1:1 agent chats; desk sync with 15s foreground polls; swarm posting/answering works while every account machine is offline; retry keeps one operation id.

Kind
documented
Locator
Viewer; account swarms; Swarm experimental; phone notifies
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:mobilerelease

Releasing the mobile app (pinned release)

App Store record Autonomous Harness (ai.autonomous.harness.ios); dated build log of TestFlight uploads (1.0.0 builds 17-48, Sept 2026) with Play-only builds noted (16, 41 went to Play only).

Kind
documented
Locator
App Store record; TestFlight and Play build log
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:appstore

App Store lookup (Autonomous Harness)

Apple lookup returns resultCount 1 for bundle ai.autonomous.harness.ios under Autonomous Inc.: a live App Store listing. Retrieved 2026-11-13.

Kind
documented
Locator
resultCount; artistViewUrl Autonomous Inc.
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:webapp

Harness web routes (pinned release)

harness.autonomous.ai serves the Flutter app (workspace front door, sign-in return, hn view links); /pair phone setup; /app redirects iPhone/iPad to App Store and Android to Google Play; /hub public gallery with publish/fork/download/snapshot/import; /agents install + commands + plugin/skill.

Kind
documented
Locator
Routes table: Flutter web workspace; /pair; /app store redirect; /hub publish/gallery; /agents
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:mcp

Harness as MCP server (pinned release)

npm @autonomous-ai/harness-mcp runs harness mcp: harness_whoami/list/search/machines/start/wait/read/close. An agent may give work to, and close, only harnesses it started. Needs the Harness CLI on PATH; MIT.

Kind
documented
Locator
Tool table; install; plugin note
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:notify

Phone notifications (pinned release)

Push via Apple APNs/Google FCM plus local notices; rings only when the person must act (command approval, unknown-device sign-in, own agent's 1:1 chat); finished turns and stuck/needs-you are badge-only; per-chat Mentions-only default; one task one notification slot.

Kind
documented
Locator
Push vs local; rings vs badge-only; 1:1 chats; mention defaults
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:tui

hn terminal client (pinned release)

hn is all of Harness in a terminal with tmux keys and ~/.tmux.conf; shell-first flow with computer (ch) and model-route (cm, Codex/Claude) pickers; same hn binary powers the Harness OS image (Try/Install, agents/terminals/Wi-Fi).

Kind
documented
Locator
tmux keys; shells; model routes; OS image note
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:negsearch

Bounded no-implementation search (pinned release)

Bounded search at the pinned commit found no implementation for: user-facing schedules/cron/recurring triggers or completion conditions (only internal poll/backoff timers); webhooks (only prose false positives); public SDK (only CLI, MCP server, loopback API); custom engine adapters (fixed 14-engine table); container/VM/OS-sandbox workload isolation (only backend self-host docker files); org SSO/SAML/SCIM/OIDC (only Google/Apple/QR login); SOC2/ISO claims; billing/purchase/subscription-tier code; epic/parent-child task entities; persistent requirements/spec entities with approvals; product code-diff review surface; export of chats; revert/rollback commands. Search terms: schedule, cron, recurr, webhook, sdk, custom engine, adapter, docker, container, lxc, gvisor, firecracker, vm, sandbox, sso, saml, scim, oidc, soc 2, iso 27001, bill, stripe, checkout, seat, plan, epic, subtask, requirement, spec, diff viewer, revert, rollback.

Kind
source-inspected
Locator
Grep across cli/src, backend/src, desktop/lib, mobile/lib, tui/src, docs, website/src at the pinned commit
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src
harness-by-autonomous:engines

Supported engines (pinned release)

Exactly 14 engines with binary, follow-method, resume and auto-approve flags: Claude Code, Codex, Cursor, OpenCode, Pi, Hermes, Command Code, Devin, Muse Code, Amp, Kilo, Grok Build, Antigravity, GitHub Copilot. Credentials stay in ~/.claude, ~/.codex, etc. Grid retarget respawns the pane with grid env; needs tmux >= 3.2.

Kind
documented
Locator
Engine table; Auto-approve; Grids
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:gridstore

Grid wrapper (pinned release)

Autonomous-grid store entry wraps the MIT upstream CLI unmodified with viewer and integration new; no price, credits, trial or billing terms stated anywhere in the entry.

Kind
documented
Locator
MIT upstream wrap; no price or credits stated
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:security

Security (pinned release)

Every signed-in device publishes its identity key to the account device log; new devices stay marked New until confirmed; QR-approved computers inherit terminals (billing still needs Google/Apple sign-in; Grid control plane asks Harness backend who holds the session).

Kind
documented
Locator
Device key log; It is mine; QR sign-in; Grid handoff
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:site

Harness product page

Store page: Harness Pro desk display $299, Harness Device $129, Harness App free download; footer offers Chat with us plus GitHub/X/Reddit links. Retrieved 2026-11-13 via curl HTML and one successful rendered fetch (page intermittently timed out headless rendering; curl HTTP 200 content + screenshot agree).

Kind
documented
Locator
Harness Pro $299; Harness Device $129; App free download; Chat with us
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:capacity

Start requirements (pinned release)

START_REQUIREMENTS: 2 GiB RAM, 10 GiB disk, maxCpuPercent 100 (momentary CPU never gates), tools include git, quotaRequired false; per-machine capability probe reports tools/devices; unverified tool only blocks with reason.

Kind
source-inspected
Locator
START_REQUIREMENTS; capability probe; no CPU cap
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/superTabs/capacity.ts
harness-by-autonomous:agentcli

Agent command verbs (pinned release)

harness super-tab verbs: messages/message/post, answer, screen, type, read ok|hold (READ-OK/HOLD verdicts), take (claim), split, goal write. Stdin forms, idle refusals, per-run operation ids.

Kind
source-inspected
Locator
post/read/split/take/goal/answer/screen/type verbs; read ok/hold verdicts; take claims; goal write
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/superTabs/command.ts
harness-by-autonomous:mcpserver

harness mcp stdio server (pinned release)

MCP server on stdin/stdout for agents reaching tools through MCP; each call runs the verb as harness itself; one caller per server, never the person; newline-delimited JSON-RPC 2.0.

Kind
source-inspected
Locator
One server per agent session; verbs run as harness; outsideCaller scoping; protocol versions
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/agentClient/mcp.ts
harness-by-autonomous:mcpclient

Machine MCP servers (pinned release)

Local stdio MCP servers attached to every agent Harness starts on the machine (e.g. lamp-mcp); kept in the machine data dir only, read at each launch; per-engine and per-project scoping; an agent may not change it.

Kind
source-inspected
Locator
harness mcp-servers add/remove; per-engine/per-project scoping; machine data dir only
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/agentClient/mcpServers.ts
harness-by-autonomous:swarmv4

Swarm v4 plan (approved 2026-11-08)

Slack for agents: people add agents, agents work together, people read along and talk only to their own agents. PM agent makes tasks (goal+chat) and assigns; agent takes next when free; messages go into named sessions as @sender lines; only agents post in channel/task chats; server enforces who reads a project; agent runs only under its own person's login; removed v2 surfaces answer empty 30 days.

Kind
documented
Locator
Model: agent/PM/tasks/channel/messages; Desktop; Remove; Design: audience/identity/compatibility
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:plugin

Agent plugin (pinned release)

harness plugin for Claude Code, Codex, Cursor: skills/harness/SKILL.md (when to use Harness vs subagents, commands, rules) + MCP server files; marketplace add/install lines; Codex runs tools without asking; Cursor loaded from local folder.

Kind
documented
Locator
Claude/Codex/Cursor install; SKILL.md; MCP files; Codex default approval
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:naming

Naming system (pinned release)

Software product Harness; open-source project/repository OpenHarness; terminal command hn, daemon harnessd; interfaces: desktop, web, mobile, terminal, OS image, device companion; Grid inference network. Agents do the work; conversation directs them.

Kind
documented
Locator
Product names; Work and interface terms
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:clients

Desktop and mobile Flutter apps (pinned release)

Desktop and mobile are Flutter apps in this repo: desktop/ targets macOS, Linux, Windows and web; mobile/ targets Android and iOS; hn TUI is Rust (tui/Cargo.toml) and the installer is Rust (installer/Cargo.toml).

Kind
source-inspected
Locator
Flutter; desktop macos/linux/windows/web dirs; mobile android/ios dirs
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
desktop/pubspec.yaml
harness-by-autonomous:product

Harness: what we build (pinned release)

A Swarm is a project anyone can join with their own agents on their own computers and subscriptions; PM agent decides work and gives each task to the agent that can ship soonest; another agent reads every change, tested before landing. Chat for people talking to people is not built; no own agent/model; no locking to one lab or servers.

Kind
documented
Locator
Swarm definition; Positioning; Never/Not built lists
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:merge

Merge-by-rule (pinned release)

Harness merges a Swarm v4 team's PRs by rule with the PM person's own gh login: ready = not draft + non-writer READ-OK on head + no HOLD + all checks green + mergeable + lands-after ordering. Ready ones land on a train (one combined checks run). Agents never merge. Behind/conflict/failed heads are told so on the PR by name.

Kind
source-inspected
Locator
Ready-to-land rule; train; told-on-PR; agents never merge
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/superTabs/githubMerge.ts
harness-by-autonomous:verdict

Verdict writes (pinned release)

read ok|hold posts READ-OK/HOLD naming the head sha; a moved head is refused HEAD_MOVED 409 (read that head, run again); same verdict in same words on same head within the hour is not reposted.

Kind
source-inspected
Locator
read ok/hold on head sha; HEAD_MOVED 409; same-verdict dedupe
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/superTabs/githubVerdict.ts
harness-by-autonomous:crew

Task model (pinned release)

Task sizes s/m/l carry minutes/ram/disk/spend; priorities p0/p1/p2 weighted; CLAIM_LIMIT 4; QUOTA_WAIT 120 min; dependsOn task numbers; builder: labels; teamOf; tasksOf links PRs to tasks.

Kind
source-inspected
Locator
SIZES minutes/ram/disk/spend; WEIGHTS p0/p1/p2; CLAIM_LIMIT; QUOTA_WAIT; dependsOn; builder labels; tasksOf
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/superTabs/assign/crew.ts
harness-by-autonomous:tasktokens

Per-task token accounting (pinned release)

A conversation's used input/output/cacheRead/cacheWrite counts per model feed per-task rows; costLine says a landed change's rows on its PR; at most COST_NUMBERS rows read per repo.

Kind
source-inspected
Locator
Counts per model per task; used(); costLine posts on PRs; COST_NUMBERS
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/superTabs/taskTokens.ts
harness-by-autonomous:retention

Roster retention (pinned release)

Unconfirmed roster lapses after 7 days (signed-out/unlinked machine); a project's Lead never lapses; assigned harnesses kept through ASSIGNED_GRACE after first assignment; unreadable retention fails closed to cleanup pause.

Kind
source-inspected
Locator
7-day lapse; Lead never stopped; assigned grace
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/superTabs/retention.ts
harness-by-autonomous:shipping

Completion reads (pinned release)

Completion reads an agent's labels: a PR that closes it merged under the person's own login; a revert is found by Revert in its title; a fixed post-merge window still counts reverts against the PR.

Kind
source-inspected
Locator
Merged-under-own-login; revert-in-title detection; first-week revert window
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
cli/src/superTabs/shippingRead.ts
harness-by-autonomous:memory

Memories agent (pinned release)

Memories reads Claude Code, Codex, Grok Build and Hermes memory dirs plus a year of Harness session index in one place; lake colored by agent and project; Recall searches memories and messages; opening sends no prompt and changes nothing.

Kind
documented
Locator
Cross-engine memory lake; Recall; read-only opening
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:handson

Hands-on sessions (pinned release)

Each craft page links the unedited real-session recording and the pane screenshot (incl. doc-review.png: real Typst PDF with review notes carried into a later revision) plus the agent direction prompt that produced it.

Kind
documented
Locator
Real-session videos and panes incl. Typst review; directions with prompts
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:keyboard

Keyboard map (pinned release)

Every key remappable in one JSONC file reloaded on save (chords to four strokes); Cmd-P/Open Project/Swarm pickers with previews; paused harness resumes on open; Ctrl-S lifecycle shortcuts.

Kind
documented
Locator
Remappable JSONC; pickers; lifecycle shortcuts
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:swarmapi

Swarm task/token API shapes (pinned release)

Route validation: per-task token rows name repository, issue number, kind, per-model input/output/cache counts, rounds and start/end instants; task offers carry a one-word decline reason; comment records track agent-posted GitHub PR comments by repo and numeric id.

Kind
source-inspected
Locator
taskTokensBody counts per model per task; taskOffers with decline reasons; agent-posted PR comment records
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
backend/src/routes/superTabs.ts
harness-by-autonomous:license

MIT License (pinned release)

Single MIT license at the repo root granting the software including all in-repo components; copyright 2026 Autonomous, Inc.; cli/package.json also carries MIT.

Kind
documented
Locator
MIT grant; 2026 Autonomous, Inc.
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:costs

Hand-reviewed model prices (pinned release)

API list prices in USD per million tokens for catalog models (Anthropic/OpenAI/OpenRouter sources, checked 2026-10-29/30); a model not listed has no cost, never guessed; cache-write 5-minute rate; Grid models at OpenRouter rates.

Kind
source-inspected
Locator
USD-per-MTok rows with provider source and checked day; unlisted = no cost
Source date
Not stated
Retrieved
2026-11-13
Commit
edd86652117e1adf469aaaa761963295f071e156
Path
backend/src/superTabs/costs/prices.ts
harness-by-autonomous:repometa

OpenHarness repository page

Autonomous-ai/openharness: The ultimate harness for coding agents and beyond; 1,485 stargazers and 145 forks observed 2026-11-13 (GitHub API same day); homepage https://www.autonomous.ai/harness; topics include agent-harness, coding-agents, mcp-server; pushed 2026-11-13.

Kind
documented
Locator
1,485 stars observed 2026-11-13; description; homepage link
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:privacy

Autonomous privacy policy

Company-wide policy: review/update account info any time; deactivate or delete the account by email; retains personal information while services are used or as needed; cookie/technology opt-out via browser/device; record-and-store support calls for training; no statement on training models with Harness agent/code data. Retrieved 2026-11-13.

Kind
documented
Locator
Account deletion by email; generic retention; Technologies opt-out; no Harness-data training statement
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:protocol

Provider protocol changelog (pinned release)

Spec changelog is a compatibility contract: additive changes are safe, breaking ones get a new revision served alongside the old with a deprecation window; 0.3.0 the first built-against revision.

Kind
documented
Locator
0.3.0 contract; additive vs breaking; deprecation service
Source date
Not stated
Retrieved
2026-11-13
harness-by-autonomous:releases

Release index

Release index shows desktop 1.4.49 and CLI 0.6.56 cut 2026-11-13 with same-day predecessors: near-daily shipped cadence, notes describe shipped changes only, no future commitments.

Kind
documented
Locator
v1.4.49_desktop + v0.6.56_cli on 2026-11-13; daily cadence; shipped notes
Source date
Not stated
Retrieved
2026-11-13

Comparisons with Harness by Autonomous

Compare Harness by Autonomous with any other product on adecomparison.com.