... built Codex Desktop Custom Models because experimenting with alternative model providers inside one desktop installation can quickly mix sessions, automation state, ports, and provider-specific configuration. Instead of modifying the main Codex setup, the project creates isolated desktop profiles. Each profile can have: its own app identity and icon a separate CODEX_HOME independent sessions and automation state a dedicated local bridge

... VibeAround v0.7.2 is out. This release is mostly about making local coding-agent setups easier to debug and less fragile: Added a Bridge recorder for local API bridge

... expose native server-side search. How it works: - VibeAround can replace provider-native `web_search` with a local search runtime. - Search runs through the git-installed `va-search-tool` plugin. - Results are normalized and fed back through the API Bridge, so the upstream model gets usable search context without needing native search support. - Search sources are configured locally in Settings; API keys stay in local settings. - Supported search source: Exa, Tavily, Grok, and Brave. Also new in this release: - Test ... ... configured web search sources directly from the desktop Settings flow. - Inspect search requests and source-separated results in the Bridge

... VibeAround v0.6.10 is out. This release focuses on bridge reliability, Gemini setup, and cleaner provider workflows. What changed: - Added Gemini Google OAuth connection support and native Gemini upstream routing. - Upgraded API bridge

... files, images, and documents - Control thinking/tool visibility - Open Web Terminal for local PTY sessions - Launch live previews for dev servers, Markdown, and HTML v0.6.3 also cleans up the model-routing layer: - Renamed the old API proxy wording to API Bridge across the app, docs, profile routing, and launch UI - Published the bridge

... Claude Tuesday: Copy paste same spec into Cursor Wednesday: Copy paste into Copilot Thursday: Which spec was I working on again? Your AI has amnesia. Your tokens are gone. Your docs are in Notion. And somehow you're the bridge. That's not a workflow. That's a part-time job. So we fixed it. v1.0.3 . Context Sync now connects directly to Notion. No more copy-paste Olympics. No more token-burning. No more "wait, did I update the Notion ... ... just the code?" Here's the new workflow: You're in Notion. Your feature spec is there, looking gorgeous as always. You open VS