Back to the Finder

Unpeel

Mac and Linux app. Agents run on your computer or on your own server.

Product websiteunpeel.com Compare with others Missing or wrong data?

Unpeel product interface, captured locally
Desktop app
Mac and Linux
Browser
No
Phone
IPhone
Command line
Yes
Agents
Claude Code, Codex, Cursor Agent, Gemini CLI, OpenCode, Pi, Grok and Antigravity
Your subscription
Works with your own plan
Agents run
On your computer and on your own server
Laptop closed
Keeps going
Isolation
Worktree
Parallel agents
Yes
Scheduled runs
Yes
Coordinator agent
Yes
Built-in issues
No
Pull requests
No
Review screen
Yes
Team
Not listed
Self-hosting
Yes
Licence
Not listed
Price from
Free
How it charges
Free plan, subscription, per machine or compute and bring your own key
Paid plans from
Not listed

Receipts

Checked
· oldest answer 2026-11-07
Findings
40 published · 22 cross-checked by a second agent · read them all
Sources
32 public pages on 3 sites: unpeel.com, raw.githubusercontent.com, github.com
Screenshot
unpeel.com, retrieved · self captured · 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

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

Source and scope for Where you use it

Agents it runs

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

Source and scope for Agents it runs

Accounts and subscriptions

Users bring provider logins and API keys.

Source and scope for Accounts and subscriptions

Where agents run

Owned hosts continue sessions independently of clients.

Source and scope for Where agents run

How work is kept apart

Unpeel uses detached Host-user PTYs, separate workspace state and optional worktrees. The scoped core has no product-provisioned per-agent container or VM isolation backend.

Source and scope for How work is kept apart

Parallel work

Multiple live sessions run concurrently.

Source and scope for Parallel work

Scheduled runs

Unpeel's headless product CLI explicitly supports starting/driving sessions from external CI or cron. It does not supply an internal scheduler; the external caller owns timing and retries.

Source and scope for Scheduled runs

Git and pull requests

Unpeel's optional Git App displays history/diffs and performs fetch, fast-forward pull and push. The scoped App/CLI has no native pull-request creation or management control; agents may use external forge CLIs.

Source and scope for Git and pull requests

Price

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and 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: WindowsNo
Desktop OS: LinuxYes
Web clientNo
Phone access: Native iOSYes
Phone access: Native AndroidNo
Phone access: Phone browserNo
CLIYes
Coding agents: Claude CodeYes cross-checked
Coding agents: CodexYes cross-checked
Coding agents: Cursor AgentYes cross-checked
Coding agents: Gemini CLIYes cross-checked
Coding agents: OpenCodeYes cross-checked
Coding agents: PiYes cross-checked
Coding agents: GrokYes cross-checked
Coding agents: AiderUnknown
Coding agents: AntigravityYes cross-checked
Use my subscriptionYes cross-checked
Where agents run: On your computerYes cross-checked
Where agents run: On your own serverYes cross-checked
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
Native issue trackingNo
Unattended triggersYes
Shared promptingUnknown
Team rolesNo
SSONo
Pull request workflowNo
Review interfaceYes
Product license: Apache-2.0Unknown
Product license: MITUnknown
Product license: GPL-3.0Unknown
Product license: GPL-3.0-or-laterUnknown
Product license: AGPL-3.0Unknown
Product license: AGPL-3.0-or-laterUnknown
Product license: Elastic License 2.0Unknown
Product license: Custom termsUnknown
Product license: ProprietaryUnknown
Self-hostingYes cross-checked
Telemetry opt-outYes
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 planNo
Pricing model: Free planYes
Pricing model: SubscriptionYes
Pricing model: Per seatNo
Pricing model: Usage-basedNo
Pricing model: Per machine or computeYes
Pricing model: Bring your own keyYes
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 closedYes cross-checked
Open-source licenseUnknown
Any desktop appYes
Paid plan up to $20/monthUnknown
Paid plan up to $40/monthUnknown
Any phone clientYes

Filter receipts

Desktop OS: macOS: Yes

Desktop OS: macOS

Typed value: Yes.

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • Mobile apps: Native iPhone/iPad client through TestFlight.
  • Browser: Architecture explicitly describes web app as later.
  • Cli: Product-owned unpeel CLI.
  • Task actions: Phone views terminals, answers input and launches sessions.
  • Notifications: Mac notifications and optional Link phone push.
  • Cross device continuity: Mac/phone/CLI attach to same Host sessions.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

Desktop OS: Windows: No

Desktop OS: Windows

Typed value: No.

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • Desktop os: Mac GUI plus native macOS/Linux CLI; Windows explicitly unsupported by the CLI installer.
  • Mobile apps: Native iPhone/iPad client through TestFlight.
  • Browser: Architecture explicitly describes web app as later.
  • Mobile browser: The web app is explicitly a later client, not a shipped phone-browser surface.
  • Cli: Product-owned unpeel CLI.
  • Task actions: Phone views terminals, answers input and launches sessions.
  • Notifications: Mac notifications and optional Link phone push.
  • Cross device continuity: Mac/phone/CLI attach to same Host sessions.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Unpeel native CLI platform restrictions

    Finding: The native CLI installer supports macOS and Linux and explicitly rejects other OSes. The shipped clients are Mac, iPhone/iPad and CLI; the web app is explicitly later, with no native Android build. CLI access is separate from a Linux GUI.

Desktop OS: Linux: Yes

Desktop OS: Linux

Typed value: Yes.

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • Desktop os: Mac GUI plus native macOS/Linux CLI; Windows explicitly unsupported by the CLI installer.
  • Mobile apps: Native iPhone/iPad client through TestFlight.
  • Browser: Architecture explicitly describes web app as later.
  • Mobile browser: The web app is explicitly a later client, not a shipped phone-browser surface.
  • Cli: Product-owned unpeel CLI.
  • Task actions: Phone views terminals, answers input and launches sessions.
  • Notifications: Mac notifications and optional Link phone push.
  • Cross device continuity: Mac/phone/CLI attach to same Host sessions.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Unpeel native CLI platform restrictions

    Finding: The native CLI installer supports macOS and Linux and explicitly rejects other OSes. The shipped clients are Mac, iPhone/iPad and CLI; the web app is explicitly later, with no native Android build. CLI access is separate from a Linux GUI.

Web client: No

Web client

Typed value: No.

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • Mobile apps: Native iPhone/iPad client through TestFlight.
  • Browser: Architecture explicitly describes web app as later.
  • Mobile browser: The web app is explicitly a later client, not a shipped phone-browser surface.
  • Cli: Product-owned unpeel CLI.
  • Task actions: Phone views terminals, answers input and launches sessions.
  • Notifications: Mac notifications and optional Link phone push.
  • Cross device continuity: Mac/phone/CLI attach to same Host sessions.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

Phone access: Native iOS: Yes

Phone access: Native iOS

Typed value: Yes.

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • Mobile apps: Native iPhone/iPad client through TestFlight.
  • Browser: Architecture explicitly describes web app as later.
  • Cli: Product-owned unpeel CLI.
  • Task actions: Phone views terminals, answers input and launches sessions.
  • Notifications: Mac notifications and optional Link phone push.
  • Cross device continuity: Mac/phone/CLI attach to same Host sessions.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. https://raw.githubusercontent.com/unpeel-com/unpeel/e2e0e647a51422683639b858e08cf48b46827c9e/README.md

    Finding: Pinned README says server and Apple client sources are included, local/direct use is free, and only operated Link backend is closed.

