Integrations
Connect the tools your team already uses through Studio's Ask AI apps catalog, then bring one into a conversation with an @-mention.
Studio's Settings → Integrations has two cards, and they connect different things.
Composio-backed toolkit catalog — the same catalog the cloud app renders. 2 connected.
Ask AI apps
This is the Composio-backed toolkit catalog — GitHub, Jira, Notion, Gmail, and the rest of the platform's app catalog — the same one the cloud app's Settings → Integrations → Ask AI apps tab renders. Each toolkit is either:
- Workspace-scoped — an admin connects it once and the whole org can use it, or
- Personal-scoped — each person connects their own.
Connect opens the vendor's own OAuth sign-in in your system browser and polls the connection until it turns active; your TestRelic session never sees the vendor's credentials. Category chips (bug tracking, code, chat, incidents, docs, productivity, and the long tail) and search narrow a large catalog, ranked by relevance to a tester rather than alphabetically, and the sidebar's Integrations list reflects only connections that are actually active — not a guess.
Chat assistant apps
A second, separate card covers the bespoke Slack and Microsoft Teams bot installs that let Ask AI answer questions inside a chat workspace. These aren't part of the Composio catalog — they're TestRelic's own bot integrations.
Using a connection from chat
Once an app is connected, @-mention it from the composer — @Jira, @GitHub, @Slack,
@Teams — the same way you'd @-mention a test. The mention tells the agent to reach for that
integration's tools specifically, and to say plainly when it isn't actually connected rather
than fake the action.
The @Jira token rides along as plain text in your sentence, plus a small "Studio note" chip
underneath that carries the instruction to the agent — collapsed by default, since a wall of
agent-directed machinery in the middle of a conversation would read worse than the sentence you
actually typed. If the integration isn't connected yet, the agent says so rather than pretending
to have filed the ticket.
Global across engines and modes
A connection is made once, through your TestRelic Cloud session, and works from every chat — whichever engine you've picked (Cloud, Claude Code, Codex, Ollama, Cursor) and on either side of the Local ⇄ Cloud boundary. Nothing about a connection is tied to one engine or one chat.
Next steps
Git integration
Studio's header Git button turns version control into buttons instead of a terminal — track, publish, sync, sign in — plus the zero-repo path that gets untracked tests onto GitHub and into CI.
Memory
Studio's window into repo Memory — Remembered lines as they happen in chat, and a dedicated Memory view over what's serving the agent, fading, or forgotten.