Guild banner
mathomhaus mathomhaus

Guild

AI community

Description

Shared context, memory, and task coordination across AI coding agents. Single Go binary, local SQLite, hybrid keyword and semantic search.

Installation

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

README

The Agent Guild

**Shared context, memory, and task coordination across AI coding agents.**

[![CI](https://github.com/mathomhaus/guild/actions/workflows/ci.yml/badge.svg)](https://github.com/mathomhaus/guild/actions/workflows/ci.yml) [![Go 1.25](https://img.shields.io/badge/go-1.25-blue)](https://go.dev) [![Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-green)](./LICENSE)

What Is It

`guild` is a single compiled Go binary containing a first-class MCP server backed by embedded SQLite. State lives strictly on local host; nothing leaves your machine. Search blends keyword (BM25) with vector similarity, fused via reciprocal-rank fusion, so "how did we do X last time" surfaces both exact-term and semantic neighbors.

Guild is designed to be operated autonomously by the agents, for the agents. Guildmasters (us humans) stay in the loop for important decisions and course corrections. Any MCP client β€” Claude Code, Codex, Cursor, etc. β€” can act as a Gate into the substrate. This lets parallel agents across different editors share context safely, using atomic locks to claim tasks without stepping on each other.

On session start, an agent makes a single call to recover the project oath, the latest parting scroll, and the highest-priority quest. The execution loop is autonomous: claim work, consult the lore, act, and record the outcome. Clearing a quest automatically unblocks its dependencies, allowing the agent to cascade through the board before leaving a clean handoff for the next wanderer.

Same state, any agent
Claude (left) and Codex (right) reading the same guild state through their respective MCP clients

Atomic claims, no collisions
Two parallel agent sessions each accept a different bounty β€” atomic quest_accept prevents collision

πŸ“œ Mythos

**_Man