Resources
Community
Stoneforge is open source and community-driven. Here’s where to find us:
Discord
The fastest way to get help, share what you’re building, and chat with other users and contributors. Join the conversation in #general, #help, #showcase, and #feature-requests.
GitHub
Star the repo, file issues, submit pull requests, and follow development. All code, documentation, and project planning happens here.
X (Twitter)
Follow for release announcements, demos, tips, and behind-the-scenes updates on development.
Getting help
Before asking, check these resources — your answer may already be there:
- This documentation — the Guides section covers most common workflows
sf doctor— run this CLI command to diagnose common setup issues- GitHub Issues — search existing issues for your error message or symptom
If you’re still stuck:
| Channel | Best for | Response time |
|---|---|---|
| Discord #help | Quick questions, debugging help, setup issues | Minutes to hours |
| GitHub Issues | Bug reports, feature requests, reproducible problems | Days |
| GitHub Discussions | Architecture questions, design proposals, general discussion | Days |
Reporting bugs
Good bug reports make fixes happen fast. Include:
## Environment- Stoneforge version: (sf --version)- Node.js version: (node --version)- OS: (macOS / Linux / WSL)- Provider: (Claude Code / OpenCode / Codex)
## What happenedA clear description of the bug.
## Steps to reproduce1. Run `sf serve`2. Register a worker with `sf agent register ...`3. ...
## Expected behaviorWhat you expected to happen.
## Actual behaviorWhat actually happened. Include full error output.Feature requests
We welcome feature requests! The best way to propose a feature:
- Check existing issues to see if it’s already been requested
- Open a new issue with the
enhancementlabel - Describe the problem you’re trying to solve, not just the solution you want — this helps us find the best approach
Feedback
Stoneforge is built to be shaped by its users. If something could work better, if a workflow feels clunky, if you have an idea for how the tool should evolve — we want to hear it. No feedback is too small.
- Something not working for your workflow? Tell us in Discord #feature-requests or open an issue
- Hit a rough edge? Even if it’s not a bug, share it — these reports drive the most impactful improvements
- Have an opinion on how something should work? Start a GitHub Discussion — design conversations happen in the open
The goal is simple: Stoneforge should be the best-performing tool for orchestrating AI coding agents. The community decides what “best” means. Every piece of feedback — a one-line Discord message, a detailed issue, a PR — helps steer the project in the right direction.
Project status
Stoneforge is actively maintained and under rapid development. The project is usable today for orchestrating multi-agent workflows with Claude Code, OpenCode, and OpenAI Codex.
Current focus areas:
- Stability — hardening rate limit handling, recovery flows, and edge cases in merge automation
- Developer experience — improving the CLI, dashboard UX, and documentation
- Provider support — expanding and improving support for all three agent providers
See the Changelog for a detailed history of what’s shipped.
License
Stoneforge is licensed under Apache 2.0. You can use it freely in personal and commercial projects. See the full LICENSE on GitHub.
Acknowledgments
Stoneforge is built by Adam King, creator of TensorTrade. Built with TypeScript, React 19, SQLite, Hono, and a lot of help from AI coding agents.