You're at the beach. Phone buzzes — production's on fire.
Old you: Panic. Find WiFi. Open laptop. Wait for IDE. Lose your tan.
Vibe Remote you: Open Slack, Discord, Telegram, or WeChat. Type "Fix the auth bug in login.py". Watch Claude Code fix it in real-time. Approve. Sip margarita.
AI works. You live.
curl -fsSL https://raw.githubusercontent.com/cyhhao/vibe-remote/master/install.sh | bash && vibeThat's it. Browser opens -> Follow the wizard -> Done.
Windows?
We recommend the WSL setup on Windows because it has the best compatibility.
- Recommended: Run Vibe Remote with WSL from Scratch
If you are new to WSL, this guide explains:
- where to install WSL
- which terminal window to use
- where to run the Vibe Remote install command
- how to launch Ubuntu and open the Web UI
| Problem | Solution |
|---|---|
| Claude Code is amazing but needs a terminal | Slack/Discord/Telegram/WeChat/Lark IS your terminal now |
| Context-switching kills flow | Stay in one app |
| Start on desktop, continue on phone | Resume the exact agent session from the current project in seconds |
| Can't code from phone | Yes you can |
| Multiple agents, multiple setups | One chat app, any agent |
Supported Agents:
- Claude Code — Deep reasoning, complex refactors
- OpenCode — Fast, extensible, community favorite
- Codex — OpenAI's coding model
| Vibe Remote | OpenClaw | |
|---|---|---|
| Setup | One command + web wizard. Done in 2 minutes. | Gateway + channels + JSON config. Expect an afternoon. |
| Security | Local-first. Socket Mode / WebSocket only. No public endpoints, no inbound ports, minimal attack surface. | Gateway exposes ports. More moving parts, more attack surface. |
| Token cost | Thin transport layer — relays messages between your IM and agent. Zero LLM overhead from the middleware itself. | Every message carries a long system context for maintaining agent persona, IM tooling, and orchestration plumbing. Tokens burn on overhead before your actual task even starts. |
OpenClaw is a personal AI assistant — great for casual chat, but its always-on agent loop makes it expensive for real productivity workloads. Vibe Remote is not an agent framework. It's a remote control — a minimal bridge between your chat app and whatever AI agent you already use. It adds no extra intelligence layer, no extra token spend, and no extra attack surface. Every token goes straight to your task.
|
One-command install, guided configuration. No manual token juggling. |
Real-time status, health monitoring, and quick controls. |
Per-channel agent configuration. Different projects, different agents. |
Get notified the moment your AI finishes. Like assigning tasks to employees — delegate, go do something else, and come back when the work is done. No need to babysit.
Each Slack/Discord/Telegram/WeChat/Lark chat scope is an isolated workspace. Open 5 chats, run 5 parallel tasks. Context stays separate.
Laptop closed. Commute started. Production still needs you.
Vibe Remote lets you reopen real agent sessions from your current working directory across Claude Code, OpenCode, and Codex. Pick the latest session, jump from desktop to mobile, and keep going without re-explaining the task, hunting for an old thread, or losing the thread of thought.
When your agent needs input — file selection, confirmation, options — your chat app pops up buttons or a modal. Full CLI interactivity, zero terminal required.
Ask your agent to schedule work for later, repeat a prompt on a cron, or queue a one-shot async follow-up after a long-running job.
- Persist recurring or one-off prompts with
vibe task - Queue a single async send with
vibe hook send - Keep session context and delivery target separate when needed
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ You │ Slack │ │ stdio │ Claude Code │
│ (anywhere) │ Discord │ Vibe Remote │ ──────────▶ │ OpenCode │
│ │ Telegram │ (your Mac) │ ◀────────── │ Codex │
│ │ WeChat │ │ │ │
│ │ Lark │ │ │ │
└──────────────┘ └──────────────┘ └──────────────┘
- You type in Slack/Discord/Telegram/WeChat/Lark: "Add dark mode to the settings page"
- Vibe Remote routes to your configured agent
- Agent reads your codebase, writes code, streams back
- You review in your chat app, iterate in thread
Your code never leaves your machine. Vibe Remote runs locally and connects via Slack Socket Mode, Discord Gateway, Telegram Bot API long polling, WeChat polling, or Lark WebSocket.
| In chat | What it does |
|---|---|
@Vibe Remote /start |
Open control panel |
/stop |
Kill current session |
| Just type | Talk to your agent |
| Reply in thread | Continue conversation |
Pro tip: Each thread = isolated session. Start multiple threads for parallel tasks.
Detailed references:
Need a different agent mid-conversation? Just prefix your message:
Plan: Design a new caching layer for the API
That's it. No menus, no commands. Type AgentName: and your message routes to that agent instantly.
Different projects, different agents:
#frontend → OpenCode (fast iteration)
#backend → Claude Code (complex logic)
#prototypes → Codex (quick experiments)
Configure in web UI → Channels.
vibe # Start everything
vibe status # Check if running
vibe stop # Stop everything
vibe doctor # Diagnose issues
vibe task # Create and manage scheduled tasks
vibe hook # Queue one-shot async sendsDetailed references:
You need at least one coding agent installed:
OpenCode (Recommended)
curl -fsSL https://opencode.ai/install | bashRequired: Add to ~/.config/opencode/opencode.json to skip permission prompts:
{
"permission": "allow"
}Claude Code
npm install -g @anthropic-ai/claude-codeCodex
npm install -g @openai/codex- Local-first — Vibe Remote runs on your machine
- Socket Mode / WebSocket — No public URLs, no webhooks
- Your tokens — Stored in
~/.vibe_remote/, never uploaded - Your code — Stays on your disk, sent only to your chosen AI provider
vibe stop && uv tool uninstall vibe-remote && rm -rf ~/.vibe_remote- Slack support
- Discord support
- Telegram support
- WeChat support
- Lark (Feishu) support
- Web UI setup wizard & dashboard
- Per-channel agent routing
- Interactive prompts (buttons, modals)
- File attachments
- SaaS Mode
- Vibe Remote Coding Agent (one agent to rule them all)
- Skills Manager
- Best practices & multi-workspace guide
- CLI Reference — Command-line usage and service lifecycle
- Slack Setup Guide — Detailed setup with screenshots
- Discord Setup Guide — Detailed setup with screenshots
- Telegram Setup Guide — BotFather setup, token validation, and chat discovery
- WeChat Setup Guide — Follow the in-app wizard (
vibe→ choose WeChat) - Lark Setup Guide — Follow the in-app wizard (
vibe→ choose Lark)
If you run Vibe Remote on a remote server, keep the Web UI bound to 127.0.0.1:5123 and access it via SSH port forwarding:
ssh -NL 5123:localhost:5123 user@server-ipSee: CLI Reference (search for "Remote Web UI Access")
Stop context-switching. Start vibe coding.
Install Now · Setup Guide · Report Bug · Follow @alex_metacraft
Built for developers who code from anywhere.