Phone access: Native Android: No

Phone access: Native Android

Typed value: No.

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • Desktop os: Mac GUI plus native macOS/Linux CLI; Windows explicitly unsupported by the CLI installer.
  • Mobile apps: Native iPhone/iPad client through TestFlight.
  • Browser: Architecture explicitly describes web app as later.
  • Mobile browser: The web app is explicitly a later client, not a shipped phone-browser surface.
  • Cli: Product-owned unpeel CLI.
  • Task actions: Phone views terminals, answers input and launches sessions.
  • Notifications: Mac notifications and optional Link phone push.
  • Cross device continuity: Mac/phone/CLI attach to same Host sessions.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Unpeel native CLI platform restrictions

    Finding: The native CLI installer supports macOS and Linux and explicitly rejects other OSes. The shipped clients are Mac, iPhone/iPad and CLI; the web app is explicitly later, with no native Android build. CLI access is separate from a Linux GUI.

Phone access: Phone browser: No

Phone access: Phone browser

Typed value: No.

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • Desktop os: Mac GUI plus native macOS/Linux CLI; Windows explicitly unsupported by the CLI installer.
  • Mobile apps: Native iPhone/iPad client through TestFlight.
  • Browser: Architecture explicitly describes web app as later.
  • Mobile browser: The web app is explicitly a later client, not a shipped phone-browser surface.
  • Cli: Product-owned unpeel CLI.
  • Task actions: Phone views terminals, answers input and launches sessions.
  • Notifications: Mac notifications and optional Link phone push.
  • Cross device continuity: Mac/phone/CLI attach to same Host sessions.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Unpeel native CLI platform restrictions

    Finding: The native CLI installer supports macOS and Linux and explicitly rejects other OSes. The shipped clients are Mac, iPhone/iPad and CLI; the web app is explicitly later, with no native Android build. CLI access is separate from a Linux GUI.

CLI: Yes

CLI

Typed value: Yes.

CLI and session-scoped MCP expose actual operations.

  • Cli: unpeel ls/new/send/wait/screen/logs/transcript.
  • Mcp server: unpeel-host __mcp__ stdio server.
  • Operations: Inspect, create and drive sessions through CLI; MCP scope follows grants.
  • Authentication: Local same-user workspace socket and session-bound MCP identity.
  • Stability: Versioned Host protocol; installed help is command authority.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. CLI reference — Unpeel Docs

    Finding: Product CLI creates, inspects, sends, waits and controls sessions; serve install configures a per-user launchd/systemd service.

Coding agents: Claude Code: Yes cross-checked

Coding agents: Claude Code

Typed value: Yes.

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

  • Harnesses: Claude Code, Codex, Gemini CLI, Cursor Agent, Grok, Kimi, Kiro, Cline, Amp, OpenCode and Pi. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.
  • Custom adapters: Any command can run as a preset; deeper runtime adapters are distinct.
  • Session integration: Real PTY with hooks, conversation binding and transcript adapters where supported.
  • Mixed harness operation: Different CLI sessions run side-by-side; no observed fixture.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  • The Antigravity runtime is scoped to macOS/Linux. Its output-based status is not marked reliable for completion or attention.
  1. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

Coding agents: Codex: Yes cross-checked

Coding agents: Codex

Typed value: Yes.

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

  • Harnesses: Claude Code, Codex, Gemini CLI, Cursor Agent, Grok, Kimi, Kiro, Cline, Amp, OpenCode and Pi. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.
  • Custom adapters: Any command can run as a preset; deeper runtime adapters are distinct.
  • Session integration: Real PTY with hooks, conversation binding and transcript adapters where supported.
  • Mixed harness operation: Different CLI sessions run side-by-side; no observed fixture.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  • The Antigravity runtime is scoped to macOS/Linux. Its output-based status is not marked reliable for completion or attention.
  1. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

Coding agents: Cursor Agent: Yes cross-checked

Coding agents: Cursor Agent

Typed value: Yes.

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

  • Harnesses: Claude Code, Codex, Gemini CLI, Cursor Agent, Grok, Kimi, Kiro, Cline, Amp, OpenCode and Pi. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.
  • Custom adapters: Any command can run as a preset; deeper runtime adapters are distinct.
  • Session integration: Real PTY with hooks, conversation binding and transcript adapters where supported.
  • Mixed harness operation: Different CLI sessions run side-by-side; no observed fixture.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  • The Antigravity runtime is scoped to macOS/Linux. Its output-based status is not marked reliable for completion or attention.
  1. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

Coding agents: Gemini CLI: Yes cross-checked

Coding agents: Gemini CLI

Typed value: Yes.

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

  • Harnesses: Claude Code, Codex, Gemini CLI, Cursor Agent, Grok, Kimi, Kiro, Cline, Amp, OpenCode and Pi. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.
  • Custom adapters: Any command can run as a preset; deeper runtime adapters are distinct.
  • Session integration: Real PTY with hooks, conversation binding and transcript adapters where supported.
  • Mixed harness operation: Different CLI sessions run side-by-side; no observed fixture.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  • The Antigravity runtime is scoped to macOS/Linux. Its output-based status is not marked reliable for completion or attention.
  1. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

Coding agents: OpenCode: Yes cross-checked

Coding agents: OpenCode

Typed value: Yes.

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

  • Harnesses: Claude Code, Codex, Gemini CLI, Cursor Agent, Grok, Kimi, Kiro, Cline, Amp, OpenCode and Pi. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.
  • Custom adapters: Any command can run as a preset; deeper runtime adapters are distinct.
  • Session integration: Real PTY with hooks, conversation binding and transcript adapters where supported.
  • Mixed harness operation: Different CLI sessions run side-by-side; no observed fixture.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  • The Antigravity runtime is scoped to macOS/Linux. Its output-based status is not marked reliable for completion or attention.
  1. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

Coding agents: Pi: Yes cross-checked

Coding agents: Pi

Typed value: Yes.

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

  • Harnesses: Claude Code, Codex, Gemini CLI, Cursor Agent, Grok, Kimi, Kiro, Cline, Amp, OpenCode and Pi. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.
  • Custom adapters: Any command can run as a preset; deeper runtime adapters are distinct.
  • Session integration: Real PTY with hooks, conversation binding and transcript adapters where supported.
  • Mixed harness operation: Different CLI sessions run side-by-side; no observed fixture.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  • The Antigravity runtime is scoped to macOS/Linux. Its output-based status is not marked reliable for completion or attention.
  1. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

Coding agents: Grok: Yes cross-checked

Coding agents: Grok

Typed value: Yes.

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

  • Harnesses: Claude Code, Codex, Gemini CLI, Cursor Agent, Grok, Kimi, Kiro, Cline, Amp, OpenCode and Pi. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.
  • Custom adapters: Any command can run as a preset; deeper runtime adapters are distinct.
  • Session integration: Real PTY with hooks, conversation binding and transcript adapters where supported.
  • Mixed harness operation: Different CLI sessions run side-by-side; no observed fixture.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  • The Antigravity runtime is scoped to macOS/Linux. Its output-based status is not marked reliable for completion or attention.
  1. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

Coding agents: Antigravity: Yes cross-checked

Coding agents: Antigravity

Typed value: Yes.

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

  • Harnesses: Claude Code, Codex, Gemini CLI, Cursor Agent, Grok, Kimi, Kiro, Cline, Amp, OpenCode and Pi. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  • The Antigravity runtime is scoped to macOS/Linux. Its output-based status is not marked reliable for completion or attention.
  1. Unpeel Antigravity support at v0.7.6

    Finding: Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

