50 of 51 criteria have a sourced finding; 47 were also cross-checked by a second agent. Every comparison that includes Poracode 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.
Electron desktop app for macOS (DMG, Apple silicon and Intel), Windows (NSIS x64/Arm64) and Linux (AppImage/.deb x64); web/PWA and a CLI/TUI connect to a host; Chrome-family sidebar extension. Native SwiftUI iOS and Compose Android clients exist in the repository, but only a TestFlight upload and an optional Play internal track are documented and no mobile binary is attached to the releases, so public availability is not established.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve), Web app / PWA served by the host, Native iOS client (SwiftUI), Native Android client (Compose), Chrome/Brave/Edge sidebar extension · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
Not separately cross-checked
Not fully established or not supported: editor_extensions; see atomic answers.
9 atomic answers
Desktop os [supported] Installers for macOS (DMG), Windows (NSIS x64/Arm64) and Linux (AppImage, .deb x64); minimum OS versions are not stated in the README. Sources: poracode:readme, poracode:faq.
Mobile apps [partial] Independent native SwiftUI iOS and Compose Android clients (ios/, android/) pair with a host and have a parity ledger; the release docs describe a TestFlight upload and an optional Google Play internal track, and the GitHub releases attach no APK, AAB or IPA, so a public store listing or download is not established. Sources: poracode:agentsmd, poracode:mobile, poracode:native, poracode:rev-relmobile, poracode:rev-relassets.
Browser [supported] Web app served by the standalone server and desktop host (`poracode serve --open`), also an installable PWA. Sources: poracode:readme, poracode:arch.
Mobile browser [supported] Mobile web/PWA is a supported client surface ("desktop browser, mobile browser/PWA, native iOS, native Android"). Sources: poracode:agentsmd, poracode:remotearch.
Editor extensions [partial] Chrome/Brave/Edge sidebar extension with chat and browser tools; no IDE (VS Code/JetBrains) extension found (Monaco editor is built into the app). Sources: poracode:ext, poracode:readme.
Task actions [supported] Clients can start, steer, stop and resume threads, resolve approval requests (scope requests:resolve), read terminals and open PR/diff review; viewer scope is read-only. Sources: poracode:readme, poracode:scopes, poracode:remotearch.
Notifications [supported] OS notifications on desktop and optional push to iOS/Android/web via the host and poracode.com push forwarding. Sources: poracode:privacy, poracode:readme.
Cross device continuity [supported] Host owns sessions; paired desktop, browser, iOS and Android clients project the same threads and reconnect through replay/snapshot recovery. Sources: poracode:remotearch, poracode:arch.
Embeds or launches 15+ named harnesses through per-provider adapters (terminal PTY, ACP, SDK or CLI runtimes) plus any ACP-registry or custom ACP agent; crossagent delegation mixes harnesses.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
5 atomic answers
Harnesses [supported] Claude, Codex, OpenCode, Gemini, Grok, Kimi Code, Qwen Code, Pi, Qoder, Factory Droid, Antigravity, Cursor, Command Code, Copilot and fx (README); registry also has DeepSeek, Devin and Muse adapters. Sources: poracode:readme, poracode:registry.
Model providers [supported] Models come from each harness; custom model providers can be configured (contracts/modelProviders.ts) and CLI has cliCustomProviders. Sources: poracode:registry, poracode:readme.
Custom adapters [supported] Any agent in the Agent Client Protocol registry or a user-defined acp-generic instance can be installed and run from settings. Sources: poracode:readme, poracode:registry.
Session integration [supported] Terminal-presentation threads run a real PTY of the agent CLI; GUI threads use the provider structured runtime (ACP/SDK/app-server); user picks the runtime where several exist. Sources: poracode:agentsmd, poracode:readme.
Mixed harness operation [supported] Crossagents lets one agent delegate to another provider and experiments run one prompt across several agents in parallel worktrees. Sources: poracode:readme, poracode:crossagent, poracode:experiment.
Bring your own: uses each provider CLI/SDK login and API keys directly from the machine; no vendor credits, no Poracode account; local models only through harnesses that support them.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: vendor_credits, local_models, account_switching, provider_restrictions; see atomic answers.
7 atomic answers
Agent subscriptions [supported] Existing Claude Max, ChatGPT Pro and similar subscriptions are used through each agent login; Live Usage shows session/weekly quota. Sources: poracode:readme, poracode:faq, poracode:usagepkg.
Api accounts [supported] README: "Bring your own agent subscriptions & API keys". Sources: poracode:readme, poracode:faq.
Vendor credits [unsupported] No Poracode credits, paid tier or licence key exist; the FAQ says no paid tier and calls are made directly to providers. Sources: poracode:faq, poracode:srch-team.
Local models [partial] Local models are possible only when an installed harness (for example OpenCode or custom ACP agents) supports them; Poracode adds no local-model runtime of its own (on-device Whisper is voice input only). Sources: poracode:readme, poracode:registry.
Account switching [partial] Agent profile adapters exist for Claude, Codex, Cursor, Gemini and Devin (agentProfiles contracts, profiles.ts), allowing separate logins; breadth per provider not enumerated. Sources: poracode:registry.
Vendor account requirement [supported] No Poracode account is required; each provider account is the only login (privacy policy: hosts are user-controlled). Sources: poracode:faq, poracode:privacy.
Provider restrictions [unknown] Provider terms on third-party harness use are not documented in the repository; they are governed by each provider. Sources: poracode:readme.
Install, add a project folder, install agent CLIs, start a thread; remote machines via SSH config or a standalone server on a VPS; no managed cloud.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: no_git, prerequisite_guidance, managed_cloud_setup; see atomic answers.
7 atomic answers
First task setup [supported] README Getting Started: install Poracode, install the agent CLIs you want, open Poracode, add a project and start. Sources: poracode:readme.
No git [partial] Home project scope exists for chats without a repository; whether arbitrary non-Git folders run agents is not stated, and worktree features need Git. Sources: poracode:arch, poracode:agentsmd.
Local git without remote [supported] Git operations run locally through the supervisor (status, commit, worktrees); remotes are needed only for PR features. Sources: poracode:git, poracode:arch.
Hosted git [supported] GitHub, GitLab, Bitbucket, Azure DevOps and Gitea adapters for PRs and reviews. Sources: poracode:forges, poracode:mcpreg.
Prerequisite guidance [partial] README tells the user to install agent CLIs; Linux `libatomic1` and Node requirements are documented for the CLI installer; no consolidated checklist per provider. Sources: poracode:readme, poracode:standalone.
Managed cloud setup [unsupported] No vendor-managed cloud runtime found in a bounded source search. Sources: poracode:srch-cloud, poracode:faq.
Byo vps onboarding [supported] "Remote Machines over SSH" installs Poracode runtime on a host from the user SSH config; standalone server has installer, systemd/launchd units and container image. Sources: poracode:readme, poracode:standalone, poracode:envadr.
Product-owned CLI (TUI, serve, one-shot run, admin), remote HTTP/WebSocket contract with scoped tokens, and built-in MCP servers that let agents control the app; no public SDK or webhooks.
Scope
Surfaces: Poracode CLI, TUI and standalone server (poracode serve), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: sdk, webhooks, stability; see atomic answers.
8 atomic answers
Cli [supported] `poracode` CLI with TUI, serve, run/-p, admin and host-run commands (src/server/cli*.ts). Sources: poracode:clipkg, poracode:standalone.
Api [supported] Authenticated remote-v3 HTTP/WebSocket contract used by web, iOS and Android clients with generated bindings. Sources: poracode:remotearch, poracode:scopes.
Sdk [unsupported] No published client SDK package; packages/ holds agents-usage, codex-protocol and the launcher only. Sources: poracode:pkgjson.
Mcp server [supported] Built-in app-controls MCP and crossagent MCP expose threads, projects, Git/GitHub, schedules, skills, settings and usage to any agent. Sources: poracode:mcpreg, poracode:crossagent, poracode:readme.
Webhooks [unsupported] No inbound or outbound webhook endpoints found in a bounded search. Sources: poracode:srch-hook.
Operations [supported] MCP/CLI cover create, inspect (read_thread/read_terminal), steer, stop/interrupt, rollback and review of threads. Sources: poracode:mcpthreads, poracode:threadtools.
Authentication [supported] Pairing credential, short-lived access tokens with refresh and revocation, scope presets operator/viewer; MCP ingress is local with Host-header gating. Sources: poracode:security, poracode:auth.
Stability [partial] Remote contract is versioned (CLIENT_HOST_HOP_VERSION and remote-v3) but the product is on a nightly 2.0 train; no external API stability promise found. Sources: poracode:agentsmd, poracode:remotearch, poracode:release.
MCP client for stdio, HTTP and SSE servers with OAuth helpers, shared skills folder and marketplace, plugin catalog, ACP agents; setup is product-managed through settings or MCP tools.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: custom_tools, permission_scope; see atomic answers.
7 atomic answers
Mcp client [supported] Add your own MCP servers over stdio, HTTP or SSE; tools add/update/remove/probe/authenticate_mcp_server. Sources: poracode:readme, poracode:mcpreg.
Custom tools [partial] Custom tools arrive through MCP servers; there is no separate in-app tool-authoring API. Sources: poracode:readme, poracode:mcpreg.
Instructions import [supported] Skills can be browsed from public marketplaces or imported into one shared folder every provider picks up; AGENTS.md/CLAUDE.md are read by harnesses. Sources: poracode:readme, poracode:mcpreg.
Authentication [supported] authenticate_mcp_server and mcpServerOauth.ts handle OAuth for MCP servers; credentials stored via OS keychain/safeStorage. Sources: poracode:mcpreg.
Permission scope [partial] Per-server scopes (mcpServerScopes.ts) and per-thread MCP launch snapshot; fine-grained tool permissions mainly come from the underlying harness. Sources: poracode:mcpreg.
Integration owner [supported] Poracode manages the MCP config; harness-native MCP setup is also supported (nativeMcpSetup contracts). Sources: poracode:mcpreg, poracode:registry.
Desktop is Electron (React 19, HeroUI v3, xterm.js); web/PWA shares the renderer; iOS is SwiftUI and Android is Jetpack Compose; helpers are Rust; TUI is a separate Bun/OpenTUI-style client.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Web app / PWA served by the host, Native iOS client (SwiftUI), Native Android client (Compose), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
4 atomic answers
Desktop implementation [supported] Electron main/preload with React 19 renderer; electron-builder produces DMG, NSIS, AppImage and .deb. Sources: poracode:arch, poracode:pkgjson.
Mobile implementation [supported] Independent native SwiftUI (ios/) and Jetpack Compose (android/) clients, not React Native; mobile web/PWA also exists. Sources: poracode:arch, poracode:agentsmd.
Hybrids [supported] Same React renderer ships in Electron, desktop web and PWA; native helpers in Rust under native/; separate TUI package. Sources: poracode:arch.
Implementation evidence [supported] Official architecture doc plus pinned source directories ios/App, android/app, src/renderer and package.json. Sources: poracode:arch, poracode:pkgjson.
Threads start from local prompts, quick composer, PR watch or schedules; issue import and chat triggers are not provided; GitHub/GitLab etc. PRs are managed, not issues.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: external_import, chat_git_triggers, sync, external_roundtrips; see atomic answers.
9 atomic answers
Local creation [supported] New threads from composer, quick composer overlay, drafts and create_thread MCP tool. Sources: poracode:readme, poracode:mcpthreads.
External import [unsupported] No issue-tracker import; Linear/Jira/Asana only appear in link-label parsing. Sessions from other tools can be imported (sessionImport). Sources: poracode:srch-tracker.
Chat git triggers [partial] PR Watch reacts to a pull request; schedules start runs; no chat-app or Git-event webhook triggers. Sources: poracode:prwatch, poracode:srch-hook.
Authoritative tracker [supported] Poracode threads and project notes are local host state; no external tracker is authoritative. Sources: poracode:arch, poracode:notes.
Stable ids [supported] Threads, projects, workspaces and schedules have stable IDs addressable via MCP and API. Sources: poracode:mcpthreads.
Sync [unsupported] No sync with an external tracker found. Sources: poracode:srch-tracker.
Supported edits [supported] Thread metadata (title etc.) editable via update_thread; notes and todos editable in the app. Sources: poracode:mcpthreads, poracode:notes.
External roundtrips [unsupported] No tracker integration exists, so there is no roundtrip. Sources: poracode:srch-tracker.
Agent plan panels (e.g. Plan 2/4) aggregate harness plans; no product-owned plan editor with acceptance criteria or revisions; checkpoints rewind conversation and files.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: plans, acceptance_criteria, editors, revisions, implementation_links; see atomic answers.
7 atomic answers
Plans [partial] Plan panel (src/supervisor/agents/planAggregator.ts) shows the agent plan with step status; plans originate from the harness. Sources: poracode:img-hero, poracode:readme.
Acceptance criteria [unsupported] No acceptance-criteria field found in thread, note or plan contracts. Sources: poracode:notes.
Editors [unsupported] Plans are not user-editable objects; project notes are a separate rich-text editor. Sources: poracode:notes.
Revisions [partial] Checkpoints rewind a conversation to an earlier message and restore files; plans themselves have no revision history. Sources: poracode:readme.
Implementation links [partial] Threads carry worktree/branch and PR metadata; plan steps are not linked to commits. Sources: poracode:git, poracode:forges.
Amendment [supported] Users can steer a running thread; the agent plan updates as the harness revises it. Sources: poracode:mcpthreads, poracode:readme.
Restart persistence [supported] Sessions are saved automatically and restored after closing the app (Session Persistence). Sources: poracode:readme, poracode:arch.
No epics or task dependency graph; hierarchy is project/workspace → thread and parent→child subagent runs; crew roles constrain delegation.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: epics, hierarchy, blockers, readiness, enforcement, state_propagation, task_to_epic, identity_retention; see atomic answers.
Hierarchy [partial] Workspaces group projects; threads group by worktree; subagent runs form parent→child trees (max 16 concurrent). Sources: poracode:readme, poracode:subrun.
Blockers [unsupported] No blocker/dependency field on threads or notes. Sources: poracode:notes.
Readiness [unsupported] No readiness model beyond thread status (idle/finished/needs_approval/needs_reply/error). Sources: poracode:mcpthreads.
Enforcement [unsupported] No dependency enforcement exists. Sources: poracode:notes.
State propagation [partial] Child run output and completion stream into the parent thread; no epic-level state roll-up. Sources: poracode:subrun.
Task to epic [unsupported] No epic conversion. Sources: poracode:mcpreg.
Identity retention [partial] A thread keeps ID, history and worktree as work grows; no promotion to a larger object. Sources: poracode:mcpthreads.
Workflow constraints [supported] No mandatory workflow; crew policy crew-only/crew-first is optional. Sources: poracode:crew.
Harness-read instruction files and skills in one shared folder with marketplace; project notes; session import/export; no managed cross-session memory.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: project_docs, memory, provenance, freshness, takeover_continuity; see atomic answers.
10 atomic answers
Instructions [supported] Project guidance text and global mention guidance in settings; AGENTS.md/CLAUDE.md are read by the harnesses. Sources: poracode:readme, poracode:agentsmd.
Skills [supported] list_skills/read_skill/set_skill_enabled MCP tools; marketplace install and import into a shared skills folder. Sources: poracode:mcpreg, poracode:readme.
Project docs [partial] Per-project notes (TipTap document + to-dos) in the notes panel; not agent-maintained specs. Sources: poracode:notes.
Memory [unsupported] No cross-session or cross-harness memory store found. Sources: poracode:srch-tracker.
Scope [supported] Skills and notes are scoped per project or global; instructions per thread/project. Sources: poracode:notes.
Provenance [unsupported] No provenance/citation metadata on notes or skills beyond marketplace source. Sources: poracode:notes.
Correction [supported] Notes, todos and skills are editable in the UI. Sources: poracode:notes.
Freshness [unsupported] No stale-context controls. Sources: poracode:notes.
Takeover continuity [partial] Threads, notes and skills live on the host, so another paired client sees them; no explicit handoff feature. Sources: poracode:remotearch.
Project file search/index and built-in LSP and browser context; no managed architecture knowledge base or review-time enforcement.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: external_knowledge, freshness, api_retrieval, citations, conflict_detection, review_enforcement; see atomic answers.
10 atomic answers
Code search [supported] ProjectSearchIndex/fileIndex plus find_files and search MCP tools and @-mention of files. Sources: poracode:mcpreg, poracode:arch.
Indexing [supported] Per-project file index and watcher workers (projectWatcher, ProjectSearchIndex). Sources: poracode:arch.
External knowledge [partial] Built-in browser attaches page context; MCP servers can add knowledge; no hosted docs index. Sources: poracode:readme.
Threads, workspaces and per-project notes/to-dos; no issue objects, priorities, labels or assignees.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: create, edit, discuss, prioritize, label, assign, project_epic_views, idea_parking, explicit_dispatch, task_session_separation, metadata; see atomic answers.
17 atomic answers
Create [partial] Create threads/projects/workspaces; notes to-dos can be created, but they are not issues. Sources: poracode:notes, poracode:mcpthreads.
Agents operate on thread, project, schedule and notes-adjacent objects through MCP; there is no shared issue record, claim or dependency model.
Scope
Surfaces: Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: claim, assign, state_changes, dependencies, attribution, permissions, conflicts; see atomic answers.
Claim [unsupported] No claim operation exists. Sources: poracode:mcpreg.
Assign [partial] An agent can create a thread with a chosen provider/model (assigning work to an agent), but cannot assign to humans. Sources: poracode:mcpthreads, poracode:crossagent.
State changes [partial] stop/interrupt and send/steer change running state; statuses are derived, not set freely. Sources: poracode:mcpthreads.
Dependencies [unsupported] No dependency tool. Sources: poracode:mcpreg.
Human visibility [supported] Created threads and child runs appear in the sidebar and parent transcript. Sources: poracode:subrun.
Attribution [partial] Child output is attributed to the child thread/run; no per-field author history. Sources: poracode:subrun.
Permissions [partial] MCP ingress is local and Host-gated; assertNotSelf stops destructive self-targeting; some tools are marked DESTRUCTIVE. Sources: poracode:mcpthreads, poracode:security.
Conflicts [partial] Rollback fails while the agent is working; no general optimistic-concurrency model. Sources: poracode:mcpthreads.
No living product specifications; project notes are free-form documents only.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: persistent_requirements, human_edits, agent_edits, revisions, approvals, implementation_links, later_retrieval, drift_detection, review_integration; see atomic answers.
9 atomic answers
Persistent requirements [unsupported] Notes persist per project but are not a requirements system. Sources: poracode:notes.
Human edits [partial] Humans can edit notes. Sources: poracode:notes.
Agent edits [unsupported] No agent write tool for notes found in the MCP registry. Sources: poracode:mcpreg.
Revisions [unsupported] No revision history on notes. Sources: poracode:notes.
Approvals [unsupported] No approval workflow for documents. Sources: poracode:notes.
Implementation links [unsupported] No requirement-to-thread links. Sources: poracode:notes.
Later retrieval [unsupported] Notes are not retrieved automatically into later tasks. Sources: poracode:notes.
Concurrent tasks [supported] Experiments run several candidate agents in parallel worktrees; schedules run alongside threads. Sources: poracode:experiment, poracode:sched.
Quotas [partial] 16 concurrent children per parent; host resource admission control exists (hostResourceAdmissionRuntime); no per-user quotas. Sources: poracode:subrun.
Observed concurrency [unsupported] No product statement of tested concurrency; this catalog does not benchmark. Sources: poracode:readme.
Status visibility [supported] Sidebar shows per-thread status, age, worktree and attention markers; usage rings per provider. Sources: poracode:img-hero, poracode:mcpthreads.
Humans assign by choosing provider/model and worktree per thread; coordinator agents spawn children; routing preferences pin providers per task type; no claims or queues.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: claims, queues, duplicate_prevention, ownership_enforcement; see atomic answers.
7 atomic answers
Human assignment [supported] User picks agent/model/worktree per thread. Sources: poracode:readme.
Agent assignment [supported] spawn_agent assigns work to another provider; crew roles select provider/model. Sources: poracode:crossagent, poracode:crew.
Claims [unsupported] No claim primitive. Sources: poracode:mcpreg.
Queues [partial] Schedules queue timed runs; no work queue for tasks. Sources: poracode:sched.
Duplicate prevention [partial] Experiments isolate candidates in separate worktrees; Git state warns when another thread shares a tree before rewind. Sources: poracode:experiment, poracode:readme.
Ownership enforcement [unsupported] No enforced exclusive ownership. Sources: poracode:mcpreg.
Product-owned crossagent MCP: parent threads spawn, steer, wait on and cancel child agent runs on other providers, with crew roles, routing and streamed output; opt-in per thread.
Scope
Surfaces: Built-in app-controls and crossagent MCP servers, Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: activation, retained_results; see atomic answers.
12 atomic answers
Roles [supported] Crew roles (id, label, brief, parallel, no-edits) with crew-only or crew-first policy. Sources: poracode:crew.
Model harness effort [supported] Each role/spawn sets provider, model, reasoning effort and fast mode. Sources: poracode:crew.
Messages [supported] steer_agent sends follow-up messages to a child; send_to_thread/steer_thread message other threads. Sources: poracode:crossagent, poracode:mcpthreads.
Cross harness [supported] Delegation works across providers (Claude, Codex, Gemini, etc.). Sources: poracode:readme, poracode:crossagent.
Orchestration owner [supported] Poracode ships the crossagent MCP and crew logic (src/supervisor/crossagentMcp). Sources: poracode:crossagent.
Activation [partial] Exposed as built-in MCP servers per thread; harness-side enablement depends on the provider MCP config. Sources: poracode:mcpreg, poracode:registry.
Authentication [supported] Local ingress with Host-header gating; no extra credentials for children beyond provider logins. Sources: poracode:security.
Live progress [supported] Child output streams into the parent and get_status/list_runs report state. Sources: poracode:subrun, poracode:crossagent.
Retained results [partial] Up to 50 settled runs retained per parent (MAX_RETAINED_RUNS_PER_PARENT). Sources: poracode:subrun.
Events [partial] PR Watch reacts to PR check/review events; no general event or webhook triggers. Sources: poracode:prwatch, poracode:srch-hook.
Recurring tasks [supported] Recurring schedules with nightly reviews/dependency sweeps as examples in README. Sources: poracode:readme, poracode:sched.
Completion conditions [supported] AI-evaluated stopWhen with confidence threshold for heartbeat automations; maxIterations up to 100. Sources: poracode:sched.
Scheduler location [supported] Scheduler is a backend service (ScheduleService), shared by desktop and standalone server. Sources: poracode:schedsvc, poracode:arch.
Overlaps [supported] Misfire policies skip, coalesce or run-latest and ScheduleRunCoordinator serialises runs. Sources: poracode:sched, poracode:schedsvc.
Retries [supported] Retry policy none, fixed or exponential with 2-6 attempts. Sources: poracode:sched.
Client independence [supported] Runs live in the host so a closed renderer does not stop them on a standalone server; desktop requires the app/host running. Sources: poracode:schedsvc, poracode:arch, poracode:standalone.
Interrupt/stop, resume, steer mid-run, approval requests (needs_approval/needs_reply), OS and push notifications and attention markers; rollback of turns.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: pause, escalation, chat_terminal_parity; see atomic answers.
10 atomic answers
Pause [partial] Interrupt a running turn and continue later; no dedicated pause object. Sources: poracode:mcpthreads.
No mandatory preset; per-thread agent/model/effort and crew roles configurable, changes during a run via steering; subagent runs visible live.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: growing_epic, presets, natural_language, retained_relationships, discoverability; see atomic answers.
10 atomic answers
Quick task [supported] Quick composer overlay and New thread start a task in seconds. Sources: poracode:readme.
Growing epic [unsupported] No epic model. Sources: poracode:mcpreg.
Presets [partial] Crew roles and routing preferences act as optional presets. Sources: poracode:crew.
Natural language [partial] Agents configure the app by natural language through app-controls MCP (settings, schedules, projects). Sources: poracode:mcpreg, poracode:readme.
Agent configuration [supported] Per-thread/role provider, model, reasoning, fast and context size. Sources: poracode:crew.
In run changes [supported] Steer a running thread and change crew config between spawns (crewConfigUpdates). Sources: poracode:mcpthreads, poracode:crew.
Agents run on your computer, on a remote machine via SSH or on a standalone server you host; no vendor cloud. Standalone server plus remote clients lets work continue with the laptop closed.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: local, own-server · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: managed_cloud, resources, region; see atomic answers.
12 atomic answers
Local [supported] Desktop host runs supervisor, PTYs and structured runtimes locally. Sources: poracode:arch.
Byo remote [supported] Remote Machines over SSH installs the runtime on a server from your SSH config and runs agents there. Sources: poracode:readme, poracode:envadr.
Self hosted [supported] Standalone server via installer, systemd/launchd, or container image; desktop attaches to it. Sources: poracode:standalone, poracode:hostown.
Managed cloud [unsupported] No vendor-hosted runtime; FAQ says Poracode talks to providers from your machine, not through a server of the vendor; relay comments place hosted cloud service out of repo scope. Sources: poracode:faq, poracode:srch-cloud.
Hybrid [supported] Desktop can attach to an existing standalone owner or SSH environment while clients stay local. Sources: poracode:hostown, poracode:envadr.
Provisioning [supported] Poracode installs its runtime on SSH hosts; server installer verifies tarball checksums. Sources: poracode:envadr, poracode:standalone.
Payer [supported] User pays for their own machine and provider accounts; Poracode itself is free. Sources: poracode:faq.
Resources [partial] Host resources are whatever the user machine provides; resource admission exists but no specs are documented. Sources: poracode:standalone.
Region [unsupported] Region is wherever the user hosts it; there is no vendor region. Sources: poracode:srch-cloud.
Expiry [supported] No idle or maximum lifetime for self-hosted hosts; services run until stopped. Sources: poracode:standalone.
Client disconnect [supported] Supervisor on the host owns agent processes; clients are projections and reconnect with replay. Sources: poracode:agentsmd, poracode:remotearch.
Other device continuation [supported] Pair a browser, phone or another desktop to the same host and follow live threads. Sources: poracode:readme, poracode:remotearch.
Git worktrees are the isolation primitive (per-thread, experiments, merge/remove tools); everything else runs with the user permissions; harness sandbox modes pass through.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: container, vm, os_sandbox, filesystem, process, network, secrets, code_separation, security_boundary; see atomic answers.
12 atomic answers
Checkout [supported] Threads can run in the main checkout, with a warning when another thread shares the same tree. Sources: poracode:readme.
Branch [supported] Branch creation and listing in the supervisor git module. Sources: poracode:git.
Os sandbox [partial] Harness sandboxMode/approvalPolicy options (contracts/agent.ts) are passed to providers such as Codex; Poracode adds no OS sandbox. Sources: poracode:registry.
Filesystem [partial] Worktree separates files only; agents can read other paths unless the harness restricts them. Sources: poracode:git.
Process [partial] Each thread gets its own PTY or runtime process spawned by the supervisor; Windows uses job objects. Sources: poracode:agentsmd.
Network [unsupported] No network boundary for agents. Sources: poracode:srch-cloud.
Secrets [partial] Credentials stored in OS keychain/safeStorage; agents inherit the user environment. Sources: poracode:privacy.
Code separation [partial] Experiments and worktrees separate candidate code; no hostile-code separation. Sources: poracode:experiment.
Security boundary [unsupported] Not a security sandbox; threat model covers remote access only. Sources: poracode:security.
Sessions persist in SQLite and restore after restart; clients reconnect with replay/snapshots; supervisor and PTY job owner manage crashes; checkpoints rewind turns.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: worker_crash, expiry, process_reconnect, context_loss, duplicate_actions, manual_repair, multi_day_continuity; see atomic answers.
12 atomic answers
Client disconnect [supported] Host keeps running agent processes; clients resync from epoch-based replay and authoritative snapshots. Sources: poracode:arch, poracode:remotearch.
Worker crash [partial] BackendHostCore delegated-agent recovery and settlement recovery handle crashed children; coverage per provider unspecified. Sources: poracode:arch.
Service restart [supported] Standalone server has a bounded SIGTERM drain, owner lease and service units; threads are inactivated and resumable. Sources: poracode:standalone, poracode:security.
Expiry [unsupported] No sandbox expiry exists for self-hosted hosts. Sources: poracode:standalone.
Transcript reload [supported] Transcripts and runtime items persist in SQLite and reload. Sources: poracode:arch.
Process reconnect [partial] Terminal sessions persist via PTY job owner/broker; reconnect semantics vary by provider. Sources: poracode:arch.
Worktree setup scripts and port forwarding exist; no shared dependency caches or service snapshots; user diagnoses dependency problems.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
Not separately cross-checked
Not fully established or not supported: dependencies, caches, snapshots, services, ports, secrets, duplicate_installs, collisions, automatic_repair; see atomic answers.
10 atomic answers
Dependencies [partial] Worktree scripts (shared/worktreeScriptShell.ts) can run setup commands, and user-configured gitignore-style patterns copy ignored files or directories from the main project into a new worktree; installation is otherwise user-defined. Sources: poracode:git, poracode:rev-copyignored.
Caches [unsupported] No shared node_modules or cache handling found. Sources: poracode:srch-cloud.
Snapshots [unsupported] No environment snapshots. Sources: poracode:srch-cloud.
Services [partial] Local port discovery and forwarding for dev servers; no service orchestration. Sources: poracode:remotearch.
Ports [partial] Port forwarding allowlist and discovery (localPorts.ts); no allocation to avoid collisions. Sources: poracode:remotearch, poracode:security.
Secrets [partial] Credentials are stored in the OS keychain; there is no per-workspace secret injection, but ignored files such as env files can be copied into a new worktree by pattern. Sources: poracode:privacy, poracode:rev-copyignored.
Duplicate installs [unsupported] No deduplication across worktrees; ignored dependency directories matched by the copy patterns are copied, not shared. Sources: poracode:rev-copyignored.
Collisions [unsupported] No port-collision avoidance between workspaces. Sources: poracode:srch-cloud.
Remote setup [supported] SSH environment bootstrap installs the Poracode runtime on the host. Sources: poracode:envadr.
Schedules have max runtime (60s-24h), iterations and retries; provider quota is displayed; no token/spend caps.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: time_limits, turn_limits, token_limits, spend_limits, timeouts, provider_failures, enforcement; see atomic answers.
8 atomic answers
Time limits [partial] maxRuntimeSeconds on scheduled runs; thread runs have no global limit. Sources: poracode:sched.
Turn limits [partial] maxIterations up to 100 for heartbeat schedules. Sources: poracode:sched.
Token limits [unsupported] No token budget enforcement found. Sources: poracode:costhist.
Spend limits [unsupported] No spend cap; usage rings show provider quota. Sources: poracode:usagepkg.
Timeouts [partial] Judge and one-shot runs use timeouts (300s experiment judge); wait_for_thread max 1800s. Sources: poracode:expjudge, poracode:mcpthreads.
Retries [supported] Retry policies fixed/exponential on schedules. Sources: poracode:sched.
Provider failures [partial] Failed runs mark error; one-shot generation falls back across providers. Sources: poracode:sched.
Enforcement [partial] Limits that exist are enforced stops (maxRuntime/iterations) rather than warnings. Sources: poracode:sched.
Logs, runtime items and terminal logs persist; per-thread token usage and cost history; thread statuses; schedule run ledger; no traces export UI found.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: traces, usage_export, agent_stats, project_stats, time_stats, performance_method, responsiveness; see atomic answers.
13 atomic answers
Logs [supported] Terminal log persistence, leveled JSONL host log with rotation (PORACODE_LOG_LEVEL) and `poracode logs`. Sources: poracode:arch, poracode:security.
Traces [partial] Diagnostics modules and runtime item streams exist; no user-facing trace view documented. Sources: poracode:arch.
Failure reasons [supported] Schedule run outcomes and thread error statuses carry reasons. Sources: poracode:sched.
Usage export [partial] Cost history contract and session export; no CSV usage export found. Sources: poracode:costhist.
Task stats [supported] Thread token usage and cost history per thread (threadTokenUsage, costHistory). Sources: poracode:costhist.
Agent stats [partial] Usage by provider shown in usage rings; breakdown per agent in cost history. Sources: poracode:costhist, poracode:usagepkg.
Project stats [partial] Project thread counts; cost aggregation per project not confirmed. Sources: poracode:costhist.
Time stats [partial] Cost history is time-bucketed. Sources: poracode:costhist.
Failure status [supported] error and inactive statuses are distinct. Sources: poracode:mcpthreads.
Approval status [supported] needs_approval / needs_reply states. Sources: poracode:mcpthreads.
Reconnect consistency [supported] Snapshot recovery with per-sequence-space dedup and reset on reconnect. Sources: poracode:arch.
Performance method [unknown] No performance numbers are produced here; ADEMark has no entry. Sources: poracode:readme.
Responsiveness [unknown] Product claims speed ("Built for Speed") without published method. Sources: poracode:readme.
Estimated cost and token categories per thread with dated model pricing; provider quota rings; subscription marginal cost is not computed.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
Not separately cross-checked
Not fully established or not supported: child_cost, epic_cost, harness_aggregation, provider_reconciliation, compute_cost, refresh_delay, alerts, export, drilldown; see atomic answers.
14 atomic answers
Task cost [supported] Per-thread cost history from token categories and pricing. Sources: poracode:costhist.
Session cost [supported] Same per-session accounting. Sources: poracode:costhist.
Child cost [partial] Child runs are separate threads; aggregation into parent not confirmed. Sources: poracode:costhist, poracode:subrun.
Epic cost [unsupported] No epic object. Sources: poracode:mcpreg.
Harness aggregation [partial] Cost history covers multiple providers; cross-harness totals per project not confirmed. Sources: poracode:costhist.
Billed vs estimated [supported] Costs are estimates from public pricing (usagePricingSchema with source and reviewedAt). Sources: poracode:costhist.
Subscription allowance [supported] Session/weekly quota utilization and resets for Claude, Codex, Copilot. Sources: poracode:usagepkg.
Provider reconciliation [unsupported] No reconciliation against provider invoices. Sources: poracode:costhist.
Compute cost [unsupported] No vendor compute is charged; self-hosted compute is the user own. Sources: poracode:faq.
Refresh delay [partial] Usage auto-refresh is settings-driven with a 5 minute default and a 2 minute floor (providers can override, for example 15 minutes for Muse); there is no real-time metering. Sources: poracode:rev-usage-refresh.
Alerts [unsupported] No budget alerts found. Sources: poracode:costhist.
Export [partial] Session export format exists; no cost export found. Sources: poracode:costhist.
Drilldown [partial] Cost history by thread and time; drill-down depth unverified. Sources: poracode:costhist.
Host resource admission and bounded queues protect the supervisor; child run cap; no per-check dedup or CPU/RAM scheduler for user work.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: concurrency, queues, cpu_ram, host_awareness, check_reuse, check_deduplication, bounded_tests, fairness, shared_limits; see atomic answers.
12 atomic answers
Concurrency [partial] 16 children per parent; host admission control (HostCanonicalAdmissionControl, hostResourceAdmissionRuntime). Sources: poracode:subrun, poracode:arch.
Single-owner host; multiple paired clients can view and, with operator scope, drive the same threads; no presence, comments or user identities.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Web app / PWA served by the host · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: discussion, comments, presence, coprompting, ordering, conflicts, attribution, plan_restrictions; see atomic answers.
11 atomic answers
Visibility [supported] Paired clients (viewer scope read-only) follow live threads and terminal output. Sources: poracode:scopes, poracode:readme.
Discussion [unsupported] No issue discussion. Sources: poracode:srch-team.
Comments [partial] PR review threads/comments via forge adapters; no in-app comments on threads. Sources: poracode:forges, poracode:threadtools.
Presence [unsupported] No presence indicators. Sources: poracode:srch-team.
Coprompting [partial] Operator-scope clients can all send to the same thread, but they share one owner identity. Sources: poracode:scopes.
Ordering [unsupported] No documented input ordering for concurrent clients. Sources: poracode:scopes.
Conflicts [unsupported] No conflict handling for simultaneous prompts documented. Sources: poracode:scopes.
Attribution [partial] Audit log records pair/exchange/revoke and thread actions per credential; messages are not attributed to people. Sources: poracode:security.
No organizations, accounts or SSO; remote clients get operator or viewer scope presets and per-route scopes.
Scope
Surfaces: Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: organization_roles, project_roles, task_roles, membership, sso, provisioning, plan_scope; see atomic answers.
9 atomic answers
Organization roles [unsupported] No organization concept in a bounded search. Sources: poracode:srch-team.
Project roles [unsupported] No project roles. Sources: poracode:srch-team.
Provider approval requests surface in the transcript and can be resolved remotely (requests:resolve); sandbox/approval modes pass through to harnesses; port forwards need tickets.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: network, secret, approver_identity, lifetime, defaults, enforcement; see atomic answers.
14 atomic answers
Command [supported] needs_approval status and request resolution through UI/remote scope. Sources: poracode:mcpthreads, poracode:scopes.
Tool [supported] Tool approvals surface through the same request flow; MCP tools flagged destructive. Sources: poracode:mcpthreads.
Revoke [supported] Revoke paired credentials and port forwards. Sources: poracode:security.
Tunnels [supported] Port forwards bind the server host with per-forward tickets and are revoked with credentials (PortForwardRevocation). Sources: poracode:security.
Defaults [partial] Defaults follow each harness; Poracode lists approvalPolicy and sandboxMode per provider. Sources: poracode:registry.
Enforcement [partial] Enforced by the harness, not by Poracode, for command/tool approvals; remote scopes are enforced by the host. Sources: poracode:security.
JSONL audit log of pair, exchange, revoke, thread create/send/stop, file read/write and forward open; transcripts persist; no editing audit with integrity guarantees.
Scope
Surfaces: Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: approvals, edits, discussion, decisions, cross_user_persistence, mutability, retention, integrity; see atomic answers.
11 atomic answers
Actions [supported] Structured audit log of remote actions. Sources: poracode:security.
Approvals [partial] Approval resolutions flow through audited routes; coverage not itemised. Sources: poracode:security, poracode:scopes.
Edits [partial] File write is audited remotely; local edits are not. Sources: poracode:security.
Diff review overlay, PR view with review threads, AI review guides, viewed files, GitHub Actions view and request-changes via forge review submissions.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: shipping_guidance, effort, missed_evidence, keyboard, context_switching, roles, retained_context; see atomic answers.
Single-owner host; a second authorized client can attach and operate the same threads, thread transfer between hosts exists; no people-level handoff.
Scope
Surfaces: Poracode CLI, TUI and standalone server (poracode serve), Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: ongoing_takeover, decisions, ownership, attribution, context_loss; see atomic answers.
12 atomic answers
Ongoing takeover [partial] Another paired operator client can continue a live thread; no formal takeover. Sources: poracode:scopes, poracode:remotearch.
Same task [supported] Same thread ID on the host. Sources: poracode:remotearch.
Session history [supported] Full transcript from replay. Sources: poracode:remotearch.
Decisions [partial] Decisions exist only as transcript turns. Sources: poracode:remotearch.
Artifacts [supported] Files/diffs live in the host worktree. Sources: poracode:git.
Permissions [supported] Scope presets decide what a second client can do. Sources: poracode:scopes.
Runtime context [supported] Runtime stays on the host. Sources: poracode:agentsmd.
Ownership [unsupported] No ownership transfer record. Sources: poracode:srch-team.
Attribution [unsupported] No per-person attribution. Sources: poracode:srch-team.
Context loss [partial] Thread transfer between hosts (RemoteAccessServer.threadTransfer) carries Git state; provider context loss varies. Sources: poracode:remotearch.
Harness transfer [supported] "Continue in provider" dialog moves a thread to another provider. Sources: poracode:readme.
Diffs, review guides, screenshots via agent vision, file attachments and browser captures are kept in thread history; no cross-task artifact gallery.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: documents, recordings, test_outputs, gallery, revision_links, child_findings, prompt_leakage; see atomic answers.
PR Watch fixes failing CI and merges; GitHub Actions view; experiments judged by AI; no product-defined required checks or spec gates.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: tests, lint, types, spec_checks, required_checks, failure_blocking, requirement_conflicts, configured_policy, enforced_policy; see atomic answers.
11 atomic answers
Tests [partial] No built-in test runner; checks run via agent/terminal or CI. Sources: poracode:readme.
Lint [unsupported] No product lint integration. Sources: poracode:readme.
Types [unsupported] No type-check integration. Sources: poracode:readme.
Ci [supported] PR Watch watches CI, fixes failures and re-checks; GitHub Actions view. Sources: poracode:prwatch, poracode:readme.
Independent review [supported] Experiment AI judge and reviews through another provider. Sources: poracode:expjudge, poracode:readme.
Integrated Git: status/diff/stage/commit with AI messages, worktrees, sync, PR create/update/merge/comment across GitHub/GitLab/Bitbucket/Azure/Gitea, PR Watch fixes CI and merges.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Built-in app-controls and crossagent MCP servers · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: rebase; see atomic answers.
9 atomic answers
Branches [supported] Branch list/create via git module and git_branch tool. Sources: poracode:git, poracode:mcpreg.
Threads link to branch/worktree and PR metadata; no deployment evidence; rewind/rollback of conversation and revert of files; no stale-approval logic.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: build_links, deployment_links, delivery_status, retained_evidence, stale_approval_invalidation; see atomic answers.
9 atomic answers
Commit links [supported] Commits appear in transcripts and git state per thread. Sources: poracode:git.
Pr links [supported] PR metadata per thread. Sources: poracode:forges.
Build links [partial] GitHub Actions runs are linked in the Actions view. Sources: poracode:readme.
Deployment links [unsupported] No deployment links. Sources: poracode:srch-cloud.
PR list and AI review guides per PR; no queue of completed agent tasks with grouping, risk filters or dependency-aware merge.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: review_queue, grouping, risk_size_filters, findings, artifacts, exact_revision_approval, dependency_queues, next_actions, stale_approval_invalidation, check_deduplication; see atomic answers.
Apache-2.0 for the whole repository (app, CLI, server, relay, mobile clients, extension, website); hosted push forwarding service at poracode.com is not in the repo.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve), Native iOS client (SwiftUI), Native Android client (Compose), Chrome/Brave/Edge sidebar extension · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: hosted_extensions, hosted_parity; see atomic answers.
Fully self-hostable (standalone server, relay, container); no vendor account; sessions export; data lives in a local profile root; push forwarding optionally uses poracode.com.
Scope
Surfaces: Poracode CLI, TUI and standalone server (poracode serve), Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: vendor_dependencies, formats, cancellation, history_portability; see atomic answers.
8 atomic answers
Self hosting [supported] Standalone server runbook with systemd, launchd and container image. Sources: poracode:standalone.
Vendor dependencies [partial] Only optional push forwarding via poracode.com and update checks; agents need provider accounts. Sources: poracode:privacy, poracode:readme.
Export [supported] Session export format v1; SQLite/profile backup documented in the runbook. Sources: poracode:standalone, poracode:arch.
Import [supported] Session import from other tools (sessionImport) and ACP agents. Sources: poracode:arch.
Formats [partial] SQLite plus JSON export; standard format coverage not stated. Sources: poracode:arch.
Cancellation [unsupported] No account to cancel. Sources: poracode:faq.
Account independence [supported] Everything works without a Poracode account. Sources: poracode:faq.
History portability [partial] Session export covers transcripts; worktrees/Git stay in the repo. Sources: poracode:arch.
Code, prompts and credentials stay on the user host and go directly to chosen providers; allowlisted PostHog events and scrubbed Sentry crashes when configured; optional push via poracode.com.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve), Chrome/Brave/Edge sidebar extension · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: retention, deletion, training, residency, subprocessors, telemetry_controls, consent_prompt; see atomic answers.
15 atomic answers
Code data [supported] Code stays on the host; agents send it to the chosen providers. Sources: poracode:privacy, poracode:faq.
Prompts [supported] Prompts go to chosen providers; analytics exclude prompts and file content. Sources: poracode:privacy.
Credentials [supported] Stored in OS secure storage / safeStorage on host; tokens never proxied by Poracode servers. Sources: poracode:privacy, poracode:readme.
Scenario costs: platform fee is zero for any team size; model/compute costs are the user own and not priced by this catalog.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: task_assumptions, concurrency, tokens, compute_hours, variable_cost, included_cost, unknown_cost; see atomic answers.
11 atomic answers
One person [supported] Poracode cost is zero; provider and compute costs are separate. Sources: poracode:faq.
Two people [supported] Same; no seats. Sources: poracode:faq.
Five people [supported] Same; no seats. Sources: poracode:faq.
Task assumptions [unknown] This catalog states no fixed workload assumptions for Poracode. Sources: poracode:faq.
Concurrency [unknown] Not priced. Sources: poracode:faq.
Tokens [unknown] Not priced. Sources: poracode:faq.
Compute hours [unknown] Not priced. Sources: poracode:faq.
Fixed cost [supported] Zero platform fixed cost. Sources: poracode:faq.
Free open source forever with no paid tier; no trial or card; need your own agent subscriptions or API keys for meaningful use.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux), Poracode CLI, TUI and standalone server (poracode serve) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: trial, credits_trial, paid_only, early_access, usage_caps, paid_evaluation; see atomic answers.
10 atomic answers
Ongoing free [supported] Free and open source, no paid tier. Sources: poracode:faq.
Trial [unsupported] No trial concept. Sources: poracode:faq.
Credits trial [unsupported] No credits. Sources: poracode:faq.
Self host cost [supported] Your own hardware; software free. Sources: poracode:faq.
Paid only [unsupported] Nothing is paid-only. Sources: poracode:faq.
Early access [partial] 2.0 stable is not out; nightly builds are public. Sources: poracode:readme.
Free scenarios [supported] Collaboration via viewer/operator pairing, BYO subscriptions, remote SSH, mobile clients and PRs are all free. Sources: poracode:faq, poracode:readme.
Card required [supported] No card. Sources: poracode:faq.
Usage caps [unsupported] None from Poracode. Sources: poracode:faq.
Paid evaluation [unsupported] No payment needed; provider accounts are separate. Sources: poracode:faq.
Transparent: no price, no overages; provider usage billed by providers.
Scope
Surfaces: Poracode desktop app (Electron; macOS, Windows, Linux) · Version: v2.0.0-nightly.202611170101 (commit c1e8c5d, 2026-11-17) · Plan: Open source (Apache-2.0); free, bring your own agents · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not fully established or not supported: units, included_limits, overages, compute_markup, model_markup, minimum_commitment, cancellation, sales_only_unknowns; see atomic answers.
Electron, web/PWA and independent native iOS/Android clients over one host; only the supervisor spawns agent processes; one owner per data root; providers are plugins.
Desktop and CLI server compose the same backend; SQLite persistence; worktrees under ~/.poracode/worktrees; React 19 + HeroUI renderer shared by Electron and web; SwiftUI and Compose clients.
Kind
documented
Locator
Layers; Process and transport boundaries; Git Integration; Database
Server binds loopback by default; installer, npx launcher, release artifact, systemd/launchd service and a container image built from the Linux tarball.
Kind
documented
Locator
Ways to run it; systemd/launchd; Container image; configuration
Free and open source under Apache-2.0; no subscription, licence key or paid tier; bring your own agent subscriptions and API keys; talks to providers directly from the user machine; installers for macOS, Windows, Linux (Apple Silicon, Intel, x64, ARM64, AppImage).
The Android job builds a signed AAB and publishes to the Google Play internal track only when a service account is configured (otherwise the AAB stays a workflow artifact); the iOS job uploads the IPA to TestFlight. No public store listing or prebuilt mobile download is stated.
Assets are desktop installers (DMG, zip, NSIS exe, AppImage, deb), server tarballs and update manifests; no APK, AAB or IPA is attached to either release.
Kind
documented
Locator
release asset list (checked through the GitHub releases API) for v2.0.0-nightly.202611170101 and v1.8.2
Collects session/weekly/monthly utilization, resets, plan tier and optional estimated cost for Claude, Codex, Copilot; never logs or persists credentials.
Built-in MCP tools let an agent create, read, steer, wait for, interrupt and roll back other threads; wait_for_thread settles on idle/finished/needs_approval/needs_reply/error; caps on pages and text.
When a worktree is created, gitignored files and directories from the main project that match user-configured gitignore-style patterns are copied into it; existing files are not overwritten. This is a copy, not a shared cache.
Usage collection is cached and throttled; the auto-refresh timer is settings-driven with a 5 minute default and a 2 minute floor, and the Muse provider descriptor sets a 15 minute default interval.