Quick tour
Fifteen minutes, three "aha" moments: chat with a local agent in the browser, do the same from an IM app, then move one conversation between surfaces. Prerequisite: VibeAround installed with at least one agent enabled...
Fifteen minutes, three "aha" moments: chat with a local agent in the browser, do the same from an IM app, then move one conversation between surfaces. Prerequisite: VibeAround installed with at least one agent enabled (Install and onboarding).
1. First chat in the browser (3 minutes)
Open the dashboard (desktop app tray → Dashboard, or the URL from va status). Go to Web Chat.
Type something real:
look at ~/dev/my-app and summarize what this project does
Watch what happens:
- An agent process spawns in a workspace — the first message creates the thread automatically, no setup.
- Output streams in as the agent reads files and works.
- If the agent wants to run a command beyond its defaults, a permission card appears; approve or deny inline.
Try /status in the chat to see what you are attached to: thread id, workspace, host agent, session.
2. Same agent, from your pocket (7 minutes)
Connect one IM channel — Telegram is the fastest first one:
- Create the bot on Telegram's side and grab its token — that part happens in Telegram, not VibeAround (what the plugin needs).
- Add the credential to VibeAround:
- Desktop app — open the channel screen, pick Telegram, paste the token. No files to edit.
- CLI / headless — add it under
channels.telegraminsettings.json, thenva channel sync. (Dedicated CLI commands for channel configuration are planned; editing the file is the current way.)
- Open a chat with your bot and say hello.
Your bot chat is now a full agent conversation:
/new start a fresh thread
fix the failing test in ~/dev/my-app and show me the diffPermission requests arrive as tappable buttons. This chat has its own thread — independent from your web chat, both can run simultaneously.
3. One conversation, two surfaces (5 minutes)
Continuity is the point, so move something:
Terminal → phone. Launch an agent CLI through VibeAround (desktop Launch, or va launch --profile <name>), work a bit, then ask the agent to run its handover tool (the vibearound skill exposes it as /vibearound handover). You get a short 4-character code, valid for two minutes. In your Telegram bot chat:
/pickup K7PQThe chat attaches to the terminal session — same context, same workspace, continue where you left off.
Watch from two places. Open Web Chat while an IM turn is running: threads fan output out to every attached surface, so you can watch the same turn stream in both.
Where to go next
| You want to… | Read |
|---|---|
| Understand what just happened (threads, routes, sessions) | Concepts |
| Use one provider subscription across agent CLIs | Model profiles guide |
| Reach the dashboard away from home | Tunnels and remote access |
| The full slash-command list | IM usage |
| Share a running dev server for 10 minutes | Web dashboard guide |
Source anchors: src/core/src/channels/prompt/handler.rs (commands), src/core/src/workspace/handover.rs (pickup), src/skills/vibearound/SKILL.md (handover skill).
Last verified: v0.7.11
Install and onboarding
Two ways to run VibeAround: the desktop app (recommended — GUI management plus the embedded server) or the npm CLI (headless server for terminal first setups and remote machines). Both produce the same daemon with the...
CLI quick start
Use the npm CLI when you want a headless VibeAround daemon, a terminal first setup, or a remote machine without the desktop app. The CLI runs the same server and uses the same /.vibearound/ data directory as the deskt...