Blog · Building in public

What our first outside tester taught us

By Shamaz Khan · 18 Nov 2026 · 4 min read

The most useful thing you can do with a developer tool is hand it to someone who owes you nothing and watch what happens. That's what our first outside tester did with Stet.

What worked

Their verdict, in their words:

“Locking the scope and running the tests every time makes sure nothing regresses. Flagging every time an out-of-scope file is changed is powerful.”

That's the core of the product working as intended: agree what the task may change, prove the important behaviours still work, and make anything outside the lines impossible to miss.

What they asked for

1. Add to a scope without resetting it

Mid-task, they realised one more file genuinely belonged in the change. Resetting the scope meant losing its starting point. The fix is a command that widens an open scope and records that it was widened, so the PR shows it.

2. Compare against the up-to-date remote base

Their local main was behind the remote, so comparisons included other people's work. Stet should fetch the base branch, compare against the up-to-date copy and warn when your branch is behind.

3. One PR format, enforced

Stet already keeps agents inside the task's files. They wanted the same for pull request descriptions: the agent writes only the "what and why", and everything else comes from git and the checks, with a lint step in CI that rejects anything else.

What shipped

All three shipped in Stet 0.7.0: stet scope add, the up-to-date remote base check, and stet pr --what with stet pr lint. Version 0.7.1 added stet ci, which writes the GitHub workflow that enforces the PR format on every pull request. See the changelog. If you try Stet and something gets in your way, tell us. This is how it gets better.

Put guardrails on your AI coding agent

Stet is a free, open-source CLI and MCP server for Claude Code, Cursor, Codex and Copilot. It runs locally: no account, your code never leaves your machine.

npx stet-cli init · Install · Setup guide · GitHub

Related