Repository navigation
fix(host): list an unreachable peer's channels as offline instead of dropping them - #283
Merged
Merged
Conversation
…dropping them Why: apps/host/src/peers.ts#function unreachable | without a team directory, a peer's last answer is the only record of its channels; dropping it on disconnect hides open conversations
This was referenced Oct 15, 2026
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.
Summary
Without a team directory, a peer's channels vanished from the sidebar whenever it was unreachable: tailnet down, sleep, or a Helper restart. The open timeline and composer went with them, and nothing said why. The host now remembers each peer's last listing and lists those channels as
offline, as it already does for channels it learns from the directory. They return to live state when the peer answers again.Found in the two-person study, scenario 14 (#218). Mac B went off the tailnet for 61s. On the other Mac, Tester A's channels disappeared and showed "Choose a channel from any project". Tester B rated the confusion 3/3: they could not post.
Testing
bun typesandbun run cipass.Built in Ace
Written from Claude Code in a lane outside Ace. Overnight, the study lead orchestrates two Macs over SSH, and an Ace channel can't drive the other Mac's tester sessions. Dogfooding gap: #5.