VibeAround Session Handover

Hands over the current coding session via the VibeAround orchestrator. The user picks it up from any IM channel connected to VibeAround — the pickup is not tied to a specific channel.

When to Use

• User says /vibearound handover
• User asks to "hand over", "transfer", or "continue" the session on their phone or another device

Prerequisites

The VibeAround MCP server must be connected (server name: vibearound). If not available, tell the user to start the VibeAround desktop app.

Handover Steps

1. Resolve the session ID

Use the /va-session skill to get the current session ID. Also read $VIBEAROUND_PROFILE_ID from the environment if present. VibeAround-launched sessions should have it, including direct; external user-started sessions may omit it.

2. Call va_mcp_prepare_handover

Tool: va_mcp_prepare_handover
Server: vibearound
Arguments:
  session_id: "<session_id from step 1>"  (pass if available)
  cwd: "<current working directory>"
  agent_kind: "<your agent type>"
  profile_id: "<VIBEAROUND_PROFILE_ID if present>"  (optional; omitted means direct)

If the workspace is not registered, ask the user for confirmation, then call va_mcp_register_workspace with the cwd, and retry.

3. Copy to clipboard and present the result

The tool returns a /pickup command string. Copy it to the user's clipboard (use whatever clipboard mechanism is available — a platform MCP tool, pbcopy on macOS, xclip/wl-copy on Linux), then also display it so the user can copy it manually. The user pastes it in any IM chat connected to VibeAround to resume the session there with the same agent context.

Error Handling

• MCP server not available: Start the VibeAround desktop app.
• Workspace not registered: Offer to register it (needs user confirmation).
• Session ID not found: The server can auto-discover in most cases. If that fails, tell the user.