Correct an agent once. Every teammate's agent knows it next session.
Ingrained is a private knowledge base for a team's coding agents. It holds what cannot be found by reading the code: how your team does things. Agents write it, read it and correct it as they work.
agent ran npm install left-pad agent ran git push Ana no, after npm install always run make notices, or the licence check fails in CI agent ran make notices saved After npm install, run make notices; otherwise the licence check fails in CI.
agent ran npm install zod ingrained After npm install, run make notices; otherwise the licence check fails in CI. from a teammate's correction, unverifiedagent ran make notices agent ran git push
An illustration, not a screenshot. Nobody told Ben's agent, and Ben never saw the mistake. Because the step then worked in a session that had been shown the entry, the entry gains trust.
How an entry gets made, used and retired
- Someone corrects an agent, or states a rule. The agent records it as one short entry, tied to the command or file it is about. If the agent does not, the client extracts it when the session ends, on the developer's own machine.
- It reaches the team's other machines. Each machine keeps a local copy of the entries for its repositories. Nothing is looked up over the network while an agent is working.
- An agent is told at the moment it matters. When a teammate's agent runs the command or touches the file, the entry arrives with that step's result, in time for the next one.
- Trust is earned, and lost. An entry is promoted only when it was shown and the step it prescribes then succeeded, or a person confirmed it. It is withheld when the code it is about changes, and retired when it stops being true.
- People stay in charge. A review page lists what the team's agents are told. Anyone on the team can confirm, edit or retire an entry. A dangerous command reaches nobody until a second person has checked it.
What leaves a developer's machine, and what never does
- Sent to the service
- The short entries themselves
- Signals about entries: shown, worked, flagged
- Counts per session
- Fingerprints of the lines an entry is about
- The addresses of the repositories it is installed in
- The text of a search an agent runs
- Never sent
- Source code
- Session transcripts
- Command output
- What people typed to their agents
Sign-in asks Google or GitHub only who you are. Ingrained never asks either for access to repositories, code, mail or files. Each team's entries are kept apart from every other team's by the database itself. The privacy page has the details.
The pilot
Ingrained is in a pilot with a small number of teams of 5 to 30 engineers who use coding agents every day. Starting a team needs an invitation code.
If that is your team, write to us and say which agent tools you use. If your team already has an invitation, sign in.