Greybook is a community-maintained troubleshooting manual for coding agents — Claude Code, Codex, Cursor, Gemini CLI, and the rest. It exists because the collective knowledge about these tools currently evaporates in chat threads and social feeds within days of being written down.
Discussion should improve a durable public answer page rather than disappear into a chronological comment thread.
On a forum, the best answer to a problem is buried on page four, written eight months ago, for a version nobody runs anymore. Here, every problem, recipe, and config is a living record with a canonical summary at the top: current status, the fastest verified fix, what did not work, and which versions it applies to. Comments still exist — but the good ones get promoted into that record, and the record is what search engines, newcomers, and future-you actually find.
Nothing here is marked “verified” because a moderator felt good about it. Verification is an accumulation of small, structured community actions: “I have this problem”, “reproduced on 2.4.1 / macOS 15”, “this fix worked”, “this fix failed”, “this is outdated”. Each action is a named, per-account signal, and the counts roll up into the status badge on the page. When enough people confirm a workaround, the status flips. When a new agent release makes a page stale, “outdated” flags push it back into review. The structured counts are the verdict; prose is just the explanation.
Trust is earned through contribution history, and each rung unlocks a little more editorial responsibility.