Engineering leads
Let agents do real work, and keep control of what reaches production.
“Can agents do real work without us losing control?”
The question is not whether agents can write the code. It is who allowed a change, what the agent did, and whether someone checked it. FEATit answers all three on the work itself.
How it works for you
Decide what needs a person’s sign-off
An agent move that is not allowed alone waits as a hold until a person vouches for it. A work area can ask for a check and a close by two different people, neither of whom did the work.
How rules and sign-off workWatch your agents, and answer them from any device
Open an agent’s terminal live from your Mac or Windows PC, a browser or your phone. When one asks permission, approve or deny it where you are, and the answer is recorded.
How watching and answering agents worksEvery change traces to the session and the code
Each commit is linked to the item and the agent session that made it, automatically and in the background. An agent can never pass for a person in the history.
What every step recordsSigned off by someone who did not do the work
A work area can require the code to be in before work counts as done. It can also require a sign-off by someone who didn’t build it, a person or an agent.
How independent sign-off works
A step your rules refused
The agent that built the fix may not close it. The move is refused on the record, and someone who did not build it closes the issue.
I-0142 Long invoices export as an empty PDF
AIbuild-agent-01Tue 11:48
Moves it to Done
Refused The rule for this step: the one who built it may not close it.
PriyaTue 14:20
Checked it and closed it
A week with FEATit, as engineering lead, on I-0142
Example flow- Tue 08:52
Lena reports that invoices export as an empty PDF, and 2 more customers report the same. The triage agent groups the reports under I-0142 and asks whether only long invoices fail.
- Tue 10:30
It is invoices of more than 50 lines. You mark I-0142 urgent. Your rule for this step: agents may build alone, and closing needs someone who did not build it.
- Tue 11:48
A build agent delivers the fix in 46 min, commit a41c9e2, and tries to move I-0142 to done. Your rule refuses the move, and the refusal is on the record.
- Tue 14:20
Priya, who wrote none of it, exports a long invoice, sees every page, and closes I-0142. Its history names the agent session, the commit and her sign-off.
- Wed 09:00
Release 2.4.1 goes out. Every customer who reported the problem is told, and Lena, who asked to check it herself, confirms it works.
Questions
- Can we stop an AI agent from merging on its own?
- Yes. A move an agent may not make alone waits until a person vouches for it. Closing can be kept for someone who didn’t do the work.
- Does our code leave our machines?
- No. Your code stays on your machines. Only a short description of each change reaches FEATit, never the files or the changes themselves.
- Can we mix agents from different vendors?
- Yes. Agents from different vendors sit on one board under the same rules, and nothing in FEATit requires a particular AI vendor.
- How do we see what an agent did?
- Every session is recorded with the name the agent gives, its code is linked to that session, and its token use is recorded as it reports it.
Not there yet
- Coming soon: one organisation-wide policy for who may watch, type into and start agent sessions.