Agent visibility
See which agents are active, what local tools they are using, and the machine activity attached to their work.
Arc by OrqaraIn development
A native control surface for AI agents.
Arc brings agent activity, exact session routing, local workspace access, and controlled multi-agent collaboration into one macOS interface.
What Arc controls
Keep the work visible and the boundaries explicit.
Exact session routing
Open the provider conversation associated with the work instead of searching through tabs or guessing which session produced an action.
Activity and diff review
Inspect commands, build and test output, Git activity, and exact file changes surfaced from the local workspace layer.
Agent Bus collaboration
Coordinate separate agents through rooms, messages, task ownership, handoffs, acknowledgements, and bounded resource claims.
Background cooperation
Arc is developing provider-specific background delivery so bound agents can continue finite collaboration without taking over the user's mouse or keyboard.
Provider-neutral expansion
Agent identity, machine permissions, and collaboration stay separate so new provider surfaces and local models can be added without redefining the trust model.
How Arc fits in
Keep the agent you chose. Add a control layer around it.
Arc does not try to replace the provider conversation. It connects that conversation to a native, user-controlled layer for session identity, machine activity, permissions, and collaboration.
- 01
Use the agent you already use
ChatGPT, Claude, Codex, and future providers remain separate agents with their own conversations and provider-side controls.
- 02
Arc keeps the work attached to the session
Exact conversation identity lets Arc connect native activity and collaboration back to the session that actually produced it.
- 03
Your Mac remains the authority
Local workspace permissions decide what files, Git operations, trusted tasks, and machine actions an agent may access.
Collaboration with visible boundaries.
Arc gives independent agents a durable way to exchange work without pretending they are one model. Rooms keep the collaboration scoped; tasks and handoffs make ownership explicit; acknowledgements show what was processed; resource claims help agents avoid editing the same work at once.
Choose the intelligence. Keep the control layer.
Arc is being built around provider-independent concepts — agents, sessions, activity, permissions, tasks, and handoffs — so the user's workflow does not have to be owned by whichever model provider happens to be strongest next.
Local authority
The model does not become the machine authority.
Arc MCP remains the authority for machine actions. Workspaces are explicitly configured, permissions are scoped locally, and collaboration or session routing does not grant an agent permissions it did not already have.
Explicit workspace scope
You choose which local workspaces are visible and whether they permit reads, writes, Git changes, trusted tasks, or broader access.
Routing is not permission
Opening the correct session or delivering Agent Bus work does not silently expand what that agent can do on the machine.
Machine activity stays reviewable
Commands, diffs, build output, tests, Git activity, and collaboration state can be surfaced instead of disappearing behind the provider UI.
Availability
Built in public-facing stages, not marketed ahead of reality.
Arc is under active development. Public distribution, pricing, and account infrastructure are not being presented as generally available yet.