[DenisM]

Suggestions? My attempts to get the agent to summarize the discussion largely failed. Other options I’m considering is capturing design, implementation plans, and maybe sub-plans. I’m Other words precursor to actions. Another idea is to get an agent to review code post-action and capture that. In other words action outcomes. The actual reasoning is between these “checkpoints” and remains hidden. But maybe that’s ok.

[vamsiraju]

What you said is pretty much the same somewhat tangential approach I am taking too. Force the agent to write code alongside another set of docs which form the basis- Intent (functional and non-functional requirements), Blueprint (architecture etc.), and Description files (describe the code at a high level alongside every source file). This information set is not the same as the reasoning/thinking trace information thats in the session, but reading this somewhat compressed set is easier, helps me better understand whats happening in the final output with lower effort than if i read the entire thinking/reasoning trace in the session and tried to grok what the agent did to generate the code.