Back to the Finder

Agent Teams

Open-source desktop app for Mac, Windows and Linux. Agents run on your computer.

Product websiteagentteams.live Compare with others Missing or wrong data?

Agent Teams product interface, supplied by its publisher
Desktop app
Mac, Windows and Linux
Browser
Yes
Phone
Not listed
Command line
No
Agents
Claude Code, Codex, Cursor Agent and OpenCode
Your subscription
Works with your own plan
Agents run
On your computer
Laptop closed
No
Isolation
Worktree
Parallel agents
Yes
Scheduled runs
Yes
Coordinator agent
Yes
Built-in issues
Yes
Pull requests
No
Review screen
Yes
Team
Not listed
Self-hosting
Yes
Licence
AGPL-3.0
Price from
Free
How it charges
No paid plan and bring your own key
Paid plans from
Not listed

Receipts

Checked
· oldest answer 2026-11-08
Findings
37 published · 30 cross-checked by a second agent · read them all
Sources
14 public pages on 1 site: github.com
Screenshot
github.com, retrieved · first party repository · shows appearance, not capability
Method
Same rules for all 103 researched ADEs. How we check · Report wrong data

What it does

Where you use it

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

Source and scope for Where you use it

Agents it runs

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

Source and scope for Agents it runs

Accounts and subscriptions

Use existing provider subscriptions or API keys, or start with a free unauthenticated model.

Source and scope for Accounts and subscriptions

Where agents run

Teams execute as local processes on the desktop host. Remote agent execution over SSH and 24/7 cloud teams remain roadmap work.

Source and scope for Where agents run

How work is kept apart

Selected teammates can get worktrees at launch. Scoped local provisioning options provide no container or VM isolation backend.

Source and scope for How work is kept apart

Parallel work

Multiple teams across projects and their agents can work in parallel.

Source and scope for Parallel work

Scheduled runs

App-owned scheduler dispatches due persisted schedules through a runtime process executor. Scope is local app/service, not future cloud teams.

Source and scope for Scheduled runs

Git and pull requests

Agent Teams provisions teammate Git worktrees and can initialize a repository with an initial local commit. Its scoped product services and HTTP/IPC/MCP surfaces do not implement pull-request creation or management; coding agents may use their own repository tools.

Source and scope for Git and pull requests

Licence and source

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

Source and scope for Licence and source

Price

Application is free. Additional provider access uses existing subscriptions or API keys.

Source and scope for Price

JSON for agentsMarkdown for agents

Report wrong dataSuggest a missing ADE

Typed filters

Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.

Typed filter values
FilterValue
Desktop OS: macOSYes
Desktop OS: WindowsYes
Desktop OS: LinuxYes
Web clientYes
Phone access: Native iOSNo
Phone access: Native AndroidNo
Phone access: Phone browserUnknown
CLINo
Coding agents: Claude CodeYes
Coding agents: CodexYes
Coding agents: Cursor AgentYes
Coding agents: Gemini CLINo
Coding agents: OpenCodeYes
Coding agents: PiNo
Coding agents: GrokNo
Coding agents: AiderNo
Coding agents: AntigravityNo
Use my subscriptionYes cross-checked
Where agents run: On your computerYes
Where agents run: On your own serverNo
Where agents run: In the vendor's cloudNo
Workspace isolation: Git worktreeYes
Workspace isolation: ContainerNo
Workspace isolation: VM or microVMNo
Parallel runsYes cross-checked
CoordinatorYes cross-checked
Native issue trackingYes cross-checked
Unattended triggersYes cross-checked
Shared promptingUnknown
Team rolesNo
SSONo
Pull request workflowNo
Review interfaceYes cross-checked
Product license: Apache-2.0No. AGPL-3.0 cross-checked
Product license: MITNo. AGPL-3.0 cross-checked
Product license: GPL-3.0No. AGPL-3.0 cross-checked
Product license: GPL-3.0-or-laterNo. AGPL-3.0 cross-checked
Product license: AGPL-3.0Yes. AGPL-3.0 cross-checked
Product license: AGPL-3.0-or-laterNo. AGPL-3.0 cross-checked
Product license: Elastic License 2.0No. AGPL-3.0 cross-checked
Product license: Custom termsNo. AGPL-3.0 cross-checked
Product license: ProprietaryNo. AGPL-3.0 cross-checked
Self-hostingYes cross-checked
Telemetry opt-outYes cross-checked
Free accessYes cross-checked
Starting price: FreeYes. Free cross-checked
Starting price: Up to $20/monthNo. Free cross-checked
Starting price: $21–40/monthNo. Free cross-checked
Starting price: $41–100/monthNo. Free cross-checked
Starting price: Over $100/monthNo. Free cross-checked
Starting price: Contact for pricingNo. Free cross-checked
Pricing model: Free, no paid planYes cross-checked
Pricing model: Free planNo
Pricing model: SubscriptionNo
Pricing model: Per seatNo
Pricing model: Usage-basedNo
Pricing model: Per machine or computeNo
Pricing model: Bring your own keyYes cross-checked
Pricing model: One-time purchaseNo
Paid plans from: No paid planUnknown
Paid plans from: $10 or less/monthUnknown
Paid plans from: $11–20/monthUnknown
Paid plans from: $21–40/monthUnknown
Paid plans from: $41–100/monthUnknown
Paid plans from: Over $100/monthUnknown
Paid plans from: Contact salesUnknown
Lifecycle status: ActiveUnknown
Lifecycle status: SunsettingUnknown
Keeps going with laptop closedNo
Open-source licenseYes. AGPL-3.0 cross-checked
Any desktop appYes
Paid plan up to $20/monthUnknown
Paid plan up to $40/monthUnknown
Any phone clientUnknown

