Skip to content

feat(server): scope a shell subscription to one founder inbox - #168

Closed
nullStack65 wants to merge 1 commit into
cursor/founder-inbox-tags-2efafrom
feat/clo-1059-server-inbox-scope
Closed

nullStack65 wants to merge 1 commit into
cursor/founder-inbox-tags-2efafrom
feat/clo-1059-server-inbox-scope

Conversation

@nullStack65

Copy link
Copy Markdown
Owner

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:read and 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, and startedBy fields this filters on. Tracked by the server-side inbox scoping issue (CLO-1059).

UI Changes

None.

Checklist

  • This PR is small and focused
  • I explained what changed and why
  • I included before/after screenshots for any UI changes
  • I included a video for animation/interaction changes

Provenance

Model: grok/grok-4.7
Task: implementation

🤖 Generated with Claude Code

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>
@nullStack65

Copy link
Copy Markdown
Owner Author

Frozen 2026-11-22 CEO portfolio audit — cash-path priority; can reopen at the Dec 18 runway check.

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.

2 participants