
What it can do
Three prompts you can paste right now:
The vocabulary
The chat uses the same terms as the rest of the portal:- Sources — everything you feed a project: documents, code, designs, tickets, crawled pages.
- Use cases — the feature map (“Features” and the “Use cases” under each) that coverage is organized around.
- Test coverage — the live set of test cases and their current status.
- Test run — one execution. A run is frozen history; a test case’s status reflects its latest run.
Project focus
A conversation is focused on one project at a time. Open the chat from a project page and that project is the focus automatically; ask it to switch (“let’s work on the Amazon project”) and it changes — a divider row like “Switched focus to Amazon.” marks every change, so you can always see which project a message applied to. The chat re-reads the focused project at every turn, so it stays current even when the change happened outside the conversation: upload a source or delete cases on the platform directly, and the next answer already reflects it. The project selector in the composer shows the current focus at all times — click it to search and switch:
Conversations
- Every conversation belongs to the workspace it was started in.
- Titles are generated from your first message; rename or delete a conversation from the conversation list.
- You can attach images and files to a message. An attachment is read on the turn you send it — quote the relevant part in a later message if you need to come back to it.
Where to Go Next
Approving Actions
How proposal cards work — approve, reject, or just answer by typing
Your First Test
The concept map the chat’s workflow follows
Key Terms
Sources, use cases, coverage, runs — the shared vocabulary