Skip to content

Dev Log 049 – Compile and Dryrun Agent Context Linking

✅ Dev Log 049 – Compile and Dryrun Agent Context Linking

This update addresses a long-standing inconsistency in how Dokugent resolves the current agent context between the compile and dryrun commands.

🔧 What Was Fixed

  • dryrun previously defaulted to a hardcoded or oldest available agent (e.g., happybot@...) instead of the currently active agent.
  • A new resolution path was implemented: dryrun now reads the agentName and birth fields directly from .dokugent/data/agents/current/identity.json and dynamically derives the agent ID used for lookup.
  • This matches the folder naming convention inside .dokugent/ops/compiled/.

🧠 Why This Matters

Agent continuity is critical for verifiable workflows. By tightly coupling the identity source (current) with the compiled certificate location, we:

  • Reduce accidental mismatches
  • Avoid stale context errors
  • Improve CLI reliability across chained commands

🛠 Example

```bash $ dokugent compile ✔ Compiled agent: merrybot@2025-06-08_04-16-35-246 ✔ Cert file: merrybot@2025-06-08_04-16-35-246.compiled.v19.cert.json

$ dokugent dryrun 🧠 Running dryrun for agent: merrybot@2025-06-08_04-16-35-246 📄 Certificate file used: compiled.v19.cert.json

Categories