gufo
AGENTS.md1.1k starsChanged 8 days agoMITView on GitHub
These rules apply to everything under docs/. They keep the documentation short, consistent and readable by people and agents alike. A public page explains how to use something. An internal page explains how it is built, measured or changed. When a page needs both, split it: the public page links to the internal one. Every public page starts with a # Title line, a blank line and a one- or two-sentence summary; the website uses both for the page title…
Trending
More talk lately.about the whole repository
Who's talking about gufo-org/gufo
- @matheus23.com“Gufo is pretty impressive. Running Qwen 3.8 Flash Next on my strix halo machine locally is now feels …”Bluesky · Oct 1, 2026 · 5 likes
- ItzCrazyKns/Vane“Every request fails with 400 "unsupported keyword: $schema" against strict OpenAI-compatible backends”GitHub · Nov 6, 2026
- mecattaf/dotfiles“Load Gufo models through llama-swap and unload them when idle”GitHub · Nov 1, 2026
- neuhaus/gufo“perf(tp2): hand pending snapshot captures the MTP execution lock”GitHub · Oct 30, 2026
- LostVector/gufo“perf(cache): retain reused frontiers and active branch checkpoints”GitHub · Oct 30, 2026
The biggest 5 of 15 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 15
Talked about on GitHub and Bluesky (15 times).
On GitHub · 14
- Nov 6, 2026Every request fails with 400 "unsupported keyword: $schema" against strict OpenAI-compatible backends — ItzCrazyKns/Vane0 reactions
- Nov 1, 2026Load Gufo models through llama-swap and unload them when idle — mecattaf/dotfiles0 reactions
- Oct 30, 2026perf(tp2): hand pending snapshot captures the MTP execution lock — neuhaus/gufo0 reactions · 2 comments
- Oct 30, 2026perf(cache): retain reused frontiers and active branch checkpoints — LostVector/gufo0 reactions
- Oct 30, 2026perf(tp2): hand pending snapshot captures the MTP execution lock — LostVector/gufo0 reactions · 1 comment
9 more on GitHub
- Oct 29, 2026How does gufo get such high prefill on Strix Halo, and what can Maya take from it? — b-iurea/project-maya0 reactions · 1 comment
- Oct 27, 2026build: use ROCm 10.1 throughout Linux images — gufo-org/toolboxes0 reactions
- Oct 27, 2026ci: follow renamed Gufo Windows build workflow — gufo-org/toolboxes0 reactions
- Oct 27, 2026docs(bench): report Phoenix CUDA/NPU experiments — mikealanni/gufo0 reactions · 1 comment
- Oct 26, 2026Add Gufo LXC script — Heretek-AI/ProxmoxVE0 reactions · 4 comments
- Oct 25, 2026ci(release): attach Windows bundles to Gufo releases — gufo-org/toolboxes0 reactions
- Oct 22, 2026Podman container-proxy worker backend (retire llama-swap) — Syakyr/orchard0 reactions
- Oct 18, 2026Model IDs containing spaces are rejected — moooossee/moose0 reactions · 2 comments
- Oct 13, 2026update: gufo (gufo v0.20.0) — mecattaf/dotfiles0 reactions · 2 comments
On Bluesky · 1
- Oct 1, 2026Gufo is pretty impressive. Running Qwen 3.8 Flash Next on my strix halo machine locally is now feels entirely differently: llama.cpp: ~400… — @matheus23.com5 likes and reposts
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- benchmark-modelSkill
- optimize-kernelSkill
The file
We split this AGENTS.md into the rules it gives an agent
12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Every public page starts with a # Title line, a blank line and a one- or two-sentence summary.
- Very specific: line 29
Write like the Gufo blog: plain, direct and exact.
- Distinctive: line 32
Prefer plain words to jargon.
- Distinctive: line 39
Use tables only to compare things across the same columns.
- Distinctive: line 43
Use plain Markdown that renders on GitHub: no MDX, HTML components or scripts.
- Distinctive: line 48
Every sentence must earn its place.
- Very specific: line 57
Don't list every flag or field.
- Very specific: line 70
Run python3 tools/ci/check-docs.py after editing.
- Distinctive: line 81
Add a figure only when it shows a structure or flow faster than prose: what sits where, what happens in which order, what is reused.
- Very specific: line 105
use fig-head for row labels, fig-title and fig-sub inside boxes, fig-note for annotations, fig-box plus one color class for boxes and …
- Distinctive: line 113
leave about 20% spare width around text, because fallback fonts differ in width from the website fonts.
- Very specific: line 116
Keep color meaning consistent within a page: one color per kind of thing, and fig-muted for anything reused, inactive or out of scope.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Documentation
These rules apply to everything under docs/. They keep the documentation
short, consistent and readable by people and agents alike.
Layout
| Path | Audience | Published |
docs/*.md, docs/models/*.md | People using or extending Gufo | Website, one copy per release |
docs/figures/ | Figures for public pages | Website, with the pages |
docs/internal/ | Contributors and agents working on Gufo | Repository only |
docs/internal/models/<model>/ | Implementation notes (README.md), benchmarks, quality and experiment evidence | Repository only |
docs/internal/server.md, docs/internal/cache.md | Complete server and cache references behind the public pages | Repository only |
docs/internal/design/ | Design RFCs | Repository only |
A public page explains how to use something. An internal page explains how it is built, measured or changed. When a page needs both, split it: the public page links to the internal one.
Every public page starts with a # Title line, a blank line and a one- or
two-sentence summary; the website uses both for the page title and
description. README.md is the documentation home: it lists every
public page in reading order, and the website builds its navigation from it.
Model pages are listed in models/README.md instead.
Style
Write like the Gufo blog: plain, direct and exact.
- Address the reader as "you". Use the active voice. Contractions are fine.
- Prefer plain words to jargon. When a term is needed, put it in bold and define it the first time it appears on the page. Use one name for one concept across all pages.
- Lead with what the reader does or gets; follow with why only when the reader needs it to decide something.
- Give numbers exactly, with units, and date measurements: "As of November
2026, ...". Link the evidence under
docs/internal/instead of repeating it. - Use tables only to compare things across the same columns. Use a numbered list only when order matters.
- Mark warnings (trust, exposure, data loss) with a blockquote starting with
**Warning:**. - Use plain Markdown that renders on GitHub: no MDX, HTML components or scripts. Code blocks name their language.
Concision
Every sentence must earn its place; a reader should find the answer without reading the whole page.
- One topic per page. One fact lives in one place; elsewhere, link to it.
- Budgets: 250 lines for a public page, 120 for a model page. Over budget means
split the page or move detail to
docs/internal/. - Public pages hold current behavior only: no history ("used to", "now",
"recently"), no PR or issue numbers, no design rationale. Rationale belongs in
docs/internal/design/. - Don't list every flag or field; show the ones a reader needs and point to
gufo <command> --helpfor the rest. - Cut filler: "simply", "just", "easily", "basically", "obviously", "note that", "it is worth", "seamless", "blazing".
Keeping docs current
- A change in user-visible behavior updates the page that owns it in the same pull request.
- A new public page needs a maintainer's agreement; prefer extending an existing page.
- Evidence files (JSON, logs, archives, charts) live only under
docs/internal/. - Run
python3 tools/ci/check-docs.pyafter editing. It enforces the title and summary, the index listing, line budgets, filler words, issue numbers on public pages and the figure rules below.
Figures
Figures are static SVG files in docs/figures/, named after what they show
(cache-reuse.svg). They render as images on GitHub and are inlined on the
website, where they pick up its fonts. Copy
figures/cache-reuse.svg as a starting point.
Add a figure only when it shows a structure or flow faster than prose: what sits where, what happens in which order, what is reused. The prose must still say everything the figure says, because agents read the text, not the picture.
Reference a figure as an image followed by an italic caption line:

*Figure 1. A repeated prefix is restored, not recomputed.*The alt text describes what the figure shows in one sentence; the caption states its point.
Each SVG must:
- set
widthandheightequal to itsviewBoxsize, 760 wide, and draw<rect class="fig-bg" rx="10">as its first shape so it reads on both light and dark GitHub themes; - embed
figures/style.cssverbatim in its<style>element and use only its classes: no inline colors, fonts orstyleattributes; - use
fig-headfor row labels,fig-titleandfig-subinside boxes,fig-notefor annotations,fig-boxplus one color class for boxes andfig-flow/fig-dashwithfig-arrowheadmarkers for arrows; - carry
role="img"and a<title>matching the alt text; - prefix every
idwith the file name (cache-reuse-arrow), because the website inlines several figures into one page; - contain no
<script>,<foreignObject>,<image>, externalhrefor web fonts, and stay under 30 KB; - leave about 20% spare width around text, because fallback fonts differ in width from the website fonts.
Keep color meaning consistent within a page: one color per kind of thing, and
fig-muted for anything reused, inactive or out of scope.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

