Support

There is a person behind this address, and the aim is a reply within two business days. Which door depends on what you need.

Something is broken

Run joxo bug in the paired folder. It prints the connector version, your OS, the agents it found and the last lines of the local logs — with every link and token scrubbed — saves the same text as .joxo/bug-report-<time>.md, and prints a GitHub link with those fields already filled in. Your coding agent can run it for you; the skill document tells it to.

• Report a bug — public, so others with the same problem find the answer. Never paste a sign-in link, an invitation, a token or the contents of .joxo/.
• Email support@joxo.ai with the saved file attached, if you would rather not post publicly.

Before either: joxo setup refreshes a stale install and fixes most of what looks like a bug, and joxo agents shows what each agent still needs.

A question, an idea, a setup worth sharing

• Discussions — how-do-I questions, what works with which agent, ideas.
• Request a feature — say what you are trying to do, not only what you want built.

Your account, your subscription, a charge

Email support@joxo.ai from the address on the account. Nothing about an account or a card belongs in a public issue. Refunds are described on the refunds page.

A security problem

Email support@joxo.ai and do not open a public issue; the security policy says what happens next.

Hackathons

Organisers get a free Pro month for every participant. Write to support@joxo.ai with the event, dates and expected headcount — see hackathons.

Nothing is reported automatically: Joxo runs no crash reporter and reads none of your prompts, transcripts or repository. A report reaches us only when you send it.