Ggprompts Tabzchrome
ggprompts-tabzchrome is a Claude Code plugin for the Build phase that adds a Chrome sidebar to manage tmux sessions alongside agent and MCP-driven terminal work.
by GGPrompts · github.com/GGPrompts/TabzChrome
Control tmux sessions from a persistent Chrome sidebar while coding agents run terminals, MCP tools, and browser workflows in parallel.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install ggprompts-tabzchrome@GGPrompts/TabzChromeBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:GGPrompts/TabzChrome") and the paste-ready config with skillselion.get_install_config("plugin:GGPrompts/TabzChrome").
What it does
ggprompts-tabzchrome is a Claude Code plugin backed by a Chrome extension that puts tmux session management in a persistent browser sidebar. Solo builders juggling Claude Code, local servers, and multiple panes often lose context when terminals hide behind editor tabs; TabzChrome surfaces sessions beside your workflow and advertises deeper hooks—MCP, automation, screenshots, spawn—for tying browser UI to terminal state. It belongs on the Build integrations shelf because it connects environments rather than shipping product features directly, though operators also use it to watch infra-style tmux layouts during long sessions. It is not a hosted SaaS or a skill checklist; it is local browser + terminal glue for power users. If you live in tmux while agents run commands, this plugin category (integration) signals exactly that pairing. Install when terminal sprawl is slowing you down and you want one sidebar to steer sessions while Claude Code or MCP tools orchestrate the rest.
Highlights
- Chrome extension with persistent sidebar for tmux session control
- Browser-side integration keywords include MCP, WebSocket, screenshots, and terminal spawn
- Tabz/TabzChrome workflow for managing many shells from one UI
- Automation-oriented tooling for agent + terminal projects (138 GitHub stars)
- Single-plugin integration bundle from GGPrompts/TabzChrome
Why builders use it
Running agents and dev servers across many tmux panes is invisible from the browser, so you constantly context-switch and lose track of which session did what.
After install, tmux sessions stay visible and controllable from Chrome while your agent stack keeps using terminals and integration tools in sync.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 138 stars, 0 votes.
FAQ
Who is ggprompts-tabzchrome for?
It is for indie developers and agent users who run tmux locally and want Chrome-side visibility and control without replacing their terminal stack.
When should I use ggprompts-tabzchrome?
Use it when you routinely spawn multiple tmux sessions for builds, agents, or MCP tools and need a persistent sidebar instead of window hopping.
How do I add ggprompts-tabzchrome to my agent?
Add the GGPrompts/TabzChrome Claude Code plugin from Skillselion, install the TabzChrome extension in Chrome, and connect it to your local tmux/MCP setup per the repo README.
Comments
Share how you use ggprompts-tabzchrome, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.