tabz-integration

Integrate external apps with TabzChrome terminals via WebSocket, JS API, and Spawn API.

147|10|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/GGPrompts/TabzChrome --skill tabz-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tabz-integration
Source: https://github.com/GGPrompts/TabzChrome/tree/main/.claude/skills/tabz-integration
Command: npx skills add https://github.com/GGPrompts/TabzChrome --skill tabz-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables developers to bridge their applications with TabzChrome terminals, allowing one-click command queuing and programmatic tab spawning from docs, CLIs, or web apps.

Core Features & Use Cases

  • HTML data-terminal-command integration for static docs and pages.
  • WebSocket and JavaScript API integrations for dynamic prompts and automation.
  • POST /api/spawn to create new terminal tabs programmatically.
  • Use cases include embedding Run in Terminal buttons on product docs, queueing commands from CLIs, and spawning Claude or other agents via Spawn API.

Quick Start

Decide which integration method you need, ensure the TabzChrome backend is running on localhost:8129 with a valid API token, then use one of:

  • HTML Buttons: attach data-terminal-command attributes to UI elements.
  • WebSocket / JS: connect to ws://localhost:8129 with a token and queue commands.
  • Spawn API: POST to /api/spawn with a JSON payload including name, workingDir, and command.

Frequently Asked Questions about tabz-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I queue terminal commands from a web app to a local browser backend?

To queue terminal commands from a web app, connect to a local backend via WebSocket or use a JavaScript API with token-based authentication to programmatically send and execute commands in the browser terminal.

How do I add a Run in Terminal button to my static HTML documentation?

Add a Run in Terminal button to static HTML documentation by attaching data-terminal-command attributes to UI elements, which the terminal backend detects to automatically queue and execute the specified commands.

Can I programmatically spawn new terminal tabs from a CLI?

Yes, you can programmatically spawn new terminal tabs from a CLI by sending an HTTP POST request to the /api/spawn endpoint with a JSON payload containing the tab name, working directory, and command.

Do I need a running backend and API token to integrate terminal control into my docs?

Yes, terminal control integration requires a backend running on localhost:8129 with valid token-based authentication to securely authorize WebSocket connections, HTML data-terminal-command execution, and Spawn API requests.

What is the difference between using HTML attributes and the Spawn API for terminal integration?

HTML attributes provide static command queuing for documentation pages, while the Spawn API offers dynamic programmatic tab creation via POST requests, allowing automated agent spawning and complex command execution from external apps.