BridgeHub / Welcome
Practice mode · settings protected
Practice mode — actions stay inside this preview. Your apps and settings are unchanged.

How to work through the bridge

1. A focused conversation for each project

Keep a separate conversation for each project. Your assistant turns agreed decisions into a focused brief, sends it to the project’s Claude Code boss, and explains the report that comes back.

One conversation for each projectYou direct three project conversations. Each conversation reaches its matching Claude Code project boss through one shared MCP bridge. Each boss can coordinate its own coding helpers. Focused briefs and reports pass both ways through the bridge. YOUYOUR CONVERSATIONSTHE BRIDGEPROJECT BOSSESHELPERS YouSet the direction Game conversationWebsite conversationApp conversationGame bossWebsite bossApp boss Clarify & briefClarify & briefClarify & briefClaude CodeClaude CodeClaude Code Bridge HubMCPRoutes messages GameplayVisualsPagesTestingFeaturesTesting Focused briefs go out. Reports come back. Your conversation assistant explains the result.

Keep one conversation focused on each project. Any conversation can reach a boss by name; each boss handles its own coding and authorized helpers. Open Claude Code when approvals or direct review need you.

2. Project, chat, and bossA project is the parent folder of the work. Each Claude Code chat starts in a folder. Many chats may belong to one project, but one is designated as the boss. Naming the boss gives your conversation assistant a route to that chat.
3. Why the full list has so many rowsConnections discovers projects from allowed folders and recent Claude Code chats. Each project row groups its chats. Select the project’s responsible chat as boss; leave helper chats alone. Existing older names can remain saved without becoming extra projects.
4. What a connection check provesRegistration means setup is saved. A new supported desktop conversation using a bridge tool confirms that the tool loaded. A boss reply proves the mailbox round trip.
5. Working with one bossYou own the decisions. Your conversation assistant keeps the goal clear and coordinates requests. The project’s boss manages coding and any authorized helpers. Choose the chat with current project knowledge, not simply the oldest chat. Keep decisions and status in project records so continuity does not depend on one conversation.