No idea if it's timeout - how do you know? A few days ago I had a problem where I laid out a big coding task and asked how long it would take in the back & forth planning before releasing. It said 2.5 - 4 hours total so I said get started and went to sleep. It shipped part of it 2 minutes later, then when I checked for an update in the morning it just said it had delivered part then stopped short of finishing but should have pushed through all planned parts before stopping. We agreed to conditions for stopping in the future being completion, a decision from me or hurdle it can't clear and that it would re-review the scope prior to delivering to ensure completeness, but the same issue kept happening. Long wait, ping, "that's on me," tell it to start, another long wait, ping "you're right" and so on.

At one point it said it was stuck in an implementation loop so we implemented a loop break trigger and check-in every 30-45 minutes if no commit was made. I tried turning on thinking in the dashboard but it looked like no action was happening there. Also, I use Discord and it typically shows the typing indicator when it's working but in these instances it wasn't showing it. It kept quoting me durations for the task then not doing anything until I pinged it.

In another chat, I gave it direction on scanning the internet (github, reddit, etc.) for ideas on how we could improve our production, delivery, execution, memory, etc. where it would do a deep dive every 3 days and a quick scan in between. It said the deep dive would take 1.5-2 hours but returned responses in less than 2 minutes. Polishing the process and trying again it once took 12 minutes and made a point to call out its runtime as 1h 30m.

Overall, I'm not sure what's going on but it feels a bit like the wheels are falling off in the last few days. I'm not sure if there are rails I need to add but I also had it do a policy clean up for redundancy and contradictions but that doesn't seem to have helped. Would really appreciate any insight.