Where builders gather.
Builders of every title: sales engineers shipping before the next meeting, agencies running a portfolio on one license, ops people retiring the load-bearing spreadsheet, developers with opinions about the control surface. This is where they compare notes and show what they made.
Early days, said plainly: the channels below are being set up, and this page will always show their real state.
GitHub Discussions and Discord. One will be primary.
We are choosing between GitHub Discussions and Discord as the primary channel, and may keep both. We will not quote member counts for either; both are places where a person answers.
GitHub Discussions — not open yet
When it opens: questions with code in them, blueprint prompts worth sharing, and issues that turn out to be feature requests. Threads stay searchable, which is why it is on the shortlist.
Discord — invite coming
Faster back-and-forth while you build, office-hours voice, and a channel per topic. Being evaluated as the primary chat channel; the invite lands here when the server opens.
Until a channel opens, support is the front door and a person reads it.
Show up, show off, keep up.
Office hours, once the cadence is set.
A standing call, when it starts: builders bring what they are building and we read the diff together — preview-solution-edit on screen, questions answered live. Cadence and channel appear here first.
Built something? Submit it.
Working apps built on the platform, told the way you would tell a colleague: the problem, the prompt, the primitives, the time it took. Selected builds are written up with your permission — the link lands with press@codemonster.ai, the inbox that writes them up. Bring your builds. The monster likes to look.
Submit to the showcaseWhat the monster ate this week.
Dated entries for the platform, the MCP server, the desktop app, custom frontends, docs and this site. Titles have some fun; bodies say exactly what shipped.
Read the changelogThe reasoning, not only the release notes.
The blog carries the arguments behind the product: what a credit actually buys, why the agent never sees your raw schema, how a demo becomes promoted software. Field notes from builders are welcome — write to us and we will help you shape one.
None scheduled yet.
We would rather run one good build day than announce three we cannot host. When a first event is confirmed — online or in a room — the date, format and sign-up appear here and in the changelog. Nothing is dated until it is real.
Want to co-host one with your team, agency or meetup? Tell partners.
Short, real, enforced.
- Be kind. Assume the other builder is competent and busy. Critique the app, the prompt or the idea — never the person.
- No harassment. None. Personal attacks, slurs, unwanted contact or pile-ons get you removed, first offense.
- No spam. No unsolicited pitches, no link-dropping, no scraping members. Sharing what you built is welcome; selling into the room is not.
- Security issues go to the disclosure process, not the forum. If you find a vulnerability, follow the disclosure page and write to security@codemonster.ai. Do not post it publicly.
- Do not punch down at other tools' users. They are builders too. Compare the model, not the people.
Moderation decisions are made by people, and you can appeal one by writing to support@codemonster.ai.
Bring us something you want built.
CodeMonster is invite only while we work directly with early adopters. Request an invite and we will meet, scope what you want to build, and get you productive. You bring the AI subscription you already pay for.