Skip to content

[Fix] Internal timers appear and connection resets stop tasks - #2479

Merged
mrubens merged 2 commits into
developfrom
fix/internal-wakeups-provider-retries-1aedvxder04ih
Sep 10, 2026
Merged

[Fix] Internal timers appear and connection resets stop tasks#2479
mrubens merged 2 commits into
developfrom
fix/internal-wakeups-provider-retries-1aedvxder04ih

Conversation

@roomote-roomote

@roomote-roomote roomote-roomote Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

  • Automatically create the internal Session follow-through timer only in the server-owned path after a successful human-requested task launch.
  • Remove internal visibility from the model-callable wakeup schemas so user reminders always remain visible, even if model input includes an extra internal field.
  • Hand an exhausted OpenCode Connection reset by server retry into Roomote's existing bounded provider recovery instead of terminating the coding task.
  • Keep visible and internal wakeups in separate deduplication identities, retain queued user follow-ups during recovery, and leave unrelated or explicitly terminal provider failures unchanged.

Why this change was made

Automatic follow-through depended on a model-controlled visibility flag: omitting it exposed the internal timer, while accepting it could let an ordinary reminder be hidden. The runtime now owns that distinction directly. Separately, OpenCode's internal retry ceiling converted a transient connection reset into a terminal error before Roomote's standard recovery budget could run.

Impact

Internal Session maintenance no longer appears as a user reminder, model-created reminders cannot opt out of the composer, and coding tasks can continue automatically after bounded OpenCode retries exhaust on this transport reset. Authentication, credits, policy, and other terminal failures retain their existing handling.

@roomote-community

roomote-community Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

No new code issues found. See task

  • Restrict the internal wakeup flag to system-owned follow-through scheduling so user reminders cannot be hidden.

Reviewed 25ddbf1

Comment thread packages/cloud-agents/src/server/fast-agent/fast-agent-native-tool-bridge.ts Outdated
@roomote-roomote

roomote-roomote Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

Resolved the internal-wakeup ownership issue in 25ddbf1b: model-created reminders can no longer set hidden visibility, and successful human-requested task launches schedule the internal follow-through timer through a server-owned path. See the task.

@mrubens
mrubens marked this pull request as ready for review September 10, 2026 18:33
@mrubens
mrubens merged commit 340df30 into develop Sep 10, 2026
17 checks passed
@mrubens
mrubens deleted the fix/internal-wakeups-provider-retries-1aedvxder04ih branch September 10, 2026 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant