In depth
Anything pulled from a CRM, email API, support log, or production database is going to contain PII. Sending that PII into LLM context is usually undesirable and sometimes illegal. A tool_end hook with regex replacements (emails, phones, IDs) catches the structured leaks, a dedicated PII module handles semantic ones (names, addresses).
Related concepts
HooksDeclarative event handlers that fire at specific points in an agent's lifecycle (turn_start, tool_end, etc).Audit logA structured record of every agent turn, including tool calls, costs, and outputs, written to a sink.Credential vaultAn encrypted store for API keys, tokens, and connection strings, referenced from YAML by name.
Read the deep dive
Hooks: 4 production patterns we ship today on Digitorn
Read article
Newsletter
Get the next post in your inbox.
Engineering notes from the Digitorn team. No marketing, no launch announcements, no "10 prompts that will change your life". Just the things we write that we'd want to read.