Jack your AI coding agents in. Isolated worlds, scoped access, full autonomy. You're the Operator. They're already inside.
jackin' is the ecosystem layer around AI coding agents — not another agent itself. It runs many agents in parallel, each in its own container, with its own file access, tool profile, and credentials. Every agent runtime (Claude Code --dangerously-skip-permissions, Codex YOLO, Amp, and the next ones to come) is most productive at full speed — and full speed against your host machine is risky. jackin' moves the boundary off the host, so the runtime can stay fast.
Documentation: https://jackin.tailrocks.com/
Current status: jackin' is experimental preview software. It has not reached a stable release yet, and breaking changes are expected while the core design and basic functionality settle. The docs track the rolling preview channel, which is the best way to see what the project is today. Claude Code and Codex ship today as fully integrated agent runtimes. Amp is under active development and will join them; full feature parity across all three is tracked on the roadmap.
brew tap jackin-project/tap
brew install jackin@previewOr build from source if you prefer.
The simplest way to use jackin' is the operator console — an interactive TUI that picks workspaces, roles, and agents for you:
jackin(Or jackin console to be explicit.) The console is the daily driver and covers the common cases of every other command.
If you'd rather see the isolation model in action with a single one-shot command, jackin load is the scriptable CLI equivalent:
jackin load agent-smithThat pulls the base image, builds the agent container, mounts your project, and drops you into the agent runtime — fully autonomous inside an isolated environment.
See the Quick Start guide for the full walkthrough, and jackin console for the TUI reference.
- Isolates each agent in its own Docker container with Docker-in-Docker enabled
- Gives agents full autonomy inside the container boundary (whatever full-speed mode the runtime ships — Claude's
--dangerously-skip-permissions, Codex's YOLO, etc.) - Separates tooling from file access — roles define the environment, workspaces define which files are visible
- Supports multiple agents simultaneously — different tool profiles against the same or different projects
- Persists agent state between sessions (conversation history, GitHub CLI auth, plugins)
Learn more: Why jackin'? · Core Concepts · Security Model · Comparison with Alternatives
| Repository | Description |
|---|---|
| jackin | CLI source code (this repo) |
| jackin-agent-smith | Default general-purpose role |
| jackin-the-architect | Rust development role (used for jackin' development) |
| construct image source | Shared base Docker image for all roles |
This README is a first impression. The full documentation at https://jackin.tailrocks.com/ is where every detail lives:
- Why jackin'? — the problem and the ecosystem framing
- Installation — install methods and prerequisites
- Quick Start — first-run walkthrough, console + CLI side by side
- Core Concepts — operators, agents, roles, constructs, workspaces
jackin console— the daily-driver TUI- Commands — full reference (TUI first, then CLI)
- Security Model — what the boundary protects and what it doesn't
- Comparison with Alternatives — honest snapshot vs. Docker Sandboxes and others
- Behind jackin' (Internals) — Architecture, Codebase Map, Roadmap
To develop jackin' itself, use The Architect — a dedicated role with the full Rust toolchain:
jackin load the-architectjackin' is an independent personal project by Alexey Zhokhov. It is not affiliated with or endorsed by any employer or client of the author.
This project is licensed under the Apache License 2.0.