A medieval pixel town in the island, fifteen screens wide, where every coding agent running on this Mac is a villager with a house and a nametag. You walk it with the arrow keys; every building opens, and walking up to an agent and pressing Enter opens its full transcript. Read the rest before installing. Bot Village reads coding-agent transcript files directly from your home directory: Cursor (~/.cursor/projects), Claude Code (~/.claude/projects), Codex (~/.codex/sessions), the Cirrulet agent harness, and Grok Bot's $AGENT_DATA layout. It is a native plugin loaded into the Cirrulet process, so it reads those files with the app's own filesystem access rather than through a brokered host capability. Transcript content appears on screen: a villager's bubble carries a summarised sentence of its agent's last turn, and the transcript panel shows whole user and assistant messages at full length, so anything an agent says can be visible on a display you may be sharing. Tool calls, tool results and reasoning are dropped in the parser and never shown. Messages travel two optional routes, both off until you set them up. The webhook sends to a URL you configure; its address and sender key live in plugin-scoped host storage and the key is never logged, echoed, or placed in an error. The Claude Code bridge, if you press Connect, writes a small script under Application Support and adds two hook entries (Stop and SubagentStop) to ~/.claude/settings.json — a file you did not hand the plugin; it is rewritten by a JSON encoder, a copy of the original is kept beside it, and Disconnect removes both entries and the script. Nothing else leaves the machine. The townsfolk indoors — the innkeeper, the smith — are the plugin's own fiction and say nothing about any agent; only villagers with nametags are real sessions.