Skip to content

stewards: write init's files on the thread's machine - #21

Merged
trotterdylan merged 1 commit into
mainfrom
bb/i-want-to-set-up-this-project-as-a-steward-proje-thr_5qzqtic3f9
Oct 18, 2026
Merged

trotterdylan merged 1 commit into
mainfrom
bb/i-want-to-set-up-this-project-as-a-steward-proje-thr_5qzqtic3f9

Conversation

@trotterdylan

Copy link
Copy Markdown
Collaborator

bb stewards init failed on bb-gate servers with HTTP 502: Local host daemon is not initialized.

It looked up the thread's machine as a top-level environmentHostId, which the SDK's thread doesn't have. The SDK keeps it at environment.hostId, as workstreams already reads it. So the lookup always came back empty, files.write went out without a hostId, and core sent the write to the server's own daemon. bb-gate's servers don't have one.

  • threadInfo now reads environment.hostId.
  • init falls back to projectHost(projectId), the same machine that steward spawns already use.

Two regression tests cover the thread's machine and the project fallback. Both fail without the fix, and the stewards suite passes with it (81 tests).

Merging restarts every developer's server when the new bb-server image rolls out.

🤖 Generated with Claude Code

— from bb thread thr_5qzqtic3f9

`bb stewards init` read the thread's machine from a top-level
`environmentHostId` that the SDK's thread does not have (it is
`environment.hostId`), so it always left the write to core, which picks
the server's own daemon. bb-gate's servers have none, and init failed
with "Local host daemon is not initialized". Read `environment.hostId`,
and fall back to the project's machine as spawns already do.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@trotterdylan
trotterdylan merged commit 91504a7 into main Oct 18, 2026
16 checks passed
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