vibe-remote 2.1.11

Local-first agent runtime for Slack - run AI coding agents from your chat

Vibe Remote

Your AI coding army, commanded from Slack.

No laptop. No IDE. Just vibes.

English | 中文

---

The Pitch

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. Type "Fix the auth bug in login.py". Watch Claude Code fix it in real-time. Approve. Sip margarita.

AI works. You live.

---

Install in 10 Seconds

curl -fsSL https://raw.githubusercontent.com/cyhhao/vibe-remote/master/install.sh | bash && vibe

That's it. Browser opens -> Follow the wizard -> Done.

Windows?

irm https://raw.githubusercontent.com/cyhhao/vibe-remote/master/install.ps1 | iex

---

Why This Exists

Problem	Solution
Claude Code is amazing but needs a terminal	Slack 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 Slack, any agent

Supported Agents:

• Claude Code — Deep reasoning, complex refactors
• OpenCode — Fast, extensible, community favorite
• Codex — OpenAI's coding model

---

Highlights

Setup Wizard One-command install, guided configuration. No manual token juggling.

Dashboard Real-time status, health monitoring, and quick controls.

Channel Routing Per-channel agent configuration. Different projects, different agents.

Instant Notifications

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.

Thread = Session

Each Slack thread is an isolated workspace. Open 5 threads, run 5 parallel tasks. Context stays separate.

Interactive Prompts

When your agent needs input — file selection, confirmation, options — Slack pops up buttons or a modal. Full CLI interactivity, zero terminal required.

---

How It Works

┌──────────────┐         ┌──────────────┐         ┌──────────────┐
│     You      │  Slack  │ Vibe Remote  │  stdio  │  AI Agent    │
│  (anywhere)  │ ──────▶ │  (your Mac)  │ ──────▶ │ (your code)  │
└──────────────┘         └──────────────┘         └──────────────┘

1. You type in Slack: "Add dark mode to the settings page"
2. Vibe Remote routes to your configured agent
3. Agent reads your codebase, writes code, streams back
4. You review in Slack, iterate in thread

Your code never leaves your machine. Vibe Remote runs locally and connects via Slack's Socket Mode.

---

Commands

In Slack	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 Slack thread = isolated session. Start multiple threads for parallel tasks.

---

Instant Agent Switching

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.

---

Per-Channel Routing

Different projects, different agents:

#frontend    → OpenCode (fast iteration)
#backend     → Claude Code (complex logic)  
#prototypes  → Codex (quick experiments)

Configure in web UI → Channels.

---

CLI

vibe          # Start everything
vibe status   # Check if running
vibe stop     # Stop everything
vibe doctor   # Diagnose issues

---

Prerequisites

You need at least one coding agent installed:

OpenCode (Recommended)

curl -fsSL https://opencode.ai/install | bash

Claude Code

npm install -g @anthropic-ai/claude-code

Codex

npm install -g @openai/codex

---

Security

• Local-first — Vibe Remote runs on your machine
• Socket Mode — 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

---

Uninstall

vibe stop && uv tool uninstall vibe-remote && rm -rf ~/.vibe_remote

---

Roadmap

• SaaS Mode
• Vibe Remote Coding Agent (one agent to rule them all)
• File attachments in Slack
• Multi-workspace

---

Docs

• CLI Reference — Command-line usage and service lifecycle
• Slack Setup Guide — Detailed setup with screenshots

Remote Server Tip (SSH)

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-ip

See: CLI Reference (search for "Remote Web UI Access")

---

Stop context-switching. Start vibe coding.

Install Now · Setup Guide · Report Bug

---

Built for developers who code from anywhere.