Getting started — DirectorHub

Part 1 · Stand up your team

Sign in

Open directorhub.app and sign in with GitHub or Google. The first time on a new account, paste your invite code — after that you just log in.

Create a project

Give it a name and a one-line goal. It ships with a default team of four — Claude, ChatGPT, Gemini, Grok — each with a role. Rewrite any of them in Agents, or start from a preset.

Add your OpenRouter key

In Settings → API keys → OpenRouter, paste and save. This is what the agents think with; your balance then shows as a chip in the top bar. Your key never touches the server — it lives only in this browser.

Run a session

Open the project, start a session, write a directive. Pick Panel, Cascade, or Direct for how the team answers. This is the whole product — you never need an executor to get value here.

Part 2 · Connect a coding agent (optional)

When you want the deliberation to become real changes, connect a coding agent in Skills & connectors. Two shapes, and you can use both: a bridge you drive (Claude Code over MCP), or hands-off mode — a small local auto-executor that runs your directives itself.

Install the watcher

Generate a token in Skills & connectors → Hands-off, then set it up. During init you pick the projects to watch, map each to a local repo path, and choose the engine per project — Claude Code or Cursor.

npm i -g directorhub-watcher
directorhub-watcher init

Optional: use Cursor or Codex

To run a project on Cursor you need Node ≥ 22.13 and a Cursor API key (Cursor dashboard → Settings → API Keys — it bills to your Cursor plan). In init, enable Cursor, paste the key (stored owner-only, never logged), and pick a model. Reports then carry execution: $0.00 (Cursor plan) when your plan covers the run. Or run it on Codex (ChatGPT plan) with no key at all — codex login once, then choose Codex in init; reports read $0.00 (ChatGPT plan).

Send a directive — and walk away

Send a small directive from the Hub to a watched project's session. No terminal. The watcher runs it and reports back on the timeline — a summary, the files it changed, a cost line — on a directive/… branch you review and merge.

Your keys stay yours. The OpenRouter key lives in your browser; the watcher's token and any Cursor key live on your machine (~/.directorhub/watcher.json, owner-only, never logged). None of them reach our server.

The executor never pushes. Whitelist-only, one directive at a time, on a local branch — and with Cursor the runtime is sandboxed with the network denied, so pushing is impossible while inference runs unaffected on Cursor's hosted models.