Vibewaiting

Vibewaiting is a browser companion for developers who run Claude Code or Codex locally. It keeps those sessions within reach while you work in the browser: see what each agent is doing, reply from an ordinary tab, attach the page you are looking at, or switch the same conversation into a familiar terminal. Why is a local companion needed? Claude Code and Codex keep their transcripts, process state, and tmux-backed terminals on the developer's computer, where Chrome's extension sandbox cannot read them. The Vibewaiting companion stays on that computer and bridges the extension to the sessions the developer already runs there. By default, session content stays on your computer. Vibewaiting has no hosted agent account, analytics, advertising, or cloud transcript service. Claude Code and Codex keep their own credentials; Vibewaiting never receives provider passwords, API keys, or login cookies. Website access is optional. If you enable it, Vibewaiting temporarily remembers the page URL and title, your selection, and the latest link, image, or visible control you point at or focus so the user-invoked Attach action works in one step. Password fields are excluded. Nothing enters a coding-agent session or paired device until you choose Attach, and you can revoke website access at any time. Optional remote access is off by default. When enabled, selected chat and terminal traffic travels over HTTPS/WSS through Cloudflare, your configured ngrok account, or a stable HTTPS relay to an authenticated device you pair. Insecure relay URLs are rejected and stopping remote access closes the route. Requires macOS or Linux, the Vibewaiting local companion, and a local Claude Code or Codex installation signed in with that provider. Chrome, Chromium, and Brave are supported in this alpha. Windows, Firefox, and other coding harnesses are not yet supported.