Repository navigation
fix(promachos): the home spans every machine the sidebar merges it over - #208
Merged
Merged
Conversation
The Promachos home named one project on one environment, so conversations started on another machine's copy of the same repository never showed in Promachos mode. The home now covers every project the sidebar's grouping merges with it, for both the conversation list and the chat presentation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
lukemaj
added a commit
that referenced
this pull request
Oct 14, 2026
…er (#208) The Promachos home named one project on one environment, so conversations started on another machine's copy of the same repository never showed in Promachos mode. The home now covers every project the sidebar's grouping merges with it, for both the conversation list and the chat presentation. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 14, 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
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.
What: Promachos mode lists and renders conversations from every machine's copy of the home, the same way the sidebar merges projects.
Why: The home named one project on one environment (
promachos · cavallo), so a conversation started on bestia'spromachosnever appeared.So what: Needs the developer's merge approval; after merge it gets staged on cavallo per the runbook.
Fix
promachosHomeRefsresolves the home to every project sharing its logical key under the user's grouping settings (deriveLogicalProjectKeyFromSettings, the sidebar's own rule).usePromachosChat) use that set. The home label drops the machine name when it spans more than one.separatekeeps a single-machine home.Evidence
~/dev/promachoswith origingithub.com/lukemaj/promachos; cavallo's grouping mode isrepository, so they merge.Proof
vp test run src/components/promachos: 4 files, 20 tests passed, including new cross-machine andseparate-mode cases.apps/webtypecheck passed; lint clean onsrc/components/promachos.Elon record
Requirements and who asked: The developer: Promachos runs on any machine and all its conversations show in Promachos mode.
Deleted: A new Promachos-specific grouping setting; the sidebar's grouping already defines "same project".
Bottleneck: The home was a single
ScopedProjectRef.Checked myself: Read both machines' project records and cavallo's grouping setting; ran the tests and typecheck above.
Opus 5.5 via Claude Code in T3 Code.
🤖 Generated with Claude Code