Glovebox
Solo builders who drive Claude Code daily install Glovebox to keep agent shell and file mutations inside a MicroVM while the orchestrator stays on the laptop.
Overview
Glovebox is a plugin marketplace for the Build phase that runs every Claude Code Bash, Read, Write, and Edit action inside a MicroVM while keeping Claude as the on-host orchestrator.
What is this marketplace?
- Single marketplace plugin (Glovebox v0.1.0) that intercepts Bash, Read, Write, and Edit for MicroVM isolation.
- Claude Code remains the on-host orchestrator; only the risky tool surface runs sandboxed.
- Targets indie workflows where one person grants agents broad repo access without a full CI sandbox farm.
- Pairs naturally with security-minded ship habits before merging agent-generated diffs.
- Low plugin count—one focused isolation layer rather than a broad skill bundle.
- 1 plugin in the glovebox marketplace (Glovebox v0.1.0).
- Sandbox scope explicitly covers Bash, Read, Write, and Edit agent actions.
What problem does it solve?
Letting a coding agent run shell and file tools on your main machine feels convenient until one bad command or overreach wipes trust in the whole workflow.
Who is it for?
Indie developers who live in Claude Code and want MicroVM isolation without standing up a separate remote dev box for every session.
Skip if: Teams that only use chat-style assistants with no Bash/Write tooling, or builders who already enforce all agent work exclusively in remote CI with no local agent tools.
What do I get? / Deliverables
After you register Glovebox, agent mutations and commands execute in an isolated MicroVM so your host stays the control plane, not the blast radius.
- Glovebox plugin registered in your Claude Code marketplace
- Agent tool actions routed through MicroVM isolation instead of bare host execution
- A repeatable local pattern for safer agent-driven shell and file work
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Glovebox wraps Claude Code’s Bash, Read, Write, and Edit paths in a MicroVM so agent workflows stay on the host while tool execution is isolated—the canonical shelf is agent tooling during product construction. Sandboxing is installed specifically to harden how coding agents touch the filesystem and shell, not as a one-off deploy checklist item.
How it compares
Execution sandbox for Claude Code plugins, not a persona skill pack or MCP server catalog.
Common Questions / FAQ
Who is Glovebox for?
Glovebox is for solo and small-team builders who orchestrate products through Claude Code and need Bash, Read, Write, and Edit isolated in a MicroVM on the same laptop.
When should I use Glovebox?
Use it whenever you let Claude Code run shell or filesystem tools against real repos—especially before trusting agent-generated changes on a machine that holds API keys and personal data.
How do I add Glovebox to my agent?
Add the Glovebox Claude Code marketplace from the jed4ever/Glovebox source, install the Glovebox plugin (v0.1.0), and enable it so agent tool calls route through the MicroVM sandbox described in the listing.