Chat
Have a back-and-forth conversation with a workspace agent. Use chat for quick questions, exploration, and advice that does not need a tracked ticket.
Chat
Chat lets you talk to an agent directly, like a DM. The conversation itself has no ticket status, but you can inspect the agent tasks and run records triggered within it. Use chat for quick back-and-forth work that does not need its own tracked ticket.
If you find yourself chatting about the same thing repeatedly, that is a signal to file a ticket and assign it to the agent instead. Chats are for transient conversations; tickets are for accountable work.
Start a Chat
- Open Chat in the sidebar
- Click New chat
- Pick the agent you want to talk to from the picker
- Type your first message and hit Enter
The conversation appears in your chat list and persists until you delete it. Each chat is private to you — no other workspace member can see it, even if they share the agent.
Send a Message
Type into the composer and press Enter (Shift+Enter for a newline). Markdown is supported. The agent streams its response back token by token. While the agent is running, you can send a cancel request to stop the current task, then send a new message.
The full conversation history is sent to the agent on every turn, so it has the context of the entire chat. Long-running chats stay coherent.
Group Chat and @mentions
When creating a chat, you can add multiple agents as participants to form a group session. In group mode, only agents explicitly @mentioned in a message are triggered — agents not mentioned are not notified.
To mention an agent, type @ in the composer and select the agent from the dropdown. Group and channel chats route agent tasks from this structured mention, not from plain-text name matching.
If a mentioned agent is not yet in the session's participant list, it is automatically added when triggered. In P2P sessions (a single agent participant), messages always route to that agent without requiring an @mention.
Attachments
Messages can include uploaded file attachments. Upload files first via the attachment upload endpoint, then include the attachment IDs with the message. Attachments are passed to the agent as part of the task context.
Session Management
- Rename: click the session title to edit its name
- Delete: deleting a session cancels all in-progress tasks in that session and removes all message history
- View tasks: click the task-list icon in the conversation header to open the current session's related tickets, standalone agent tasks, and run records
- View a message's run: when a message triggered one or more agent tasks, use the run-record icons beside its reaction controls to inspect each task directly
Sessions connected to an external channel show the source platform icon in the conversation list. The icon identifies Lark/Feishu, WeCom, or another supported channel independently from whether the session is a direct or group chat.
Topic Lifecycle
Topic creators and workspace Owners/Admins can rename, archive, restore, or permanently delete a topic. Ordinary members can leave a topic; leaving removes only their own membership and does not affect other participants.
Archived topics remain visible in the bottom Archived section with their history intact, but are read-only until restored. Permanent deletion removes the topic and its messages, participants, attachments, run data, and related records; active agent tasks are cancelled as part of the deletion.
Use Cases
| Scenario | Why chat fits |
|---|---|
| Quick question | "How do I tune MySQL's innodb_buffer_pool_size?" — Faster than filing a ticket and waiting for a run to complete. |
| Configuration advice | "What is the difference between SCAN IP and VIP in Oracle RAC?" — Confirm the concept before deciding whether to file a ticket. |
| Troubleshooting | "How do I read this slow query's execution plan?" — Iterative back-and-forth that would feel heavy as a ticket. |
| Knowledge check | "What is the relationship between WAL archiving and streaming replication in PostgreSQL?" — Get feedback without creating a tracked artifact. |
For anything that needs an outcome, a record, or coordination across humans, file a ticket and assign it to the agent. Chats do not appear in the inbox and do not have a status.
Context Note
A chat is not a continuation of any specific ticket. The agent does not know which tickets you are looking at or which projects you own unless you tell it. If you want it to consider a specific ticket, paste the ticket ID or its description into the conversation.
The agent's instructions (its persona) still apply in chat. A Release Notes Writer agent will still write in customer-facing tone when you chat with it; a SQL Analyst will still try to write queries. Pick the right agent for the conversation.
Requirements
For a chat to work:
- The agent must be online — its status is Idle or Working, not Offline
- At least one daemon must be connected and hosting the agent's provider CLI
If the agent is offline, the chat composer is disabled with a tooltip explaining what to fix.