Use my subscription: Yes cross-checked

Use my subscription

Typed value: Yes.

Users bring provider logins and API keys.

  • Agent subscriptions: Existing agent CLI accounts/subscriptions.
  • Api accounts: Own API keys.
  • Vendor account requirement: Local use requires no Unpeel account or activation.
  • Provider restrictions: Hook, resume and MCP support differ by runtime.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

Where agents run: On your computer: Yes cross-checked

Where agents run: On your computer

Typed value: Yes.

Owned hosts continue sessions independently of clients.

  • Local: Mac bundled server.
  • Byo remote: Owned headless Mac/Linux host, including cloud VM.
  • Self hosted: Same complete open-source server.
  • Provisioning: Installer and per-user service command.
  • Resources: 64-bit Linux glibc 2.31+; provider/runtime compatibility still being validated.
  • Client disconnect: Disconnecting client never stops host session.
  • Other device continuation: Mac/phone/CLI reconnect to same workspace.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Headless Host — Unpeel Docs

    Finding: Same server runs on an owned Mac/Linux host with service-manager setup and phone/Mac clients; full cloud-machine matrix remains under validation.

  2. Workspaces — Unpeel Docs

    Finding: Local, SSH and paired workspaces retain sessions/data on the owning host; additional local workspaces are experimental.

  3. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

Where agents run: On your own server: Yes cross-checked

Where agents run: On your own server

Typed value: Yes.

Owned hosts continue sessions independently of clients.

  • Local: Mac bundled server.
  • Byo remote: Owned headless Mac/Linux host, including cloud VM.
  • Self hosted: Same complete open-source server.
  • Provisioning: Installer and per-user service command.
  • Resources: 64-bit Linux glibc 2.31+; provider/runtime compatibility still being validated.
  • Client disconnect: Disconnecting client never stops host session.
  • Other device continuation: Mac/phone/CLI reconnect to same workspace.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Headless Host — Unpeel Docs

    Finding: Same server runs on an owned Mac/Linux host with service-manager setup and phone/Mac clients; full cloud-machine matrix remains under validation.

  2. Workspaces — Unpeel Docs

    Finding: Local, SSH and paired workspaces retain sessions/data on the owning host; additional local workspaces are experimental.

  3. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

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

Where agents run: In the vendor's cloud

Typed value: No.

Owned hosts continue sessions independently of clients.

  • Local: Mac bundled server.
  • Byo remote: Owned headless Mac/Linux host, including cloud VM.
  • Self hosted: Same complete open-source server.
  • Provisioning: Installer and per-user service command.
  • Resources: 64-bit Linux glibc 2.31+; provider/runtime compatibility still being validated.
  • Client disconnect: Disconnecting client never stops host session.
  • Other device continuation: Mac/phone/CLI reconnect to same workspace.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Headless Host — Unpeel Docs

    Finding: Same server runs on an owned Mac/Linux host with service-manager setup and phone/Mac clients; full cloud-machine matrix remains under validation.

  2. Workspaces — Unpeel Docs

    Finding: Local, SSH and paired workspaces retain sessions/data on the owning host; additional local workspaces are experimental.

  3. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

Workspace isolation: Git worktree: Yes

Workspace isolation: Git worktree

Typed value: Yes.

Unpeel uses detached Host-user PTYs, separate workspace state and optional worktrees. The scoped core has no product-provisioned per-agent container or VM isolation backend.

  • Branch: Worktree branch/base-ref selection.
  • Worktree: Experimental worktrees off by default.
  • Filesystem: Each workspace has its own state home.
  • Process: Separate workspace worker processes.
  • Code separation: Child-project worktree directory.
  • Security boundary: Host commands run as same user; cooperative policy is not OS sandbox.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Git worktrees — Unpeel Docs

    Finding: Optional worktrees are off by default and create child projects; agent worktree preparation requires an additional grant.

Workspace isolation: Container: No

Workspace isolation: Container

Typed value: No.

Unpeel uses detached Host-user PTYs, separate workspace state and optional worktrees. The scoped core has no product-provisioned per-agent container or VM isolation backend.

  • Container: No container provisioning/launch backend in scoped Host session execution.
  • Vm: No per-agent VM isolation backend; a user-selected cloud VM is a Host location.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel PTY session execution and persistent model

    Finding: The core launches detached PTYs as the Host OS user and stores sessions/projects/presets, with optional Git worktrees. It has no per-agent container/VM provisioning or separate native issue entity. Host timer jobs are runtime observation/heartbeats, not an agent-work scheduler. The CLI explicitly supports script/CI/cron session control.

Workspace isolation: VM or microVM: No

Workspace isolation: VM or microVM

Typed value: No.

Unpeel uses detached Host-user PTYs, separate workspace state and optional worktrees. The scoped core has no product-provisioned per-agent container or VM isolation backend.

  • Container: No container provisioning/launch backend in scoped Host session execution.
  • Vm: No per-agent VM isolation backend; a user-selected cloud VM is a Host location.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel PTY session execution and persistent model

    Finding: The core launches detached PTYs as the Host OS user and stores sessions/projects/presets, with optional Git worktrees. It has no per-agent container/VM provisioning or separate native issue entity. Host timer jobs are runtime observation/heartbeats, not an agent-work scheduler. The CLI explicitly supports script/CI/cron session control.

Parallel runs: Yes cross-checked

Parallel runs

Typed value: Yes.

Multiple live sessions run concurrently.

  • Concurrent sessions: Split panes launch independent agents/shells.
  • Concurrent tasks: Different projects or optional worktrees.
  • Status visibility: Busy, Done and Needs you per session.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Git worktrees — Unpeel Docs

    Finding: Optional worktrees are off by default and create child projects; agent worktree preparation requires an additional grant.

  3. Activity & the menu bar — Unpeel Docs

    Finding: Busy/done/needs-you states use provider hooks or output heuristics with explicit limits; status survives app restart.

Coordinator: Yes

Coordinator

Typed value: Yes.

In the pinned v0.7.6 core, a session granted Create & remove can create worker sessions, inspect transcripts/state, wait and send instructions through Unpeel MCP. The 0.7.5 release note and implemented permission checks resolve the earlier documentation-parity gap.

  • Roles: Product-owned Create & remove session role enables delegation; scoped MCP tools identify the caller and its peers.
  • Messages: MCP send_text/send_keys and peer reports route instructions/results under live grants.
  • Orchestration owner: Unpeel supplies the elevated session role, start/inspection/wait and messaging tools.
  • Some current web documentation still says agents cannot create/close sessions. This answer is bounded to the published 0.7.5 change and pinned v0.7.6 implementation with explicit Create & remove permission; no hands-on run was performed.
  1. Unpeel released MCP delegation role

    Finding: The pinned core exposes create_session, list/inspect peers, read_screen/read_output/read_transcript, waits and send_text/send_keys. A session granted Create & remove, represented by McpRole::Manage, can create workers and communicate with them. Release 0.7.5 introduced this access; the older docs prohibition on agent-created sessions is stale for this implementation.

Native issue tracking: No

Native issue tracking

Typed value: No.

The scoped Unpeel core persists projects, presets and terminal sessions, without a native issue/backlog entity separate from sessions. Sidebar groups organize sessions rather than issue state.

  • Task session separation: The product state model has no issue/task entity independent of terminal sessions.
  • Durable states: Session runtime/status is not an independent issue lifecycle.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel PTY session execution and persistent model

    Finding: The core launches detached PTYs as the Host OS user and stores sessions/projects/presets, with optional Git worktrees. It has no per-agent container/VM provisioning or separate native issue entity. Host timer jobs are runtime observation/heartbeats, not an agent-work scheduler. The CLI explicitly supports script/CI/cron session control.