Filter receipts

Desktop OS: macOS: Yes

Desktop OS: macOS

Typed value: Yes.

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

  • Desktop os: macOS, Windows and Linux desktop downloads.
  • Notifications: Configurable task completion, response-needed, comment and error alerts.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Desktop OS: Windows: Yes

Desktop OS: Windows

Typed value: Yes.

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

  • Desktop os: macOS, Windows and Linux desktop downloads.
  • Notifications: Configurable task completion, response-needed, comment and error alerts.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Desktop OS: Linux: Yes

Desktop OS: Linux

Typed value: Yes.

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

  • Desktop os: macOS, Windows and Linux desktop downloads.
  • Notifications: Configurable task completion, response-needed, comment and error alerts.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Web client: Yes

Web client

Typed value: Yes.

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

  • Mobile apps: Desktop and standalone browser build targets contain no native iOS or Android app.
  • Browser: The limited standalone dashboard is shipped for local/trusted-network use; Electron-only runtime functions are stubbed.
  • Cli: Scoped product entry points launch the desktop/browser renderer or MCP protocol server; there is no separate product-owned user/session CLI command interface.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/main/standalone.ts

    Finding: The shipped limited standalone mode serves the renderer and API without Electron; full web runtime parity remains in development. Release targets build desktop clients, with no native iOS/Android target. The product-owned agent-teams-mcp executable starts its MCP command-line server.

Phone access: Native iOS: No

Phone access: Native iOS

Typed value: No.

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

  • Mobile apps: Desktop and standalone browser build targets contain no native iOS or Android app.
  • Browser: The limited standalone dashboard is shipped for local/trusted-network use; Electron-only runtime functions are stubbed.
  • Cli: Scoped product entry points launch the desktop/browser renderer or MCP protocol server; there is no separate product-owned user/session CLI command interface.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/main/standalone.ts

    Finding: The shipped limited standalone mode serves the renderer and API without Electron; full web runtime parity remains in development. Release targets build desktop clients, with no native iOS/Android target. The product-owned agent-teams-mcp executable starts its MCP command-line server.

Phone access: Native Android: No

Phone access: Native Android

Typed value: No.

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

  • Mobile apps: Desktop and standalone browser build targets contain no native iOS or Android app.
  • Browser: The limited standalone dashboard is shipped for local/trusted-network use; Electron-only runtime functions are stubbed.
  • Cli: Scoped product entry points launch the desktop/browser renderer or MCP protocol server; there is no separate product-owned user/session CLI command interface.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/main/standalone.ts

    Finding: The shipped limited standalone mode serves the renderer and API without Electron; full web runtime parity remains in development. Release targets build desktop clients, with no native iOS/Android target. The product-owned agent-teams-mcp executable starts its MCP command-line server.

CLI: No

CLI

Typed value: No.

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

  • Mobile apps: Desktop and standalone browser build targets contain no native iOS or Android app.
  • Browser: The limited standalone dashboard is shipped for local/trusted-network use; Electron-only runtime functions are stubbed.
  • Cli: Scoped product entry points launch the desktop/browser renderer or MCP protocol server; there is no separate product-owned user/session CLI command interface.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/main/standalone.ts

    Finding: The shipped limited standalone mode serves the renderer and API without Electron; full web runtime parity remains in development. Release targets build desktop clients, with no native iOS/Android target. The product-owned agent-teams-mcp executable starts its MCP command-line server.

  2. Agent Teams mcp-server/src/index.ts

    Finding: The only published command executable starts an MCP protocol server with transport/host/port options. The controller package exports a JavaScript library; the standalone command launches the browser renderer. No product-owned user/session CLI command parser or verbs are implemented in the scoped entry points. Underlying coding-agent CLIs are separate.

Coding agents: Claude Code: Yes

Coding agents: Claude Code

Typed value: Yes.

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Session integration: Reads local runtime/session data.
  • Mixed harness operation: Teams can use different runtimes/models.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Coding agents: Codex: Yes

Coding agents: Codex

Typed value: Yes.

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Session integration: Reads local runtime/session data.
  • Mixed harness operation: Teams can use different runtimes/models.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Coding agents: Cursor Agent: Yes

Coding agents: Cursor Agent

Typed value: Yes.

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Harnesses: Managed Claude Code, Codex and OpenCode runtime paths; Cursor Agent companion CLI bridge. Gemini provider selection uses the Claude runtime rather than Gemini CLI.
  • Custom adapters: Provider/model extensions use supported runtime transports; the bounded runtime/companion registry has no Pi, Grok CLI, Aider or Antigravity adapter.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/features/runtime-provider-management/main/infrastructure/cli-companion/definitions/CursorAgentCompanionDefinition.ts

    Finding: Cursor companion installation/authentication and process-attribution paths invoke the cursor-agent coding CLI through the OpenCode bridge. The Gemini team provider is a model/auth backend of the Claude runtime, not a separate Gemini CLI executable. The scoped provider/runtime tables and launch adapters have no Pi, Grok CLI, Aider or Antigravity coding-harness adapter; SuperGrok is model/provider access.

Coding agents: Gemini CLI: No

Coding agents: Gemini CLI

