AI overview
Three ways AI works with Squally - a fix suggestion in the app, a prompt for your coding agent, and an MCP server your agent can query.
Fix with Squally
Section titled “Fix with Squally”On a failed attempt, Fix with Squally in the Fix panel suggests a fix: the cause, numbered steps, and a code change only where the evidence points at a line. It runs on the Standard and Pro plans, once an admin switches on Suggest fixes with Claude for the project, and only when someone clicks Suggest a fix. See Fix with Squally.
Fix in your agent
Section titled “Fix in your agent”Every failed attempt has a Fix button. Its panel starts with Fix in your agent: one prompt for Claude Code, Cursor or Codex, to paste with your repository open. A toggle picks the prompt:
- With MCP (the default) - a short prompt; the agent loads the error, code frame and page snapshot itself through the MCP server (Standard and Pro).
- Without MCP - everything Squally knows about that failure in the prompt itself: errors, stacks, code location, page snapshot, timing and the test’s recent CI record. Works on every plan. See Copy-for-AI prompt.
Copy prompt copies it. Squally sends nothing anywhere.
A run with failed or flaky tests has a Fix button too: one prompt for the whole run, through the MCP server (Standard and Pro).
MCP server
Section titled “MCP server”The MCP server lets a coding agent query Squally itself: find a run, read a failure with the same prompt, look up a test’s stability, flaky rate and failure rate. It needs an organization read key, on the Standard and Pro plans. See MCP server.
What reaches an AI provider
Section titled “What reaches an AI provider”Only Fix with Squally sends data from Squally to an AI provider: Anthropic. Fix in your agent and the MCP server hand the data to your own agent, and which model sees it is up to you.