VibeAround Agent Collaboration

Initialize a VibeAround multi-agent turn from the current host agent, then wait for subagent reports before finalizing.

When to Use

• The user message starts with subagent=
• The first supported mode is subagent=parallel

Protocol

All host-to-subagent and subagent-to-host control messages must use va-agent-protocol.

VibeAround intercepts protocol envelopes in the thread. The raw envelope is hidden from the web UI and forwarded internally to the target agent. The protocol envelope must be the final content in the assistant message; do not write prose after it.

Use this envelope for structured messages:

<va-agent-protocol>
{
  "protocol": "va-agent-protocol",
  "kind": "assignment",
  "turn_id": "<multi_agent_turn_id>",
  "to_agent_id": "<subagent_guid>",
  "task": "<clear task for this subagent>",
  "context": "<only the relevant context>"
}
</va-agent-protocol>

Subagents must report back with:

<va-agent-protocol>
{
  "protocol": "va-agent-protocol",
  "kind": "report",
  "turn_id": "<multi_agent_turn_id>",
  "from_agent_id": "<subagent_guid>",
  "status": "completed",
  "summary": "<what changed or what was found>",
  "files_changed": [],
  "tests": [],
  "notes": []
}
</va-agent-protocol>

Initialize Parallel Subagents

Call the VibeAround MCP tool:

Tool: initialize_subagents
Server: vibearound
Arguments:
  thread_id: "<value of $VIBEAROUND_THREAD_ID>"
  cwd: "<current working directory>"
  mode: "parallel"
  agents:
    - name: "<host-chosen display name, e.g. John Planner>"
      agent_kind: "codex"
      task: "<parallel task>"
    - name: "<host-chosen display name, e.g. Maya Reviewer>"
      agent_kind: "codex"
      task: "<parallel task>"

Then wait for the turn to finish:

Tool: wait_for_subagents
Server: vibearound
Arguments:
  thread_id: "<value of $VIBEAROUND_THREAD_ID>"
  turn_id: "<turn id returned by initialize_subagents>"

Rules:

• Choose concise human names for subagents. Names are display aliases; the MCP tool returns GUID agent IDs.
• For parallel, default to exactly 2 subagents.
• Use codex for subagents by default, even when the host is Claude Code.
• Only create more than 2 subagents or use another agent_kind when the user explicitly asks.
• For parallel, split the user's request into independent tasks that can run in separate git worktrees.
• VibeAround handles missing Git repositories by running git init and creating an empty initial commit when needed. If Git itself is missing, VibeAround attempts a platform install before reporting an error.
• Do not merge or clean up worktrees automatically. The host agent decides after reviewing results.
• If VibeAround reports a dirty workspace or worktree creation error, tell the user and stop the multi-agent turn.
• VibeAround injects subagent role/system guidance at session startup. Keep assignments focused on the task and relevant context.

After initialize_subagents returns, do not produce a final answer yet. Call wait_for_subagents, review the returned reports and any visible subagent messages, then synthesize the host answer.

Continue Delegating

After initialize_subagents returns, the host can continue delegating to an existing subagent by emitting an assignment envelope in the host response. VibeAround intercepts the envelope and sends it to the target subagent:

<va-agent-protocol>
{
  "protocol": "va-agent-protocol",
  "kind": "assignment",
  "turn_id": "<multi_agent_turn_id>",
  "to_agent_id": "<subagent_guid>",
  "task": "<follow-up task>",
  "context": "<only what changed since the previous assignment>"
}
</va-agent-protocol>

Rules:

• Use exactly the turn_id and to_agent_id returned by initialize_subagents.
• Include a non-empty task.
• Put the envelope at the end of the assistant message. Do not write anything after the closing </va-agent-protocol> tag.
• Do not use MCP for follow-up delegation. The protocol envelope is the control path.

VibeAround Markdown Preview

After you create or update a markdown document, generate a styled preview so the user can read it in their browser or phone with beautiful formatting.

When to Use

• You just created or updated a README.md, documentation, or any .md file
• The user asks to "show me the doc", "preview the README", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After creating or updating any markdown file, proactively ask the user if they'd like to preview it (e.g. "Want me to generate a preview link so you can see it?"). If the user confirms, call md_preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Call md_preview

