A coding team you can see.
AgentCraft brings AI coding work into a Minecraft studio. Here is what the project does, how its parts fit together, and a browser illustration of the idea.
Minecraft is the interface. Code is the work.
The upstream project describes a lead agent planning a coding goal, workers doing tasks, and a person reviewing the result. A Minecraft room makes that work visible through desks, monitors, a task wall, and a shared library. Read the project overview
The useful idea is spatial visibility: where an agent is standing can help explain what it is doing and whether it needs your attention. That is our interpretation of the design. The room is an interface to a coding system, rather than a tool for converting an image into Minecraft blocks.
A readable team
People, places, and task cards give the workflow a visible shape.
Separate workspaces
The upstream coding system uses Git worktrees to isolate task changes.
A human checkpoint
The project includes decision prompts and a diff review before a merge.
The idea, in miniature
Walk through the workflow.
Watch a small, predefined story about adding a dark theme. We built this browser illustration to explain the project; it is not a recording of AgentCraft running.
Marlow
Juniper
Kit
Wren
Rowan
ToveStatic studio map. The workflow explanation is available below.
Sample stage 1
A goal arrives
Sample goal: add a dark theme to a small website. The lead receives the goal; no repository is connected here.
Marlow
Ready
Juniper
Ready
Kit
Ready
Wren
Ready
Rowan
Ready
Tove
Ready
Playback only. This presentation does not run agents, access a repository, or call an AI model. Motion is paused by default to match your device preference.
Read all six stages
- 1. A goal arrives
Sample goal: add a dark theme to a small website. The lead receives the goal; no repository is connected here.
- 2. The lead makes a plan
Marlow divides the work into research, interface changes, and tests. Dependencies help the team work in the right order.
- 3. Workers build separately
The illustration shows parallel work. In AgentCraft, coding tasks use separate Git worktrees; the game displays their activity.
- 4. A decision needs you
Sample question: should the theme follow the device setting? Real AgentCraft can request a human decision. This sample has no answer form.
- 5. Changes are reviewed
In the real project, a person reviews the actual diff and approves a merge. The podium here only illustrates that checkpoint.
- 6. The team keeps its context
Plans and decisions belong in shared memory. The sample ends here; it has generated, tested, and merged no code.
Six faces, different roles.
Marlow is the lead. The five workers have distinct visual identities and specialties in the upstream cast. The names and portraits below are from AgentCraft; the sample activity above is ours.
Marlow
Lead · plans & reviews
Juniper
Research
Kit
Build & test
Wren
Interface design
Rowan
Refactor & review
Tove
Archive & QA
Cast source: AgentCraft character definitions.
Three layers behind the room.
01
Minecraft mod
The Fabric mod presents the studio, characters, activity, and user decisions.
02
Foreman service
The Node.js service coordinates goals, task states, decisions, and persistent context.
03
Coding backend
The Claude Agent SDK backend performs coding work; a separate simulation backend is also included.
The connection carries structured state, not just a video feed. The protocol definitions describe agents, tasks, goals, decisions, memory entries, and activity updates. That separation is why the same task can appear as a card, a character status, or a detailed review.
This page borrows the presentation idea, not the execution service. In the inspected server implementation, connections carrying a browser Origin are rejected by default. Connecting a public browser UI would require a separate, carefully designed service boundary. Nothing on this page connects to Foreman.
What to know before trying the real project.
- The inspected setup targets Minecraft: Java Edition with Fabric, Java 25, Node.js 22+, and Git. It is separate from the browser illustration and from Bedrock Edition.
- Real agent work requires supported Claude access and can incur provider costs. This page does not request credentials or start model calls.
- The upstream simulation avoids AI API usage, but its demo workflow can still perform real Git operations. Treat its launcher as executable software, not a harmless animation.
- The room helps surface state. It cannot establish that a change is correct: review the code, tests, permissions, and repository behavior yourself.
For setup and operating details, follow the upstream launcher documentation and Foreman documentation. Check the current repository before installing: an early project can change quickly.
How we checked this introduction
We read the project documentation, protocol and connection-handling source, and character definitions at revision 0be815d on October 4, 2026. We have not run its Minecraft client or a real coding-agent session. Upstream demonstrations and test results are the maintainers' reports, not our independent verification.
This is an independent explanation by Minecraft Pixel Art Editorial Team. We are not affiliated with AgentCraft, Anthropic, or Mojang. Our room layout is an adaptation; the six skins and portraits are credited to AgentCraft contributors under the MIT license.
Found an error? Send a correction with the source. See our editorial methodology for how we handle factual updates.