The chat assistant lets you work with Coroid conversationally rather than through forms. You’ll find it under Chat.
What it excels at
Kicking off work from a half-formed idea. When you know the desired outcome but struggle to phrase it as a specification, a conversation helps you reach that point faster than filling out a blank form — you can answer clarifying questions instead of guessing what to include.
Checking on the current status. Find out what is running, what is blocked, and why a task failed — without needing to navigate through multiple screens to get the answer.
Getting details about the codebase. Discover where specific functionality is handled and what depends on what.
Adjusting work that is already in progress. Add context to a running task or respond to a question it has raised.
It uses the same governed tools
The assistant is not a separate system with its own set of privileges. It operates through the same tool registry as all other components, so any task it initiates follows the standard workflow — specification, plan, verification, review, and pull request.
This is important: using conversation to start a task does not skip the approval stage. A task launched from chat still results in a specification that you must approve.
Conversation is not a specification
One habit to adopt: when the assistant generates a specification from your conversation, treat it as a proper specification.
Conversations are flexible — you can clarify as you go. A specification, however, is applied literally. Ideas that seem clear in conversation may end up vague in writing, and it is the written version that is used to build the product.
See Specifications.
Integrate Chat into your existing tools
If a chat platform is integrated, some of these features are available in the channel your team already uses. See Chat platforms.
For programmatic access via your own assistants and editors, Coroid can function as an MCP server — see Coroid as an MCP server.