One Install Command, Every Coding Agent Your Team Uses.
Your team doesn't all use the same editor, and it shouldn't have to. testsprite agent install <name> wires up the same TestSprite setup across Claude Code, Cursor, Cline, Windsurf, Antigravity, Codex, Copilot, and Kiro — so nobody's stuck configuring testing from scratch for their agent of choice.
One CLI, Eight Coding Agents
One Command, Any Agent
testsprite agent install <name> handles the setup for whichever agent you name — claude, cursor, cline, windsurf, antigravity, codex, copilot, or kiro — so you never have to look up per-editor instructions.
Same Commands After Setup
Once installed, the same test create, test run, and test rerun commands work no matter which agent is calling them — the underlying testing setup doesn't change per editor.
Check What's Installed
agent list shows which integrations are available and which are already set up, so you can see your team's coverage at a glance.
Confirm It's Healthy
agent status reports whether each installed integration is actually working, so a broken setup doesn't sit unnoticed until someone hits it mid-task.
$ testsprite agent install cursor Detecting Cursor configuration... Installed TestSprite integration for cursor $ testsprite agent install claude Detecting Claude Code configuration... Installed TestSprite integration for claude $ testsprite agent status claude ok cursor ok windsurf not installed
Stop Reinventing Test Setup for Every Editor
Mixed tooling shouldn't mean mixed testing setups. Whether someone on your team works in Claude Code, Cursor, Windsurf, or any of the other supported agents, agent install gets them to the same place.
Built for Teams Running Mixed Tooling
Eight Agents, One Path
Claude Code, Cursor, Cline, Windsurf, Antigravity, Codex, Copilot, and Kiro are all supported through the same agent install <name> command — pick the name, not a separate guide.
CI-Friendly Setup Too
testsprite setup --from-env --yes --agent <name> reads your TESTSPRITE_API_KEY and sets up non-interactively, so onboarding a new agent integration isn't a manual step blocking a pipeline.
Free Community Version
Offers a free community version, making us accessible to everyone.
Starter Tests, If You Want Them
Pair setup with the testsprite-onboard skill to read your codebase and author a starter test suite once your agent integration is installed.
Trusted By Businesses Worldwide
"TestSprite offers rich test case generation, clear structure, and easy-to-read code. It also supports simple online debugging with the ability to quickly expand by generating new test cases."
"TestSprite's automation helps us reduce tons of manual work. The developers can easily catch and resolve bugs earlier in the development process."
FAQ
Which coding agents does testsprite agent install support?
Eight, by name: claude, cursor, cline, windsurf, antigravity, codex, copilot, and kiro. Run testsprite agent install <name> with whichever one your editor uses.
Do I need a different testing setup for each agent my team uses?
No — that's the point. agent install sets up the same TestSprite integration regardless of which of the eight supported agents you name, so a team with mixed tooling isn't maintaining separate configs.
How do I check which agents are already set up?
Run agent list to see available and installed integrations, or agent status to check whether each installed one is actually working.
Is there a non-interactive way to install for CI or scripted setup?
Yes — testsprite setup --from-env --yes --agent <name> reads the TESTSPRITE_API_KEY environment variable and completes setup without prompts.
Once installed, do the commands differ between agents?
No — after agent install, the same CLI commands (test create, test run, test rerun, and the rest) work the same way no matter which agent triggered them.