Repository navigation
feat(server): scope a shell subscription to one founder inbox - #168
Closed
nullStack65 wants to merge 1 commit into
Closed
nullStack65 wants to merge 1 commit into
nullStack65 wants to merge 1 commit into
Conversation
A vanilla mobile client passes an inbox and receives only that founder's threads, in the HTTP shell snapshot and on the live shell stream. A thread that moves out of scope is removed rather than left on screen. Desktop and web clients pass nothing and still receive every thread. The scope is a parameter, not a property of the pairing token: auth scopes are capability grants and carry no founder identity. Model: grok/grok-4.7 Task: implementation Agent: CTO standing thread Co-Authored-By: Claude Code <noreply@anthropic.com>
Owner
Author
|
Frozen 2026-11-22 CEO portfolio audit — cash-path priority; can reopen at the Dec 18 runway check. |
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 Changed
A client can now scope the orchestration shell to one founder. The HTTP shell snapshot (
GET /api/orchestration/shell?inbox=jeff) and the live shell subscription (subscribeShell({ inbox })) both return only the threads that founder would see in the desktop sidebar: threads they own, needs-human threads addressed to them, and threads they started. Bot work stays hidden.A thread that moves out of scope is sent as a removal, so a client that already holds it drops it. A removal for a thread the client never received is a no-op.
Clients that pass no inbox are unchanged and still receive every thread. The desktop and web shell snapshot call passes an empty payload, so it stays unscoped.
Why
Founder-inbox filtering lived entirely in the desktop sidebar, so a vanilla mobile client connecting to the server received all 200+ background and agent threads. The visibility rule already existed; this applies it on the server for a session that asks for it.
The scope is a request parameter rather than a property of the pairing token. Auth scopes are capability grants (
orchestration:readand the rest) and carry no founder identity, so binding an inbox to the token would need a new scope design. The parameter is the fallback the request allowed.Depends on the founder-inbox tags pull request (t3code #57), which adds the
owner,threadType, andstartedByfields this filters on. Tracked by the server-side inbox scoping issue (CLO-1059).UI Changes
None.
Checklist
Provenance
Model: grok/grok-4.7
Task: implementation
🤖 Generated with Claude Code