You need: Windows 10 or 11, macOS, or Linux, Java 25, Node 22+, git, and a copy of Minecraft: Java Edition.

For the real agents you need Claude API access, either of these:

• ANTHROPIC_API_KEY: create a key at console.anthropic.com, then setx ANTHROPIC_API_KEY sk-ant-... and open a new terminal.
• A cloud provider supported by the Agent SDK: Amazon Bedrock (CLAUDE_CODE_USE_BEDROCK=1), Google Vertex AI (CLAUDE_CODE_USE_VERTEX=1) or Microsoft Foundry (CLAUDE_CODE_USE_FOUNDRY=1), with that provider's usual credentials.

Then:

git clone https://github.com/blendi-remade/agentcraft
cd agentcraft

tools\launch.ps1 -Backend sim                    # try it first: a simulated team, no API usage
tools\launch.ps1 -Repo C:\path\to\your\repo      # real agents on your repo
tools\stop.ps1                                   # stop everything launch.ps1 started

On macOS, install Java 25 with brew install openjdk@25. On Linux, install your distribution's Java 25 JDK (on Arch: pacman -S jdk25-openjdk) or point JAVA_HOME at one. Then run from the checkout (the script selects that JDK without changing your system Java):

node tools/unix.mjs launch --backend sim                 # try the studio without API usage
node tools/unix.mjs stop --profile sim
node tools/unix.mjs launch --repo /path/to/your/repo --use-claude-login
node tools/unix.mjs stop

This launcher installs npm dependencies on first run, downloads Minecraft and Fabric through Gradle, starts the Foreman and game in the background, and waits for the studio world. Use --dev for a muted client that does not take focus; --no-game starts only the Foreman, which is also how you pair it with your own launcher instance (Prism and the like). See tools/README.md for options, logs and the own-launcher setup.

The first launch installs npm dependencies and lets Gradle download Minecraft and Fabric, which takes a few minutes. After that, a launch reaches the studio in under a minute. The HQ builds itself the first time; in an older world, rebuild it with /agentcraft hq.

Personal use with Claude Code. If you already use Claude Code, tools\launch.ps1 -UseClaudeLogin runs the agents on your own claude CLI login instead of an API key. Anthropic does not allow third party tools to offer claude.ai login to their users, so this is off by default and meant for running AgentCraft yourself. To make it permanent for yourself, put {"claude": {"useClaudeLogin": true}} in ~/.agentcraft/config.json.

Codex. AgentCraft also runs Codex agents. With the Codex CLI or the Codex desktop app installed and logged in (codex login, with ChatGPT or an OpenAI API key):

tools\launch.ps1 -Backend codex -Repo C:\path\to\your\repo                       # an all-Codex team
tools\launch.ps1 -Repo C:\path\to\your\repo -ForemanArgs '--worker-engine','codex'   # Claude lead, Codex workers

Codex agents live in the same studio and follow the same rules: their own git worktrees, every command checked by AgentCraft's policy (and asked in game when it needs you), the lead's review, and your Merge. They never get your own Codex MCP servers, plugins, apps or web search. Pick models with --codex-model, and mix engines per agent with --engines kit=codex,wren=claude. Every agent's nameplate shows the model it runs, like Opus 5.5 or GPT-6 Astra, so a mixed team is easy to read at a glance.

Your name. The agents call you by your OS user name. Change it with -ForemanArgs '--user-name','Sam', AGENTCRAFT_USER_NAME, or {"userName": "Sam"} in ~/.agentcraft/config.json.

<br>