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, or Lark. 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?
irm https://raw.githubusercontent.com/cyhhao/vibe-remote/master/install.ps1 | iex| Problem | Solution |
|---|---|
| Claude Code is amazing but needs a terminal | Slack/Discord/Lark IS your terminal now |
| Context-switching kills flow | Stay in one app |
| 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
|
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/Lark thread is an isolated workspace. Open 5 threads, run 5 parallel tasks. Context stays separate.
When your agent needs input — file selection, confirmation, options — your chat app pops up buttons or a modal. Full CLI interactivity, zero terminal required.
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ You │ Slack │ │ stdio │ Claude Code │
│ (anywhere) │ Discord │ Vibe Remote │ ──────────▶ │ OpenCode │
│ │ Lark │ (your Mac) │ ◀────────── │ Codex │
└──────────────┘ └──────────────┘ └──────────────┘
- You type in Slack/Discord/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, 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.
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 issuesYou 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
- 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
- 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.





