GitHub Discussions
Ask questions, share ideas
Product questions, design conversations, half-formed ideas — anything that isn't a concrete bug. If you're not sure where to start, start here.
Community
Community
Watchfire is open source and built in the open. Here’s where to ask questions, share what you’ve built, and help shape what ships next.
For the license, contributors wall, and how to sponsor the project, see /open-source. For the curated reading list on AI coding agents, see /resources.
Where to ask & talk.
The whole conversation happens on GitHub and the two social feeds — no Discord, no Slack, no waiting room.
GitHub Issues
Report a bug or concrete feature
File an issue when you have a repro for a bug or a well-scoped feature request. Open-ended ideas are a better fit for Discussions.
Bluesky
Follow on Bluesky
Release notes, screenshots, and the occasional rant about agent ergonomics. Most posts also cross-post to X.
X / Twitter
Follow on X
Same shape as Bluesky, different timeline. Pick whichever one you're already on.
Stuck on something?
Two steps, in order. The docs answer most questions faster than a thread will.
Read the docs first.
These four pages catch most things people get stuck on:
- Documentation home — Concepts, components, and the full commands reference.
- Troubleshooting — Common failure modes — agent stuck, worktree dirty, ports in use, sandbox denials.
- Tips — Patterns that move you from “it runs” to “it ships” — task scoping, acceptance criteria, recovering bad runs.
- Recipes — End-to-end walkthroughs: refactor a module, add tests, run a migration, ship a docs sprint.
Still stuck? Ask in Discussions.
A good help post saves everyone’s afternoon:
- What you ran and what you expected to happen.
- OS and Watchfire version (
watchfire --version). - A minimal repro — the smaller, the faster the answer.
- What you already tried. Be kind, be concise.
Help build it.
Three honest ways to push the project forward — not just “PRs welcome.” All three count.
Code
Code contributions
Small fixes go straight to a PR. Larger changes are best shaped in an issue or discussion first so the design conversation doesn't happen in a review.
Documentation
Documentation
Docs improvements move the project forward as much as code. Every docs page has an Edit on GitHub link in the right sidebar — typos, sharper sentences, missing context all welcome.
Word of mouth
Talk about it
Linking to the project, tagging #watchfire on social, writing a blog post about your setup — for an OSS project this early, this matters as much as a PR. It's how the next contributor finds the repo.
Stay in the loop.
Subscribe by email for release notes and deep-dive posts. Star the repo to see new releases land in your GitHub feed — it’s also how other developers find the project.
Get updates
Releases, deep dives, and the occasional behind-the-scenes note. No spam.
Code of conduct
This community follows the Contributor Covenant. Treat each other with respect, assume good faith, and report conduct issues privately to info@watchfire.io. The full text lives in CODE_OF_CONDUCT.md in the repo.
See you on GitHub.
The fastest way to get involved is to open a discussion, file an issue, or send a small PR. We respond to every one.