fizzy
AGENTS.md8.3k starsChanged 12 months agoLicence not identifiedView on GitHub
Fizzy is a kanban-style project management and issue tracker: cards move across columns on boards, with comments, mentions, and assignments. These instructions are defaults with reasons, not law — when…
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about basecamp/fizzy
- rails/rails“Passkeys”GitHub · Mar 30, 2026 · 46 reactions
- A Hacker News story“37signals open-sources Kanban tracking tool Fizzy”Hacker News · Dec 4, 2025 · 8 points
- rubyaustralia/melbourne-ruby“Talk Proposal: Exploring Fizzy inside and out”GitHub · Dec 3, 2025 · 6 reactions
- A Hacker News story“Basecamp/Fizzy”Hacker News · Dec 3, 2025 · 4 points
- A Hacker News story“Fizzy, the Kanban tracking tool for issues and ideas by 37signals”Hacker News · Dec 2, 2025 · 4 points
The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 57
Talked about on GitHub, Hacker News, Bluesky and Stack Overflow (57 times).
On GitHub · 50
- Mar 30, 2026Passkeys — rails/rails46 reactions · 10 comments
- Dec 3, 2025Talk Proposal: Exploring Fizzy inside and out — rubyaustralia/melbourne-ruby6 reactions
- Feb 26, 2026fix: rename body to description in card payload — robzolkos/n8n-nodes-fizzy2 reactions · 1 comment
- Dec 11, 2025[App Request] - Fizzy — getumbrel/umbrel-apps1 reaction · 1 comment
- Dec 3, 2025Add basecamp/fizzy — eliotsykes/real-world-rails1 reaction
45 more on GitHub
- Nov 16, 2025Make flaky parallel tests easier to diagnose by deterministically assigning tests to workers — rails/rails1 reaction · 2 comments
- Nov 13, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 12, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 11, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 10, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 9, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 8, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 7, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 6, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 5, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 4, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 3, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 2, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Nov 1, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 31, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 30, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 29, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 28, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 27, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 26, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 25, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 24, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 23, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 22, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 21, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 20, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 19, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 18, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 17, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 16, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 15, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 14, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 13, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 12, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 11, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 10, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 9, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 8, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 7, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 6, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 5, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 4, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Oct 3, 2026chore: Update fizzy-api submodule (1 commits) — rawwerks/fizzy-cli0 reactions
- Sep 17, 2026Stabilize reflected model class methods across schema-loading order — lost-in-the/woods0 reactions
- Sep 17, 2026Resolve ERB-backed recurring schedule configuration before extraction — lost-in-the/woods0 reactions
On Hacker News · 3
- Dec 4, 202537signals open-sources Kanban tracking tool Fizzy8 points · 1 comment
- Dec 3, 2025Basecamp/Fizzy4 points · 1 comment
- Dec 2, 2025Fizzy, the Kanban tracking tool for issues and ideas by 37signals4 points · 1 comment
On Bluesky · 3
- Dec 2, 2025🥹 It's like Christmas came early! After Campfire Once and Writebook, there's now Fuzzy, available as open source:… — @xavier.sinapse.blue2 likes and reposts
- Dec 5, 2025今日のGitHubトレンド basecamp/fizzy このリポジトリは、37signalsが開発した、課題やアイデアを追跡するためのカンバン形式のトラッキングツール「Fizzy」のソースコードを提供する。… — @dailygithubtrends.bsky.social1 likes and repost
- Dec 5, 2025🎉 Celebrating! 🎉 (500+ new stars) 📦 basecamp / fizzy ⭐ 2,539 (+829) 🗒 Ruby Kanban as it should be. Not as it has been. — @github-trending.bsky.social0 likes and reposts · 1 reply
On Stack Overflow · 1
- Jul 17, 2026Access Attribute of Rails Test Fixture in Associated FixtureSet0 votes
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 31,439 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 repository2 other files it gives its agents.
- saas/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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.
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.