Unattended triggers: Yes

Unattended triggers

Typed value: Yes.

Unpeel's headless product CLI explicitly supports starting/driving sessions from external CI or cron. It does not supply an internal scheduler; the external caller owns timing and retries.

  • Schedules: External cron can invoke the documented headless session commands.
  • Events: CI can invoke the documented new/send/wait command surface without a human starting each run.
  • Scheduler location: External cron or CI, not the Unpeel Host timer jobs.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel documented CI/cron command surface

    Finding: The public headless command surface explicitly supports agents, CI and cron driving sessions without a UI or desktop app. The new command creates a preset session programmatically and send/wait manage its work. Scheduling/event ownership stays with external cron or CI.

Team roles: No

Team roles

Typed value: No.

Unpeel's core uses paired-client Host access. Agent-session MCP grants are separate from human team roles; the scoped core has no organization/project human role model or enterprise SSO.

  • Organization roles: Agent MCP grants are not organization human membership roles.
  • Project roles: No named human project permission model in the scoped core.
  • Sso: Core access uses pairing rather than enterprise SAML/OIDC federation.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel human access versus agent grants

    Finding: Human access is paired-client Host access. Read/Write/Create & remove controls apply to agent sessions, not named organization/project human roles. The scoped open-source core has no enterprise SAML/OIDC SSO flow; operated Link account/relay internals are separate.

SSO: No

SSO

Typed value: No.

Unpeel's core uses paired-client Host access. Agent-session MCP grants are separate from human team roles; the scoped core has no organization/project human role model or enterprise SSO.

  • Organization roles: Agent MCP grants are not organization human membership roles.
  • Project roles: No named human project permission model in the scoped core.
  • Sso: Core access uses pairing rather than enterprise SAML/OIDC federation.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel human access versus agent grants

    Finding: Human access is paired-client Host access. Read/Write/Create & remove controls apply to agent sessions, not named organization/project human roles. The scoped open-source core has no enterprise SAML/OIDC SSO flow; operated Link account/relay internals are separate.

Pull request workflow: No

Pull request workflow

Typed value: No.

Unpeel's optional Git App displays history/diffs and performs fetch, fast-forward pull and push. The scoped App/CLI has no native pull-request creation or management control; agents may use external forge CLIs.

  • Commits: The Git App browses existing commits; creating commits remains an external agent/terminal operation.
  • Pull requests: No PR create/manage action in Git App remote actions or the scoped CLI command inventory.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel PTY session execution and persistent model

    Finding: The core launches detached PTYs as the Host OS user and stores sessions/projects/presets, with optional Git worktrees. It has no per-agent container/VM provisioning or separate native issue entity. Host timer jobs are runtime observation/heartbeats, not an agent-work scheduler. The CLI explicitly supports script/CI/cron session control.

  2. Unpeel optional Git review App

    Finding: The first-party Git App, install slug diffs and binary unpeel-diffs, is registered in the App catalog. It displays staged/unstaged/conflicted/untracked changes and unified code patches, plus commit-history patches, using the same terminal/native App Kit renderer. It supports fetch/pull/push but no pull-request create/manage operation.

Review interface: Yes

Review interface

Typed value: Yes.

Unpeel's optional first-party Git sidebar App displays proposed working-tree code changes and commit patches in native/terminal renderers. Image-gallery markup remains a separate review path.

  • Change understanding: The Git App Changes/History tabs open unified syntax-highlighted code patches, including staged, unstaged and untracked changes.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel optional Git review App

    Finding: The first-party Git App, install slug diffs and binary unpeel-diffs, is registered in the App catalog. It displays staged/unstaged/conflicted/untracked changes and unified code patches, plus commit-history patches, using the same terminal/native App Kit renderer. It supports fetch/pull/push but no pull-request create/manage operation.

Self-hosting: Yes cross-checked

Self-hosting

Typed value: Yes.

Core local/direct functionality can be hosted without Link.

  • Self hosting: Complete local Host on user-controlled machine.
  • Vendor dependencies: Local/direct works without Link; relay/push service optional.
  • Export: Markdown provider transcript and readable state files.
  • Formats: Plain JSON/state files and Markdown transcripts.
  • Account independence: Local use needs no vendor account.
  • History portability: Provider conversation and local state can be backed up.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. CLI reference — Unpeel Docs

    Finding: Product CLI creates, inspects, sends, waits and controls sessions; serve install configures a per-user launchd/systemd service.

  2. Headless Host — Unpeel Docs

    Finding: Same server runs on an owned Mac/Linux host with service-manager setup and phone/Mac clients; full cloud-machine matrix remains under validation.

  3. https://raw.githubusercontent.com/unpeel-com/unpeel/e2e0e647a51422683639b858e08cf48b46827c9e/README.md

    Finding: Pinned README says server and Apple client sources are included, local/direct use is free, and only operated Link backend is closed.

Telemetry opt-out: Yes

Telemetry opt-out

Typed value: Yes.

Host content stays local; relay and notifications have different metadata paths.

  • Code data: Files/session content remain on owned Host.
  • Prompts: Agent provider receives its own requests; Unpeel stores no cloud copy.
  • Artifacts: Screenshots and Plugin state stay on Host.
  • Retention: Anonymous install-count rows kept historically.
  • Deletion: Account/control-plane deletion requested by contact; Host content is not held by service.
  • Subprocessors: Cloudflare, Stripe, email provider and Apple Push.
  • Telemetry disclosure: No behavioral analytics; update checks record random install ID/version/day dates.
  • Telemetry controls: UNPEEL_NO_UPDATE disables terminal-UI update counting; no equivalent Mac toggle established.
  • Provider separation: Agent providers have their own accounts/privacy policies.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Privacy policy — Unpeel

    Finding: No behavioral analytics; anonymous update records persist. Terminal UI can disable update checks with UNPEEL_NO_UPDATE. Relay cannot decrypt content; push carries bounded metadata.

Free access: Yes cross-checked

Free access

Typed value: Yes.

Local application and direct pairing are free.

  • Ongoing free: No trial, account, license or credit card for local Mac use.
  • Self host cost: Own host/provider accounts remain separate.
  • Free scenarios: Local agents, same-network direct pairing and self-hosted core.
  • Card required: No card required for local use.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

Starting price: Free: Yes. Free cross-checked

Starting price: Free

Typed value: Yes. Free.

Local application and direct pairing are free.

  • Ongoing free: No trial, account, license or credit card for local Mac use.
  • Self host cost: Own host/provider accounts remain separate.
  • Free scenarios: Local agents, same-network direct pairing and self-hosted core.
  • Card required: No card required for local use.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

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

Starting price: Up to $20/month

Typed value: No. Free.

Local application and direct pairing are free.

  • Ongoing free: No trial, account, license or credit card for local Mac use.
  • Self host cost: Own host/provider accounts remain separate.
  • Free scenarios: Local agents, same-network direct pairing and self-hosted core.
  • Card required: No card required for local use.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

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

Starting price: $21–40/month

Typed value: No. Free.

Local application and direct pairing are free.

  • Ongoing free: No trial, account, license or credit card for local Mac use.
  • Self host cost: Own host/provider accounts remain separate.
  • Free scenarios: Local agents, same-network direct pairing and self-hosted core.
  • Card required: No card required for local use.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

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

