Blog · Analysis
The hidden developer win: append-only session logs
August 14, 2026 · dshbase
One of the most developer-friendly — and most overlooked — features of DeepSeek Harness is how it stores sessions: as an append-only event log.
What's in the log
Everything the model sees and does becomes an event:
- System prompts and user messages
- Reasoning content
- Tool calls and their results
- Permission changes
- Context injections and compression
- Sub-agent scheduling
Next turn history is re-derived
The model's history for the next turn is re-derived from this log — not from a black-box state. That design choice is what makes the whole thing inspectable.
Why it matters: observability, auditing, reproducibility
When most agents fail, you only see "task failed" or an infinite loop — you can't tell where it went off the rails. DeepSeek Harness's trajectory view lets you inspect each run by source. For developers, that means:
- Observable — see exactly which step derailed a task.
- Auditable — trace every tool call and permission decision.
- Reproducible — replay a run from its event log.
That's genuinely valuable for research and for debugging production agents.
Related
See the four modes guide — the Create mode and session logs together are what make DeepSeek Harness an agent framework rather than a finished product.