Support tools end at "we've passed this to the team." Codus is the team: chats from your SaaS land inside the editor, agents answer from your actual product, and when a customer hits a real bug, the quadrant that builds the app verifies it, ships the fix, and tells them right in the chat.
a codus module · answers even while your mac is closed
A visitor reports a bug, an agent reproduces it in the codebase, files it as an executable issue, ships the patch from the owning quadrant, and the visitor hears back in the same chat. No ticket queue in between.
Agents verify before they fix: a flagged chat becomes an issue, the issue is reproduced in the code, and only a confirmed bug gets a patch.
A clean chat bubble in your accent colour that promises nothing it cannot keep: "Usually replies in minutes." The visitor watches a live presence line, real typing dots, and honest statuses, from "an agent is on this conversation" to "you are talking to the team" when a human takes over. When the fix ships, the good news arrives in the same thread and the bubble lights up.
A single script tag, under 30KB, no dependencies. The widget lives in a Shadow DOM so it cannot leak styles into your page or absorb yours, and it takes your product name and accent colour.
Codus distils a product brief from the bound repository, in user language only, and refreshes it every few hours. Each instance shows how fresh its brief is, with one click to regenerate.
A call-centre band of warm agent workers consumes the thread queue, scaling from two to ten. An atomic claim means exactly one worker owns a conversation, and the visitor sees an agent pick it up in seconds.
Every support worker is an ordinary, observable terminal. Open any one from the roster and watch it read the thread, check the product, and write its reply, live.
A wedged worker is freed after four minutes, the turn retries twice, and if it still cannot answer the thread is parked for a human with an honest note. A visitor is never silently stranded.
Every thread has a take-over box in the sidebar, the Support Floor, and the phone cockpit. Type and the conversation is instantly human-led; a mid-turn takeover beats the agent reply.
Each product gets its own instance with a publishable site key, a domain allowlist, and a repo binding that follows the GitHub repo, so it works on any teammate's checkout.
app.trycodus.com/support mirrors the desktop: every conversation live, take-over from the browser, the issues queue, and widget creation with a live preview and copy-paste embed.
A support agent talks to people you have never met, so it is built like it. The workers that face your customers get a deliberately tiny tool surface and hard walls that are enforced in the permission system, not just promised in a prompt.
Your desktop heartbeats while it is open, and the moment it goes quiet a cloud responder takes the queue, answering every minute from the same product brief, never from your code. It files bug-shaped reports as real issues, parks honestly rather than guessing, and hands every thread back the moment your editor returns. Cloud-answered threads are labelled, so you always know who said what.
The Support module is switched on per seat from codus cloud, like the other disciplines. Embed the snippet, bind the repo, and the next bug report can come back to your customer as a deploy.