Repository navigation
fix(web): keep standing bots in the sidebar for both founders - #160
Open
nullStack65 wants to merge 1 commit into
Open
nullStack65 wants to merge 1 commit into
nullStack65 wants to merge 1 commit into
Conversation
A standing launch with no inbox was filed as Agents with background attention. Routing that thread to a founder by audience left the background attention in place, and a founder lane does not show background, so the bot disappeared. Standing now defaults to Shared with FYI attention. A route out of Agents into a founder or Shared inbox lifts omitted background attention to FYI. Linked thread lists carry the persona, and a non-archived standing bot stays in Bots for both founders unless its environment is hidden. Project scope and the Inbox and From checkboxes no longer drop it. The filter popover is wide enough to show full inbox and environment names. Committed with --no-verify. This host's Node v22.22.1 is not compiled with TypeScript support, so the pre-commit hook cannot load oxlint-plugin-t3code/index.ts or knip's TypeScript schemas. vp fmt passed on these 20 files. CI runs lint and knip. Model: grok-4.7 Task: fix Agent: Platform Harness: t3
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
Standing bots launched with no inbox were filed as Agents with background attention. A later route that only set
audienceto a founder leftattentionKind: "background"in place. A founder lane shows only action or FYI, and the sidebar applies the inbox filter before it splits Bots, so those bots vanished. Growth stayed visible because it was already Shared with FYI.A standing launch with inbox and audience omitted now files Shared with FYI (
reason: fyi). Setting a persona refiles an Agents inbox to Shared with FYI, and lifts background attention on a founder or Shared inbox to FYI. A route out of Agents into kameron, jeff, or shared upgrades omitted background attention to FYI and assigns the named founder. An explicit attention kind, including background, is kept.Linked thread lists now carry
standing. A non-archived standing bot stays in Bots for both founders, on the local machine and on linked environments, unless that environment is hidden or the thread is archived. Project scope and the Inbox and From filters no longer drop it, and a running standing bot still counts for its environment. The viewer's own founder-audience bots stay in My Bots. Shared, the other founder, agent-only, and unspecified standing bots stay in Shared Bots.The inbox filter popover uses a wide explicit width (
40rem, capped to the viewport). Option labels no longer truncate to a few characters.Stored rows change inbox only when this server handles a launch,
set_standing, orroute. Peers omitstandinguntil they run this build, so both sides need the fleet deploy before a remote bot is recognized as standing.Model: grok-4.7
Task: fix
Agent: Platform
Harness: t3
Deploy: fleet
Verified
packages/contractsthreadInboxtests: 24 passed (vp test run, head6bf87eeaf11c96143237c6a56dc59e2893ebfa0f)packages/client-runtimelinkedSidebartests: 5 passedapps/serverpeerlinkedSidebartest: 1 passedapps/webbot presence, sidebar logic, and filter tests: 109 passed, via a standalone unit config. This host cannot loadapps/web/vite.config.ts(ERR_NO_TYPESCRIPTon Node v22.22.1)vp fmton the 20 changed filesNot verified here
oxlint-plugin-t3code/index.ts. The commit used--no-verifyafter fmt. The same local knip gap is recorded on fix(web): the thread action menu test loads again #153. CI is the lint and knip gate.updatedAttest was not re-run. The reducer still does not setupdatedAt.Do not merge from this change. Fleet deploy is the rollout.