Reach a human
who ships.
Every request lands with the team that builds Kaeonix. Start with the channel that matches what you need — the docs answer most configuration questions outright, and anything account-specific goes through the form below.
Documentation
Installation, permissions, project configuration, API and CLI reference. Searchable, and versioned with the model.
Community
GitHub for reproducible cases — an issue with a session id and a diff is the fastest thing anyone can act on.
Direct support
Billing, account access, plan changes, and anything that involves your own code. The form below reaches the same inbox.
Tell us what happened.
One reply from an engineer, not a queue. Include the session id from your terminal if the issue involves the agent — a copy of what you send arrives in your own inbox too.
The session id
Every terminal session prints one. It is what lets an engineer find the exact turn rather than reconstruct it from a description.
Your version
The output of kaeonix --version, plus your OS and shell.
What you expected
The task you gave the agent and the result you wanted. A transcript helps more than a summary.
Security reports
Send vulnerabilities to support@kaeonix.com rather than through this form — it reaches a smaller group, faster.
Solved before you write in
The terminal agent cannot sign in
Run kaeonix login again — a credential is bound to an account, and a plan change re-mints it. Behind a proxy, set HTTPS_PROXY before launching.
Sessions feel slower than usual
Check the status page for a capacity notice first, then your account for the monthly ceiling. Sessions slow before they stop.
The agent refuses to edit a file
The path is outside what you have allowed for the project. Approve it at the prompt, or widen the rule in your settings so the next turn does not ask again.
A device cannot sign in
An account signs in on a fixed number of devices, and a browser session and a terminal sign-in each count as one. Sign an old device out from account settings to free a slot.
Chat and the terminal disagree on usage
Both draw on one balance, and the terminal reports only its own session. The console shows the combined figure.
Billing looks wrong
Plan changes prorate mid-month, so an invoice can carry two lines for what feels like one month. The usage record in the console reconciles it.
Not on Kaeonix yet?
Support is for people already running it. If you are still deciding, the pricing page is the shorter read — and the model page is the honest one.