Typed value: No.

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Harnesses: Managed Claude Code, Codex and OpenCode runtime paths; Cursor Agent companion CLI bridge. Gemini provider selection uses the Claude runtime rather than Gemini CLI.
  • Custom adapters: Provider/model extensions use supported runtime transports; the bounded runtime/companion registry has no Pi, Grok CLI, Aider or Antigravity adapter.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/features/runtime-provider-management/main/infrastructure/cli-companion/definitions/CursorAgentCompanionDefinition.ts

    Finding: Cursor companion installation/authentication and process-attribution paths invoke the cursor-agent coding CLI through the OpenCode bridge. The Gemini team provider is a model/auth backend of the Claude runtime, not a separate Gemini CLI executable. The scoped provider/runtime tables and launch adapters have no Pi, Grok CLI, Aider or Antigravity coding-harness adapter; SuperGrok is model/provider access.

Coding agents: OpenCode: Yes

Coding agents: OpenCode

Typed value: Yes.

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Session integration: Reads local runtime/session data.
  • Mixed harness operation: Teams can use different runtimes/models.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Coding agents: Pi: No

Coding agents: Pi

Typed value: No.

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Harnesses: Managed Claude Code, Codex and OpenCode runtime paths; Cursor Agent companion CLI bridge. Gemini provider selection uses the Claude runtime rather than Gemini CLI.
  • Custom adapters: Provider/model extensions use supported runtime transports; the bounded runtime/companion registry has no Pi, Grok CLI, Aider or Antigravity adapter.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/features/runtime-provider-management/main/infrastructure/cli-companion/definitions/CursorAgentCompanionDefinition.ts

    Finding: Cursor companion installation/authentication and process-attribution paths invoke the cursor-agent coding CLI through the OpenCode bridge. The Gemini team provider is a model/auth backend of the Claude runtime, not a separate Gemini CLI executable. The scoped provider/runtime tables and launch adapters have no Pi, Grok CLI, Aider or Antigravity coding-harness adapter; SuperGrok is model/provider access.

Coding agents: Grok: No

Coding agents: Grok

Typed value: No.

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Harnesses: Managed Claude Code, Codex and OpenCode runtime paths; Cursor Agent companion CLI bridge. Gemini provider selection uses the Claude runtime rather than Gemini CLI.
  • Custom adapters: Provider/model extensions use supported runtime transports; the bounded runtime/companion registry has no Pi, Grok CLI, Aider or Antigravity adapter.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/features/runtime-provider-management/main/infrastructure/cli-companion/definitions/CursorAgentCompanionDefinition.ts

    Finding: Cursor companion installation/authentication and process-attribution paths invoke the cursor-agent coding CLI through the OpenCode bridge. The Gemini team provider is a model/auth backend of the Claude runtime, not a separate Gemini CLI executable. The scoped provider/runtime tables and launch adapters have no Pi, Grok CLI, Aider or Antigravity coding-harness adapter; SuperGrok is model/provider access.

Coding agents: Aider: No

Coding agents: Aider

Typed value: No.

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Harnesses: Managed Claude Code, Codex and OpenCode runtime paths; Cursor Agent companion CLI bridge. Gemini provider selection uses the Claude runtime rather than Gemini CLI.
  • Custom adapters: Provider/model extensions use supported runtime transports; the bounded runtime/companion registry has no Pi, Grok CLI, Aider or Antigravity adapter.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/features/runtime-provider-management/main/infrastructure/cli-companion/definitions/CursorAgentCompanionDefinition.ts

    Finding: Cursor companion installation/authentication and process-attribution paths invoke the cursor-agent coding CLI through the OpenCode bridge. The Gemini team provider is a model/auth backend of the Claude runtime, not a separate Gemini CLI executable. The scoped provider/runtime tables and launch adapters have no Pi, Grok CLI, Aider or Antigravity coding-harness adapter; SuperGrok is model/provider access.

Coding agents: Antigravity: No

Coding agents: Antigravity

Typed value: No.

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Harnesses: Managed Claude Code, Codex and OpenCode runtime paths; Cursor Agent companion CLI bridge. Gemini provider selection uses the Claude runtime rather than Gemini CLI.
  • Custom adapters: Provider/model extensions use supported runtime transports; the bounded runtime/companion registry has no Pi, Grok CLI, Aider or Antigravity adapter.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/features/runtime-provider-management/main/infrastructure/cli-companion/definitions/CursorAgentCompanionDefinition.ts

    Finding: Cursor companion installation/authentication and process-attribution paths invoke the cursor-agent coding CLI through the OpenCode bridge. The Gemini team provider is a model/auth backend of the Claude runtime, not a separate Gemini CLI executable. The scoped provider/runtime tables and launch adapters have no Pi, Grok CLI, Aider or Antigravity coding-harness adapter; SuperGrok is model/provider access.

Use my subscription: Yes cross-checked

Use my subscription

Typed value: Yes.

Use existing provider subscriptions or API keys, or start with a free unauthenticated model.

  • Agent subscriptions: Existing subscription access for named supported providers.
  • Api accounts: API key provider connections.
  • Vendor account requirement: Free model requires no signup, key or card.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Where agents run: On your computer: Yes

Where agents run: On your computer

Typed value: Yes.

Teams execute as local processes on the desktop host. Remote agent execution over SSH and 24/7 cloud teams remain roadmap work.

  • Local: Reads local project and runtime data.
  • Managed cloud: Launching 24/7 cloud teams is unchecked in roadmap, not a shipped execution mode.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Where agents run: On your own server: No

Where agents run: On your own server

Typed value: No.

