I'm on a deep dive fine-tuning how I organize and manage my personal knowledge base - focused on entity extraction and strategic information retrieval and based on the AgREE paper from Apple[0] and persisting it in Memgraph.
I've got a nice ingest, extract, enrich process going for the graph - I'm currently working on a fork of claude-mem[1] that uses the graph as a contextual backend for agentic coding workflows.
If you're like me you're doing it to establish a greater level of trust in generated code. It feels easier to draw out the hard guard-rails and have something fill out the middle -- giving both you, and the models, a reference point or contract as to what's "correct"
This is a great use case for sub-agents IMO. By default, sub-agents use sonnet. You can have opus orchestrate the various agents and get (close to) the best of both worlds.
- settings.json - set for machine, project
- env var - set for an environment/shell/sandbox
- slash command - set for a session
- magical keyword - set for a turn