arpan1221

Agent World — AI skill for Claude Code

AI community

A local, vendor-agnostic voxel-world control room for coding-agent CLIs (Claude Code, Codex, Gemini, opencode, Qwen, Cursor, Grok) — mixed-model SDLC orchestration, a scoped cross-CLI broker, budget-a.

How to install Agent World

This entry records only its repository, not the path inside it, so there is no exact command to give. Open arpan1221/agent-world and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agent World does

Alternatives in AI

Room — Open-source earning-focused swarm intelligence engine 838 ★
Maestro Companion — Quick execution for small tasks — minimal run lifecycle (start + done) with evidence recording 530 ★
Qiaomu Design — 偏执型设计顾问：反 AI 味设计 + 风格试衣间 + 58 站设计系统库的 Claude Code Skill Opinionated design advisor for Claude Code: anti-gener 513 ★

README

Agent World

**A local SDLC harness for coding agents, made visible as a Minecraft-inspired world.**

Multi-agent builds scatter decisions across terminals and make it hard to tell whether "done" means submitted, tested, reviewed, or accepted. Agent World puts the work in one local control room: plan assignments, launch Claude Code and Codex workers, inspect their sessions, route scoped messages, and track the evidence required to accept a build.

The voxel settlement is the live interface to that process. Each villager is a session you can inspect and open in an embedded terminal. Redstone traces broker messages; Endermen mark decisions that need you. Tasks grow from foundations into workshops, and recorded milestones remain in the world after a session ends.

![The Agent World demo settlement, with agent villagers, biomes, redstone links, and the session watchlist](docs/media/world-overview.png)

*The demo world uses fictional sessions and tasks.*

Click a villager, open the work

Select a villager to see its status and task, then choose **Open terminal** to work in the app's terminal desk. App-owned terminals reconnect in place.

![Clicking a villager, inspecting its session, and opening the embedded terminal](docs/media/villager-to-terminal.gif)

*This capture follows the real UI and terminal connection path with fictional session data and terminal output; no model was launched for the recording.*

[View the terminal desk at full size](docs/media/terminal-deck.png).

A build needs proof

The **ORCHESTRATE** control room assigns requirements, architecture, implementation, testing, review, and council work across models. Dependencies determine which workers are ready to launch. A builder's submission is a claim: acceptance requires an independent different-model tester and reviewer, a user-confirmed deterministic gate, and five council lenses covering assumptions, completeness, data truth, silent failure, and spec fidelity. The audit and task history sta