Teams execute as local processes on the desktop host. Remote agent execution over SSH and 24/7 cloud teams remain roadmap work.

  • Byo remote: README marks remote SSH launch/manage as unchecked roadmap work; SSH file monitoring is separate from execution.
  • Client disconnect: The current agent process launch path remains on the desktop host; it does not move work off the sleeping execution machine.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/main/services/team/TeamProvisioningService.ts

    Finding: The desktop launches local agent processes through spawnCli and optional worktree provisioning. The complete provisioning/runtime option model has no container or VM isolation backend. Remote team execution over SSH and autonomous cloud teams are unchecked roadmap work.

Where agents run: In the vendor's cloud: No

Where agents run: In the vendor's cloud

Typed value: No.

Teams execute as local processes on the desktop host. Remote agent execution over SSH and 24/7 cloud teams remain roadmap work.

  • Local: Reads local project and runtime data.
  • Managed cloud: Launching 24/7 cloud teams is unchecked in roadmap, not a shipped execution mode.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Workspace isolation: Git worktree: Yes

Workspace isolation: Git worktree

Typed value: Yes.

Selected teammates can get worktrees at launch. Scoped local provisioning options provide no container or VM isolation backend.

  • Checkout: Shared main checkout available.
  • Worktree: Per-teammate worktree option.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Workspace isolation: Container: No

Workspace isolation: Container

Typed value: No.

Selected teammates can get worktrees at launch. Scoped local provisioning options provide no container or VM isolation backend.

  • Container: The complete team launch/provisioning options spawn local processes and optional worktrees, without container isolation.
  • Vm: No VM/microVM backend in the scoped provisioning/runtime option model.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/main/services/team/TeamProvisioningService.ts

    Finding: The desktop launches local agent processes through spawnCli and optional worktree provisioning. The complete provisioning/runtime option model has no container or VM isolation backend. Remote team execution over SSH and autonomous cloud teams are unchecked roadmap work.

Workspace isolation: VM or microVM: No

Workspace isolation: VM or microVM

Typed value: No.

Selected teammates can get worktrees at launch. Scoped local provisioning options provide no container or VM isolation backend.

  • Container: The complete team launch/provisioning options spawn local processes and optional worktrees, without container isolation.
  • Vm: No VM/microVM backend in the scoped provisioning/runtime option model.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/main/services/team/TeamProvisioningService.ts

    Finding: The desktop launches local agent processes through spawnCli and optional worktree provisioning. The complete provisioning/runtime option model has no container or VM isolation backend. Remote team execution over SSH and autonomous cloud teams are unchecked roadmap work.

Parallel runs: Yes cross-checked

Parallel runs

Typed value: Yes.

Multiple teams across projects and their agents can work in parallel.

  • Concurrent sessions: Parallel agents and teams.
  • Concurrent tasks: Autonomous task execution on board.
  • Status visibility: Live task statuses and agent diagnostics.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Coordinator: Yes cross-checked

Coordinator

Typed value: Yes.

App-owned lead/teammate orchestration exposes cross-team direct/group messages, task comments and review.

  • Roles: Provisioning prompt defines lead and teammate roles.
  • Messages: Direct and group agent messages across teams.
  • Results return: Task-specific output and review workflow retained.
  • Orchestration owner: App own orchestration layer.
  • Live progress: Kanban, runtime logs and organizations live map.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Native issue tracking: Yes cross-checked

Native issue tracking

Typed value: Yes.

App owns shared tasks with descriptions, comments, attachments and durable board status/history.

  • Create: Human or agents create tasks.
  • Edit: Agents manage tasks; human task editing.
  • Discuss: Task comments.
  • Task session separation: Task-specific runtime logs matched to board tasks.
  • Durable states: Kanban states with task timeline.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Unattended triggers: Yes cross-checked

Unattended triggers

Typed value: Yes.

App-owned scheduler dispatches due persisted schedules through a runtime process executor. Scope is local app/service, not future cloud teams.

  • Schedules: Due schedules use nextRunAt and executor dispatch.
  • Completion conditions: Executor awaits process exit and captures result.
  • Scheduler location: Desktop app main-process service.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. src/main/services/schedule/SchedulerService.ts

    Finding: Pinned scheduler implementation uses due-run checks and nextRunAt to dispatch persisted schedules through the executor. Renderer schedule components expose configuration, linking it to an accessible product feature.

  2. src/main/services/schedule/ScheduledTaskExecutor.ts

    Finding: Pinned scheduled executor resolves runtime binary, spawns with prompt, tracks process, persists output/result and offers cancellation. Supported Claude launch accepts max-budget-usd.

Team roles: No

Team roles

Typed value: No.

The scoped desktop/trusted-network dashboard has no named human workspace roles or enterprise SSO. Agent organization roles do not grant human permissions.

  • Organization roles: Organization/teammate roles organize AI agents; the inspected HTTP/app context has no human roles or membership permission model.
  • Sso: No enterprise SSO or identity-provider integration in the scoped human access paths.
  • Source inspection covers the scoped release only. Unanswered atomic questions remain unknown; no live scenario was run.
  1. Agent Teams src/main/services/infrastructure/HttpServer.ts

    Finding: The scoped application serves local OS-account data and a trusted-network HTTP dashboard. HTTP admission has CORS and path/context validation but no human membership, workspace-role or enterprise SSO system. Organization and teammate roles model AI-agent organization, not human user permissions.

SSO: No

SSO

Typed value: No.

