vibearound

Solid

Hand over the current coding session to VibeAround so the user can continue on their phone or another device

Code & Development 379 stars 44 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
86
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
73
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# VibeAround Session Handover Hand over the current coding session via the VibeAround orchestrator. The user can then pick it up from any connected IM channel (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. Call prepare_handover Call the `prepare_handover` tool on the `vibearound` MCP server. ``` Tool: prepare_handover Server: vibearound Arguments: cwd: "<current working directory>" agent_kind: "kiro" ``` If you know the current session ID, you can provide it explicitly: ``` Tool: prepare_handover Server: vibearound Arguments: session_id: "<sessionId>" cwd: "<current working directory>" agent_kind: "kiro" ``` If the tool says the workspace is not registered, ask the user for confirmation, then call `register_workspace` with the `cwd`, and retry. ### 2. Present the result Show the `/pickup` command returned by the tool. The user can paste it in any IM chat connected to VibeAround to resume the session there with the same agent. ## Error Handling - **MCP server not available**: Start the VibeAround desktop app. - **Workspace not registered**: Offer to register it (needs user confirmation).

Details

Author
jazzenchen
Repository
jazzenchen/VibeAround
Created
3 months ago
Last Updated
today
Language
Rust
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category