The chat assistant lets you work with Coroid conversationally rather than through forms. Find it under Chat.
What it is good at
Starting work from a half-formed idea. When you know the outcome but not how to phrase it as a specification, a conversation gets there faster than a blank field — you can be asked clarifying questions instead of guessing what to include.
Asking about state. What is running, what is blocked, why did this fail. The answer arrives without navigating to find it.
Asking about the codebase. Where something is handled, what depends on what.
Steering work in flight. Adding context to a running task, or answering a question it has raised.
It uses the same governed tools
The assistant is not a separate mechanism with its own privileges. It works through the same tool registry as everything else, so anything it starts goes through the normal path — specification, plan, verification, review, pull request.
This matters: asking conversationally does not bypass approvals. A task started from chat still produces a specification you approve.
Assistant and Prepare Work
The chat has two modes. Ask Coroid opens it in Assistant mode, where the assistant creates tasks and plans directly, without Qualification.
A Prepare Work chat is the guided SDLC workflow. It drafts an intent and a specification with you, and the approved specification goes through Qualification before planning starts. Start one from the chat's add menu, or turn on the SDLC workflow on the New Work form. See The SDLC workflow.
Work on a conversation together
A new conversation is private to you. To bring teammates in, open it and choose Share at the top. Search for people by name or email and choose Add. Anyone you add can read the whole conversation, including what was said before they joined, its attachments and its work documents.
I updated the intent: email alerts only, with at most 10 saved searches per account. The specification draft is ready for review under Work documents.
A shared Prepare Work conversation: teammates discuss in the thread, Coroid answers when asked, and everyone reviews the same documents. Illustrative data.
You can add active members of your organization only. To work with someone new, invite them under Organization settings → Members first. The Free plan has a single member, so sharing needs Professional or Enterprise.
In a shared conversation, messages go to your team. Coroid answers only when you ask it: mention @Coroid in your message or turn on Ask Coroid before you send. Type @ and a name to mention a teammate, who is then notified.
In a Prepare Work chat, participants review the intent, specification and implementation plan in the conversation and can approve them, unless the work needs an assigned reviewer role. The Shared and Review filters above the thread list show the conversations shared with you and those waiting for your review.
- Copy link in the Share dialog copies a link that opens only for participants.
- The owner can make another participant the owner, remove participants, and archive or reopen the conversation. An archived conversation stays saved.
- A participant who is not the owner can leave.
- An organization administrator can Recover ownership of a shared conversation, for example when its owner has left.
Releases from chat
The assistant can prepare and follow releases through the same Release API as the Releases screens. Ask it things like:
- "Release the latest commit of the shop project." It pins that commit, and the project's version source decides the version and build number.
- "What would ship to production if we released now?"
- "Run the checks for release 1.4.0 on staging."
- "Is 1.4.0 running in production?" It answers with the last deployment, the version your pipeline reported and whether the version check verified it.
- "Draft the release notes."
Approving a release and asking your pipeline to deploy always wait for you to confirm in the chat. Coroid never deploys by itself: the release counts as deployed only when your pipeline reports success. See Releases.
Conversation is not specification
The one habit worth forming: when the assistant produces a specification from your conversation, read it as a specification.
A conversation is forgiving — you can clarify as you go. A specification is executed literally. Things that felt settled in conversation sometimes land vaguely in the written version, and it is the written version that gets built.
See Specifications.
Chat in your own tools
The assistant does not answer in Slack, Discord, Telegram or SMS. A Slack or Telegram message can still become a request through an event automation. See Chat platforms.
Your own assistants, such as Hermes, Codex or Claude Code, can use Coroid's tools through its MCP server. See Coroid as an MCP server.