The scoped desktop/trusted-network dashboard has no named human workspace roles or enterprise SSO. Agent organization roles do not grant human permissions.

  • Organization roles: Organization/teammate roles organize AI agents; the inspected HTTP/app context has no human roles or membership permission model.
  • Sso: No enterprise SSO or identity-provider integration in the scoped human access paths.
  • Source inspection covers the scoped release only. Unanswered atomic questions remain unknown; no live scenario was run.
  1. Agent Teams src/main/services/infrastructure/HttpServer.ts

    Finding: The scoped application serves local OS-account data and a trusted-network HTTP dashboard. HTTP admission has CORS and path/context validation but no human membership, workspace-role or enterprise SSO system. Organization and teammate roles model AI-agent organization, not human user permissions.

Pull request workflow: No

Pull request workflow

Typed value: No.

Agent Teams provisions teammate Git worktrees and can initialize a repository with an initial local commit. Its scoped product services and HTTP/IPC/MCP surfaces do not implement pull-request creation or management; coding agents may use their own repository tools.

  • Commits: The product can create an initial local commit when preparing a repository; general commit management is not established by that setup path.
  • Pull requests: The scoped Git services, routes and MCP operations have no product-owned pull-request creation or management path.
  • Pinned source inspection covers the product-owned Git services, HTTP/IPC and MCP tool surfaces. Agent-generated shell commands and externally configured tools are separate; no hands-on test ran.
  1. Agent Teams src/main/services/team/TeamWorktreeGitService.ts

    Finding: Product Git services inspect repositories, create an initial local commit and provision teammate worktrees. The scoped HTTP/IPC/MCP operations have no product-owned pull-request creation, review-comment management, PR status store or forge merge path. The inbox relay only tells agents to verify PR claims through an available repository/GitHub tool; that is an agent instruction rather than a product PR workflow.

Review interface: Yes cross-checked

Review interface

Typed value: Yes.

Task diff review supports accept, reject and comments on individual hunks.

  • Change understanding: Task-scoped full diff view.
  • Comments: Comment on code hunks.
  • Request changes: Reject individual changes.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Product license: Apache-2.0: No. AGPL-3.0 cross-checked

Product license: Apache-2.0

Typed value: No. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Product license: MIT: No. AGPL-3.0 cross-checked

Product license: MIT

Typed value: No. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Product license: GPL-3.0: No. AGPL-3.0 cross-checked

Product license: GPL-3.0

Typed value: No. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Product license: GPL-3.0-or-later: No. AGPL-3.0 cross-checked

Product license: GPL-3.0-or-later

Typed value: No. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Product license: AGPL-3.0: Yes. AGPL-3.0 cross-checked

Product license: AGPL-3.0

Typed value: Yes. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Product license: AGPL-3.0-or-later: No. AGPL-3.0 cross-checked

Product license: AGPL-3.0-or-later

Typed value: No. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Product license: Elastic License 2.0: No. AGPL-3.0 cross-checked

Product license: Elastic License 2.0

Typed value: No. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Product license: Custom terms: No. AGPL-3.0 cross-checked

Product license: Custom terms

Typed value: No. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Product license: Proprietary: No. AGPL-3.0 cross-checked

Product license: Proprietary

Typed value: No. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Self-hosting: Yes cross-checked

Self-hosting

Typed value: Yes.

Core desktop app and local orchestration run on user hardware; app does not have a cloud backend for storing project code.

  • Self hosting: Build and run Electron source locally.
  • Vendor dependencies: Provider runtime traffic remains under external provider terms.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Telemetry opt-out: Yes cross-checked

Telemetry opt-out

Typed value: Yes.

App says it does not upload/sync project code to Agent Teams servers. External coding runtimes talk to their own providers.

  • Telemetry defaults: Anonymous crash, performance and product usage telemetry is on by default in builds that include it.
  • Telemetry controls: Settings, General, Privacy has a Send anonymous telemetry toggle; turning it off stops Sentry and drops events.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams settings: Privacy telemetry toggle

    Finding: Settings, General, Privacy shows a Send anonymous telemetry toggle (crash, performance and product usage data) bound to general.telemetryEnabled whenever telemetry is built in. The same toggle is present at release tag v2.18.6.

  2. Agent Teams main-process telemetry gate

    Finding: The persisted telemetryEnabled flag is read before Sentry starts; turning it off shuts Sentry down and drops events. The default configuration sets telemetryEnabled to true, so telemetry is on until the user disables it.

Free access: Yes cross-checked

Free access

Typed value: Yes.

Free app can begin with a free model requiring no signup, key or card; other providers retain their costs.

  • Ongoing free: Free application.
  • Free scenarios: Start team using free unauthenticated model.
  • Card required: No card for initial free model.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Starting price: Free: Yes. Free cross-checked

Starting price: Free

Typed value: Yes. Free.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Starting price: Up to $20/month: No. Free cross-checked

Starting price: Up to $20/month

Typed value: No. Free.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Starting price: $21–40/month: No. Free cross-checked

Starting price: $21–40/month

Typed value: No. Free.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Starting price: $41–100/month: No. Free cross-checked

Starting price: $41–100/month

Typed value: No. Free.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Starting price: Over $100/month: No. Free cross-checked

Starting price: Over $100/month

Typed value: No. Free.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Starting price: Contact for pricing: No. Free cross-checked

Starting price: Contact for pricing

Typed value: No. Free.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Pricing model: Free, no paid plan: Yes cross-checked

Pricing model: Free, no paid plan

Typed value: Yes.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Pricing model: Free plan: No

Pricing model: Free plan

Typed value: No.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Pricing model: Subscription: No

