Skip to content

feat(temporal): Kept a step's tools and seal on the worker that made its model call. - #16

Closed
moetemp wants to merge 1 commit into
moe/worker-affinityfrom
moe/pinned-queues
Closed

moetemp wants to merge 1 commit into
moe/worker-affinityfrom
moe/pinned-queues

Conversation

@moetemp

@moetemp moetemp commented Sep 15, 2026

Copy link
Copy Markdown
Collaborator

This PR sends the tools and the seal of a step back to the worker that made its model call, on a queue that worker polls on its own. On by default; OPENCODE_TEMPORAL_STEP_AFFINITY=0 turns it off.

The tools of one step write the tree that worker is standing in. Keeping them there lets them run at once and see each other's writes through the filesystem, rather than by shipping the tree between hosts, which is what made them serial in the PR below. The queue is keyed by host as well as directory, because two containers can serve /project and share none of it.

A pin nobody answers moves unstarted work to the shared queue after a schedule-to-start bound. A pinned attempt that started is never retried: a timeout settles the workflow's promise without saying whether the tool behind it stopped, so a retry could run a tool twice. Shared dispatches wait for the pinned batch before they run, for the same reason.

Tests: the stepped turn, pinned to a worker cases in packages/temporal/test/stepped-turn.test.ts.

@github-actions

Copy link
Copy Markdown

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

  • PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

The tools of one step write the tree that worker is standing in, so sending them back to it on a queue it polls alone lets them run at once and see each other's writes through the filesystem. A pin nobody answers moves unstarted work to the shared queue after a schedule-to-start bound; a pinned attempt that started is never retried, because a timeout does not say whether the tool behind it stopped.
@github-actions

Copy link
Copy Markdown

This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new pull request that follows our guidelines.

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