session-hub

Name: session-hub
Availability: InStock
Author: Ryan

Coordinates parallel Claude Code sessions through a shared append-only HTML hub.

Updated Aug 30, 2026

Search Tags:#git workflow #claude code #codex #multi-agent #parallel sessions #session coordination #html hub

Ready to run

npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill session-hub-ryanportfolio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-hub
Source: https://github.com/ryanportfolio/threejs-interview-test/tree/main/.agents/skills/session-hub
Command: npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill session-hub-ryanportfolio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple AI coding sessions work on the same repository in parallel, edits and commits from one session can silently conflict with or overwrite another. This Skill provides a shared coordination hub so parallel sessions stay aware of each other's changes. ## Core Features & Use Cases - Shared Session Hub: Maintains an append-only HTML hub on the Desktop where parallel Claude Code sessions publish and read activity. - Parallel Session Coordination: Triggered via $session-hub, requests to run parallel sessions, or when unexpected edits or commits appear in the checkout. - Canonical Workflow Delegation: Reads the canonical workflow from .claude/skills/session-hub/SKILL.md and adapts Claude Code tool names to the Codex environment. - Use Case: You launch two AI sessions on different branches of the same repo; the hub lets each session detect the other's commits before merging or rebasing. ## Quick Start Ask the assistant to run parallel sessions on this repository using the session hub so each session can see the others' edits and commits.

Frequently Asked Questions about session-hub

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

FAQPage Schema

How do I coordinate parallel Claude Code sessions on one repository?▼

Invoke the session-hub skill or ask to run parallel sessions on the repository. Each session publishes activity to a shared append-only HTML hub on the Desktop, letting sessions detect edits and commits made by the others.

How do I detect unexpected commits from another AI session?▼

The session-hub skill triggers proactively when edits or commits appear in the checkout that the current session did not make. It reads the shared hub to identify which parallel session produced those changes.

Does session-hub work with Codex instead of Claude Code?▼

Yes, the skill acts as a Codex adapter that reads the canonical workflow from .claude/skills/session-hub/SKILL.md and translates Claude Code tool names to Codex equivalents, following the repository's AGENTS.md guidance.

Can session-hub commit or push changes automatically?▼

No, invoking the skill alone does not authorize commits, pushes, pull requests, merges, or dependency installation. Those outward actions require an explicit user request, per the skill's stated constraints.

What are the limitations of the session-hub approach?▼

The hub is append-only and stored locally on the Desktop, so it coordinates sessions on the same machine only. It also requires the Codex session to expose multi-agent tools before running any Task, Agent, or Workflow steps.