Pricing model: Subscription

Typed value: No.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Pricing model: Per seat: No

Pricing model: Per seat

Typed value: No.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Pricing model: Usage-based: No

Pricing model: Usage-based

Typed value: No.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Pricing model: Per machine or compute: No

Pricing model: Per machine or compute

Typed value: No.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Pricing model: Bring your own key: Yes cross-checked

Pricing model: Bring your own key

Typed value: Yes.

Use existing provider subscriptions or API keys, or start with a free unauthenticated model.

  • Agent subscriptions: Existing subscription access for named supported providers.
  • Api accounts: API key provider connections.
  • Vendor account requirement: Free model requires no signup, key or card.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Pricing model: One-time purchase: No

Pricing model: One-time purchase

Typed value: No.

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Workspace fees: No application charge.
  • Model cost: Provider costs separate.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

Keeps going with laptop closed: No

Keeps going with laptop closed

Typed value: No.

Teams execute as local processes on the desktop host. Remote agent execution over SSH and 24/7 cloud teams remain roadmap work.

  • Byo remote: README marks remote SSH launch/manage as unchecked roadmap work; SSH file monitoring is separate from execution.
  • Client disconnect: The current agent process launch path remains on the desktop host; it does not move work off the sleeping execution machine.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. Agent Teams src/main/services/team/TeamProvisioningService.ts

    Finding: The desktop launches local agent processes through spawnCli and optional worktree provisioning. The complete provisioning/runtime option model has no container or VM isolation backend. Remote team execution over SSH and autonomous cloud teams are unchecked roadmap work.

Open-source license: Yes. AGPL-3.0 cross-checked

Open-source license

Typed value: Yes. AGPL-3.0.

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Client license: AGPL-3.0.
  • Source visibility: Public application source.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

Any desktop app: Yes

Any desktop app

Typed value: Yes.

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

  • Desktop os: macOS, Windows and Linux desktop downloads.
  • Notifications: Configurable task completion, response-needed, comment and error alerts.
  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

All public findings

Findings may summarize a source. They are not presented as verbatim statements.

agent-teams:ACC-01: Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

agent-teams:ACC-01

Desktop supports macOS, Windows and Linux. A released limited standalone dashboard serves the renderer/API over HTTP; the full web runtime remains in development. Native phone apps are absent from the scoped build targets. The product owns an agent-teams-mcp executable.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

  2. Agent Teams src/main/standalone.ts

    Finding: The shipped limited standalone mode serves the renderer and API without Electron; full web runtime parity remains in development. Release targets build desktop clients, with no native iOS/Android target. The product-owned agent-teams-mcp executable starts its MCP command-line server.

  3. Agent Teams mcp-server/src/index.ts

    Finding: The only published command executable starts an MCP protocol server with transport/host/port options. The controller package exports a JavaScript library; the standalone command launches the browser renderer. No product-owned user/session CLI command parser or verbs are implemented in the scoped entry points. Underlying coding-agent CLIs are separate.

agent-teams:ACC-02: Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

agent-teams:ACC-02

Claude Code, Codex and OpenCode are managed runtimes. Source also establishes Cursor Agent through a CLI companion bridge. The Gemini team provider is model access through the Claude runtime, not Gemini CLI. Model-provider access such as SuperGrok does not establish Grok CLI.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

  2. Agent Teams src/features/runtime-provider-management/main/infrastructure/cli-companion/definitions/CursorAgentCompanionDefinition.ts

    Finding: Cursor companion installation/authentication and process-attribution paths invoke the cursor-agent coding CLI through the OpenCode bridge. The Gemini team provider is a model/auth backend of the Claude runtime, not a separate Gemini CLI executable. The scoped provider/runtime tables and launch adapters have no Pi, Grok CLI, Aider or Antigravity coding-harness adapter; SuperGrok is model/provider access.

agent-teams:ACC-03: Use existing provider subscriptions or API keys, or start with a free unauthenticated model. cross-checked

agent-teams:ACC-03

Use existing provider subscriptions or API keys, or start with a free unauthenticated model.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:ACC-04: Download desktop app, choose project, define team roles/provisioning prompt and launch. Setup detects runtimes and guides provider auth. cross-checked

agent-teams:ACC-04

Download desktop app, choose project, define team roles/provisioning prompt and launch. Setup detects runtimes and guides provider auth.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:ACC-06: Built-in MCP server and agent plugins support tool integration; universal secure plugin system remains roadmap work. cross-checked

agent-teams:ACC-06

Built-in MCP server and agent plugins support tool integration; universal secure plugin system remains roadmap work.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:ACC-07: Desktop app uses Electron 40, React 19, TypeScript, Tailwind and Zustand. cross-checked

agent-teams:ACC-07

Desktop app uses Electron 40, React 19, TypeScript, Tailwind and Zustand.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:PLAN-01: Humans create tasks on the board or send attachments to the lead, which creates described tasks. cross-checked

agent-teams:PLAN-01

Humans create tasks on the board or send attachments to the lead, which creates described tasks.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:PLAN-02: Task descriptions, comments and attachments retain assignment context. Formal editable plan revisions remain unestablished. cross-checked

agent-teams:PLAN-02

Task descriptions, comments and attachments retain assignment context. Formal editable plan revisions remain unestablished.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:PLAN-03: Organizations can nest teams and show dependencies/delegation. Exact blocker enforcement is not established here. cross-checked

agent-teams:PLAN-03

