Start chat conversation
Create a new chat conversation and send its first message.
This is the recommended way to author tests. The QA.tech agent explores the site, grounds tests in what actually exists, and sets up login and config dependencies, so the tests are reliable rather than flaky. Prefer it over create_test_case unless you have already verified the flow exists and gathered the details that tool requires.
Returns 202 immediately with the created conversation. Processing is asynchronous: poll
GET /chat/{chatConversationShortId} until the latest assistant message has
status: 'COMPLETED' to read the reply.
Body
Request body for sending a chat message
The message text to send. Example: 'Generate a login flow test for staging'.
1Optional per-application environment overrides to apply for this conversation.
Target a specific project by its prefixed short ID (proj-slug_shortId or proj_shortId), as returned by the projects API. Required for organization-scoped API keys; project-scoped keys may only pass their own project's short ID.
^proj(-.+_.+|_.+)$Response
The request has been accepted for processing, but processing has not yet completed.
Conversation data with recent messages (newest first).
^chat(-.+_.+|_.+)$Dashboard URL for the conversation.
Where the conversation originated. api for conversations created via this API, ui for the dashboard, github/gitlab for VCS-triggered chats, and system for everything else.
api, ui, github, gitlab, system Recent messages, newest first. Empty on creation; poll GET /chat/{chatConversationShortId} to retrieve.