Gateton

Session Hub — Development skill for Claude Code

Development community

Continue work you left in another coding agent: find a session from Claude Code, Codex, OpenCode, Crush, JCode or Pi, bring its context into the one you are using, or reopen it where it lives.

How to install Session Hub

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

What Session Hub does

Continue work you left in another coding agent: find a session from Claude Code, Codex, OpenCode, Crush, JCode or Pi, bring its context into the one you are using, or reopen it where it lives.

Alternatives in Development

  • Create Handoff — You are tasked with writing a handoff document to hand off your work to another agent in a new session 10k ★
  • Claude Coder — Kodu is an autonomous coding agent that lives in your IDE 5.2k ★
  • Claude Code Sub Agent Collective — 🧠 Context Engineering Research - Not just another agent collection, but using research and context engineerin 523 ★

README

session-hub: your coding sessions, everywhere. Browse, continue, switch.

session-hub

Every coding agent on your machine, in one session list.
Continue in this one the work you left in that one.

Node 22.5 or newer License: MIT MCP: three read-only tools

OpenCode · Claude Code · Codex

Reads sessions from Pi, Claude Code, Codex, OpenCode, Crush and JCode · local, read-only, no network


The problem

You work across more than one coding agent. You start a refactor in OpenCode, then open Claude Code for a second opinion, or you are deep in a Codex session and want to finish it somewhere else.

Every agent keeps its own history, in its own format, in its own directory. Nothing carries over. So you do the only thing left: re-explain. What the task was, which files you touched, what the error said, which approach you already ruled out. The context window resets and you spend the first ten minutes rebuilding what you already knew.

`session-hub` removes that step. It reads the session stores every agent already writes, puts them in one list, and turns the one you pick into a context package the agent you are in now can actually use. It ships as an MCP server with three read-only tools, plus a plugin for each agent that puts them inside the chat you are already in.

What it does