Tool: md_preview
Server: vibearound
Arguments:
  file: "<path to the markdown file>"  (absolute or relative to cwd)
  cwd: "<current working directory>"
  title: "<document title>"  (optional, defaults to filename)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

2. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Markdown preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Markdown preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent. The share link is temporary and needs no auth.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• File not found: Verify the file path is correct and the file exists.

VibeAround Live Preview

After you finish building a web application, HTML page, or any browsable artifact, start a live preview so the user can see the result immediately via a shareable URL.

When to Use

• You just started a dev server (next dev, vite, python -m http.server, etc.)
• You created HTML/CSS/JS files the user should see
• The user asked to "show me", "preview", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After starting a dev server or creating a web artifact, proactively ask the user if they'd like a preview link (e.g. "Want me to generate a preview link so you can see it on your phone?"). If the user confirms, call preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Start the server (if not already running)

Before calling preview, make sure:

• The port you want is free: lsof -i :<port> should return nothing
• The server is actually listening (wait for "Listening on..." or similar in the output)
• Use --host 0.0.0.0 when available for broader compatibility

2. Get your session ID

Use the /va-session skill to resolve your current session ID.

3. Call preview

Tool: preview
Server: vibearound
Arguments:
  port: <the port your server is running on>
  cwd: "<current working directory>"
  session_id: "<session_id from step 2>"  (pass if available)
  title: "<short description of what you built>"  (optional)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

4. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent (requires browser pairing). The share link is temporary and needs no auth — ideal for sending to others.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• Port in use: Check with lsof -i :<port> and choose a different port.

VibeAround Session ID

Resolve your current session ID. Other VibeAround skills reference this skill when they need session context for lifecycle management.

How to Resolve

Read these values if available:

• Current working directory
• $VIBEAROUND_LAUNCH_ID
• $VIBEAROUND_PROFILE_ID
• $VIBEAROUND_CHANNEL_KIND
• $VIBEAROUND_CHAT_ID

For Claude Code and Claude Desktop, use this rendered value as the current session ID:

${CLAUDE_SESSION_ID}

Call the get_session_id MCP tool. Include only optional arguments whose values are present. If the rendered Claude value is empty or is still the literal placeholder text, omit session_id.

Tool: get_session_id
Server: vibearound
Arguments:
  agent_kind: "claude"
  session_id: "<rendered ${CLAUDE_SESSION_ID} if valid>"
  cwd: "<current working directory>"
  launch_id: "<value of $VIBEAROUND_LAUNCH_ID if present>"
  profile_id: "<value of $VIBEAROUND_PROFILE_ID if present>"
  channel_kind: "<value of $VIBEAROUND_CHANNEL_KIND if present>"
  chat_id: "<value of $VIBEAROUND_CHAT_ID if present>"

Return Value

Return the session ID string from the MCP tool. If the tool cannot resolve one, return nothing — callers handle the missing case gracefully.

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. Get your session ID

Use the /va-session skill to resolve your 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 prepare_handover

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

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

3. Copy to clipboard and present the result

Copy the /pickup command to the user's clipboard, then show it. 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).
• Session ID not found: The server can auto-discover in most cases. If that fails, tell the user.

VibeAround Agent Collaboration

Initialize a VibeAround multi-agent turn from the current host agent, then wait for subagent reports before finalizing.

When to Use

• The user message starts with subagent=
• The first supported mode is subagent=parallel

Protocol

All host-to-subagent and subagent-to-host control messages must use va-agent-protocol.

VibeAround intercepts protocol envelopes in the thread. The raw envelope is hidden from the web UI and forwarded internally to the target agent. The protocol envelope must be the final content in the assistant message; do not write prose after it.

Use this envelope for structured messages:

<va-agent-protocol>
{
  "protocol": "va-agent-protocol",
  "kind": "assignment",
  "turn_id": "<multi_agent_turn_id>",
  "to_agent_id": "<subagent_guid>",
  "task": "<clear task for this subagent>",
  "context": "<only the relevant context>"
}
</va-agent-protocol>

Subagents must report back with:

<va-agent-protocol>
{
  "protocol": "va-agent-protocol",
  "kind": "report",
  "turn_id": "<multi_agent_turn_id>",
  "from_agent_id": "<subagent_guid>",
  "status": "completed",
  "summary": "<what changed or what was found>",
  "files_changed": [],
  "tests": [],
  "notes": []
}
</va-agent-protocol>