Organizations can nest teams and show dependencies/delegation. Exact blocker enforcement is not established here.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:PLAN-04: Instructions and task context survive compaction through app recovery mechanisms. cross-checked

agent-teams:PLAN-04

Instructions and task context survive compaction through app recovery mechanisms.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:PLAN-06: App owns shared tasks with descriptions, comments, attachments and durable board status/history. cross-checked

agent-teams:PLAN-06

App owns shared tasks with descriptions, comments, attachments and durable board status/history.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:PLAN-07: Agents create/manage shared tasks and leave comments visible to humans. cross-checked

agent-teams:PLAN-07

Agents create/manage shared tasks and leave comments visible to humans.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:COORD-01: Multiple teams across projects and their agents can work in parallel. cross-checked

agent-teams:COORD-01

Multiple teams across projects and their agents can work in parallel.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:COORD-02: Agents plan, delegate and create shared tasks through the app's orchestration layer, and the team lead turns a human message with attachments into a described task. Humans add work through direct messages, task comments and kanban quick actions.

agent-teams:COORD-02

Agents plan, delegate and create shared tasks through the app's orchestration layer, and the team lead turns a human message with attachments into a described task. Humans add work through direct messages, task comments and kanban quick actions.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:COORD-03: App-owned lead/teammate orchestration exposes cross-team direct/group messages, task comments and review. cross-checked

agent-teams:COORD-03

App-owned lead/teammate orchestration exposes cross-team direct/group messages, task comments and review.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:COORD-04: App-owned scheduler dispatches due persisted schedules through a runtime process executor. Scope is local app/service, not future cloud teams. cross-checked

agent-teams:COORD-04

App-owned scheduler dispatches due persisted schedules through a runtime process executor. Scope is local app/service, not future cloud teams.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. src/main/services/schedule/SchedulerService.ts

    Finding: Pinned scheduler implementation uses due-run checks and nextRunAt to dispatch persisted schedules through the executor. Renderer schedule components expose configuration, linking it to an accessible product feature.

  2. src/main/services/schedule/ScheduledTaskExecutor.ts

    Finding: Pinned scheduled executor resolves runtime binary, spawns with prompt, tracks process, persists output/result and offers cancellation. Supported Claude launch accepts max-budget-usd.

agent-teams:COORD-05: Direct messages course-correct agents, diagnostics/restart address stuck teammates, and board badges flag human input. cross-checked

agent-teams:COORD-05

Direct messages course-correct agents, diagnostics/restart address stuck teammates, and board badges flag human input.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:COORD-06: Organization map shows nested teams, agent status, tasks, dependencies and cross-team messages; no high-load fixture was run. cross-checked

agent-teams:COORD-06

Organization map shows nested teams, agent status, tasks, dependencies and cross-team messages; no high-load fixture was run.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:COORD-07: Teams may begin in solo mode, expand later, and use provisioning prompts to set roles and branch rules. cross-checked

agent-teams:COORD-07

Teams may begin in solo mode, expand later, and use provisioning prompts to set roles and branch rules.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:RUN-01: Teams execute as local processes on the desktop host. Remote agent execution over SSH and 24/7 cloud teams remain roadmap work.

agent-teams:RUN-01

Teams execute as local processes on the desktop host. Remote agent execution over SSH and 24/7 cloud teams remain roadmap work.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

  2. Agent Teams src/main/services/team/TeamProvisioningService.ts

    Finding: The desktop launches local agent processes through spawnCli and optional worktree provisioning. The complete provisioning/runtime option model has no container or VM isolation backend. Remote team execution over SSH and autonomous cloud teams are unchecked roadmap work.

agent-teams:RUN-02: Selected teammates can get worktrees at launch. Scoped local provisioning options provide no container or VM isolation backend.

agent-teams:RUN-02

Selected teammates can get worktrees at launch. Scoped local provisioning options provide no container or VM isolation backend.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

  2. Agent Teams src/main/services/team/TeamProvisioningService.ts

    Finding: The desktop launches local agent processes through spawnCli and optional worktree provisioning. The complete provisioning/runtime option model has no container or VM isolation backend. Remote team execution over SSH and autonomous cloud teams are unchecked roadmap work.

agent-teams:RUN-03: Task context persists; app has compaction recovery and guarded nudges after known rate-limit cooldowns. No crash continuity test performed. cross-checked

agent-teams:RUN-03

Task context persists; app has compaction recovery and guarded nudges after known rate-limit cooldowns. No crash continuity test performed.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

  2. v2.18.6

    Finding: v2.18.6 was published 2026-11-05. Release notes describe the scoped changes; this is not a hands-on check.

agent-teams:RUN-05: Monthly token/estimated-cost budgets offer threshold alerts; supported scheduled Claude runs can receive a max-budget flag. This is not proof of hard global billing enforcement. cross-checked

agent-teams:RUN-05

Monthly token/estimated-cost budgets offer threshold alerts; supported scheduled Claude runs can receive a max-budget flag. This is not proof of hard global billing enforcement.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

  2. src/main/services/schedule/ScheduledTaskExecutor.ts

    Finding: Pinned scheduled executor resolves runtime binary, spawns with prompt, tracks process, persists output/result and offers cancellation. Supported Claude launch accepts max-budget-usd.

agent-teams:RUN-06: Per-task logs show tool actions and messages; analytics and live process/resource sections expose activity. cross-checked

agent-teams:RUN-06

Per-task logs show tool actions and messages; analytics and live process/resource sections expose activity.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:RUN-07: Token analytics include input/output/cache/reasoning and estimated cost across tasks, agents and runs. Estimates are not invoices. cross-checked

