Two-way tool connections: Read specs, file bugs, from one connection

Shared by Ines • September 01, 2026

Filing a bug from Thunders used to mean a form: one project, a handful of fields it exposed. Getting Thunders AI to read anything back from your tools wasn't possible at all. Both changed.

Connect a tool: from Connectors, or the connect-tools shortcut inside Thunders AI. Covers Jira Cloud, Confluence Cloud, Azure DevOps, Linear, Notion, ClickUp, and Shortcut. Xray and the Data Center integrations are unchanged.
Set guidance once per tool: "put it in triage, severity high, assign to me," and every bug Thunders AI files into that tool follows it, no retyping it per report.
Read from your tools, not just write to them: ask Thunders AI to pull in a spec or look up an issue, then write a test grounded in what it found.
Bring your own connector: don't see your tool listed? Add its MCP server yourself. It works the same way as a native one.
Your own connection, not the project's: a connection used to be shared with the whole project, so one person's login carried everyone. Now each person connects their own account.

This is what makes Thunders AI a colleague that can act on your tools, not just talk about them.

#Sprint30