Starting price: $41–100/month

Typed value: No. Free.

Local application and direct pairing are free.

  • Ongoing free: No trial, account, license or credit card for local Mac use.
  • Self host cost: Own host/provider accounts remain separate.
  • Free scenarios: Local agents, same-network direct pairing and self-hosted core.
  • Card required: No card required for local use.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

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

Starting price: Over $100/month

Typed value: No. Free.

Local application and direct pairing are free.

  • Ongoing free: No trial, account, license or credit card for local Mac use.
  • Self host cost: Own host/provider accounts remain separate.
  • Free scenarios: Local agents, same-network direct pairing and self-hosted core.
  • Card required: No card required for local use.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

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

Starting price: Contact for pricing

Typed value: No. Free.

Local application and direct pairing are free.

  • Ongoing free: No trial, account, license or credit card for local Mac use.
  • Self host cost: Own host/provider accounts remain separate.
  • Free scenarios: Local agents, same-network direct pairing and self-hosted core.
  • Card required: No card required for local use.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

Pricing model: Free, no paid plan: No

Pricing model: Free, no paid plan

Typed value: No.

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

  • Currency: USD.
  • Interval: Link $59 per year.
  • Seats: Current activation seat is one Host machine.
  • Included usage: Local app and updates free; Link adds relay/push.
  • Model cost: Users provide coding-agent/provider subscriptions or API keys and pay those providers separately.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

Pricing model: Free plan: Yes

Pricing model: Free plan

Typed value: Yes.

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

  • Currency: USD.
  • Interval: Link $59 per year.
  • Seats: Current activation seat is one Host machine.
  • Included usage: Local app and updates free; Link adds relay/push.
  • Model cost: Users provide coding-agent/provider subscriptions or API keys and pay those providers separately.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

Pricing model: Subscription: Yes

Pricing model: Subscription

Typed value: Yes.

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

  • Currency: USD.
  • Interval: Link $59 per year.
  • Seats: Current activation seat is one Host machine.
  • Included usage: Local app and updates free; Link adds relay/push.
  • Model cost: Users provide coding-agent/provider subscriptions or API keys and pay those providers separately.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

Pricing model: Per seat: No

Pricing model: Per seat

Typed value: No.

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

  • Currency: USD.
  • Interval: Link $59 per year.
  • Seats: Current activation seat is one Host machine.
  • Included usage: Local app and updates free; Link adds relay/push.
  • Model cost: Users provide coding-agent/provider subscriptions or API keys and pay those providers separately.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

Pricing model: Usage-based: No

Pricing model: Usage-based

Typed value: No.

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

  • Currency: USD.
  • Interval: Link $59 per year.
  • Seats: Current activation seat is one Host machine.
  • Included usage: Local app and updates free; Link adds relay/push.
  • Model cost: Users provide coding-agent/provider subscriptions or API keys and pay those providers separately.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

Pricing model: Per machine or compute: Yes

Pricing model: Per machine or compute

Typed value: Yes.

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

  • Currency: USD.
  • Interval: Link $59 per year.
  • Seats: Current activation seat is one Host machine.
  • Included usage: Local app and updates free; Link adds relay/push.
  • Model cost: Users provide coding-agent/provider subscriptions or API keys and pay those providers separately.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

Pricing model: Bring your own key: Yes

Pricing model: Bring your own key

Typed value: Yes.

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

  • Currency: USD.
  • Interval: Link $59 per year.
  • Seats: Current activation seat is one Host machine.
  • Included usage: Local app and updates free; Link adds relay/push.
  • Model cost: Users provide coding-agent/provider subscriptions or API keys and pay those providers separately.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

  2. Unpeel provider-owned account and API-key setup

    Finding: Unpeel launches and manages installed coding-agent CLIs but does not replace their accounts or API keys. The user supplies those credentials and pays the separate agent/provider billing.

Pricing model: One-time purchase: No

Pricing model: One-time purchase

Typed value: No.

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

  • Currency: USD.
  • Interval: Link $59 per year.
  • Seats: Current activation seat is one Host machine.
  • Included usage: Local app and updates free; Link adds relay/push.
  • Model cost: Users provide coding-agent/provider subscriptions or API keys and pay those providers separately.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

Keeps going with laptop closed: Yes cross-checked

Keeps going with laptop closed

Typed value: Yes.

Owned hosts continue sessions independently of clients.

  • Local: Mac bundled server.
  • Byo remote: Owned headless Mac/Linux host, including cloud VM.
  • Self hosted: Same complete open-source server.
  • Provisioning: Installer and per-user service command.
  • Resources: 64-bit Linux glibc 2.31+; provider/runtime compatibility still being validated.
  • Client disconnect: Disconnecting client never stops host session.
  • Other device continuation: Mac/phone/CLI reconnect to same workspace.
  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Headless Host — Unpeel Docs

    Finding: Same server runs on an owned Mac/Linux host with service-manager setup and phone/Mac clients; full cloud-machine matrix remains under validation.

  2. Workspaces — Unpeel Docs

    Finding: Local, SSH and paired workspaces retain sessions/data on the owning host; additional local workspaces are experimental.

  3. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

Any desktop app: Yes

Any desktop app

Typed value: Yes.

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • Mobile apps: Native iPhone/iPad client through TestFlight.
  • Browser: Architecture explicitly describes web app as later.
  • Cli: Product-owned unpeel CLI.
  • Task actions: Phone views terminals, answers input and launches sessions.
  • Notifications: Mac notifications and optional Link phone push.
  • Cross device continuity: Mac/phone/CLI attach to same Host sessions.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

Any phone client: Yes

Any phone client

Typed value: Yes.

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • Mobile apps: Native iPhone/iPad client through TestFlight.
  • Browser: Architecture explicitly describes web app as later.
  • Cli: Product-owned unpeel CLI.
  • Task actions: Phone views terminals, answers input and launches sessions.
  • Notifications: Mac notifications and optional Link phone push.
  • Cross device continuity: Mac/phone/CLI attach to same Host sessions.
  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. https://raw.githubusercontent.com/unpeel-com/unpeel/e2e0e647a51422683639b858e08cf48b46827c9e/README.md

    Finding: Pinned README says server and Apple client sources are included, local/direct use is free, and only operated Link backend is closed.

All public findings

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

unpeel:ACC-01: Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

unpeel:ACC-01

Unpeel ships a native Apple-Silicon Mac GUI, iPhone/iPad clients and a native macOS/Linux CLI. The CLI rejects Windows. Android is absent from the complete current client list and the web client is explicitly later.

  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  3. CLI reference — Unpeel Docs

    Finding: Product CLI creates, inspects, sends, waits and controls sessions; serve install configures a per-user launchd/systemd service.

  4. https://raw.githubusercontent.com/unpeel-com/unpeel/e2e0e647a51422683639b858e08cf48b46827c9e/README.md

    Finding: Pinned README says server and Apple client sources are included, local/direct use is free, and only operated Link backend is closed.

  5. Unpeel native CLI platform restrictions

    Finding: The native CLI installer supports macOS and Linux and explicitly rejects other OSes. The shipped clients are Mac, iPhone/iPad and CLI; the web app is explicitly later, with no native Android build. CLI access is separate from a Linux GUI.

unpeel:ACC-02: CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration. cross-checked

unpeel:ACC-02