Initialize Parallel Subagents

Call the VibeAround MCP tool:

Tool: initialize_subagents
Server: vibearound
Arguments:
  thread_id: "<value of $VIBEAROUND_THREAD_ID>"
  cwd: "<current working directory>"
  mode: "parallel"
  agents:
    - name: "<host-chosen display name, e.g. John Planner>"
      agent_kind: "codex"
      task: "<parallel task>"
    - name: "<host-chosen display name, e.g. Maya Reviewer>"
      agent_kind: "codex"
      task: "<parallel task>"

Then wait for the turn to finish:

Tool: wait_for_subagents
Server: vibearound
Arguments:
  thread_id: "<value of $VIBEAROUND_THREAD_ID>"
  turn_id: "<turn id returned by initialize_subagents>"

Rules:

• Choose concise human names for subagents. Names are display aliases; the MCP tool returns GUID agent IDs.
• For parallel, default to exactly 2 subagents.
• Use codex for subagents by default.
• Only create more than 2 subagents or use another agent_kind when the user explicitly asks.
• For parallel, split the user's request into independent tasks that can run in separate git worktrees.
• VibeAround handles missing Git repositories by running git init and creating an empty initial commit when needed. If Git itself is missing, VibeAround attempts a platform install before reporting an error.
• Do not merge or clean up worktrees automatically. The host agent decides after reviewing results.
• If VibeAround reports a dirty workspace or worktree creation error, tell the user and stop the multi-agent turn.
• VibeAround injects subagent role/system guidance at session startup. Keep assignments focused on the task and relevant context.

After initialize_subagents returns, do not produce a final answer yet. Call wait_for_subagents, review the returned reports and any visible subagent messages, then synthesize the host answer.

Continue Delegating

After initialize_subagents returns, the host can continue delegating to an existing subagent by emitting an assignment envelope in the host response. VibeAround intercepts the envelope and sends it to the target subagent:

<va-agent-protocol>
{
  "protocol": "va-agent-protocol",
  "kind": "assignment",
  "turn_id": "<multi_agent_turn_id>",
  "to_agent_id": "<subagent_guid>",
  "task": "<follow-up task>",
  "context": "<only what changed since the previous assignment>"
}
</va-agent-protocol>

Rules:

• Use exactly the turn_id and to_agent_id returned by initialize_subagents.
• Include a non-empty task.
• Put the envelope at the end of the assistant message. Do not write anything after the closing </va-agent-protocol> tag.
• Do not use MCP for follow-up delegation. The protocol envelope is the control path.

VibeAround Markdown Preview

After you create or update a markdown document, generate a styled preview so the user can read it in their browser or phone with beautiful formatting.

When to Use

• You just created or updated a README.md, documentation, or any .md file
• The user asks to "show me the doc", "preview the README", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After creating or updating any markdown file, proactively ask the user if they'd like to preview it (e.g. "Want me to generate a preview link so you can see it?"). If the user confirms, call md_preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Call md_preview

Tool: md_preview
Server: vibearound
Arguments:
  file: "<path to the markdown file>"  (absolute or relative to cwd)
  cwd: "<current working directory>"
  title: "<document title>"  (optional, defaults to filename)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

2. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Markdown preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Markdown preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent. The share link is temporary and needs no auth.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• File not found: Verify the file path is correct and the file exists.

VibeAround Live Preview

After you finish building a web application, HTML page, or any browsable artifact, start a live preview so the user can see the result immediately via a shareable URL.

When to Use

• You just started a dev server (next dev, vite, python -m http.server, etc.)
• You created HTML/CSS/JS files the user should see
• The user asked to "show me", "preview", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After starting a dev server or creating a web artifact, proactively ask the user if they'd like a preview link (e.g. "Want me to generate a preview link so you can see it on your phone?"). If the user confirms, call preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Start the server (if not already running)

Before calling preview, make sure:

• The port you want is free: lsof -i :<port> should return nothing
• The server is actually listening (wait for "Listening on..." or similar in the output)
• Use --host 0.0.0.0 when available for broader compatibility

2. Get your session ID

Use the va-session skill to resolve your current session ID.

3. Call preview

