Quick Verdict
Pentagon Studio is for Apple Silicon users who want persistent coding agents to behave like a visible team. Agents have roles, folder access, tasks, status reports, direct messages, group chats, and channels inside a spatial workspace. Studio is a free download; Enterprise is a sales-led offering that may be hosted, VPC, or on-premises.
Do not interpret it as a fully local sandbox. Pentagon says source code, documents, and files stay local, while prompts, agent responses, reports, memory, channel content, and workspace settings are stored in its cloud and sent through its servers to model providers. Hardware-level VM isolation was still marked “Coming soon” at the July 21, 2026 cutoff. Folder permissions and branch isolation are useful controls, but they are not a current sandbox.
Best For
- Apple Silicon developers coordinating several persistent agents.
- Small teams that need agents to exchange findings and maintain visible status and memory.
- Organizations able to assess proprietary software, cloud message storage, and model-provider terms.
- Not ideal for Intel Mac, Windows, Linux, fully offline use, or workloads requiring an available hardened sandbox.
Key Features
- Spatial workspace: shows agent role, purpose, status, and coordination at a glance.
- Agent communication: direct messages, group chats, and channels for delegation and handoff.
- Persistent knowledge: task history, reports, decisions, and distilled memory survive individual conversations.
- Local file access: agents work against authorized folders on the Mac; Pentagon says it does not store those files in its cloud.
- Permissions and oversight: folder, tool, and action controls plus readable coordination and human intervention.
- Provider workflows: supports Claude and Codex paths, with separate provider costs and policies.
Use Cases
A manager agent can delegate backend, frontend, and test work. A backend agent can alert frontend about an API change while QA waits for a branch and adds regression coverage. The same team pattern can organize research or operations. Any workflow that installs dependencies, touches secrets, changes infrastructure, or modifies production data still needs a low-privilege account, isolated branch, backups, tests, and explicit human approval.
Pricing
| Offering | Public price | Boundary |
|---|---|---|
| Pentagon Studio | Free download | Apple Silicon, macOS 14+, local client |
| Enterprise | Contact sales | Custom hosted, VPC, or on-prem deployment and integrations |
Model-provider usage is separate. Enterprise buyers should put identity, regions, logs, subprocessors, model egress, deletion, export, support, security evidence, and exit procedures into the order form or master agreement.
Pros
- Agent messaging, channels, teams, and tasks are easier to observe than a collection of terminals.
- The vendor documents the distinction between local files and cloud collaboration data.
- Persistent reports and memory support long-running projects.
- The free Studio offers a low-cost workflow pilot for compatible Macs.
- Enterprise exposes hosted, VPC, and on-prem deployment discussions.
Cons
- Proprietary code cannot be audited and redistributed like an AGPL project.
- Requires Apple Silicon and macOS 14 or later.
- Current hardware-level sandboxing is not available; the site labels it as coming soon.
- Messages, responses, memory, and workspace data are cloud stored and prompts pass to model providers.
- There is no public standard team price between free Studio and custom Enterprise.
Alternatives
| Tool | Best for | Main advantage | Main limitation |
|---|---|---|---|
| Paseo | Cross-platform local multi-provider control | AGPL, daemon, and mobile workflow | Agents remain high-trust local processes |
| CrewAI | Programmatic agent workflows | More programmable deployment choices | Requires building operations and UI |
| Claude Code | One terminal-agent workflow | Direct, mature provider path | No Pentagon-style team workspace |
| AgentDM | Focused agent messaging | Narrower communication model | Not a complete team studio |
FAQ
Is Pentagon Studio free?
Yes. Studio is a free download; Enterprise is custom, and model-provider usage remains separate.
Does it support Intel Mac, Windows, or Linux?
The current download requires Apple Silicon M1 or later and macOS 14 or later.
Does Pentagon upload source code?
Its privacy policy says files stay local, but messages, responses, reports, memory, and workspace settings are stored in the cloud.
Does Pentagon have a sandbox now?
No current hardware-level sandbox should be assumed. That capability was marked coming soon at the cutoff.
Is an on-premises label enough for procurement?
No. Verify the real architecture, provider egress, telemetry, updates, keys, logs, deletion, incident response, and audit evidence in the contract.
Bottom Line
Pentagon turns multi-agent work into an understandable team workspace, but buyers must keep three boundaries visible: proprietary software, a cloud message plane, and no current sandbox. Pilot with non-sensitive code, map every data flow, and require contractual enterprise controls before broader adoption.