Quick Start
Load your first agent
Section titled “Load your first agent”In jackin’, the first thing you choose is usually an agent class. That is the tool profile you want to run. agent-smith is the default starter class included by this project.
-
Navigate to your project directory
Terminal window cd ~/Projects/my-app -
Load an agent
Terminal window jackin load agent-smithThe first time you run this, jackin’ will:
- Pull the construct base image
- Clone the agent-smith repository
- Build a derived Docker image with Claude Code installed
- Create an isolated Docker network
- Launch the container with your current directory mounted
-
You’re inside
Claude Code starts automatically with full permissions inside the container. Your project directory is mounted at the same path, so the agent sees the same file layout you do.
-
Exit when done
Press
Ctrl+Cor type/exitin Claude Code to leave. The container stops, but its state is persisted for next time.
If you already know you want a more specialized agent class, swap agent-smith for something else such as the-architect.
Use the interactive launcher
Section titled “Use the interactive launcher”If you prefer a visual interface:
jackin launchThis opens a TUI where you can:
- Pick from saved workspaces or use the current directory
- Preview which directories will be mounted
- Choose which agent to load
Reconnect to a running agent
Section titled “Reconnect to a running agent”If you close your terminal but the agent is still running:
jackin hardline agent-smithThis reattaches your terminal to the running container’s session.
Stop an agent
Section titled “Stop an agent”# Stop a specific agentjackin eject agent-smith
# Stop ALL running agentsjackin exileCommon workflows
Section titled “Common workflows”# Start of day — load agent into your projectjackin load agent-smith ~/Projects/my-app
# Work with Claude Code inside the container...
# End of day — stop the agentjackin eject agent-smith# Save workspaces for your projectsjackin workspace add frontend --workdir ~/Projects/frontendjackin workspace add backend --workdir ~/Projects/backend
# Load agents into different workspacesjackin load agent-smith frontendjackin load agent-smith backend
# Both agents run simultaneously in isolated containers# Same project access boundary, different tool profilesjackin workspace add monorepo --workdir ~/Projects/monorepo
jackin load agent-smith monorepojackin load the-architect monorepo
# Same files, different environment and plugins# Mount a reference codebase as read-onlyjackin load agent-smith ~/Projects/my-app \ --mount ~/Projects/shared-lib:/shared:roNext steps
Section titled “Next steps”- Learn the Core Concepts behind jackin’s architecture
- Set up Workspaces for your projects
- Understand the Security Model