KolyshkinYafim

Chat Hub — AI skill for Claude Code

AI community

Desktop cockpit for AI coding agents: Claude Code / Codex / Grok / OpenCode side by side — worktree-per-session, surfaces dock (files/terminal/diff/browser), MCP browser control, permission broker.

How to install Chat Hub

This entry records only its repository, not the path inside it, so there is no exact command to give. Open KolyshkinYafim/chat-hub and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Chat Hub does

Desktop cockpit for AI coding agents: Claude Code / Codex / Grok / OpenCode side by side — worktree-per-session, surfaces dock (files/terminal/diff/browser), MCP browser control, permission broker. Electron + React + TS

Alternatives in AI

Adopt AI Properly — Workflow recipe — the org-side AI adoption arc, policy to proof, by chaining 4 skills 1.3k ★
Browserwing — BrowserWing turns your browser actions into MCP commands Or Claude Skill, allowing AI agents to control browse 1.2k ★
Dinotty — Multi-device terminal server for AI coding agents 643 ★

README

Chat Hub

[![CI](https://github.com/KolyshkinYafim/chat-hub/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/KolyshkinYafim/chat-hub/actions/workflows/ci.yml)

Chat Hub is a desktop cockpit for AI coding agents: one window that runs Claude Code, Codex, Grok and OpenCode sessions side by side, each in its own project and, optionally, its own git worktree. Around the transcript it adds the working context a coding session actually needs — files, terminal, browser, diffs, a project board — and it stays wired into Session Monitor, the Swift menu-bar app in the sibling repo, so session status and permission prompts follow you outside the window.

Electron · TypeScript · React · pnpm — macOS first.

![Chat Hub workbench](docs/screenshots/workbench.png)

Features

Multi-provider sessions — adapters for Claude Code, Codex, Grok and OpenCode CLIs (auto-detected on PATH), plus a mock provider for UI work. Streaming transcripts with tool cards, diffs, plans, mermaid diagrams and usage stats; honest status driven by process events, never a stuck "Working".
Surfaces dock — per-session panels next to the chat: file browser with code editor and image/media/PDF preview, real terminal (node-pty + xterm), git diff / source control with per-hunk staging, project board (todos and notes the agent can edit too), embedded browser, and session history.
Agent browser control — any of the four CLIs can drive the Browser surface over MCP: open pages, read them as ref-tagged trees, click, type, screenshot, read console and network logs — in the same webview the user is watching. See docs/browser-control.md.
MCP manager — Settings → Connections edits a per-project server list (.chathub/mcp.json) and materializes it into each provider's native config format.
Voice dictation — hands-free composer input through Handy, a local dictation app; Chat Hub never touches audio.