Interactive Examples
agentvisor exec mode bridges your terminal directly into the sandbox, letting you run any interactive command — Claude Code, Aider, a shell, or a custom script — with the same policy-enforced HTTP proxying and credential substitution that serve mode provides.
Prerequisites
- No Temporal required
- No HTTP API configuration needed
- Just
agentvisor exec .(or--commandto override)
The framework configuration (mav-agent-config.yaml) selects the interactive provider and uses framework.command to specify what runs inside the sandbox:
framework:
provider: interactive
command: ["claude", "--dangerously-skip-permissions"]
How It Differs from serve/run
| Aspect | agentvisor serve | agentvisor exec |
|---|---|---|
| Entry point | LangGraph graph via HTTP API | Any command (shell, AI coding tool, etc.) |
| Temporal required | Yes | No |
| HTTP API exposed | Yes (port 8090) | No |
| Session type | Non-interactive, API-driven | Interactive, TTY-attached |
| Checkpointing | Yes (Temporal) | No |
| SSE streaming | Yes | No |
When to Use exec Mode
- Running Claude Code or another AI coding assistant inside an isolated sandbox
- Running Aider, Cursor (CLI), or similar tools that need network access restricted to specific APIs
- Dropping into a bash shell inside the sandbox for debugging or exploration
- Executing a custom one-shot script that needs the proxy or MCP gateway but not Temporal
Available Downcalls
| Feature | Available |
|---|---|
| HTTP proxy (with credential substitution) | Yes |
| MCP gateway | Yes |
| A2A gateway | Yes |
| Key-value store | Yes |
| Log forwarding | Yes |
| Checkpointing | No |
| SSE streaming | No |
Checkpointing and SSE streaming require Temporal workflows and the HTTP API, which exec mode intentionally omits.
Key Concepts
The example pages below use a few terms without re-explaining them each time:
| Concept | What It Is |
|---|---|
| Downcall | A host-initiated RPC into the guest (the reverse of the guest-initiated calls that carry HTTP proxying, MCP/A2A gateway access, the key-value store, and log forwarding). The Available Downcalls table above lists which of these host-to-guest operations apply in exec mode. |
--mount | A CLI flag that bind-mounts a host directory into the sandbox for the session, e.g. --mount $PWD:/work:rw:cwd (path:mountpoint:ro|rw[:cwd]). Absent by default — without it, the sandbox has no access to your project files at all. See Simple Shell: Coding Agent with Project Access for the full syntax and read-only vs. read-write tradeoffs. |
| Sandbox templating | {{.Image}} and similar {{.Xxx}} placeholders in a project's Dockerfile, resolved at build time to the correct base image and variant so a custom Dockerfile doesn't have to hardcode a version tag. See exec reference — Customizing the Sandbox Environment for the full variable list. |
Examples
| Example | Description |
|---|---|
| Simple Shell | The minimum interactive provider config — a plain /bin/sh shell with an Ollama-only HTTP policy, no credential brokering |
| Claude Code | Sandboxed Claude Code CLI with credential brokering and Anthropic-only HTTP policy |
| VS Code Tunnel | Full VS Code IDE connected via Microsoft's tunnel relay, sandboxed with a GitHub + VS Code infrastructure HTTP policy |