VibeAround is a lightweight Tauri desktop app that gives you two ways to reach your local AI coding agent from anywhere: chat from your daily IM (Telegram, Slack, Discord, Feishu…), or a browser-based web terminal with tmux support. Works with 7 agents including Claude Code, Gemini CLI, and Codex CLI — all speaking ACP over stdio. Hand sessions between terminal and phone with /handover + /pickup, switch agents mid-conversation, Preview dev servers and markdown remotely and on your phone.
The big update: Codex can now work with OpenAI Chat API-compatible providers through VibeAround.
That means you can run Codex locally, but route it through providers such as DeepSeek V4 or other OpenAI-compatible endpoints without constantly editing config files or changing your global setup.
One part of VibeAround that is easy to miss: your local coding agent can generate a preview link from an IM chat, then pair your phone browser with a short code.
Just added a new Quick Launch module to VibeAround.
The problem: every AI coding CLI has its own config files, env vars, model names, API endpoints, and terminal behavior. If you use multiple agents or providers, switching gets messy fast.
Hey everyone, I'm Jazzen, the maker of VibeAround.
I built this out of a simple frustration: AI coding agents like Claude Code and Codex are incredibly powerful, but they're trapped in your terminal. Step away from your desk and you lose all access — can't check progress, can't nudge the agent, can't review what it wrote.
My fix: turn the IM apps you already use into an interface for your local agent. Open Telegram on your phone, send a message, and Claude Code starts writing code on your machine at home. Need a full shell? Open the web terminal in any browser. Started something in terminal but heading out? `/handover` exports the session, `/pickup` resumes it on your phone with full context.
It's built with Rust + Tauri, every IM channel is a plugin, and everything speaks ACP. No vendor lock-in — your agent, your machine, your API keys.
I'd love to hear what you think.
VibeAround exposes powerful local capabilities over tunnels and chat: what’s your security/threat model (auth, token rotation, least-privilege for channel plugins), and what would you change for teams with stricter requirements (audit logs, workspace isolation, sandboxed agents)?
All tunnel URLs are gated by a pairing-code auth flow — browsers must verify ownership via a connected IM channel before getting access.
Channel plugins run as isolated Node.js subprocesses responding only to configured users.
Agents communicate over stdio via ACP, no network ports exposed.
For teams with stricter requirements (Still in the design phase.)
The current version is designed as a single-machine desktop app. For team/enterprise use, the plan is to move away from Tauri distribution and run VibeAround as a containerized service — on-demand sandboxed containers per user, with session history and environment persisted as blobs in the org's own infrastructure.
The phone is designed as a flexible, lightweight complement. When you're away from your desk, it gives you a way to tap into the most capable coding agents — Claude Code, Gemini CLI, Codex — that otherwise only live in a terminal.
I've been using it daily myself. For single-agent tasks, once you get used to the chat-style interaction, the experience is almost on par with desktop. However, IM has its limits — you're working within chat bubbles, and multi-agent workflows aren't as fluid there. That's exactly why I added the web terminal as an option.
Each channel plugin uses the platform's native SDK and rendering features (Telegram's markdown, Slack's blocks, etc.) rather than a lowest-common-denominator layer.
Report
Interesting to note this is a Tauri App - Have you considered electron js as an alternative?
@dhruba_patra Yes, I considered Electron early on. Went with Tauri mainly because the core is a Rust daemon managing agent processes and tunnels over stdio — having the backend in Rust natively made the architecture much simpler. The smaller binary size (~15 MB vs 150 MB+) was a nice bonus.
@talwesingh Thanks and good question! A few key differences:
VibeAround doesn't require any official subscription — your agent runs locally with your own API key, so it works with third-party providers too. And it's not limited to Claude — 7 agents supported, switchable mid-conversation.
Beyond IM chat, you also get a web terminal (full shell in any browser, with tmux support) and live preview (your agent's dev server rendered on your phone through a short-lived link). These surfaces don't exist in a single-agent remote control setup.
As for OpenClaw — different focus. OpenClaw is a general-purpose personal assistant; VibeAround is built specifically for coding workflows with dedicated features like web terminal, live preview, session handover between devices, and agent switching.
VibeAround
Product Hunt
VibeAround
@curiouskitty
Current security model:
All tunnel URLs are gated by a pairing-code auth flow — browsers must verify ownership via a connected IM channel before getting access.
Channel plugins run as isolated Node.js subprocesses responding only to configured users.
Agents communicate over stdio via ACP, no network ports exposed.
For teams with stricter requirements (Still in the design phase.)
The current version is designed as a single-machine desktop app. For team/enterprise use, the plan is to move away from Tauri distribution and run VibeAround as a containerized service — on-demand sandboxed containers per user, with session history and environment persisted as blobs in the org's own infrastructure.
Athena
VibeAround
@maya_elor Thanks!
The phone is designed as a flexible, lightweight complement. When you're away from your desk, it gives you a way to tap into the most capable coding agents — Claude Code, Gemini CLI, Codex — that otherwise only live in a terminal.
I've been using it daily myself. For single-agent tasks, once you get used to the chat-style interaction, the experience is almost on par with desktop. However, IM has its limits — you're working within chat bubbles, and multi-agent workflows aren't as fluid there. That's exactly why I added the web terminal as an option.
Each channel plugin uses the platform's native SDK and rendering features (Telegram's markdown, Slack's blocks, etc.) rather than a lowest-common-denominator layer.
Interesting to note this is a Tauri App - Have you considered electron js as an alternative?
VibeAround
@dhruba_patra Yes, I considered Electron early on. Went with Tauri mainly because the core is a Rust daemon managing agent processes and tunnels over stdio — having the backend in Rust natively made the architecture much simpler. The smaller binary size (~15 MB vs 150 MB+) was a nice bonus.
Clera
I like the idea in general. But how does this differentiate compared to Claude remote control. Or you could also just text your openclaw, right?
VibeAround
@talwesingh Thanks and good question! A few key differences:
VibeAround doesn't require any official subscription — your agent runs locally with your own API key, so it works with third-party providers too. And it's not limited to Claude — 7 agents supported, switchable mid-conversation.
Beyond IM chat, you also get a web terminal (full shell in any browser, with tmux support) and live preview (your agent's dev server rendered on your phone through a short-lived link). These surfaces don't exist in a single-agent remote control setup.
As for OpenClaw — different focus. OpenClaw is a general-purpose personal assistant; VibeAround is built specifically for coding workflows with dedicated features like web terminal, live preview, session handover between devices, and agent switching.
Clera
@jazzenchen Okay, I see. Yea web terminal is actually pretty sweet. Will give this a go
VibeAround
@talwesingh Awesome, let me know how it goes! If you run into anything during setup, feel free to open an issue on GitHub.