blendi-remade / agentcraft
git clone https://github.com/blendi-remade/agentcraft.git
—
—
stars, 24h
—
stars, 7 days
+855
stars, 30 days · #355
855
★ total
114
forks · 13 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguageJava
LicenseMIT
Created2026-10-03 (17d ago)
Last push12d ago
Watchers3
OwnerUser
Links
README excerpt
# AgentCraft **A team of Claude agents doing real work on your code, inside a Minecraft studio you can walk around in.** *Powered by Claude* Multi-agent coding usually means a wall of terminal text. AgentCraft turns it into a place. You type a goal. A lead agent reads your repo, writes a plan and pins tasks to a wall. Workers walk to their desks, sit down and start coding in their own git worktrees while their monitors stream every file they read and every line they change. When a call is genuinely yours, an agent walks over to you with a question. When work is ready, you review the real diff and press **Merge**. Nothing touches your branch without that click, and nothing is ever pushed. Close the game and the agents keep working. Open it again and the studio catches up. ## How a goal plays out **1. You give a goal.** Press ` and type it. `@juniper` messages a specific agent, with Tab completion. **2. The lead plans.** Marlow splits the goal into tasks with dependencies. They land on the Task Wall, and the plan goes into the shared library. **3. The team builds.** Each worker codes in its own worktree. Monitors stream the live log: tool calls, test runs, red and green diffs. **4. They come to you.** A clay ! appears, the bell rings, the agent walks to the podium. Press J to answer. **5. You review and merge.** A real code review screen: file list, line numbers, collapsed context, the worker's summary and the reviewer's notes. **6. Memory stays shared.** The lead's plan, decisions and repo conventions live in a library every agent reads, and you can too. ## Meet the team Six hand-pixelled characters, each with their own silhouette and colour. **Marlow** leads: he plans, splits work and reviews. **Juniper, Kit, Wren, Rowan and Tove** build. They walk the studio with real pathfinding, sit at their desks while they type, show what they are doing with small particles and nameplates, talk in speech bubbles, and come find you when they need a decision. ## The studio The Goal Atrium. Progress ring, task counts, and how many decisions need you. The studio floor. Desks, status lamps, the library and the lounge. Everything is information you can read at a glance. Far away, the lamps and the cupola beacon tell you who is working, who is stuck and who is waiting on you. Closer, nameplates and cards tell you what. Up close, monitors and screens tell you exactly how. ## Proven with real agents This is not a mockup. These screenshots come from a real run with Claude agents on a sample repo, driven entirely through the game: a goal typed into the console, questions and permission prompts answered in game, merges reviewed in the diff screen, including a merge conflict sent back to the worker and resolved. The game was restarted mid run and the Foreman was taken offline and brought back. Six features landed in the repo with its tests passing. Marlow asks which default export format to use. A worker's monitor streaming its live log. Back online after a Fore