CLI runtime integration is provider- and launch-specific. Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  • The Antigravity runtime is scoped to macOS/Linux. Its output-based status is not marked reliable for completion or attention.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

  3. Agent runtimes — Unpeel Docs

    Finding: Managed launches bind provider conversation identity; merely observing a CLI in a blank terminal does not grant safe resume or transcript access.

  4. Unpeel Antigravity support at v0.7.6

    Finding: Unpeel v0.7.6 includes a built-in Antigravity runtime, agy launch preset, native resume capability and MCP configuration.

unpeel:ACC-03: Users bring provider logins and API keys. cross-checked

unpeel:ACC-03

Users bring provider logins and API keys.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Supported agents — Unpeel Docs

    Finding: Named CLI runtime launch, hooks, transcript and resume support differ; Pi uses output heuristics and MCP support is provider-specific.

unpeel:ACC-04: App setup bundles server; headless hosts have a supported installer. cross-checked

unpeel:ACC-04

App setup bundles server; headless hosts have a supported installer.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Headless Host — Unpeel Docs

    Finding: Same server runs on an owned Mac/Linux host with service-manager setup and phone/Mac clients; full cloud-machine matrix remains under validation.

unpeel:ACC-05: CLI and session-scoped MCP expose actual operations.

unpeel:ACC-05

CLI and session-scoped MCP expose actual operations.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. CLI reference — Unpeel Docs

    Finding: Product CLI creates, inspects, sends, waits and controls sessions; serve install configures a per-user launchd/systemd service.

  3. Overview — Unpeel Docs

    Finding: One session-scoped MCP server provides browser, peer sessions, runtimes, workspace setup and artifacts; grants control visibility and use.

unpeel:ACC-06: Built-in MCP and optional Plugins expose tools with per-session grants.

unpeel:ACC-06

Built-in MCP and optional Plugins expose tools with per-session grants.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Agent runtimes — Unpeel Docs

    Finding: Managed launches bind provider conversation identity; merely observing a CLI in a blank terminal does not grant safe resume or transcript access.

  2. Git worktrees — Unpeel Docs

    Finding: Optional worktrees are off by default and create child projects; agent worktree preparation requires an additional grant.

  3. Overview — Unpeel Docs

    Finding: One session-scoped MCP server provides browser, peer sessions, runtimes, workspace setup and artifacts; grants control visibility and use.

  4. Overview — Unpeel Docs

    Finding: Standalone terminal plugins can be surfaced as sessions/companions; widget rail is roadmap work, not current UI.

unpeel:ACC-07: Apple clients use Swift platform packages. cross-checked

unpeel:ACC-07

Apple clients use Swift platform packages.

  • Source statements were checked; no hands-on scenario was run.
  1. https://raw.githubusercontent.com/unpeel-com/unpeel/e2e0e647a51422683639b858e08cf48b46827c9e/README.md

    Finding: Pinned README says server and Apple client sources are included, local/direct use is free, and only operated Link backend is closed.

  2. https://raw.githubusercontent.com/unpeel-com/unpeel/e2e0e647a51422683639b858e08cf48b46827c9e/clients/native/UnpeelNative/Package.swift

    Finding: Apple client uses a Swift package with platform UI dependencies, linked to the shared Unpeel client/Host components.

  3. https://raw.githubusercontent.com/unpeel-com/unpeel/e2e0e647a51422683639b858e08cf48b46827c9e/clients/ios/UnpeelIOS/Package.swift

    Finding: Apple client uses a Swift package with platform UI dependencies, linked to the shared Unpeel client/Host components.

unpeel:PLAN-01: Project folders and presets provide session intake. cross-checked

unpeel:PLAN-01

Project folders and presets provide session intake.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Projects & presets — Unpeel Docs

    Finding: Users manage launch presets and project folders; arbitrary commands remain supported.

unpeel:PLAN-04: Provider transcripts and skill guidance are distinct from managed product memory. cross-checked

unpeel:PLAN-04

Provider transcripts and skill guidance are distinct from managed product memory.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Overview — Unpeel Docs

    Finding: One session-scoped MCP server provides browser, peer sessions, runtimes, workspace setup and artifacts; grants control visibility and use.

  2. Agents — Unpeel Docs

    Finding: Recognized runtime occurrences can be listed, read and waited on; stale occurrence references are rejected.

unpeel:PLAN-05: Browser tools and image attachments provide task context. cross-checked

unpeel:PLAN-05

Browser tools and image attachments provide task context.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Overview — Unpeel Docs

    Finding: One session-scoped MCP server provides browser, peer sessions, runtimes, workspace setup and artifacts; grants control visibility and use.

  2. Session gallery — Unpeel Docs

    Finding: Session gallery shows browser captures/downloads and user images; phone markup/attachment and Host-dependent write parity are documented. Video is not supported yet.

unpeel:PLAN-06: The scoped Unpeel core persists projects, presets and terminal sessions, without a native issue/backlog entity separate from sessions. Sidebar groups organize sessions rather than issue state.

unpeel:PLAN-06

The scoped Unpeel core persists projects, presets and terminal sessions, without a native issue/backlog entity separate from sessions. Sidebar groups organize sessions rather than issue state.

  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel PTY session execution and persistent model

    Finding: The core launches detached PTYs as the Host OS user and stores sessions/projects/presets, with optional Git worktrees. It has no per-agent container/VM provisioning or separate native issue entity. Host timer jobs are runtime observation/heartbeats, not an agent-work scheduler. The CLI explicitly supports script/CI/cron session control.

unpeel:COORD-01: Multiple live sessions run concurrently. cross-checked

unpeel:COORD-01

Multiple live sessions run concurrently.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Git worktrees — Unpeel Docs

    Finding: Optional worktrees are off by default and create child projects; agent worktree preparation requires an additional grant.

  3. Activity & the menu bar — Unpeel Docs

    Finding: Busy/done/needs-you states use provider hooks or output heuristics with explicit limits; status survives app restart.

unpeel:COORD-02: Workspace process leases and occurrence checks prevent stale targeting. cross-checked

unpeel:COORD-02

Workspace process leases and occurrence checks prevent stale targeting.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Agents — Unpeel Docs

    Finding: Recognized runtime occurrences can be listed, read and waited on; stale occurrence references are rejected.

unpeel:COORD-03: In the pinned v0.7.6 core, a session granted Create & remove can create worker sessions, inspect transcripts/state, wait and send instructions through Unpeel MCP. The 0.7.5 release note and implemented permission checks resolve the earlier documentation-parity gap.

unpeel:COORD-03

In the pinned v0.7.6 core, a session granted Create & remove can create worker sessions, inspect transcripts/state, wait and send instructions through Unpeel MCP. The 0.7.5 release note and implemented permission checks resolve the earlier documentation-parity gap.

  • Some current web documentation still says agents cannot create/close sessions. This answer is bounded to the published 0.7.5 change and pinned v0.7.6 implementation with explicit Create & remove permission; no hands-on run was performed.
  1. Overview — Unpeel Docs

    Finding: One session-scoped MCP server provides browser, peer sessions, runtimes, workspace setup and artifacts; grants control visibility and use.

  2. Sessions — Unpeel Docs

    Finding: Docs describe peer reads and directional write approval, but say agents cannot create/close sessions; this conflicts with newer 0.7.5 release notes.

  3. Changelog — Unpeel

    Finding: 0.7.5 removes archive/restore and old stopped scrollback, adds session-scoped Read/Write/Create & remove grants and OSC status reporting.

  4. Unpeel released MCP delegation role

    Finding: The pinned core exposes create_session, list/inspect peers, read_screen/read_output/read_transcript, waits and send_text/send_keys. A session granted Create & remove, represented by McpRole::Manage, can create workers and communicate with them. Release 0.7.5 introduced this access; the older docs prohibition on agent-created sessions is stale for this implementation.

