Every agent · Coding agents · open source
Aider
A terminal pair-programmer that commits changes to git; the human reviews diffs. Where the code goes depends entirely on the model key the developer supplied, which is usually a personal one.
executes with approval
acts on
yes
human in the loop by default
configurable
data leaves the tenant by default
The git repository it runs in and whichever model API key it is given
reaches by default
What that means for the register
It acts, but a person approves each action by default; the risk moves to whoever relaxes that setting. Whether data leaves your tenant depends on how it is deployed. Pasted with only its name it lands as control until an owner is named.
This week
Find out which model API key each developer has configured; that is where your code goes.
Do this for every tool your teams use
Paste the list and get this classification for every entry at once, with the owner column, the findings per department, and the controls the register is evidence for. Ten entries free, no account.
Build my agent register