Support
Stuck? Here's the fastest path to unstuck.
CCOS support is built differently on purpose. We've skipped email tickets and live chat — because the real fix usually comes from leaning into the system itself, not tapping out of it.
Why we do it this way
CCOS is a system that corrects itself — if you let it.
Email and live chat sound helpful, but they train you to bail on the system the second something feels off. That's the opposite of how CCOS is designed to work. It's an agent built to solve problems through iteration — describe what's wrong, tell it when it's off, and it will re-plan, re-try, and usually get you there. You just have to stay in the loop with it a little longer than feels comfortable.
The members who get the most out of CCOS all do the same thing: they spend real time with the system first. That's step one of every support path below.
The support ladder
Work the steps in order — most issues don't make it past step two.
- 1
Run
/cc-helpfirst. Always.It's your concierge. Describe what's happening, what you expected, what actually happened. If the first answer misses, tell it why — CCOS iterates. Give it three or four turns before you move on. A surprising amount of the time, you'll never need step two.
Install the Help plugin → - 2
Post in the community.
If
Open the community →/cc-helpcan't crack it, bring it to the community. Search first — someone may have already hit this exact issue. If not, post it. A public post helps the next member who runs into the same wall, and it means our team plus other experienced members can all jump in. - 3
DM me or the team.
Still stuck, or it's something private like billing? Inside the community you can DM me or the team directly. This is the last step, not the first — by the time you get here, you've already done the work that makes the answer easy to give.
How to post so you get answers fast
The more context you bring, the more attention your post gets.
We're not being gatekeepers — it's just math. A post with details gets answered in minutes. A post that says "it's not working" gets a bunch of follow-up questions and sits there for a day. Help us help you.
What you were trying to do
The skill, plugin, or command. The goal you were after — in one sentence.
What actually happened
The error, the weird output, the hang. Exact wording if there was a message.
What you already tried
Including what /cc-help said and why it didn't get you there.
Screenshots — or better, a screen recording
Loom, CleanShot, the built-in macOS recorder. Thirty seconds of you showing the problem is worth a thousand words.
Your setup
Which AI platform (Claude, ChatGPT, Gemini), desktop vs. browser, and anything you changed recently.
Urgency, if it matters
Shipping something today vs. just exploring — that helps us triage.
FAQ
Questions we get about how support works.
Why don't you offer email or live chat support?
Because they make it too easy to skip the part that actually works. When you lean into the system, describe your problem clearly, and let it iterate with you, CCOS solves most issues on its own. Email and chat train people to tap out before the system has had a real chance.
What counts as 'spending time with the system'?
Run /cc-help. Describe what's happening in detail — what you tried, what you expected, what actually happened. If it gives you a wrong answer, tell it why it's wrong and let it correct itself. CCOS is designed to self-correct, but only if you give it something to work with.
Why post in the community instead of DMing you?
Because a question answered in public helps the next ten members who hit the same thing. One-on-one threads disappear. Community threads become a living knowledge base — and the answer may already be waiting for you there before you even post.
What makes a good community post?
Context, details, screenshots, and (if you can) a short screen recording. Tell us what you were trying to do, which skill or plugin, the exact prompt or command, what went wrong, and what you already tried. Posts like that get answered fast.
Can I DM you directly?
Yeah — inside the community you can DM me or the team. But it's the last step, not the first. Start with /cc-help, then the community, then DMs if it's still stuck.
What if it's a billing or account issue?
Post it in the community in the #billing channel or DM the team. Those we handle privately, not in public.
Ready to get unstuck?
Start inside CCOS with /cc-help. If you need backup, head to the community with your details in hand.