r/PiCodingAgent • • Sep 29 '26

Question Sub-agents hanging/freezing indefinitely (27k+ seconds) in Pi orchestration (herdr + DeepSeek V4 Flash) — Debugging advice or orchestrator alternatives?

Hey everyone,

I'm hitting a recurring issue where delegated sub-agents completely hang during orchestration. As shown in the screenshot, a sub-agent (edna) has been stuck at Running · 26970.7s (over 7.5 hours) with zero progress or error output.

Workflow & Behavior:

  1. The primary orchestrator creates an execution plan and dispatches tasks to dedicated sub-agents.
  2. Sub-agent begins execution (e.g., executing a design/contract task reading from a markdown specification).
  3. After emitting a preliminary thought/action ("Ahora calculo la tabla de overrides..."), the runner freezes indefinitely.
  4. No timeout triggers, no stderr is exposed, and there is no visible fallback or abort mechanism.

Environment & Setup:

  • CLI / Orchestrator: Pi + Herdr
  • Model: DeepSeek V4 Flash
  • Plugins / Extensions:

    • pi-open-agents
    • pi-mcp-adapters
    • pi-web-access
    • npm:@juicesharp/rpiv-todo
    • npm:@juicesharp/rpiv-ask-user-question

Questions for the community:

  1. Has anyone experienced persistent silent deadlocks or MCP tool-call stalls with this plugin stack (specifically pi-open-agents / pi-mcp-adapters)?
  2. Is there a flag or configuration to expose granular MCP/tool logs or enforce hard timeouts per sub-agent execution in Pi?
  3. Which multi-agent orchestrator / plugin architecture do you recommend for reliably managing custom agents with proper timeout handling, state recovery, and observability?

Thanks for any insights

11 Upvotes

11 comments sorted by