Timeout issues and false "Task completed" status when processing large data tasks

[leon7786]

Issue Description:

1. 300s Timeout Termination
   The process is automatically terminated by Claude once the execution time hits the 300-second (5-minute) threshold. This prevents the completion of longer-running tasks. Is there a way to configure or extend this timeout?

2. False Completion Reporting
   I attempted to have the agent download tick-by-tick BTC transaction data from 2025 to the present. After running for a significant amount of time, the agent replied with:

✅ Task completed. Tools used: ExitPlanMode, TodoWrite, Read, Edit, Write

However, upon checking the project directory, no files were generated and no data was actually downloaded. It seems the agent is hallucinating a successful outcome or exiting the loop prematurely without verifying the output of the tools.

[xiaotonng]

The 300s hard timeout and hallucinated "Task completed" are two sides of the same coin — if you kill the CLI process on timeout, you lose the real exit status and have to guess whether it finished. pikiclaw handles this with a watchdog + sleep prevention system in process-control.ts that keeps long tasks alive indefinitely, combined with structured stream parsing in agent/stream.ts that only reports completion based on actual CLI exit codes and output, never inferred status. We also have a task queue with "Steer" — you can send follow-up instructions while the agent is still working, so you never need to wait-and-timeout. If you've dealt with long-running agent reliability issues, we'd love help on xiaotonng/pikiclaw#8. Try npx pikiclaw@latest to see the difference.

GitHub: https://github.com/xiaotonng/pikiclaw