Skip to content

fix(conductor): pass through sessionKeyPrefix from portable spawn result - #425

Closed
waylonkenning wants to merge 1 commit into
outsourc-e:mainfrom
waylonkenning:fix-conductor-session-key-prefix
Closed

fix(conductor): pass through sessionKeyPrefix from portable spawn result#425
waylonkenning wants to merge 1 commit into
outsourc-e:mainfrom
waylonkenning:fix-conductor-session-key-prefix

Conversation

@waylonkenning

Copy link
Copy Markdown

Summary

Fixes a bug where sessionKeyPrefix was hardcoded to null in conductor-spawn.ts, breaking async session resolution when the dashboard backend returns a prefix value from the spawn result.

Change

  • conductor-spawn.ts: Changed sessionKeyPrefix: null to read the value from the spawn result: (result as Record<string, unknown>).sessionKeyPrefix ?? null

This mirrors the existing sessionKey pattern and ensures the downstream job/session routing can correctly resolve sessions when the backend provides a prefix.

How it was found

After getting the Conductor page working locally with a dashboard-backed backend, missions were spawning but the async session resolver could not find them because the hardcoded null blocked prefix-based lookups.

Co-authored-by: Hermes Agent

sessionKeyPrefix was hardcoded to null in conductor-spawn.ts, breaking
async session resolution when the dashboard backend returns a prefix.
Now mirrors the sessionKey pattern and passes through the value from
the spawn result.

Co-authored-by: Hermes Agent
@outsourc-e

Copy link
Copy Markdown
Owner

Closing as superseded by #432. The validated fix was folded into the consolidated batch branch fix/issue-sweep-batch-20260514 for one review/merge path.

@outsourc-e outsourc-e closed this May 14, 2026
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.

2 participants