Skip to main content
← All articles

Agent Workspace

6 articles tagged with this topic.

Agent Architecture · 9 min read

Decoupled Brain and Hand: Architecture Design and Boundary Governance for Enterprise Agent Platforms

Moving single-node agents into enterprise multi-tenant environments requires crossing four chasms: host corruption, credential leakage, gateway timeouts, and asset ownership. The enterprise agent platform architecture decouples brain and hand: a high-availability control plane (Harness) owns the reasoning loop and state machine, while an elastic sandbox pool leases isolated compute on demand. This article explains the four system boundaries of enterprise agent platforms: control-plane and execution decoupling, secret exclusion with egress proxies, append-only incremental state, and team workspaces as persistent assets.

Every Agent · 10 min read

Every Agent: Enterprise Agents Shift from Personal Replicas to Shared Teammates

Every (Every.to), a tech publication focused on AI workflows, initially deployed isolated cloud agents for every employee before switching to a single shared agent for the entire company. This shift highlights an architectural reality: enterprise agents belong in team workspaces rather than per-user silos, sharing durable capabilities while strictly isolating sessions, credentials, and execution environments.

Manus · 7 min read

Manus 2.0 Cloud Computer: Agents Need Persistent Work Environments

Manus uses temporary remote Sandboxes for individual tasks. Cloud Computer preserves files, installed tools, and running processes across sessions. CubePlex retains working files in persistent storage, with separate environments for personal and team work.