agent-teams:RUN-07

Token analytics include input/output/cache/reasoning and estimated cost across tasks, agents and runs. Estimates are not invoices.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:TEAM-02: The scoped desktop/trusted-network dashboard has no named human workspace roles or enterprise SSO. Agent organization roles do not grant human permissions.

agent-teams:TEAM-02

The scoped desktop/trusted-network dashboard has no named human workspace roles or enterprise SSO. Agent organization roles do not grant human permissions.

  • Source inspection covers the scoped release only. Unanswered atomic questions remain unknown; no live scenario was run.
  1. Agent Teams src/main/services/infrastructure/HttpServer.ts

    Finding: The scoped application serves local OS-account data and a trusted-network HTTP dashboard. HTTP admission has CORS and path/context validation but no human membership, workspace-role or enterprise SSO system. Organization and teammate roles model AI-agent organization, not human user permissions.

agent-teams:TEAM-03: Users can require manual approval for supported tool actions, with readable requests and notifications. cross-checked

agent-teams:TEAM-03

Users can require manual approval for supported tool actions, with readable requests and notifications.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:TEAM-04: Task timeline records state changes, participants and workflow actions. cross-checked

agent-teams:TEAM-04

Task timeline records state changes, participants and workflow actions.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:TEAM-05: Task diff review supports accept, reject and comments on individual hunks. cross-checked

agent-teams:TEAM-05

Task diff review supports accept, reject and comments on individual hunks.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:SHIP-01: Tasks retain attachments and matched runtime logs/changes, with document and code preview/editing. cross-checked

agent-teams:SHIP-01

Tasks retain attachments and matched runtime logs/changes, with document and code preview/editing.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:SHIP-03: Agent Teams provisions teammate Git worktrees and can initialize a repository with an initial local commit. Its scoped product services and HTTP/IPC/MCP surfaces do not implement pull-request creation or management; coding agents may use their own repository tools.

agent-teams:SHIP-03

Agent Teams provisions teammate Git worktrees and can initialize a repository with an initial local commit. Its scoped product services and HTTP/IPC/MCP surfaces do not implement pull-request creation or management; coding agents may use their own repository tools.

  • Pinned source inspection covers the product-owned Git services, HTTP/IPC and MCP tool surfaces. Agent-generated shell commands and externally configured tools are separate; no hands-on test ran.
  1. Agent Teams README FAQ: parallel teams

    Finding: Multiple teams can run in one or several projects at once; git worktree isolation can be enabled for selected teammates at launch, and branch or merge rules are left to the provisioning prompt.

  2. Agent Teams src/main/services/team/TeamWorktreeGitService.ts

    Finding: Product Git services inspect repositories, create an initial local commit and provision teammate worktrees. The scoped HTTP/IPC/MCP operations have no product-owned pull-request creation, review-comment management, PR status store or forge merge path. The inbox relay only tells agents to verify PR claims through an available repository/GitHub tool; that is an agent instruction rather than a product PR workflow.

agent-teams:OWN-01: Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant. cross-checked

agent-teams:OWN-01

Main application public repository uses AGPL-3.0. CLA enables additional sublicensing but does not replace this grant.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

  2. LICENSE

    Finding: Repository application license is AGPL-3.0. The CLA does not replace that public license.

agent-teams:OWN-02: Core desktop app and local orchestration run on user hardware; app does not have a cloud backend for storing project code. cross-checked

agent-teams:OWN-02

Core desktop app and local orchestration run on user hardware; app does not have a cloud backend for storing project code.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:OWN-03: App says it does not upload/sync project code to Agent Teams servers. External coding runtimes talk to their own providers. cross-checked

agent-teams:OWN-03

App says it does not upload/sync project code to Agent Teams servers. External coding runtimes talk to their own providers.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

  2. Agent Teams settings: Privacy telemetry toggle

    Finding: Settings, General, Privacy shows a Send anonymous telemetry toggle (crash, performance and product usage data) bound to general.telemetryEnabled whenever telemetry is built in. The same toggle is present at release tag v2.18.6.

  3. Agent Teams main-process telemetry gate

    Finding: The persisted telemetryEnabled flag is read before Sentry starts; turning it off shuts Sentry down and drops events. The default configuration sets telemetryEnabled to true, so telemetry is on until the user disables it.

agent-teams:OWN-04: Application is free. Additional provider access uses existing subscriptions or API keys. cross-checked

agent-teams:OWN-04

Application is free. Additional provider access uses existing subscriptions or API keys.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

agent-teams:OWN-06: Latest listed v2.18.6 was published November 5; current release requires macOS 13+, with older 2.17.1 for macOS 12. cross-checked

agent-teams:OWN-06

Latest listed v2.18.6 was published November 5; current release requires macOS 13+, with older 2.17.1 for macOS 12.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.

  2. v2.18.6

    Finding: v2.18.6 was published 2026-11-05. Release notes describe the scoped changes; this is not a hands-on check.

agent-teams:OWN-08: Free app can begin with a free model requiring no signup, key or card; other providers retain their costs. cross-checked

agent-teams:OWN-08

Free app can begin with a free model requiring no signup, key or card; other providers retain their costs.

  • Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
  1. README.md

    Finding: Free Electron app on three desktop OSes owns lead/teammate orchestration, tasks, comments, messaging, review diffs, optional worktrees and token/cost analytics. Runtime subscriptions/API keys are reused. Cloud 24/7 and account switching are roadmap items, not current cloud execution.