unpeel:COORD-04: Unpeel's headless product CLI explicitly supports starting/driving sessions from external CI or cron. It does not supply an internal scheduler; the external caller owns timing and retries.

unpeel:COORD-04

Unpeel's headless product CLI explicitly supports starting/driving sessions from external CI or cron. It does not supply an internal scheduler; the external caller owns timing and retries.

  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel documented CI/cron command surface

    Finding: The public headless command surface explicitly supports agents, CI and cron driving sessions without a UI or desktop app. The new command creates a preset session programmatically and send/wait manage its work. Scheduling/event ownership stays with external cron or CI.

unpeel:COORD-05: Terminal state and intervention remain visible across clients.

unpeel:COORD-05

Terminal state and intervention remain visible across clients.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. CLI reference — Unpeel Docs

    Finding: Product CLI creates, inspects, sends, waits and controls sessions; serve install configures a per-user launchd/systemd service.

  2. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

  3. Sessions — Unpeel Docs

    Finding: Docs describe peer reads and directional write approval, but say agents cannot create/close sessions; this conflicts with newer 0.7.5 release notes.

  4. Sessions & terminals — Unpeel Docs

    Finding: Provider conversation resume differs from PTY survival; precise IDs or provider-specific fallbacks are used, and ambiguous process ownership refuses replacement.

  5. Activity & the menu bar — Unpeel Docs

    Finding: Busy/done/needs-you states use provider hooks or output heuristics with explicit limits; status survives app restart.

  6. Changelog — Unpeel

    Finding: 0.7.5 removes archive/restore and old stopped scrollback, adds session-scoped Read/Write/Create & remove grants and OSC status reporting.

unpeel:COORD-06: Fleet activity groups attention without requiring every transcript. cross-checked

unpeel:COORD-06

Fleet activity groups attention without requiring every transcript.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Activity & the menu bar — Unpeel Docs

    Finding: Busy/done/needs-you states use provider hooks or output heuristics with explicit limits; status survives app restart.

unpeel:COORD-07: Any command can run in a configurable preset. cross-checked

unpeel:COORD-07

Any command can run in a configurable preset.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. CLI reference — Unpeel Docs

    Finding: Product CLI creates, inspects, sends, waits and controls sessions; serve install configures a per-user launchd/systemd service.

  2. Projects & presets — Unpeel Docs

    Finding: Users manage launch presets and project folders; arbitrary commands remain supported.

unpeel:RUN-01: Owned hosts continue sessions independently of clients. cross-checked

unpeel:RUN-01

Owned hosts continue sessions independently of clients.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Headless Host — Unpeel Docs

    Finding: Same server runs on an owned Mac/Linux host with service-manager setup and phone/Mac clients; full cloud-machine matrix remains under validation.

  2. Workspaces — Unpeel Docs

    Finding: Local, SSH and paired workspaces retain sessions/data on the owning host; additional local workspaces are experimental.

  3. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

unpeel:RUN-02: Unpeel uses detached Host-user PTYs, separate workspace state and optional worktrees. The scoped core has no product-provisioned per-agent container or VM isolation backend.

unpeel:RUN-02

Unpeel uses detached Host-user PTYs, separate workspace state and optional worktrees. The scoped core has no product-provisioned per-agent container or VM isolation backend.

  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Git worktrees — Unpeel Docs

    Finding: Optional worktrees are off by default and create child projects; agent worktree preparation requires an additional grant.

  3. Overview — Unpeel Docs

    Finding: One session-scoped MCP server provides browser, peer sessions, runtimes, workspace setup and artifacts; grants control visibility and use.

  4. Overview — Unpeel Docs

    Finding: Standalone terminal plugins can be surfaced as sessions/companions; widget rail is roadmap work, not current UI.

  5. Unpeel PTY session execution and persistent model

    Finding: The core launches detached PTYs as the Host OS user and stores sessions/projects/presets, with optional Git worktrees. It has no per-agent container/VM provisioning or separate native issue entity. Host timer jobs are runtime observation/heartbeats, not an agent-work scheduler. The CLI explicitly supports script/CI/cron session control.

unpeel:RUN-03: Client/worker recovery differs from process death and stopped-output retention. cross-checked

unpeel:RUN-03

Client/worker recovery differs from process death and stopped-output retention.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Sessions & terminals — Unpeel Docs

    Finding: Provider conversation resume differs from PTY survival; precise IDs or provider-specific fallbacks are used, and ambiguous process ownership refuses replacement.

  3. Changelog — Unpeel

    Finding: 0.7.5 removes archive/restore and old stopped scrollback, adds session-scoped Read/Write/Create & remove grants and OSC status reporting.

unpeel:RUN-04: Host service and browser engine have product-owned setup.

unpeel:RUN-04

Host service and browser engine have product-owned setup.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Headless Host — Unpeel Docs

    Finding: Same server runs on an owned Mac/Linux host with service-manager setup and phone/Mac clients; full cloud-machine matrix remains under validation.

  3. Overview — Unpeel Docs

    Finding: One session-scoped MCP server provides browser, peer sessions, runtimes, workspace setup and artifacts; grants control visibility and use.

unpeel:RUN-05: Runtime identity checks bound resume operations. cross-checked

unpeel:RUN-05

Runtime identity checks bound resume operations.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. CLI reference — Unpeel Docs

    Finding: Product CLI creates, inspects, sends, waits and controls sessions; serve install configures a per-user launchd/systemd service.

  2. Sessions & terminals — Unpeel Docs

    Finding: Provider conversation resume differs from PTY survival; precise IDs or provider-specific fallbacks are used, and ambiguous process ownership refuses replacement.

unpeel:RUN-06: Status authority and retained diagnostic limits are explicit.

unpeel:RUN-06

Status authority and retained diagnostic limits are explicit.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Activity & the menu bar — Unpeel Docs

    Finding: Busy/done/needs-you states use provider hooks or output heuristics with explicit limits; status survives app restart.

  3. Changelog — Unpeel

    Finding: 0.7.5 removes archive/restore and old stopped scrollback, adds session-scoped Read/Write/Create & remove grants and OSC status reporting.

  4. https://raw.githubusercontent.com/unpeel-com/unpeel/e2e0e647a51422683639b858e08cf48b46827c9e/README.md

    Finding: Pinned README says server and Apple client sources are included, local/direct use is free, and only operated Link backend is closed.

unpeel:RUN-07: Usage plugins are optional external views; billing reconciliation remains unverified.

unpeel:RUN-07

Usage plugins are optional external views; billing reconciliation remains unverified.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Overview — Unpeel Docs

    Finding: Standalone terminal plugins can be surfaced as sessions/companions; widget rail is roadmap work, not current UI.

  2. unpeel-usage README (pinned Unpeel repository)

    Finding: Optional standalone unpeel-usage Plugin reuses local CLI logins to show provider usage: Claude 5-hour/7-day and Grok/Codex weekly allowance percentages used, plus local token totals and per-project tokens. It is not per-task billing.

unpeel:TEAM-01: Paired clients can enter the same terminal session.

unpeel:TEAM-01

Paired clients can enter the same terminal session.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Workspaces — Unpeel Docs

    Finding: Local, SSH and paired workspaces retain sessions/data on the owning host; additional local workspaces are experimental.

  2. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

