← Back to Skills Marketplace
yayayahei

Terminal In Chrome

by yayayahei · GitHub ↗ · v1.1.13 · MIT-0
cross-platform ⚠ suspicious
52
Downloads
0
Stars
1
Active Installs
7
Versions
Install in OpenClaw
/install terminal-in-chrome
Description
Manages the Web Terminal Chrome Extension local backend server. Use this skill to start, stop, or check the status of the local terminal server running on po...
README (SKILL.md)

Web Terminal Extension Skill

Overview

This skill manages the local backend server for the Web Terminal Chrome Extension, which injects a fully functional, resizable local terminal into any website via xterm.js.

Architecture

  1. Server (/server): A lightweight Node.js backend running locally (ws://localhost:8989) that spawns the actual terminal process (bash or zsh) using node-pty.
  2. Extension (/extension): A Chrome extension that injects xterm.js into websites and connects back to the local server via WebSockets.

Operations

Start the Server

Trigger phrases: "start web terminal", "run terminal server", "start terminal backend"

Action: Navigate to the server directory and start the Node.js server in the background.

cd server
npm start

The server will run on port 8989.

Stop the Server

Trigger phrases: "stop web terminal", "kill terminal server", "stop terminal backend"

Action: Find the process running on port 8989 and kill it.

lsof -i :8989
kill -9 \x3CPID>

Check Status

Trigger phrases: "web terminal status", "is terminal running?", "check terminal server"

Action: Check if port 8989 is in use to determine if the server is running.

lsof -i :8989

User Instructions for Extension

If the user asks how to use the extension, provide these steps:

  1. Open Google Chrome and navigate to chrome://extensions/
  2. Enable Developer mode (toggle in the top right corner).
  3. Click Load unpacked.
  4. Select the extension folder from this project (web-terminal-extension/extension).
  5. Go to any website.
  6. Press Ctrl + \``** or **Cmd + J` to toggle the terminal.
  7. Drag the top border to resize it.
Usage Guidance
Install only if you deliberately want a Chrome extension that can open a local shell connected to your machine. Use it only in a controlled environment, restrict it to trusted sites, add authentication and strict origin checks to the localhost server, avoid exposing sensitive environment variables, and make terminal sessions expire when disconnected.
Capability Tags
crypto
Capability Assessment
⚠ Purpose & Capability
The README and SKILL.md disclose a browser-injected local terminal, and the server does spawn an interactive shell as that terminal backend. However, the published package description emphasizes server management while the bundled artifacts provide broad local command execution through a Chrome extension.
⚠ Instruction Scope
The extension runs content scripts on all URLs and connects to a localhost WebSocket terminal. The artifacts provide a blocked-sites list, but no default allowlist, authentication, strict origin checks, or per-session consent before shell input is accepted.
ℹ Install Mechanism
The package uses ordinary Node and Chrome extension files, with npm start launching server.js. I did not find obfuscated install scripts or hidden install-time behavior; the main risk is the disclosed runtime design.
⚠ Credentials
The backend accepts WebSocket messages and writes them directly into a spawned PTY, using the user's shell, home directory, and full inherited process environment. That exposes high-impact local authority and potentially sensitive environment variables.
⚠ Persistence & Privilege
Terminal instances are keyed by a client-provided page URL and intentionally persist after clients disconnect, retaining shell state and output history until the server restarts.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install terminal-in-chrome
  3. After installation, invoke the skill by name or use /terminal-in-chrome
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.13
- Updated extension/manifest.json (details not provided). - No user-facing changes in documentation or usage instructions.
v1.1.12
- Major cleanup: removed redundant and unused files from the repository. - Added a root-level package.json to centralize package management. - Simplified and minimized the Chrome extension's manifest. - No changes to user-facing features or core functionality.
v1.1.10
Initial release of the "Terminal in Chrome" skill: - Added Node.js backend server to provide a local terminal interface via WebSockets on port 8989. - Introduced a Chrome extension that injects xterm.js into websites and connects to the local server. - Provided start, stop, and status operations to manage the server process. - Included detailed setup instructions and user documentation. - Packaged all components and assets required for extension and server functionality.
v1.1.9
Version 1.1.9 of terminal-in-chrome - No file changes detected in this release. - No updates to features, functionality, or documentation.
v1.1.8
- Updated extension/manifest.json (details not shown). - No user-facing changes to the skill’s description or documentation. - Version incremented to 1.1.8.
v1.1.7
Version 1.1.7 of terminal-in-chrome - No file changes detected in this release. - Documentation and usage instructions remain unchanged. - No new features, bug fixes, or updates since the previous version.
v1.1.6
- Added detailed documentation in SKILL.md, including instructions for starting, stopping, and checking the status of the terminal server. - Clarified trigger phrases for each operation. - Provided step-by-step user instructions for installing and using the Chrome extension.
Metadata
Slug terminal-in-chrome
Version 1.1.13
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 7
Frequently Asked Questions

What is Terminal In Chrome?

Manages the Web Terminal Chrome Extension local backend server. Use this skill to start, stop, or check the status of the local terminal server running on po... It is an AI Agent Skill for Claude Code / OpenClaw, with 52 downloads so far.

How do I install Terminal In Chrome?

Run "/install terminal-in-chrome" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Terminal In Chrome free?

Yes, Terminal In Chrome is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Terminal In Chrome support?

Terminal In Chrome is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Terminal In Chrome?

It is built and maintained by yayayahei (@yayayahei); the current version is v1.1.13.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463556 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259610 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200551 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191226 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190235 · by oswalpalash

💬 Comments