Tool: preview
Server: vibearound
Arguments:
  port: <the port your server is running on>
  cwd: "<current working directory>"
  session_id: "<session_id from step 2>"  (pass if available)
  title: "<short description of what you built>"  (optional)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

4. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent (requires browser pairing). The share link is temporary and needs no auth — ideal for sending to others.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• Port in use: Check with lsof -i :<port> and choose a different port.

VibeAround Session ID

Resolve the current Codex session ID. Other VibeAround Codex skills reference this skill when they need session context for lifecycle management.

How to Resolve

Read these values if available:

• Current working directory
• $VIBEAROUND_LAUNCH_ID
• $VIBEAROUND_PROFILE_ID
• $VIBEAROUND_CHANNEL_KIND
• $VIBEAROUND_CHAT_ID

Method 1: Via Codex MCP metadata (preferred)

Call the get_session_id MCP tool with agent_kind set to codex. Include only optional arguments whose values are present:

Do not inspect MCP resources or resource templates for this step. VibeAround exposes get_session_id as a tool; Codex's /mcp command can be used only for human diagnostics.

Tool: get_session_id
Server: vibearound
Arguments:
  agent_kind: "codex"
  cwd: "<current working directory>"
  launch_id: "<value of $VIBEAROUND_LAUNCH_ID if present>"
  profile_id: "<value of $VIBEAROUND_PROFILE_ID if present>"
  channel_kind: "<value of $VIBEAROUND_CHANNEL_KIND if present>"
  chat_id: "<value of $VIBEAROUND_CHAT_ID if present>"

VibeAround reads Codex's MCP call metadata and returns the current Codex thread/session ID and records it against the launch context when launch_id is available.

Return Value

Return the session ID string to the calling skill. If neither method succeeds, return nothing — callers handle the missing case gracefully.

VibeAround Session Handover

Hand over the current Codex 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. Get your session ID

Use the va-session skill to resolve your 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 prepare_handover

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

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

3. Copy to clipboard and present the result

Copy the /pickup command to the user's clipboard, then show it. 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).
• Session ID not found: The server can auto-discover in most cases. If that fails, tell the user.

VibeAround Markdown Preview

After you create or update a markdown document, generate a styled preview so the user can read it in their browser or phone with beautiful formatting.

When to Use

• You just created or updated a README.md, documentation, or any .md file
• The user asks to "show me the doc", "preview the README", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After creating or updating any markdown file, proactively ask the user if they'd like to preview it (e.g. "Want me to generate a preview link so you can see it?"). If the user confirms, call md_preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Call md_preview

Tool: md_preview
Server: vibearound
Arguments:
  file: "<path to the markdown file>"  (absolute or relative to cwd)
  cwd: "<current working directory>"
  title: "<document title>"  (optional, defaults to filename)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

2. Present BOTH links

Always show both Owner and Share URLs. Never omit either link.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• File not found: Verify the file path is correct and the file exists.

VibeAround Live Preview

After you finish building a web application, HTML page, or any browsable artifact, start a live preview so the user can see the result immediately via a shareable URL.

When to Use

• You just started a dev server (next dev, vite, python -m http.server, etc.)
• You created HTML/CSS/JS files the user should see
• The user asked to "show me", "preview", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After starting a dev server or creating a web artifact, proactively ask the user if they'd like a preview link. Do NOT call the tool without asking first.

Steps

1. Start the server (if not already running)

Make sure the port is free and the server is listening.

2. Get your session ID

Use the /va-session skill to resolve your current session ID.

3. Call preview

Tool: preview
Server: vibearound
Arguments:
  port: <port>
  cwd: "<current working directory>"
  session_id: "<session_id from step 2>"  (pass if available)
  title: "<description>"  (optional)

4. Share both URLs

Always present both URLs (owner + share) to the user. Never omit either link.

VibeAround Live Preview

After you finish building a web application, HTML page, or any browsable artifact, start a live preview so the user can see the result immediately via a shareable URL.

When to Use

• You just started a dev server (next dev, vite, python -m http.server, etc.)
• You created HTML/CSS/JS files the user should see
• The user asked to "show me", "preview", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After starting a dev server or creating a web artifact, proactively ask the user if they'd like a preview link (e.g. "Want me to generate a preview link so you can see it on your phone?"). If the user confirms, call preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Start the server (if not already running)

Before calling preview, make sure:

