The cadence is in the rooms.
Discord and Telegram are the daily channels — questions, in-flight changes, testers reporting back from real projects, and the regular "wait, does anyone else hit this" threads that turn into the next release. If you want to lurk, lurk. If you want to ask, ask.
Discord — discord.gg/nyFRDqQR89
Telegram — t.me/+isN9TIm_4mlmZmEx
X — @TheTacoCatBot
All three are public. Discord and Telegram mirror most of the active discussion. X is where shipping notes and the occasional ramble go.
File issues — github.com/jmagly/aiwg/issues. Bug reports, feature requests, tester reports, and imported reports each have a template. The kernel skills aiwg-issue and aiwg-pr walk an agent through filing one correctly.
Test on your stack — AIWG runs against Claude, Codex, Cursor, Copilot, Factory AI, Hermes, OpenCode, OpenClaw, tinyhumans.ai, Warp, Windsurf, and increasingly local models. If something breaks on your provider or your hardware, that's the kind of report that lands fixes fastest.
Contribute upstream — the project-local path means you can build something inside .aiwg/, prove it on a real project, and aiwg promote it to upstream when it's ready. No fork required for most contributions.
AIWG is the cognitive layer of a wider open-source stack. The runtime and the surrounding infrastructure are backed by partners and sponsors.
> /partners — Integro Labs, Roko Network, Selfient.
