Repository navigation
feat(threads): founder inboxes from owner and type tags - #57
Open
nullStack65 wants to merge 1 commit into
Open
nullStack65 wants to merge 1 commit into
nullStack65 wants to merge 1 commit into
Conversation
Shared threads can record who they are for, what kind of work they are, and who started them. Founder inboxes hide bot-to-bot threads until search or a toggle asks for them, and untagged threads stay on the shared list. Model: Grok 4.7 Task: feature Agent: cursor Co-authored-by: Kameron Smith <nullStack65@users.noreply.github.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
4 tasks done
Owner
Author
|
Frozen 2026-11-22 CEO portfolio audit — cash-path priority; can reopen at the Dec 18 runway check. |
This branch has not been deployed
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
Threads in the shared pool can carry three optional tags:
owner: free-form string. The sidebar suggests Kameron, Jeff, Lead, and Jeff's Lead, and any browser can add more names.threadType:needs-human,fyi, orbot-work.startedBy: who opened the thread, same free-form identity space.They can be set on
thread.createand onthread.turn.startbootstrapcreateThread, and changed later withthread.meta.update(passnullto clear). The web sidebar (desktop uses the same UI) has an inbox picker, a show/hide control for bot work, and defaults stamped onto threads that browser starts. The thread action menu sets owner and type on an existing thread. Search reveals bot-work threads inside the current inbox. Mobile hides bot-work unless the list is searching.The
t3-codeMCP server exposesset_thread_routingso a bot in a thread can tag that thread or another thread id.Untagged threads omit the fields. With "All threads" selected they stay on the list they are on today.
Audit
T3 cannot filter a shared pool by person today.
createdByorcreationSource.historyImportonly marks an imported transcript.executionScopeiscodingorcoordinator. Pull-request author is the PR author, not who started the thread.t3_thread_list,t3_thread_organize,t3_thread_launch,create_threads,t3_thread_update,t3_thread_configure) are not in this fork. They live in upstream T3. A live check of those tools (Nov 14, 2026) matches the source gap: lists filter by project, run status, title text, settled, and snoozed. Organizing is pin, snooze, settle, archive, and mark unread.t3-code: preview, device, and pull requests. Sidebar sections are pinned, active, snoozed, settled, and archived.Stopgap before this ships
Keep bot-only work in its own project, and auto-settle those threads when the turn finishes. Settled threads leave the active list, and
t3_thread_listwithsettled=trueis how to find them again. That uses today's project scope and settlement. It does not give each founder an inbox.How bots should tag
Adopt this in closura-agent-config. The wire names are
owner,threadType, andstartedBy.On create (
thread.create, orthread.turn.start→bootstrap.createThread, which is whatt3_thread_launchandcreate_threadsshould pass through once those tools are updated):owner:Kameron,Jeff,Lead,Jeff's Lead, or any other non-empty namethreadType:needs-human,fyi, orbot-workstartedBy: the identity that opened the threadLater, call
set_thread_routingon thet3-codeMCP server, or sendthread.meta.updatewith the same fields. Omit a field to leave it.nullclears it.Until the upstream orchestrator tools accept those fields, bots on this fork tag with
set_thread_routingafter the thread exists.Founder inbox rule: show a thread when
owneris me, orthreadTypeisneeds-humanandowneris me, orstartedByis me.bot-workstays hidden until "Show bot work" or a search. Untagged threads stay on All threads.Why
One shared T3 pool, with each founder's inbox as a filter, instead of a separate compute pool per person or bot.
UI Changes
Sidebar inbox picker, bot-work toggle, and new-thread owner/type defaults. Thread menus gain Set owner and Set type. No screenshot in this run: the dev server was not paired, so the check was the filter tests and typecheck rather than a browser pass.
Checklist
Verification
GitHub Actions are disabled on this fork. Local results, Node 24.13.1,
vp0.3.3:vp run -r --concurrency-limit 2 typecheck: 15 packages, exit 0. Effect diagnostics are suggestions only.vp lint: exit 0. Remaining output is existing warnings.vp run -r teststopped onpackages/shared/src/isolationRoot.test.ts(expected messageunowned files, got an ownership/private-profile error). That file is untouched.apps/server: 5712 passed, 11 skipped, 1 failed:scripts/deploy-relay-workflow.test.tsexpects only thenullStack65repository identity and the workflow now also nameskameron-smith-closura. Untouched by this PR.apps/desktop: 1353 passed, 4 suites failed loading becauseElectron.appis undefined while the Electron binary was downloading. Untouched by this PR.Provenance
Model: Grok 4.7
Task: feature