Architecture
Understand the local agent, Jio bridge, remote workspace, and the boundary between them.
Jio divides agent-driven development into a local control plane and a remote execution plane. MCP is the narrow interface between them.
Your machine
Local agent
Model, prompts, planning, and conversation history stay with you.
Connection
Jio bridge
A narrow MCP interface carries approved tool requests across the boundary.
Remote machine
Workspace
Files, dependencies, commands, and build output live in the sandbox.
What lives where
| Local agent environment | Remote workspace |
|---|---|
| Model and provider credentials | Project files and generated artifacts |
| Prompts and conversation history | Installed dependencies |
| Planning and tool selection | Filesystem operations |
| MCP client and Jio bridge | Commands, processes, and output |
| User approval interface | Resource and network enforcement |
The distinction is architectural, not cosmetic. If a tool can still reach arbitrary paths or processes on the local machine, the execution boundary has not been established.
Request lifecycle
The agent selects a tool
The local model decides that it needs to inspect a file, make a change, or run a command.
The bridge validates the request
Jio translates the MCP call, attaches workspace identity, and applies the relevant approval policy.
The remote service performs the operation
Execution happens inside the configured workspace with its filesystem, resource, and network controls.
A structured result returns
The agent receives output, exit status, or a policy error and decides what to do next.
Workspace lifecycles
A persistent workspace keeps repositories, dependency caches, and build output across sessions. It is useful for long-running projects, but needs maintenance and periodic cleanup.
Design consequence
Keep the bridge small. Every extra local capability expands the trusted surface. Workspace operations belong on the remote side unless a feature genuinely requires local state.
Remote does not automatically mean isolated
The host still needs operating-system permissions, resource limits, and network controls. Jio provides the tool boundary; your deployment enforces the machine boundary.