by cyhhao
Your AI agent army, commanded from Slack/Discord/Telegram/Wechat/Lark. Stream Claude Code, OpenCode, or Codex in real-time — from anywhere.
# Add to your Claude Code skills
git clone https://github.com/cyhhao/vibe-remoteLast scanned: 5/19/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-19T07:47:00.000Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": false
}No comments yet. Be the first to share your thoughts!
No laptop. No IDE. Just vibes.
Supported Platforms
Supported Agents

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://avibe.bot/install.sh | bash && vibe
Open source — view the script on GitHub. The short URL is a 307 redirect to that file.
That's it. Browser opens -> Follow the wizard -> Done.
Need to open the Web UI from another device or a remote server? Run:
vibe remote
We recommend the WSL setup on Windows because it has the best compatibility.
If you are new to WSL, this guide explains:
Not an agent framework. Not a hosted coding VM. Vibe Remote is the local-first way to bring the AI agents already running on your machine into the chat apps where you already collaborate.
vibe remote opens your local Web UI through a secure avibe.bot tunnel.| Problem | Solution | |---------|----------| | Claude Code is amazing but lives in a terminal | Slack/Discord/Telegram/WeChat/Lark can become the collaboration surface | | 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:
Lives in your Slack, Discord, Telegram, Lark, or WeChat. Reads the room. Picks up where you left off. Asks the right question when it's not sure. Goes quiet when you're heads-down. Ships at 2am because that's when the vibe hits — then leaves a note about what it touched.
Vibe Remote is the wire. Vibey is the colleague on the other end.
Forgets nothing. Holds opinions. Says thanks when you fix its bugs.
| | 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 | No extra reasoning loop in the middleware. Tokens go to your chosen agent, not to a second assistant layer. | 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 is a local-first collaboration runtime for the AI agents you already trust: the agent stays itself, your data stays local, and the colleague experience comes from putting the agent into the same communication flow where human work already happens. Coding is the first strong workload, not the product boundary. 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