[Bug] Agent stops without leaving artifacts #3050

Activity

1. awaescher

   added

   bugSomething isn't workingSomething isn't working

   on Aug 21, 2026
2. openchamber-bot

   added

   area:agentsAgents, subagents, multi-run, agent managerAgents, subagents, multi-run, agent manager

   platform:macosmacOS desktop (Electron/Tauri)macOS desktop (Electron/Tauri)

   priority:highMaintainer-set only: blocks core workflows, data loss, or many usersMaintainer-set only: blocks core workflows, data loss, or many users

   needs-infoNeeds more info from reporter to reproduceNeeds more info from reporter to reproduce

   reproduction-steps:false

   on Aug 21, 2026
3. openchamber-bot commented on Aug 21, 2026

   

   openchamber-botBot

   on Aug 21, 2026

   Contributor

   More actions

   Thanks for the report. An agent run that ends without any chat or file output is a core workflow breaker, and seeing it on both ox-alpha and local Qwen suggests it's not tied to one model.

   To help us pin this down, could you share a bit more?

   • The logs section came through empty. Any log output from around the time the run stops would help a lot.
   • Does the run stop with an error, or does it just go quiet? Does the session still show up in the sidebar afterward?
   • Does it happen at a particular point (start of a run, mid-response), or does it feel random?

   The screenshot is helpful too. If anything on screen looks unusual at the moment it stops, that's worth mentioning.
4. awaescher commented on Aug 21, 2026

   

   awaescher

   on Aug 21, 2026

   Author

   More actions

   I can't find any thinking traces that got cut off, which could show that the model came to a limit and had to stop, forced by the provider. But it looks okay to me in OpenChamber.

   

   ---

   However, I did the same in the OpenCode UI and it did not finish either. Here however it looks like it got force-stopped:

   
5. btriapitsyn

   removed

   reproduction-steps:false

   on Aug 28, 2026
6. yulia-ivashko commented on Sep 15, 2026

   

   yulia-ivashko

   on Sep 15, 2026

   Contributor

   More actions

   Your comparison with the OpenCode UI shows the turn was stopped there too. 563911ad8, included in v1.23.0, improves OpenChamber's handling by displaying failed-turn errors and diagnostic history instead of leaving the failure silent. It does not repair the underlying OpenCode/provider turn failure, so this is closing as not planned here. Thanks for checking both clients and sharing the results.

   👀React with 👀1Reacted by Andreas Wäscher
7. yulia-ivashko

   closed this as not plannedon Sep 15, 2026
8. awaescher commented on Sep 16, 2026

   

   awaescher

   on Sep 16, 2026

   Author

   More actions

   Related to #2809, setting OPENCODE_EXPERIMENTAL_OUTPUT_TOKEN_MAX actually works. Defining max_tokens in the OpenCode provider config does not work (yet).

   Discusstion over at: anomalyco/opencode#1735