advice candidate goes to: this-edition V villager
The secret goes from the drop into the tool, never into the chat
Classify the credential before it touches anything; an agent told something cannot untell it; the lethal trifecta.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Where it comes from
- Handing secrets to agents and browsers the rule (newsroom)
- Seven vaults, one method classify the credential first (newsroom)
- A skill behaviour policy the lethal trifecta (newsroom)
What it answers in the 2018 book
- Pointers unanswered outline, Security
- Strings should be banned unanswered outline, Security
Where it goes
Chapter Controlling your agent: RiskMandate, part Build it without a server (drafting); topic Security for the agent era: least code, supply chain, secrets, learning to hack.
Other ideas proposed for the same chapter: Mandate, reach and the gap: hope versus enforcement, Code is a liability; the future is the smallest code that does the job, Learning to hack is still how you learn how things work: draw the line where the attacker is, Security experience is what lets you ship with known gaps: list them, match them to the reader, say what would change the call.
Node idea:secrets-never-in-the-chat in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.