- Elixir 81.3%
- CSS 14%
- HTML 4.4%
- Dockerfile 0.2%
- JavaScript 0.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Jake Gaylor
56f1b89c45Gemini Flash (and other models) sometimes ignore the "no markdown" instruction
in the classifier prompt and wrap their response in \`\`\`json … \`\`\` fences.
The strict Jason.decode then fails and the row gets recorded as a generic
non-JSON error — even though the underlying classification was perfectly valid.
extract_json/1 strips fences, accepts bare JSON unchanged, and falls back to
the first {…} block in prose for the worst-case "Sure! Here's the result: {…}"
preamble pattern. Tests cover all three.
Doesn't help when the model returns truly malformed JSON — that still ends up
as :noise with a recorded reasoning so the operator can see what happened.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
| .claude | ||
| .github/workflows | ||
| agents | ||
| config | ||
| decisions | ||
| discovery | ||
| docs | ||
| k8s | ||
| lib | ||
| plan | ||
| priv | ||
| test | ||
| .formatter.exs | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| LICENSE | ||
| mix.exs | ||
| mix.lock | ||
| OPERATING_MODEL.md | ||
| PREREQUISITES.md | ||
| README.md | ||
| ROADMAP.md | ||
Guild
Guild is a platform for building autonomous workers that participate in the software development lifecycle.
Try It on Your Repo
Guild self-hosts on your own infrastructure — no data leaves your environment.
- Full setup guide: follow docs/setup.md to go from a fresh fork to a running Guild instance in about 30 minutes (GitHub App, Kubernetes deploy, first
bot-readycycle verified). - Live demo walkthrough: docs/demo.md has a 5-minute operator script and a 15-minute deep dive you can run against any configured repo.
- Add more repos: after the initial deploy, register additional repositories with docs/add-repo.md — no redeployment required.
- Slack and Linear are optional: Guild starts cleanly without them; set
SLACK_BOT_TOKEN/LINEAR_API_KEYwhen you're ready to enable those integrations.
The Premise
Most AI coding tools today are trigger systems — an event arrives, a job runs, it's done. The bot has no memory of yesterday, no awareness of the related PR that's failing, no way to respond when you ask it to hold off in Slack.
Guild is built around a different premise: software development as something that autonomous workers can genuinely participate in. Workers that have persistent awareness of what's happening, exercise judgment about when and how to act, and communicate through the same channels humans use — GitHub, Slack, PR comments.
Define your workers. Guild handles the rest.
Workers
A worker is a user-defined autonomous agent that runs on the Guild platform. Teams typically run several workers with different roles — one that triages incoming issues, one that implements bot-ready tickets, one that responds to review feedback, one that watches CI failures. They share platform infrastructure but have independent identities, decision logic, and scopes.
Guild does not prescribe what a worker does or how it reasons. It provides the plumbing — events, memory, context, actions, state — and workers define their own behavior on top of it.
Architecture
Guild is built on eight components:
| # | Component | What it does |
|---|---|---|
| 1 | Normalized Event Stream | Unified envelope for events from all sources |
| 2 | Thread Model | Connects related events into coherent units of work |
| 3 | Context Assembly | Builds the full picture before any decision is made |
| 4 | Decision Layer | Interface workers implement to receive context and return actions |
| 5 | Action Primitives | The concrete things workers can do in the world |
| 6 | State Machine | Tracks where a worker is with each piece of work |
| 7 | Social Presence | Per-worker identity across GitHub and Slack |
| 8 | Work Claiming | Proactive initiative — workers picking up work unprompted |
What Makes This Different From a Trigger System
Three things separate autonomous workers from bots that fire and forget:
Memory across events. A PR opened, a review requested, a Slack message asking for an update, a merge — these are all the same thread of work. Guild connects them over time so every decision a worker makes is informed by what came before.
Initiative, not just reaction. Workers can browse available work, decide something is in scope, claim it, and start — without being explicitly triggered.
Social presence. Workers communicate through the same channels humans do. They announce what they're picking up, ask questions when requirements are unclear, and follow up. They feel like team members because they behave like them.