• The port you want is free: lsof -i :<port> should return nothing
• The server is actually listening (wait for "Listening on..." or similar in the output)
• Use --host 0.0.0.0 when available for broader compatibility

2. Call preview

Tool: preview
Server: vibearound
Arguments:
  port: <the port your server is running on>
  cwd: "<current working directory>"
  title: "<short description of what you built>"  (optional)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

3. Share the URL

Include the returned URL in your reply. The user can tap it to see the live preview in their browser or phone. The link expires in 5 minutes.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• Port in use: Check with lsof -i :<port> and choose a different port.

VibeAround Session ID

How to Resolve

Call the get_session_id MCP tool. Include only optional arguments whose values are present:

Read these values if available:

• Current working directory
• $VIBEAROUND_LAUNCH_ID
• $VIBEAROUND_PROFILE_ID
• $VIBEAROUND_CHANNEL_KIND
• $VIBEAROUND_CHAT_ID

Tool: get_session_id
Server: vibearound
Arguments:
  agent_kind: "cursor"
  cwd: "<current working directory>"
  launch_id: "<value of $VIBEAROUND_LAUNCH_ID if present>"
  profile_id: "<value of $VIBEAROUND_PROFILE_ID if present>"
  channel_kind: "<value of $VIBEAROUND_CHANNEL_KIND if present>"
  chat_id: "<value of $VIBEAROUND_CHAT_ID if present>"

Return the session ID string from the MCP tool. If the tool cannot resolve one, return nothing — callers handle the missing case gracefully.

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. Get your session ID

Use the /va-session skill to resolve your 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 prepare_handover

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

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).

VibeAround Markdown Preview

After you create or update a markdown document, generate a styled preview so the user can read it in their browser or phone with beautiful formatting.

When to Use

• You just created or updated a README.md, documentation, or any .md file
• The user asks to "show me the doc", "preview the README", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After creating or updating any markdown file, proactively ask the user if they'd like to preview it (e.g. "Want me to generate a preview link so you can see it?"). If the user confirms, call md_preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Call md_preview

Tool: md_preview
Server: vibearound
Arguments:
  file: "<path to the markdown file>"  (absolute or relative to cwd)
  cwd: "<current working directory>"
  title: "<document title>"  (optional, defaults to filename)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

2. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Markdown preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Markdown preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent. The share link is temporary and needs no auth.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• File not found: Verify the file path is correct and the file exists.

VibeAround Live Preview

After you finish building a web application, HTML page, or any browsable artifact, start a live preview so the user can see the result immediately via a shareable URL.

When to Use

• You just started a dev server (next dev, vite, python -m http.server, etc.)
• You created HTML/CSS/JS files the user should see
• The user asked to "show me", "preview", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After starting a dev server or creating a web artifact, proactively ask the user if they'd like a preview link (e.g. "Want me to generate a preview link so you can see it on your phone?"). If the user confirms, call preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Start the server (if not already running)

Before calling preview, make sure:

• The port you want is free: lsof -i :<port> should return nothing
• The server is actually listening (wait for "Listening on..." or similar in the output)
• Use --host 0.0.0.0 when available for broader compatibility

2. Get your session ID

Use the /va-session skill to resolve your current session ID.

3. Call preview

Tool: preview
Server: vibearound
Arguments:
  port: <the port your server is running on>
  cwd: "<current working directory>"
  session_id: "<session_id from step 2>"  (pass if available)
  title: "<short description of what you built>"  (optional)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

4. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent (requires browser pairing). The share link is temporary and needs no auth — ideal for sending to others.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• Port in use: Check with lsof -i :<port> and choose a different port.

VibeAround Session ID

Resolve your current session ID. Other VibeAround skills reference this skill when they need session context for lifecycle management.

How to Resolve

Call the get_session_id MCP tool. Include only optional arguments whose values are present:

Read these values if available:

• Current working directory
• $VIBEAROUND_LAUNCH_ID
• $VIBEAROUND_PROFILE_ID
• $VIBEAROUND_CHANNEL_KIND
• $VIBEAROUND_CHAT_ID

Tool: get_session_id
Server: vibearound
Arguments:
  agent_kind: "gemini"
  cwd: "<current working directory>"
  launch_id: "<value of $VIBEAROUND_LAUNCH_ID if present>"
  profile_id: "<value of $VIBEAROUND_PROFILE_ID if present>"
  channel_kind: "<value of $VIBEAROUND_CHANNEL_KIND if present>"
  chat_id: "<value of $VIBEAROUND_CHAT_ID if present>"

