tabz-integration

# TabzChrome Integration Guide

Connect any project to TabzChrome terminals via REST API, WebSocket, HTML attributes, or MCP tools.

## When to Use This Skill

Trigger when users ask about:
- Spawning terminals from scripts or code
- Adding "Run in Terminal" buttons to web pages
- Connecting to TabzChrome from external apps
- Setting up MCP tools for browser automation
- Using TTS/audio notifications programmatically
- Queuing commands to the sidebar chat input

## Quick Start

### Spawn a Terminal (Most Common)

```bash
TOKEN=$(cat /tmp/tabz-auth-token)
curl -X POST http://localhost:8129/api/spawn \
  -H "Content-Type: application/json" \
  -H "X-Auth-Token: $TOKEN" \
  -d '{"name": "Worker", "workingDir": "~/projects", "command": "claude"}'
```

### Add HTML Buttons (No Auth)

```html
<button data-terminal-command="npm run dev">Start Dev Server</button>
```

### Queue to Chat Input

```bash
echo '{"type":"QUEUE_COMMAND","command":"npm test"}' | \
  websocat "ws://localhost:8129?token=$(cat /tmp/tabz-auth-token)"
```

## Integration Methods

| Method | Auth Required | Use Case |
|--------|---------------|----------|
| HTML `data-terminal-command` | None | Static buttons on web pages |
| WebSocket + websocat | Token file | CLI scripts, shell functions |
| WebSocket + JS | API endpoint | Web applications |
| POST /api/spawn | Token header | Create new terminal tabs |
| MCP tools | Backend running | Browser automation from Claude |
| Audio API | None | TTS notifications from code |

For detailed examples, see `references/integration-examples.md`.

## REST API Endpoints

| Endpoint | Method | Purpose |
|----------|--------|---------|
| `/api/spawn` | POST | Create terminal with optional command |
| `/api/health` | GET | Health check (no auth) |
| `/api/agents` | GET | List active terminals |
| `/api/agents/:id` | DELETE | Kill a terminal |
| `/api/audio/speak` | POST | TTS playback |
| `/api/audio/generate` | POST | Generate TTS audio URL |

**Authentication:** Most en