Talk to us
The short answer
Everything reaches hello@codemesh.com. There is one mailbox rather than five, and a person reads it. What decides how fast you get a real answer is what you put in the first message, so the sections below say exactly that.
Something is broken
Include your organisation name, the repository that misbehaved, roughly when it happened, and what the panel was showing. The daemon log is more useful than a description of it.
A repository will not sync
Tell us the repository, whether the panel shows it as syncing or failed, and whether it worked before. Include the absolute path if the repository is local only.
My agent cannot connect
Which agent and which version, whether you connected over MCP or OAuth, and what the agent printed when it failed.
Plan or billing
Your organisation name and the charge or invoice in question. If it is about an upgrade or a seat, say which date you expected to be billed on.
Enterprise, dedicated or on-premises
Number of developers, and whether the concern is the shared instance or the network boundary. That is enough for a real quote instead of a discovery call.
A data request
Access, correction, deletion, export, or an objection. Also the right address if your name appears in a customer's graph through their git history and you have never used CodeMesh.
Before you write about a bug
The editor panel has a support view that submits a ticket with the context already attached, which saves the round trip where we ask which version you are on. If you can still open the panel, that is the faster path. If you cannot, mail is the right call.