Menu
Integrate projects with TabzChrome terminals via Markdown links, HTML attributes, WebSocket, JS API, or Spawn API
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | integration |
| description | Integrate projects with TabzChrome terminals via Markdown links, HTML attributes, WebSocket, JS API, or Spawn API |
| user-invocable | true |
Help users integrate their projects with TabzChrome terminals.
| Method | Auth | Best For |
|---|---|---|
Markdown tabz: links | None | Project dashboards, docs in file viewer |
HTML data-terminal-command | None | Static buttons on web pages |
| WebSocket + websocat | File token | CLI/tmux workflows |
| WebSocket + JS | API token | Prompt libraries, web apps |
| POST /api/spawn | Token | Creating new terminal tabs |
First, ask which integration the user needs:
questions:
- question: "Which TabzChrome integration methods do you need?"
header: "Integration"
multiSelect: true
options:
- label: "Markdown Links"
description: "tabz: protocol for project dashboards in file viewer"
- label: "HTML Buttons"
description: "data-terminal-command for 'Run in Terminal' buttons"
- label: "CLI/Scripts"
description: "WebSocket via websocat for shell scripts"
- label: "Web App JS"
description: "JavaScript WebSocket for prompt libraries"
- label: "Spawn API"
description: "POST /api/spawn to create new tabs"
Then provide the relevant reference:
| Selection | Reference |
|---|---|
| Markdown Links | references/markdown-links.md |
| HTML Buttons | references/html-integration.md |
| CLI/Scripts | references/cli-websocket.md |
| Web App JS | references/javascript-api.md |
| Spawn API | references/spawn-api.md |
| Context | Method |
|---|---|
| CLI / Scripts | TOKEN=$(cat /tmp/tabz-auth-token) |
| Extension Settings | Click "API Token" → "Copy Token" |
| External web pages | User pastes token (stored in localStorage) |
Web Page / CLI / App
│
▼
TabzChrome Backend (localhost:8129)
│
▼ WebSocket broadcast
Chrome Extension
│
▼
Sidepanel → Terminal Tabs
For security considerations on HTTPS sites, see references/security.md.
Spawn and manage terminal tabs via TabzChrome REST API. Use when spawning workers, creating terminals programmatically, setting up worktrees for parallel work, or crafting prompts for Claude workers.
Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications.
Spawn and manage terminal tabs via TabzChrome REST API. Use when spawning workers, creating terminals programmatically, setting up worktrees for parallel work, or crafting prompts for Claude workers.
Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications.
Integrate projects with TabzChrome terminals via HTML attributes, WebSocket, JS API, or Spawn API
Patterns for building and debugging TabzChrome itself. Use when working on Terminal.tsx, xterm.js integration, WebSocket I/O, resize handling, or any TabzChrome extension/backend code.