The MCP tool resolves the session from VibeAround route state or workspace-aware auto-discovery, and records it against the launch context when launch_id is available.

Return Value

Return the session ID string to the calling skill. If neither method succeeds, return nothing — callers handle the missing case gracefully.

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. Get your session ID

Use the /va-session skill to resolve your current session ID. The server can also auto-discover Gemini sessions, so this is optional but recommended. 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 prepare_handover

Tool: prepare_handover
Server: vibearound
Arguments:
  session_id: "<session_id from step 1>"  (optional — server can auto-discover)
  cwd: "<current working directory>"
  agent_kind: "gemini"
  profile_id: "<VIBEAROUND_PROFILE_ID if present>"  (optional; omitted means direct)

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

3. Copy to clipboard and present the result

Copy the /pickup command to the user's clipboard, then show it. 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).
• Session ID not found: Provide the session_id explicitly. You can find it by checking recent sessions with /resume.

VibeAround Markdown Preview

After you create or update a markdown document, generate a styled preview so the user can read it in their browser or phone with beautiful formatting.

When to Use

• You just created or updated a README.md, documentation, or any .md file
• The user asks to "show me the doc", "preview the README", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After creating or updating any markdown file, proactively ask the user if they'd like to preview it (e.g. "Want me to generate a preview link so you can see it?"). If the user confirms, call md_preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Call md_preview

Tool: md_preview
Server: vibearound
Arguments:
  file: "<path to the markdown file>"  (absolute or relative to cwd)
  cwd: "<current working directory>"
  title: "<document title>"  (optional, defaults to filename)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

2. Present BOTH links

Always show both Owner and Share URLs. Never omit either link.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• File not found: Verify the file path is correct and the file exists.

VibeAround Live Preview

Start a live preview so the user can see your work via a shareable URL.

Steps

1. Start the server (if not already running)

2. Get your session ID

Use the /va-session skill to resolve your current session ID.

3. Call preview

Tool: preview
Server: vibearound
Arguments:
  port: <port>
  cwd: "<current working directory>"
  session_id: "<session_id from step 2>"  (pass if available)
  title: "<description>"  (optional)

4. Present BOTH links to the user

Always show both Owner and Share URLs. Never omit either link.

Format:

Preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

VibeAround Live Preview

After you finish building a web application, HTML page, or any browsable artifact, start a live preview so the user can see the result immediately via a shareable URL.

When to Use

• You just started a dev server (next dev, vite, python -m http.server, etc.)
• You created HTML/CSS/JS files the user should see
• The user asked to "show me", "preview", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After starting a dev server or creating a web artifact, proactively ask the user if they'd like a preview link (e.g. "Want me to generate a preview link so you can see it on your phone?"). If the user confirms, call preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Start the server (if not already running)

Before calling preview, make sure:

• The port you want is free: lsof -i :<port> should return nothing
• The server is actually listening (wait for "Listening on..." or similar in the output)
• Use --host 0.0.0.0 when available for broader compatibility

2. Call preview

Tool: preview
Server: vibearound
Arguments:
  port: <the port your server is running on>
  cwd: "<current working directory>"
  title: "<short description of what you built>"  (optional)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

3. Share the URL

Include the returned URL in your reply. The user can tap it to see the live preview in their browser or phone. The link expires in 5 minutes.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• Port in use: Check with lsof -i :<port> and choose a different port.

VibeAround Session ID

How to Resolve

Call the get_session_id MCP tool. Include only optional arguments whose values are present:

Read these values if available:

• Current working directory
• $VIBEAROUND_LAUNCH_ID
• $VIBEAROUND_PROFILE_ID
• $VIBEAROUND_CHANNEL_KIND
• $VIBEAROUND_CHAT_ID

Tool: get_session_id
Server: vibearound
Arguments:
  agent_kind: "kiro"
  cwd: "<current working directory>"
  launch_id: "<value of $VIBEAROUND_LAUNCH_ID if present>"
  profile_id: "<value of $VIBEAROUND_PROFILE_ID if present>"
  channel_kind: "<value of $VIBEAROUND_CHANNEL_KIND if present>"
  chat_id: "<value of $VIBEAROUND_CHAT_ID if present>"

