Community
Ask the people
who build it.
Most questions about agent teams do not have a documentation page yet, because nobody has written one. So we run the channels where those questions get answered — by us, and increasingly by each other.
Where to find us
Six places, each with a job
Pick the one that matches what you need. Posting in the wrong place is fine — someone will move you, politely.
Discord
The busy room. Setup questions, role contract tuning, deployment target patterns, and the channel where people post a plan and ask whether it looks sane.
GitHub discussions
The slow, searchable room. Longer write-ups, reproducible problems, and answers you can link to six months later without them scrolling away.
Monthly office hours
One hour, live, with whoever is building the thing you want to talk about. Bring a run that went wrong. No slides, and no demo unless somebody asks.
Feature requests
Describe the workflow you are stuck in and we will tell you which roadmap bucket it landed in — including when the answer is no.
The changelog
Everything that shipped, with the date it landed and what it changes about how you work. Written for people who already use the product.
Community showcase
Role contracts, health check scripts and deployment target setups that other teams have shared. Copy them, break them, send back the improvement.
Getting an answer
How to get help fastest
The difference between an answer in four minutes and an answer tomorrow is almost always what is in the first message.
Search first, briefly
Two minutes in the docs and the help centre. If the answer is there, you get it now instead of after lunch.
Bring the run
Paste the task report — summary, files modified, blockers — or the deploy and health check output. The report is designed to be pasted.
Say what you expected
"The reviewer rejected it and I thought it would pass" tells us where to look. "It's broken" starts a game of twenty questions.
Escalate real breakage
Anything touching your production systems goes to support, not Discord. That route is tracked and has a response time.
Guidelines
How we behave in here
Short, specific, and enforced. If a rule below reads like it was written after something happened, that is because it was.
- Redact before you paste. Reports and deploy logs pick up hostnames, tokens and customer data. Nobody in a public channel needs your production connection string.
- Ask the whole question in one message. "Anyone around?" costs everyone an hour. Ask, then wait — someone will be around.
- Answer the question that was asked. If you want to argue that they should be doing something else entirely, answer first, then say so.
- Nobody's setup is stupid. Half the people here inherited a codebase from someone who left. "Why would you do it that way" is never the useful sentence.
- Say when you are guessing. A confident wrong answer about a deployment target can cost somebody their evening. "I think, but check it" is a complete answer.
- Post the fix. If you solve it yourself, reply to your own thread. The next person searching is the entire reason discussions exist.
- No recruiting, no pitching, no scraping. Not in the channels, and not in unsolicited direct messages to people who posted in them.
- Disagree with us in public. Criticism of the product belongs in the open channel, not a private message. We would rather answer it where everyone can see the answer.
Worth reading first
Things people link to constantly
The six answers that account for most of what gets asked in Discord.
Documentation
Connecting a repository, building a team, writing a deployment target, and the first request end to end.
Read the docsHelp centre
Billing, plans, agent run allowances, and the account questions that are not really about the product.
Browse articlesWriting role contracts
How to tighten a specialist, add a house rule, and stop a role doing the thing it keeps doing.
See the rolesSecurity and access
What we can reach, what we cannot, where your code lives, and what an investigation is allowed to do.
Read the detailThe changelog
What shipped, when, and what it means for the way you already work. Updated as things land.
Catch upBlog
Longer pieces on gates, autonomy and what breaks when you let a team of agents near production.
Read postsMonthly update
One email a month. That is the whole offer.
What shipped, what moved on the roadmap, and one thing we got wrong. No drip sequence, no sales follow-up, and no re-adding you if you leave.
Questions
Before you post
Do I need a paid plan to join?
No. Discord, GitHub discussions and office hours are open to everyone, including people on the Free plan and people who have not signed up at all.
What a paid plan buys is a support response time, which is a different thing. The community is not a cheaper support queue and we do not treat it as one.
Should I report a bug here or to support?
Anything affecting your production systems goes to support. That route is tracked, it has a response time attached to your plan, and it does not depend on who happens to be reading Discord.
Community channels are best for questions, patterns, and the ones where you are not yet sure whether it is a bug or you.
What actually happens at office hours?
An hour, monthly, with the people building the product. You bring a plan that went sideways, a role contract you are tuning, or a roadmap question.
There is no presentation and no demo unless somebody asks for one. If nobody has a question we finish early, which has happened exactly once.
Can I share my role contracts and deploy scripts?
Please do. Role contracts are Markdown, deployment target commands are shell, and both are more useful shared than hoarded.
Redact hostnames and anything that looks like a credential first. If you want it in the showcase, post it and say so.
Do you answer at weekends?
Sometimes, and you should not plan around it. The community runs on people choosing to be there.
If something is broken at 2am, the product is designed so you do not need us: the health check fails, your rollback command runs, and an investigation opens on its own.
Do you moderate?
Yes, and quietly. Recruiting, pitching and unsolicited direct messages get a warning and then a removal.
Criticism of Capybari is not moderated at all — we would rather answer it in the open channel where everyone can see the answer.
Prefer to talk privately? Write to us — a person replies.
Come and ask the awkward question
The one about letting agents near your production servers. Somebody in there has already asked it, and the answer is better than a marketing page.
Free on every plan · Office hours monthly · Moderated, quietly