What the TestSprite CLI can do today, what’s on the roadmap, and what stays in the Web Portal or MCP.
The TestSprite CLI is production-ready for the workflows listed below, with a stable --output json contract that agents and CI can rely on today. Changes are strictly additive: new fields may appear, but existing fields, exit codes, and command shapes will not change.
Stability promise: the JSON output contract and exit codes are stable. New commands or flags may be added, but nothing currently documented will be removed or renamed without a major version bump.
Frontend: create from an agent-supplied plan file (--plan-from) with full planSteps[]; replace plan steps (test plan put)
Backend: create from a test code file (--code-file, typically Python/pytest); declare captured variables (--produces/--needs) and teardown tests (--category teardown) for wave-ordered dependency runs; replace code with ETag-guarded optimistic concurrency (test code put)
The CLI gets better when you share what’s rough. Join the community to tell us what broke, what was confusing, or what you wished the CLI could do — your feedback directly shapes the roadmap.