Kiro does not currently have a VibeAround local session-file reader. The MCP tool can resolve route-managed sessions and records them against the launch context when launch_id is available.

Return the session ID string from the MCP tool. If the tool cannot resolve one, return nothing — callers handle the missing case gracefully.

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. Get your session ID

Use the /va-session skill to resolve your 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 prepare_handover

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

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).

VibeAround Markdown Preview

After you create or update a markdown document, generate a styled preview so the user can read it in their browser or phone with beautiful formatting.

When to Use

• You just created or updated a README.md, documentation, or any .md file
• The user asks to "show me the doc", "preview the README", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After creating or updating any markdown file, proactively ask the user if they'd like to preview it (e.g. "Want me to generate a preview link so you can see it?"). If the user confirms, call md_preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Call md_preview

Tool: md_preview
Server: vibearound
Arguments:
  file: "<path to the markdown file>"  (absolute or relative to cwd)
  cwd: "<current working directory>"
  title: "<document title>"  (optional, defaults to filename)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

2. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Markdown preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Markdown preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent. The share link is temporary and needs no auth.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• File not found: Verify the file path is correct and the file exists.

VibeAround Live Preview

After you finish building a web application, HTML page, or any browsable artifact, start a live preview so the user can see the result immediately via a shareable URL.

When to Use

• You just started a dev server (next dev, vite, python -m http.server, etc.)
• You created HTML/CSS/JS files the user should see
• The user asked to "show me", "preview", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After starting a dev server or creating a web artifact, proactively ask the user if they'd like a preview link (e.g. "Want me to generate a preview link so you can see it on your phone?"). If the user confirms, call preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Start the server (if not already running)

Before calling preview, make sure:

• The port you want is free: lsof -i :<port> should return nothing
• The server is actually listening (wait for "Listening on..." or similar in the output)
• Use --host 0.0.0.0 when available for broader compatibility

2. Get your session ID

Use the /va-session skill to resolve your current session ID.

3. Call preview

Tool: preview
Server: vibearound
Arguments:
  port: <the port your server is running on>
  cwd: "<current working directory>"
  session_id: "<session_id from step 2>"  (pass if available)
  title: "<short description of what you built>"  (optional)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

4. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent (requires browser pairing). The share link is temporary and needs no auth — ideal for sending to others.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• Port in use: Check with lsof -i :<port> and choose a different port.

VibeAround Session ID

Resolve your current session ID. Other VibeAround skills reference this skill when they need session context for lifecycle management.

How to Resolve

Call the get_session_id MCP tool. Include only optional arguments whose values are present:

Read these values if available:

• Current working directory
• $VIBEAROUND_LAUNCH_ID
• $VIBEAROUND_PROFILE_ID
• $VIBEAROUND_CHANNEL_KIND
• $VIBEAROUND_CHAT_ID

Tool: get_session_id
Server: vibearound
Arguments:
  agent_kind: "qwen-code"
  cwd: "<current working directory>"
  launch_id: "<value of $VIBEAROUND_LAUNCH_ID if present>"
  profile_id: "<value of $VIBEAROUND_PROFILE_ID if present>"
  channel_kind: "<value of $VIBEAROUND_CHANNEL_KIND if present>"
  chat_id: "<value of $VIBEAROUND_CHAT_ID if present>"

The MCP tool resolves the session from VibeAround route state or workspace-aware auto-discovery, and records it against the launch context when launch_id is available.

Return Value

Return the session ID string to the calling skill. If neither method succeeds, return nothing — callers handle the missing case gracefully.

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. Get your session ID

Use the /va-session skill to resolve your 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 prepare_handover

Tool: prepare_handover
Server: vibearound
Arguments:
  session_id: "<session_id from step 1>"  (pass if available)
  cwd: "<current working directory>"
  agent_kind: "qwen-code"
  profile_id: "<VIBEAROUND_PROFILE_ID if present>"  (optional; omitted means direct)

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

3. Copy to clipboard and present the result

Copy the /pickup command to the user's clipboard, then show it. 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).
• Session ID not found: The server can auto-discover in most cases. If that fails, tell the user.

VibeAround Markdown Preview