unpeel:TEAM-02: Unpeel's core uses paired-client Host access. Agent-session MCP grants are separate from human team roles; the scoped core has no organization/project human role model or enterprise SSO.

unpeel:TEAM-02

Unpeel's core uses paired-client Host access. Agent-session MCP grants are separate from human team roles; the scoped core has no organization/project human role model or enterprise SSO.

  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel human access versus agent grants

    Finding: Human access is paired-client Host access. Read/Write/Create & remove controls apply to agent sessions, not named organization/project human roles. The scoped open-source core has no enterprise SAML/OIDC SSO flow; operated Link account/relay internals are separate.

unpeel:TEAM-03: Peer writes and device access are scoped and revocable. cross-checked

unpeel:TEAM-03

Peer writes and device access are scoped and revocable.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

  2. Overview — Unpeel Docs

    Finding: One session-scoped MCP server provides browser, peer sessions, runtimes, workspace setup and artifacts; grants control visibility and use.

  3. Sessions — Unpeel Docs

    Finding: Docs describe peer reads and directional write approval, but say agents cannot create/close sessions; this conflicts with newer 0.7.5 release notes.

unpeel:TEAM-04: Host files and provider transcripts retain inspectable history.

unpeel:TEAM-04

Host files and provider transcripts retain inspectable history.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. How Unpeel runs — Unpeel Docs

    Finding: Rust Host owns detached PTY sessions and clients only attach; server/worker restarts can preserve sessions, but machine reboot cannot.

  2. Agents — Unpeel Docs

    Finding: Recognized runtime occurrences can be listed, read and waited on; stale occurrence references are rejected.

  3. Changelog — Unpeel

    Finding: 0.7.5 removes archive/restore and old stopped scrollback, adds session-scoped Read/Write/Create & remove grants and OSC status reporting.

unpeel:TEAM-05: Unpeel's optional first-party Git sidebar App displays proposed working-tree code changes and commit patches in native/terminal renderers. Image-gallery markup remains a separate review path.

unpeel:TEAM-05

Unpeel's optional first-party Git sidebar App displays proposed working-tree code changes and commit patches in native/terminal renderers. Image-gallery markup remains a separate review path.

  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Session gallery — Unpeel Docs

    Finding: Session gallery shows browser captures/downloads and user images; phone markup/attachment and Host-dependent write parity are documented. Video is not supported yet.

  2. Unpeel optional Git review App

    Finding: The first-party Git App, install slug diffs and binary unpeel-diffs, is registered in the App catalog. It displays staged/unstaged/conflicted/untracked changes and unified code patches, plus commit-history patches, using the same terminal/native App Kit renderer. It supports fetch/pull/push but no pull-request create/manage operation.

unpeel:TEAM-06: Another paired client can inspect and continue the same session. cross-checked

unpeel:TEAM-06

Another paired client can inspect and continue the same session.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Workspaces — Unpeel Docs

    Finding: Local, SSH and paired workspaces retain sessions/data on the owning host; additional local workspaces are experimental.

  2. Agents — Unpeel Docs

    Finding: Recognized runtime occurrences can be listed, read and waited on; stale occurrence references are rejected.

unpeel:SHIP-01: Per-session image artifacts connect browser output to phone review.

unpeel:SHIP-01

Per-session image artifacts connect browser output to phone review.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

  2. Overview — Unpeel Docs

    Finding: One session-scoped MCP server provides browser, peer sessions, runtimes, workspace setup and artifacts; grants control visibility and use.

  3. Session gallery — Unpeel Docs

    Finding: Session gallery shows browser captures/downloads and user images; phone markup/attachment and Host-dependent write parity are documented. Video is not supported yet.

unpeel:SHIP-03: Unpeel's optional Git App displays history/diffs and performs fetch, fast-forward pull and push. The scoped App/CLI has no native pull-request creation or management control; agents may use external forge CLIs.

unpeel:SHIP-03

Unpeel's optional Git App displays history/diffs and performs fetch, fast-forward pull and push. The scoped App/CLI has no native pull-request creation or management control; agents may use external forge CLIs.

  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Unpeel PTY session execution and persistent model

    Finding: The core launches detached PTYs as the Host OS user and stores sessions/projects/presets, with optional Git worktrees. It has no per-agent container/VM provisioning or separate native issue entity. Host timer jobs are runtime observation/heartbeats, not an agent-work scheduler. The CLI explicitly supports script/CI/cron session control.

  2. Unpeel optional Git review App

    Finding: The first-party Git App, install slug diffs and binary unpeel-diffs, is registered in the App catalog. It displays staged/unstaged/conflicted/untracked changes and unified code patches, plus commit-history patches, using the same terminal/native App Kit renderer. It supports fetch/pull/push but no pull-request create/manage operation.

unpeel:OWN-02: Core local/direct functionality can be hosted without Link. cross-checked

unpeel:OWN-02

Core local/direct functionality can be hosted without Link.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. CLI reference — Unpeel Docs

    Finding: Product CLI creates, inspects, sends, waits and controls sessions; serve install configures a per-user launchd/systemd service.

  2. Headless Host — Unpeel Docs

    Finding: Same server runs on an owned Mac/Linux host with service-manager setup and phone/Mac clients; full cloud-machine matrix remains under validation.

  3. https://raw.githubusercontent.com/unpeel-com/unpeel/e2e0e647a51422683639b858e08cf48b46827c9e/README.md

    Finding: Pinned README says server and Apple client sources are included, local/direct use is free, and only operated Link backend is closed.

unpeel:OWN-03: Host content stays local; relay and notifications have different metadata paths. cross-checked

unpeel:OWN-03

Host content stays local; relay and notifications have different metadata paths.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

  2. Privacy policy — Unpeel

    Finding: No behavioral analytics; anonymous update records persist. Terminal UI can disable update checks with UNPEEL_NO_UPDATE. Relay cannot decrypt content; push carries bounded metadata.

unpeel:OWN-04: Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

unpeel:OWN-04

Local app is free; optional Link is billed yearly per Host seat. Installed coding agents retain the user's own provider accounts and API keys.

  • This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

  2. Unpeel provider-owned account and API-key setup

    Finding: Unpeel launches and manages installed coding-agent CLIs but does not replace their accounts or API keys. The user supplies those credentials and pays the separate agent/provider billing.

unpeel:OWN-05: Costs separate free local software from optional service and agent usage. cross-checked

unpeel:OWN-05

Costs separate free local software from optional service and agent usage.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

unpeel:OWN-06: A dated release and contact support are available. cross-checked

unpeel:OWN-06

A dated release and contact support are available.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

  2. Changelog — Unpeel

    Finding: 0.7.5 removes archive/restore and old stopped scrollback, adds session-scoped Read/Write/Create & remove grants and OSC status reporting.

unpeel:OWN-08: Local application and direct pairing are free. cross-checked

unpeel:OWN-08

Local application and direct pairing are free.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Getting started — Unpeel Docs

    Finding: Free Apple-Silicon Mac client bundles server. Projects can be any folder; provider CLI accounts are separate.

  2. Unpeel Link — Unpeel Docs

    Finding: Link is optional operated encrypted relay and push; service does not store session content and host must remain reachable.

  3. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.

unpeel:OWN-09: Optional service price and cancellation are public. cross-checked

unpeel:OWN-09

Optional service price and cancellation are public.

  • Documentation establishes only the named atomic answers; remaining questions and hands-on behavior are unverified.
  1. Terms of service — Unpeel

    Finding: Mac application is free without trial/account/license; Link is $59 per Host seat yearly. Terms prohibit redistribution of modified app builds.