The Hub gathers every Claude Code session on your Mac in one window and, when one account's quota runs out, keeps the session going on the next account.
See what it does Setup guideFirst a check that touches nothing, then one command.
Shortened sample. The real check prints every line in Turkish and English.
./install.sh --check./install.shclaude-hub openEach Claude account's 5 hour and weekly quota, reset time and weekly forecast side by side.
When an account is full, the open session continues on the next account, same conversation, where it left off.
Whichever account started it, every Claude Code session is here: search, pin, open side by side.
Permissions, questions and messages in Follow-up, with a suggested answer. Sending always needs your approval.
The job is done in a separate working copy, previewed, reviewed by a three-member jury, and lands in Ready.
A job waiting for a decision reaches your phone as a notification; you look and answer from there. Optional.
Five features, up close. The screens are samples drawn with the real interface's layout; names and numbers are made up.
Write what you want. The Hub asks a question or two if needed, has the job done in a separate working copy, publishes it to a preview address, opens it in a real browser to check it and has a three-member jury review it. If you like it, one tap takes it live.
Preview and live publishing need a Cloudflare account in the vault; without one the job is still done and merged into the main branch.
Each agent has its own role, instructions, model and thinking level. The team lead splits the job into parts and hands them out. A team has its own MCP connections and secret keys, kept apart from other teams.
There are two account orders: the account whose weekly quota resets first goes first (default), or the emptiest account goes first. When an account is full, the session carries on in the next one where it left off. You can also pick the account for each job by hand.
Another Mac or a Windows PC connects to the center as a satellite; it opens no port and only connects outward. From the center you see every machine's sessions, accounts and waiting jobs, and send tasks and messages to them. Your phone connects to the same center.
The center is optional and runs on your own server. Without it the Hub runs on this Mac only.
You add the Hub MCP once. Then a Claude in your terminal or the desktop app can open a new job in the Hub, start a task, plan team work or send a message to an open session. Granting permissions and going live are closed to MCP; they always stay with you.
In the command, <Hub folder> is the folder you installed the Hub in. Sessions the Hub opens itself only see the read tools, so no loops form.
Four points, briefly.
There are two account orders: the account whose weekly quota resets first goes first (default), or the emptiest account goes first. When an account is full, the session carries on in the next one with the same conversation; if all are full, it resumes by itself at the first reset.
Done in a closed area (sandbox), opened and checked in a real browser, reviewed by a three-member jury. By morning it is in Ready.
The Hub never says yes to a permission prompt. Going live needs a one-time approval valid for 2 minutes, and your own tap.
The server only listens on 127.0.0.1:7788 and is not reachable from outside. Data lives in ~/.claude-hub.
What it won't do on purpose, and its limits.