After you create or update a markdown document, generate a styled preview so the user can read it in their browser or phone with beautiful formatting.

When to Use

• You just created or updated a README.md, documentation, or any .md file
• The user asks to "show me the doc", "preview the README", or "let me see it"
• Only when the VibeAround MCP server is connected

Proactive behavior: After creating or updating any markdown file, proactively ask the user if they'd like to preview it (e.g. "Want me to generate a preview link so you can see it?"). If the user confirms, call md_preview. Do NOT call the tool without asking first.

Prerequisites

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

Steps

1. Call md_preview

Tool: md_preview
Server: vibearound
Arguments:
  file: "<path to the markdown file>"  (absolute or relative to cwd)
  cwd: "<current working directory>"
  title: "<document title>"  (optional, defaults to filename)

If the tool says the workspace is not registered, call register_workspace with the cwd first, then retry.

2. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Markdown preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Markdown preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent. The share link is temporary and needs no auth.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• File not found: Verify the file path is correct and the file exists.

VibeAround Live Preview

Exposes a local dev server or static files as a live preview via a shareable URL, so the user can view the result in their browser or on a mobile device.

When to Use

• After starting a dev server (next dev, vite, python -m http.server, etc.)
• After creating HTML/CSS/JS files the user should see
• The user asks to "show me", "preview", "let me see it on my phone", or "share a preview link"

Proactive behavior: After starting a dev server or creating a web artifact, ask the user if they'd like a preview link (e.g. "Want me to generate a preview link so you can see it on your phone?"). Only call preview after the user confirms.

Prerequisites

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

Steps

1. Ensure the server is listening

• Verify the port is free: lsof -i :<port> should return nothing before starting
• Wait for the server's "Listening on..." message before proceeding
• Use --host 0.0.0.0 when available for broader network compatibility

2. Resolve the session ID

Use the /va-session skill to get the current session ID.

3. Call preview

Tool: preview
Server: vibearound
Arguments:
  port: <the port your server is running on>
  cwd: "<current working directory>"
  session_id: "<session_id from step 2>"  (pass if available)
  title: "<short description of what you built>"  (optional)

If the workspace is not registered, call register_workspace with the cwd first, then retry.

4. Present BOTH links to the user

The tool returns an Owner link and a Share link. Always show both in this format:

Preview 已就绪：
- 你的预览: <owner_url>
- 分享链接: <share_url>（10 分钟有效）

Or in English:

Preview ready:
- Owner: <owner_url>
- Share: <share_url> (expires in 10 min)

Never omit either link. The owner link is permanent (requires browser pairing). The share link is temporary and needs no auth — ideal for sending to others or testing on mobile.

Error Handling

• MCP server not available: The VibeAround desktop app may not be running.
• Workspace not registered: Call register_workspace first, then retry.
• Port in use: Check with lsof -i :<port> and choose a different port.

VibeAround Session ID

Resolves the current session ID. Other VibeAround skills call this when they need session context for preview, handover, or lifecycle management.

How to Resolve

Call the get_session_id MCP tool. Include only optional arguments whose values are present:

Read these values if available:

• Current working directory
• $VIBEAROUND_AGENT_KIND or $VIBEAROUND_LAUNCH_TARGET
• $VIBEAROUND_LAUNCH_ID
• $VIBEAROUND_PROFILE_ID
• $VIBEAROUND_CHANNEL_KIND
• $VIBEAROUND_CHAT_ID

Tool: get_session_id
Server: vibearound
Arguments:
  agent_kind: "<value of $VIBEAROUND_AGENT_KIND or $VIBEAROUND_LAUNCH_TARGET if present>"
  cwd: "<current working directory>"
  launch_id: "<value of $VIBEAROUND_LAUNCH_ID if present>"
  profile_id: "<value of $VIBEAROUND_PROFILE_ID if present>"
  channel_kind: "<value of $VIBEAROUND_CHANNEL_KIND if present>"
  chat_id: "<value of $VIBEAROUND_CHAT_ID if present>"

The MCP tool resolves the session from explicit parameters, VibeAround route state, agent metadata, or workspace-aware auto-discovery, and records it against the launch context when launch_id is available.

Return Value

Return the session ID string to the calling skill. If neither method succeeds, return nothing — callers handle the missing case gracefully.

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 prepare_handover

Tool: 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 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.