You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7e46f87
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): record import provenance on the provider thread
The first version keyed the resume decision on `providerSessionId === null`
at `resumeThread`, but the orchestrator binds a provider session to the
provider thread when it starts the run, before the turn-start service ever
reaches the adapter, so the guard could not fire in production.
Both import paths now stamp `nativeMetadata.nativeThreadOrigin = "imported"`
on the provider thread they write, and `ClaudeAdapterV2.openQuery` reads it
from the turn's provider thread next to the existing resume signals. The
provenance is persisted with the row, so it survives idle release and a
failed first follow-up, and threads this adapter minted carry no origin and
keep creating their session.
0 commit comments