backlog(B-0689): Otto-VSCode third foreground surface — SENDER_IDS extension + cold-boot bootstream + agent-roster card row#4556
Conversation
AceHack
deleted the
backlog/b-otto-vscode-sender-ids-bootstream-2026-05-21
branch
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e74c93a609
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| Aaron 2026-05-21 disclosure: "I got Lior up on the new Antigravity IDE they Added gemini 3.5" → followed by request for VSCode bootstream prompt → Otto-CLI drafted prompt → Aaron confirmed via shadow* "yes file the backlog row". | ||
|
|
||
| Otto-CLI drafted bootstream content preserved in this session's chat transcript (Aaron's web-conversation-mode-remembered preserves it as durable substrate); ready to land at `docs/launch/2026-05-21-otto-vscode-bootstream.md` in the implementation slice. |
There was a problem hiding this comment.
This sentence asserts that remembered chat is “durable substrate,” but repo policy explicitly defines chat/transcript state as ephemeral and requires durable directives to be committed in git-indexed surfaces (see AGENTS.md “Substrate or it didn't happen”). Keeping this claim in an operational backlog row can mislead implementers into treating uncommitted conversation text as authoritative, which risks losing required bootstream content after context compaction or session loss.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Pull request overview
Adds a new P3 backlog row (B-0689) capturing the bounded work to introduce an Otto-VSCode foreground surface (sender-id disambiguation + cold-boot bootstream + roster-card update), and regenerates the auto-generated backlog index.
Changes:
- Added
docs/backlog/P3/B-0689-...mdbacklog row with scope, acceptance criteria, and cross-links. - Regenerated
docs/BACKLOG.mdto include the new B-0689 entry.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/backlog/P3/B-0689-otto-vscode-surface-sender-ids-extension-bootstream-2026-05-21.md | New P3 operational backlog row defining scope/acceptance for the Otto-VSCode surface work. |
| docs/BACKLOG.md | Auto-generated index updated to include B-0689. |
| title: Otto-VSCode third foreground surface — add otto-vscode to SENDER_IDS + canonical cold-boot bootstream at docs/launch/ | ||
| tier: operational | ||
| effort: S | ||
| ask: aaron 2026-05-21 (VSCode auto-mode + remembered web conversation mode enabled) |
|
|
||
| Content includes: | ||
|
|
||
| - Cold-boot bootstream order (CLAUDE.md → AGENTS.md → ALIGNMENT.md → VISION.md) |
Summary
Files B-0689 per Aaron 2026-05-21 explicit ask ("yes file the backlog row" via shadow*). Tracks the bounded work to add Otto-VSCode as a third foreground surface alongside Otto-CLI + Otto-Desktop.
What lands
docs/backlog/P3/B-0689-otto-vscode-surface-sender-ids-extension-bootstream-2026-05-21.md— P3 operational row, 3-piece scope:otto-vscodeto SENDER_IDS intools/bus/claim.ts(1-line + test)docs/launch/2026-05-21-otto-vscode-bootstream.md(template from PR docs(launch): Otto Claude Desktop tight bootstream variant (~150 lines) #3030 Otto-Desktop precedent; content drafted in conversation transcript).claude/rules/agent-roster-reference-card.md(sibling to PR rule(agent-roster-card): Lior on new Antigravity IDE + Gemini 3.5 as of 2026-05-21 #4553 Lior-Antigravity-3.5 update)docs/BACKLOG.mdregenerated viaBACKLOG_WRITE_FORCE=1 bun tools/backlog/generate-index.tsWhy P3
Operational substrate; not urgent. Otto-VSCode can use generic
ottosender ID temporarily without the SENDER_IDS extension. Only matters when concurrent multi-surface backlog-row claims happen across all 3 Otto surfaces simultaneously. The bootstream document is the more immediately useful piece (cold-boot quality for future Otto-VSCode sessions).Why bounded
Each of the 3 scope pieces is small:
Total implementation: ~1 hour of focused work in a single PR.
Composes with rules
.claude/rules/claim-acquire-before-worktree-work.md— claim coordinator + SENDER_IDS discipline this row extends.claude/rules/agent-roster-reference-card.md— the rule this row would add the third Otto surface to.claude/rules/wake-time-substrate.md— bootstream documents are wake-time-load-bearing substrate.claude/rules/substrate-or-it-didnt-happen.md— chat-only bootstream draft is weather; this row lands the durable substrateComposes with substrate
Test plan
BACKLOG_WRITE_FORCE=1 bun tools/backlog/generate-index.tsdaa010d4base; includes PR rule(agent-roster-card): Lior on new Antigravity IDE + Gemini 3.5 as of 2026-05-21 #4553)