abx-managed-agent

Connect an agent's file and shell tools to remote sandboxes via harness bindings.

11|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/scitix/Agent-Sandbox --skill abx-managed-agent-scitix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: abx-managed-agent
Source: https://github.com/scitix/Agent-Sandbox/tree/main/plugin/skills/abx-managed-agent
Command: npx skills add https://github.com/scitix/Agent-Sandbox --skill abx-managed-agent-scitix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents that run bash, read, write, and edit tools on the host machine lose their work on restart and clutter the local environment. This Skill binds those tools to a remote sandbox per conversation, so work survives restarts, is browsable from a file UI, and is reclaimed on a timer. ## Core Features & Use Cases - Harness Bindings: Provides hands bindings for Claude Agent SDK, OpenCode, and a generic MCP binding for any other harness, all sharing one core behavior. - Platform Setup Guidance: Walks through the prerequisites that must exist first — an env with an E2B-compatible template, a pool sized to concurrent conversations, and a tenant key for the right identity. - Identity & Credential Model: Explains per-person versus service-owned sandbox identity, and how decoy credentials with egress-sidecar substitution keep real secrets out of the sandbox. - Use Case: You run a Claude Agent SDK-based product and want each user conversation to execute shell commands in its own durable sandbox instead of on your server. This Skill tells you which binding to wire, how to size the pool, and which identity model to choose. ## Quick Start Ask the agent to connect your Claude Agent SDK harness's bash and file tools to an AgentBox sandbox for the current conversation.

Frequently Asked Questions about abx-managed-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect Claude Agent SDK tools to a remote sandbox?

Use the hands binding at sdk/hands/typescript/src/harness/claude-code/, which replaces the built-in bash, read, write, edit, grep, glob, and apply_patch tools with sandbox-backed versions. The binding talks to the sandbox over the E2B API through the hands daemon.

How do I integrate sandboxed tools with OpenCode or another agent harness?

OpenCode has a dedicated binding at sdk/hands/typescript/src/harness/opencode/. Any other harness uses the generic MCP binding at sdk/hands/typescript/src/harness/mcp/. All bindings share the same core behavior and differ only in harness vocabulary.

Does sandboxing an agent's tools isolate the agent from my machine?

No. Confinement of tools is not isolation — the agent process still runs on your host with your files and credentials, and only its tool actions move into the sandbox. For real isolation, run the harness itself inside a container.

How do I size the sandbox pool for concurrent agent sessions?

Size the pool against concurrent conversations, not total users — ten people with one session each means ten replicas. Use abx scale envs <env> pools <pool> --replicas 10, and see the abx-resource-capacity skill for detailed sizing.

Should each user get their own sandbox identity or share a service identity?

Both models work: per-person identity lands sandboxes in each user's namespace and quota, while service-owned identity uses one namespace with conversation ownership recorded in sandbox metadata. Pick one deliberately, and always use a tenant key, never an admin key.

Can an agent inside the sandbox steal API keys or credentials?

The sandbox holds no real credentials — decoy values sit in the environment and the egress sidecar substitutes real ones per host and header on the way out. Third-party tokens should be delivered through the vault and injection rules, not environment variables.