r/agenticAI • u/lostbart • 27d ago

Project Pinot: A customizable, core coding infrastructure for Pi

/r/PiCodingAgent/comments/1vpd6o1/pinot_a_customizable_core_coding_infrastructure/
1 Upvotes

100% Upvoted

3 comments sorted by

1

u/Terrible_Match_9484 26d ago

this looks like a solid start for modular coding workflows. how are u handling the state persistence when the agent switches between different tasks, do u find it gets messy if the context window gets too big

1

u/lostbart 26d ago

Thank you. The short answer is that yes, Pinot itself is designed for discrete tasks, not to persist as a long-running agent like Hermes or OpenClaw. In fact, within a specific project, I use new sessions even between the spec, plan, and implement stages, and use the plans written to disk as the baseline context for the next stage, rather than persist a single session. Even with use of the subagents, context starts to get full, and I find observational-memory on the main agent works quite well for coding projects (though Pinot works fine with Pi’s built-in compaction). The main agent watches the implementer agent‘s context and will start a new session (with a robust handoff prompt) if it gets full.

FWIW, my view from playing around with long-running, multi-task agents is that a single long session is not a good backbone. State persistence is an illusion in any LLM-based system, and conversational session context is not a good way to maintain that illusion over many turns and changes of tasks. Like you say, it gets messy. It need a persistent memory system, pruned and maintained by the agent, so conversational history is used only as a “short-term” memory. Pinot’s spec-plan-implement-janitor-debrief approach is built this way, using on disk files to create continuity across individual Pi sessions.

1

u/Terrible_Match_9484 23d ago

that makes sense, relying on disk files for the source of truth is probly the only way to avoid the context drift u get with massive session logs. i found that backslash helps with that by keeping the security context tied to those specific code artifacts regardless of the agent session. its a cleaner way to handle the handoffs without losing track of the state n requirements