New sessions spawn under holders - #102
Merged
Merged
Conversation
karngyan
force-pushed
the
holder-3-spawn
branch
from
August 18, 2026 22:03
16c8eff to
72bd6ff
Compare
karngyan
force-pushed
the
holder-3-spawn
branch
from
August 19, 2026 05:52
72bd6ff to
d2d7b0b
Compare
Spawn and Revive run each session under its own holder once the registry is pointed at the holder executable and root, which flue serve now does; FLUE_NO_HOLDER=1 keeps the in-process path. The identity record written beside each socket is the daemon-owned half a reattach needs, and the keep affordance's ephemeral flip lands there too. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
karngyan
force-pushed
the
holder-3-spawn
branch
from
August 19, 2026 08:58
d2d7b0b to
1fe42af
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Third in the holder-sessions stack, on top of #101.
flue servepoints the registry at the holder executable and<config>/holders, so every Spawn and Revive now runs its session out-of-process.FLUE_NO_HOLDER=1is the escape hatch back to in-process sessions, and tests keep exercising the engine directly. Each holder directory carries the daemon-ownedsession.jsonidentity record (id, display cmd, group, ephemeral, createdAt); the keep affordance's ephemeral flip is persisted there so a later reattach honors it.Smoke-tested against the real binary: spawn over the ws wire, then
kill -9the daemon — the holder and the session's child keep running. (Reattach on daemon start is the next PR; until then a restarted daemon does not yet pick live holders back up.)🤖 Generated with Claude Code