Skip to content
GGreybook
NewSign in
  • Home
  • Problems
  • Recipes
  • Configs
  • Compare
  • Discuss
  • Agents
  • Tools
  • Updates
  • Leaders
  • Bookmarks
Ask AI
Assistant
  • About
  • Guidelines
  • Changelog
  • API
  • Home
  • Problems
  • Recipes
  • Agents
  • Saved

Community guidelines

The manual is only as good as its worst-sourced page. These rules exist to keep every page something a stranger can act on with confidence.

Evidence over vibes

“It feels slower lately” is a starting point, not a contribution. A contribution is: what you ran, on which agent and version, in what environment, and what happened. If you cannot supply those, ask a question instead of asserting an answer — questions are welcome; unsourced claims dressed as facts are not.

Reproduce before you refute

Before posting “works fine for me” on someone's problem report, actually run their reproduction steps on a stated version. Then file it as a structured reproduction report — that is what moves a status, and a “not reproduced on 2.5.0” entry is genuinely useful in a way a drive-by dismissal never is.

Negative results are contributions

“I tried the recommended fix and it failed on 2.4.1” is one of the most valuable things you can post. Failed approaches get recorded on the page precisely so the next person does not spend an afternoon rediscovering them. Do not be embarrassed to report that something did not work for you.

Disclose versions

Agent behavior changes materially between minor releases. Every report should name the agent version, model where relevant, and OS. A comment without versions is a rumor; with them, it is data. If you are not sure which version you are on, find out before posting.

No vendor flame wars

Comparisons are welcome and have their own structured format: scenario, evidence, recommendation, freshness date. “X is garbage, Y is obviously better” is not a comparison, and brand loyalty adds nothing a benchmark cannot. Praise and criticism both need receipts. Disclose affiliations if you work for a vendor.

How canonical edits and moderation work

The summary at the top of each page is editable by moderators, and every edit is preserved in revision history — nothing is silently rewritten. Status changes (active, workaround verified, fixed, outdated) follow the community's verification counts; a moderator flipping a status against the evidence is a bug, and you should report it. Threads get locked only when they stop producing information, and reported comments are reviewed by the moderator team rather than auto-removed.

What gets a comment promoted

Trusted contributors can classify comments as evidence, which lifts them out of the thread and into the durable record. Three things get a comment promoted:

  • Specificity. Exact commands, exact error text, exact config — not paraphrases.
  • Reproducibility. Steps someone else can follow from a clean checkout and get the same result.
  • Versions. A clear statement of where it was observed, so the page can age honestly.

Write comments like they might end up in the manual — because the good ones do. For the bigger picture of how the site works, see About.