@quantiya/codevibe-claude-plugin 1.0.9 → 1.0.11

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "codevibe-claude",
-  "version": "1.0.9",
+  "version": "1.0.11",
   "description": "Sync Claude Code sessions with iOS mobile app via AWS backend. Control Claude Code from your phone with real-time bidirectional synchronization.",
   "author": {
     "name": "CodeVibe Team"

package/README.md

@@ -1,295 +1,133 @@
-# CodeVibe Claude Plugin
+# CodeVibe for Claude Code
 
-Control Claude Code from your phone with real-time bidirectional synchronization. This plugin enables seamless communication between your desktop Claude Code sessions and the CodeVibe mobile app.
+**Control Claude Code from your iPhone and Android.** See your agent's work, approve file edits, dictate prompts by voice — all from your phone, anywhere you are.
 
-## Features
+🌐 **[quantiya.ai/codevibe](https://quantiya.ai/codevibe)** — landing page, demo video, and one-liner installer
 
-- **Real-time Sync** - See desktop conversations on mobile instantly (~100-500ms latency)
-- **Mobile Control** - Send prompts from your phone that execute in the correct desktop session
-- **Locked Screen Support** - Works even when your Mac screen is locked (via tmux)
-- **Interactive Prompts** - Answer permission dialogs with numbered options (1=Yes, 2=Yes for project, 3=Reject)
-- **Voice Input** - Dictate prompts using iOS speech-to-text
-- **Image Attachments** - Send screenshots and photos with your messages
-- **Markdown Rendering** - Code blocks and formatting displayed beautifully
-- **Secure** - Uses AWS AppSync with Cognito authentication (Sign in with Apple/Google)
-- **Complete Capture** - Syncs user prompts, assistant responses, tool usage, and file changes
-- **Session-Aware** - Multiple Claude Code sessions work independently
-- **Auto-execution** - Mobile prompts execute immediately (same trust model as desktop)
+📱 **[Download on the App Store](https://apps.apple.com/app/id6756500217)** · **[Get it on Google Play](https://play.google.com/store/apps/details?id=ai.quantiya.app.codevibe)**
 
-## Prerequisites
-
-- **macOS** (darwin platform)
-- **Node.js** 18.0.0 or higher
-- **tmux** (for locked screen support): `brew install tmux`
-- **Claude Code** with plugin system enabled
-
-## Installation
-
-### Step 1: Install Wrapper Command (One-time)
-
-Install the CodeVibe wrapper command via npm:
-
-```bash
-npm install -g @quantiya/codevibe
-```
-
-This puts `codevibe-claude` (and `codevibe-gemini`, `codevibe-codex`) in your PATH.
-
-### Step 2: Register MCP Plugin (One-time)
-
-Claude Code also needs its MCP plugin registered. Inside a Claude Code session, run:
-
-```
-/plugin marketplace add https://github.com/hendryyeh/quantiya-codevibe-marketplace
-```
+---
 
-Then:
+## Why CodeVibe for Claude Code
 
-```
-/plugin install codevibe-claude
-```
+- **🚀 Real-time sync** — every prompt, response, and file change shows up on your phone in 100–500ms
+- **✅ Approve from anywhere** — review full file diffs and approve or reject Edit/Write operations from your phone, with the same numbered options Claude Code shows in the terminal
+- **🎙️ Voice prompts** — dictate your next prompt with speech-to-text, no keyboard required
+- **📷 Image attachments** — send screenshots and photos directly to the agent
+- **🔔 Push notifications** — get notified when your agent needs input so you never block on approvals
+- **🔒 End-to-end encrypted** — AES-256-GCM with ECDH key exchange; your prompts never pass through a server that can read them
+- **🔓 Locked screen support** — works even when your computer screen is locked (via tmux)
+- **🧠 Session-aware** — runs multiple concurrent Claude Code sessions independently
 
-### Step 3: Authenticate (One-time)
+## Install in 30 seconds
 
-Login to your CodeVibe account:
+The fastest path installs everything (Node, tmux, Claude Code, CodeVibe) in one command:
 
 ```bash
-codevibe-claude login
+curl -fsSL https://quantiya.ai/codevibe/install.sh | bash
 ```
 
-This opens a browser for OAuth authentication (Sign in with Apple or Google). Your tokens are stored securely in `~/.codevibe-claude/`.
-
-Other auth commands:
-```bash
-codevibe-claude status   # Check authentication status
-codevibe-claude logout   # Sign out and clear tokens
-```
-
-### Step 5: Start Claude Code with Mobile Support
-
-**Important:** You must use the `codevibe-claude` wrapper instead of `claude` directly:
+Then download the **[iOS app](https://apps.apple.com/app/id6756500217)** or **[Android app](https://play.google.com/store/apps/details?id=ai.quantiya.app.codevibe)**, sign in with the same Apple or Google account, and start a session:
 
 ```bash
 codevibe-claude
 ```
 
-This wrapper:
-- Creates a tmux session for the Claude Code instance
-- Enables mobile prompts to work even when your Mac screen is locked
-- Supports multiple concurrent Claude Code sessions
-
-**Note:** Running `claude` directly without the wrapper will prevent mobile prompts from working when your screen is locked.
-
-### Step 6: Download the iOS App
-
-Download "CodeVibe" from the App Store and sign in with the same account you used in Step 4.
-
-## Usage
+Your session appears on your phone automatically. That's it.
 
-### Using the `codevibe-claude` Wrapper
+### Manual install (if you already have Claude Code)
 
 ```bash
-# Start a new session (same as running `claude`)
+npm install -g @quantiya/codevibe
+claude plugin marketplace add https://github.com/hendryyeh/quantiya-codevibe-marketplace
+claude plugin install codevibe-claude@codevibe-marketplace
+codevibe login
 codevibe-claude
-
-# Resume the last session
-codevibe-claude --resume
-
-# Start with a prompt
-codevibe-claude -p "fix the bug"
-
-# All other claude arguments work too
-codevibe-claude --model sonnet
 ```
 
-### Benefits of `codevibe-claude`
-
-| Feature | `codevibe-claude` | Regular `claude` |
-|---------|-------------------|------------------|
-| Mobile prompts | Works always | Only when screen unlocked |
-| Screen locked support | Yes (via tmux) | No |
-| Mouse scrolling | Yes | Yes |
-| Same experience | Yes | Yes |
+## Requirements
 
-### Desktop to Mobile Sync
+- **macOS, Linux, or WSL Ubuntu** — Windows without WSL is not supported
+- **Node.js** 18.0.0+
+- **tmux** — `brew install tmux` on macOS, `apt install tmux` on Linux/WSL
+- **Claude Code** with the plugin system enabled
 
-Everything you do in Claude Code is automatically synced to mobile:
+## How it works
 
-- **User Prompts** - Your questions and commands
-- **Assistant Responses** - Claude's complete responses
-- **Tool Usage** - File edits, reads, writes
-- **Interactive Prompts** - Y/n permission requests
-- **Notifications** - System messages
-
-### Mobile to Desktop Control
-
-From the iOS app:
-
-1. Open the CodeVibe app
-2. Select your active session
-3. Type a message or response
-4. It executes immediately in your desktop Claude Code session
-5. See the response on both desktop and mobile
-
-### Responding to Permission Prompts from Mobile
-
-When Claude needs permission to edit or write files, you can respond directly from your phone.
-
-**Available Options:**
-
-| Reply | Description |
-|-------|-------------|
-| `1` | **Approve** - Allow this specific file operation |
-| `2` | **Always Allow** - Approve and skip future prompts for this project |
-| `3` | **Reject** - Decline the operation |
-| `3 <message>` | **Reject with Instructions** - Decline and tell Claude what to do instead |
-
-**Examples:**
 ```
-1                          -> Approves the edit
-2                          -> Approves and trusts this project
-3                          -> Rejects the edit
-3 use a different approach -> Rejects and redirects Claude
+┌─────────────┐    ┌──────────────┐    ┌─────────────┐
+│ Claude Code │ →→ │  CodeVibe    │ →→ │ Your phone  │
+│  on desktop │    │  E2E encrypt │    │  (iOS/Android)│
+└─────────────┘    └──────────────┘    └─────────────┘
+        ↑                                       │
+        └────────── mobile prompts ←────────────┘
 ```
 
-**Other Inputs:**
-- `Y` / `N` - For yes/no confirmation prompts
-- `exit`, `quit` - To cancel running operations
-- Any other text - Sent as a new prompt to Claude
+Every prompt, response, tool call, and file edit in Claude Code gets encrypted and relayed to your phone in real time via AWS AppSync. Messages from your phone execute immediately in the correct desktop session via tmux — no polling, no manual refresh.
 
-## Troubleshooting
+## Responding to permission prompts from your phone
 
-### "codevibe-claude: command not found"
+When Claude asks for permission to edit a file, you see the **same numbered options on your phone** as in the terminal. Reply by typing or voice-inputting the option number:
 
-**Cause:** PATH not updated or shell not reloaded.
+| Reply | What it does |
+|---|---|
+| `1` | Approve this specific file operation |
+| `2` | Always allow for this project |
+| `3` | Reject the operation |
+| `3 use a different approach` | Reject and redirect Claude with new instructions |
 
-**Solution:**
-```bash
-source ~/.zshrc  # or ~/.bashrc
-```
-
-Or check if PATH was added:
-```bash
-grep "codevibe-claude" ~/.zshrc
-```
-
-### "Not authenticated" error
-
-**Cause:** User hasn't logged in or tokens expired.
-
-**Solution:**
-```bash
-codevibe-claude login
-```
-
-### Mobile messages not executing
-
-**Cause:** Not using the codevibe-claude wrapper.
-
-**Solution:** Start Claude Code with:
-```bash
-codevibe-claude
-```
-Not just `claude`.
-
-### Plugin hooks not firing
-
-**Cause:** Plugin not properly installed.
-
-**Solution:**
-```
-# In Claude Code
-/plugin list              # Check if installed
-/plugin uninstall codevibe-claude
-/plugin install codevibe-claude
-```
+You can also reply with any text to send a new prompt.
 
-### Port already in use
+## Benefits of the `codevibe-claude` wrapper
 
-**Error:** `EADDRINUSE: address already in use :::3456`
+| | `codevibe-claude` | plain `claude` |
+|---|---|---|
+| Mobile prompts | ✅ Always | ⚠️ Only when screen unlocked |
+| Screen-locked support | ✅ Yes (via tmux) | ❌ No |
+| Multiple concurrent sessions | ✅ Yes | ❌ No |
 
-**Solution:** Another MCP server is already running. Kill it:
+Use `codevibe-claude` anywhere you'd use `claude` — all the same flags (`--resume`, `-p`, `--model`, etc.) work identically.
 
-```bash
-pkill -f "node dist/server.js"
-```
-
-## Mac Power Settings (for Locked Screen Support)
-
-To ensure mobile prompts work when your Mac screen is locked:
-
-1. **System Settings** -> **Battery** (or **Energy**) -> Set "Computer sleep" to **Never** (when on power)
-2. In Terminal:
-   ```bash
-   sudo pmset -a tcpkeepalive 1
-   sudo pmset -a womp 1
-   ```
-
-This keeps network connections alive during sleep.
-
-## Architecture
-
-```
-Desktop -> Mobile:
-+-------------+    +----------+    +---------+    +----------+    +--------+
-| Claude Code | -> |   Hook   | -> |   MCP   | -> | AppSync  | -> | Mobile |
-|             |    | Scripts  |    | Server  |    | GraphQL  |    |  App   |
-+-------------+    +----------+    +---------+    +----------+    +--------+
-
-Mobile -> Desktop:
-+--------+    +----------+    +---------+    +-------------+
-| Mobile | -> | AppSync  | -> |   MCP   | -> | Claude Code |
-|  App   |    | GraphQL  |    | Server  |    | (tmux keys) |
-+--------+    +----------+    +---------+    +-------------+
-```
+## Power settings for reliable locked-screen mode
 
-## Development
-
-If you want to contribute or run from source:
-
-### Clone and Build
+For mobile prompts to keep working when your screen is locked, keep your computer awake on AC power:
 
+**macOS:**
 ```bash
-git clone https://github.com/hendryyeh/quantiya-codevibe-claude-plugin.git
-cd quantiya-codevibe-claude-plugin
-npm install
-npm run build
+sudo pmset -a tcpkeepalive 1
+sudo pmset -a womp 1
 ```
+Then set **System Settings → Battery → Computer sleep: Never** (when on power).
 
-### Local Testing
-
-For local development and testing:
+**Linux / WSL Ubuntu:** disable sleep in your desktop environment's power settings, or use `systemd-inhibit --what=sleep:idle sleep infinity &`. On WSL, configure Windows power settings on the host.
 
-```bash
-./install-local.sh
+## Troubleshooting
 
-# In Claude Code
-/plugin marketplace add ./dev-marketplace
-/plugin install codevibe-claude@codevibe-claude-dev
-```
+- **"command not found: codevibe-claude"** — reload your shell: `source ~/.zshrc` (or `~/.bashrc`)
+- **"not authenticated"** — run `codevibe login`
+- **Mobile messages not executing** — make sure you launched via `codevibe-claude`, not plain `claude`
+- **Plugin hooks not firing** — `codevibe update`, then start a fresh session
 
-### View Logs
+### View logs
 
 ```bash
-# MCP Server logs
 tail -f /tmp/codevibe-claude-mcp.log
-
-# Hook scripts logs
 tail -f /tmp/codevibe-claude-hooks.log
 ```
 
 ## Support
 
-- **Issues:** [GitHub Issues](https://github.com/hendryyeh/quantiya-codevibe-claude-plugin/issues)
+- **Email:** support@quantiya.ai
+- **Landing page:** [quantiya.ai/codevibe](https://quantiya.ai/codevibe)
+- **Privacy policy:** [quantiya.ai/privacy](https://quantiya.ai/privacy)
 
-## Related
+## Part of the CodeVibe family
 
-- **CodeVibe iOS App** - Available on the App Store
+- **[@quantiya/codevibe](https://www.npmjs.com/package/@quantiya/codevibe)** — meta-package with the `codevibe` CLI (install this, not this plugin directly)
+- **[@quantiya/codevibe-core](https://www.npmjs.com/package/@quantiya/codevibe-core)** — shared library used by all plugins
+- **[@quantiya/codevibe-gemini-plugin](https://www.npmjs.com/package/@quantiya/codevibe-gemini-plugin)** — Gemini CLI support
+- **[@quantiya/codevibe-codex-plugin](https://www.npmjs.com/package/@quantiya/codevibe-codex-plugin)** — OpenAI Codex CLI support
 
 ## License
 
-MIT License - see [LICENSE](LICENSE) file for details.
-
----
-
-**Made with care by the CodeVibe Team**
+MIT

package/hooks/session-start.sh

@@ -35,6 +35,192 @@ else
   MAPPING_FILE=""
 fi
 
+# ─── Orphan daemon sweep ───────────────────────────────────────────────────
+#
+# When Claude Code terminates abnormally (crash, force-kill, window closed
+# without /exit, network drop), the SessionEnd hook doesn't fire and the
+# background daemon is never sent SIGTERM. Because the daemon is a PPID=1
+# process (detached from the hook that launched it), nothing in the OS
+# cleans it up — it keeps holding its AppSync subscription, sending
+# heartbeats, and showing the session as "desktop connected" on iOS forever.
+#
+# This sweep runs on every SessionStart and cleans up orphan daemons whose
+# tmux session no longer exists. Daemons belonging to live tmux sessions
+# (including our own) are left alone.
+#
+# Scope: the sweep only considers daemons that have an instance mapping file
+# (i.e. were launched under a tmux session). Daemons launched without tmux
+# have no mapping and cannot be safely identified as orphans, so we leave
+# them alone.
+#
+# Safety guards:
+#
+# (A) PID reuse: before killing a PID, verify via `ps -o command=` that the
+#     process is actually a node + codevibe-claude + server.js invocation.
+#     PIDs are recyclable (macOS cycles through ~32K), so a stale mapping
+#     from weeks ago could end up pointing at an unrelated user process.
+#     Without identity verification, we'd kill random things.
+#
+# (B) tmux unavailable: if the `tmux` binary is missing or fails for a reason
+#     other than "session doesn't exist", we conservatively treat the session
+#     as alive and leave the daemon alone. This prevents a degraded-tmux
+#     environment from causing a sweep-induced mass kill.
+
+# Check whether a PID is still identifiable as a codevibe-claude daemon.
+# Returns 0 if yes, non-zero otherwise.
+is_codevibe_daemon() {
+  local pid="$1"
+  local cmd
+  cmd=$(ps -o command= -p "$pid" 2>/dev/null)
+  # Pattern: "node" + "codevibe-claude" + "server.js" somewhere in the command line.
+  # Matches both the cache path (...codevibe-marketplace/codevibe-claude/X.Y.Z/dist/server.js)
+  # and the dev path (...codevibe-claude-plugin/dist/server.js).
+  case "$cmd" in
+    *node*codevibe-claude*server.js*) return 0 ;;
+    *) return 1 ;;
+  esac
+}
+
+# Return 0 if the tmux session is alive OR we can't tell.
+# Return non-zero ONLY when we can prove the session is gone: tmux binary exists,
+# tmux server is reachable, and the server says this specific session doesn't exist.
+# Every other failure mode (no binary, server down, socket error, permission issue)
+# returns 0 — conservative, we'd rather leak a daemon than kill the wrong thing.
+tmux_session_alive() {
+  local tmux_name="$1"
+  if ! command -v tmux >/dev/null 2>&1; then
+    return 0  # no tmux binary → can't verify → assume alive
+  fi
+  # Verify the tmux server itself is reachable before trusting has-session.
+  # `tmux ls` exits 0 when the server is running and has at least one session.
+  # If it fails (server not running, socket error, no sessions at all), we can't
+  # reliably distinguish "this session is gone" from "tmux is broken." Conservative
+  # choice: assume the session might still be alive (or recoverable when the server
+  # comes back).
+  if ! tmux ls >/dev/null 2>&1; then
+    return 0  # server unreachable or empty → can't verify → assume alive
+  fi
+  # Server is confirmed reachable and has sessions. has-session non-zero now
+  # reliably means "this specific session does not exist."
+  tmux has-session -t "$tmux_name" 2>/dev/null
+}
+
+sweep_orphan_daemons() {
+  local swept=0
+  local kept=0
+  local cleaned_stale=0
+
+  # Pass 1: walk mapping files, which are the source of truth for (tmux_session, pid) pairs
+  shopt -s nullglob
+  local map_file
+  for map_file in "${CODEVIBE_TMPDIR}"/codevibe-claude-instance-*.json; do
+    # Extract tmux session name from filename
+    local orphan_tmux
+    orphan_tmux=$(basename "$map_file" .json | sed 's/^codevibe-claude-instance-//')
+
+    # Skip our own tmux session — we handle it in the existing reuse path below
+    if [ -n "$TMUX_SESSION" ] && [ "$orphan_tmux" = "$TMUX_SESSION" ]; then
+      continue
+    fi
+
+    local orphan_pid
+    orphan_pid=$(jq -r '.pid // empty' "$map_file" 2>/dev/null)
+
+    # Empty or missing PID in mapping — clean up the mapping file
+    if [ -z "$orphan_pid" ]; then
+      log "INFO" "Orphan sweep: removing mapping with no PID: $map_file"
+      rm -f "$map_file"
+      cleaned_stale=$((cleaned_stale + 1))
+      continue
+    fi
+
+    # PID is no longer running — clean up the stale mapping.
+    # NOTE: do NOT touch the pidfile or portfile by session UUID here. If /resume
+    # or a UUID collision caused a stale mapping to reference the same session
+    # UUID as a currently-live pidfile, we'd delete the live one. Pass 2 below
+    # handles pidfile cleanup by verifying each pidfile's content independently.
+    if ! ps -p "$orphan_pid" > /dev/null 2>&1; then
+      log "INFO" "Orphan sweep: removing stale mapping for dead PID $orphan_pid (tmux $orphan_tmux)"
+      rm -f "$map_file"
+      cleaned_stale=$((cleaned_stale + 1))
+      continue
+    fi
+
+    # PID is alive. Is its tmux session still alive (or unknowable)?
+    if tmux_session_alive "$orphan_tmux"; then
+      # Live other session — or tmux is unavailable and we can't tell. Either
+      # way, the conservative choice is to leave the daemon alone.
+      log "DEBUG" "Orphan sweep: tmux $orphan_tmux is alive (or tmux unavailable), leaving daemon $orphan_pid"
+      kept=$((kept + 1))
+      continue
+    fi
+
+    # tmux is gone but the PID is alive — looks like an orphan. But before
+    # killing, verify the PID actually belongs to a codevibe-claude daemon.
+    # If PID reuse has handed this PID to an unrelated process, we must not
+    # touch it. Just clean up the stale mapping and move on.
+    if ! is_codevibe_daemon "$orphan_pid"; then
+      log "INFO" "Orphan sweep: PID $orphan_pid is alive but is not a CodeVibe daemon (likely PID reused), removing stale mapping only"
+      rm -f "$map_file"
+      cleaned_stale=$((cleaned_stale + 1))
+      continue
+    fi
+
+    # Verified: this is our daemon and its tmux is gone. Kill it.
+    log "WARN" "Orphan sweep: killing orphan daemon PID $orphan_pid (tmux $orphan_tmux is gone)"
+
+    # SIGTERM first — lets the daemon run its graceful shutdown (mark session INACTIVE, etc.)
+    kill "$orphan_pid" 2>/dev/null || true
+
+    # Give it a moment to exit cleanly, then SIGKILL if it's still alive
+    sleep 0.5
+    if ps -p "$orphan_pid" > /dev/null 2>&1; then
+      log "WARN" "Orphan sweep: daemon $orphan_pid did not exit from SIGTERM, sending SIGKILL"
+      kill -9 "$orphan_pid" 2>/dev/null || true
+    fi
+
+    # Remove the mapping file. Do NOT touch pidfile/portfile by session UUID —
+    # Pass 2 below will pick up the now-dead PID and clean the pidfile (and its
+    # matching portfile) safely, based on PID content, not mapping contents.
+    rm -f "$map_file"
+    swept=$((swept + 1))
+  done
+
+  # Pass 2: defensive cleanup of stale pidfiles that have no mapping and are dead
+  # (e.g. daemons that died before writing a mapping file, or legacy non-tmux launches)
+  local pid_file
+  for pid_file in "${CODEVIBE_TMPDIR}"/codevibe-claude-*.pid; do
+    # Skip the instance-mapping files' PID files (they have 'instance' in the name and are .json not .pid,
+    # but be explicit in case the glob matches something unexpected)
+    local base
+    base=$(basename "$pid_file")
+    case "$base" in
+      codevibe-claude-instance-*) continue ;;
+    esac
+
+    local pid
+    pid=$(cat "$pid_file" 2>/dev/null)
+    if [ -z "$pid" ] || ! ps -p "$pid" > /dev/null 2>&1; then
+      log "INFO" "Orphan sweep: removing stale pidfile $pid_file (PID ${pid:-empty} not alive)"
+      rm -f "$pid_file"
+      # Also clean up the corresponding portfile
+      local port_file="${pid_file%.pid}.port"
+      rm -f "$port_file"
+      cleaned_stale=$((cleaned_stale + 1))
+    fi
+  done
+  shopt -u nullglob
+
+  if [ $swept -gt 0 ] || [ $cleaned_stale -gt 0 ]; then
+    log "INFO" "Orphan sweep: killed $swept orphan daemon(s), cleaned $cleaned_stale stale file(s), kept $kept live session(s)"
+  else
+    log "DEBUG" "Orphan sweep: nothing to clean (kept $kept live session(s))"
+  fi
+}
+
+# Run the sweep before touching the mapping file for our own session
+sweep_orphan_daemons || log "WARN" "Orphan sweep failed (non-fatal, continuing)"
+
 # Check if there's an MCP server running for this Claude Code instance
 EXISTING_SERVER_PORT=""
 EXISTING_SERVER_PID=""

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "@quantiya/codevibe-claude-plugin",
-  "version": "1.0.9",
-  "description": "Mobile companion for Claude Code - monitor and control your Claude Code sessions from your phone with CodeVibe",
+  "version": "1.0.11",
+  "description": "Control Claude Code from your iPhone and Android — real-time sync, approve file edits, send prompts by voice. Part of CodeVibe.",
   "main": "dist/server.js",
   "bin": {
     "codevibe-claude": "./bin/codevibe-claude"
   },
   "files": [
-    "dist",
+    "dist/**/*.js",
     "bin",
     "hooks",
     ".claude-plugin",
@@ -24,10 +24,6 @@
     "watch": "tsc --watch",
     "test": "jest --config jest.config.js --forceExit"
   },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/hendryyeh/quantiya-codevibe-claude-plugin.git"
-  },
   "keywords": [
     "claude",
     "claude-code",
@@ -35,6 +31,7 @@
     "plugin",
     "mobile",
     "ios",
+    "android",
     "codevibe",
     "remote-control",
     "ai",
@@ -43,9 +40,9 @@
   "author": "Quantiya <support@quantiya.ai>",
   "license": "MIT",
   "bugs": {
-    "url": "https://github.com/hendryyeh/quantiya-codevibe-claude-plugin/issues"
+    "email": "support@quantiya.ai"
   },
-  "homepage": "https://github.com/hendryyeh/quantiya-codevibe-claude-plugin#readme",
+  "homepage": "https://quantiya.ai/codevibe",
   "engines": {
     "node": ">=18.0.0"
   },