Every AI you run — Hermes on your laptop, Gemini Ultra, Microsoft 365 Copilot, Claude, ChatGPT, Codex and GitHub — on one board. See how each one connects, what it's best at, open it in one tap, or compose a mission and hand it off.
Write the mission once, with its deliverable and definition of done. Launch queues it on the mission board below and copies a ready-to-paste brief — dispatch is still manual relay today, so nothing is sent on its own. The plan summary under the form is a proposal you review before anything moves.
Review this before launching. Launching queues the mission on the board and copies the brief; the agent still gets it by manual relay.
Launched missions land in Queued. Move them as work progresses — this board is saved in this browser only, until server sync arrives in a later phase.
One room for the whole council. This is the static room: each member joins through the real channel listed on their seat, and what they actually said gets pasted into a permanent, append-only transcript. Live multi-agent posting arrives in a later phase — nothing here posts by itself.
Start a session with a topic or agenda. Sessions and transcripts are saved in this browser and included in Export / Import.
No session yet.
Phase 1 roles — they run on the connections above, routed by model tier, and they're in the composer picker too. Subjects are proposed drafts; correct them and they get locked in. Each role's evidence gate below must be fully checked before one of its missions can be verified.
One pattern for everything — including services with no API, like Gemini Ultra and ChatGPT on subscription.
Why it works: Tailscale reaches Hermes, and Hermes reaches everything else — the same pattern your copilot-broker prototype already proved for Microsoft 365 Copilot. Gemini runs the identical bridge against gemini.google.com. The Hermes link itself is verified end-to-end; the Gemini and ChatGPT browser bridges are the next build step, so those two run on manual relay (copy-paste) until then.
The specialty map — Gemini's five are in its own words, from its first Ensemble brief.
| Task | Goes to |
|---|---|
| Google Workspace work | Gemini — Gmail, Drive, Docs, Calendar, YouTube natively |
| Live research | Gemini — search-grounded, cited, up to date |
| Huge context | Gemini — whole codebases, PDFs, thousands of notes in one pass |
| Video / audio / screenshots | Gemini — native multimodal analysis |
| Microsoft 365 work | Copilot — via the copilot-broker bridge |
| Local files & automation | Hermes — terminal, cron, your C:\tools projects |
| Hard reasoning & writing | Claude — flagship tier, with Opus as fallback |
| Repos, issues, PRs | GitHub — via the ghcp profile & Copilot quota |
Already live on your laptop — this is Ensemble's cost-routing model.
GPT-6.1-Sol first, Claude Opus 5 as fallback. For work that has to be right — planning, legal, security, final synthesis.
Claude Sonnet 5 running on your GitHub Copilot quota — strong model, already paid for.
Budget Claude Sonnet 5 for bulk and routine jobs — summaries, sorting, drafts.
Morning Briefing, revenue loops, memory mirrors and more — the automations Ensemble orchestrates rather than replaces.
Every model call enters through one gateway and climbs only as high as the task demands.
| Approach | Est. / month |
|---|---|
| All-frontier, everything | ~$400 |
| Tiered — 10% planner + 90% workers | ~$56 |
| Tiered + batch jobs | ~$32 |
Self-reported manual tracker — there's no live billing feed into this page, so type in what each bucket has cost. Saved in this browser only.
All three laptop jobs are done. Nothing is waiting on you at the machine.
The tunnel is up at https://pacemaker-flagstone-cursive.ngrok-free.dev, forwarding to Hermes on :8642, and the rotated API key is held in the secure vault (custom.hermes-ngrok). This is now the standing access path — just keep the ngrok window open on the laptop.
The 6 TB Seagate (D:) is mounted again, and the rclone backup to Google Drive is running, skipping anything already on Drive. Leave the laptop on and plugged in while it works through ~270 GB — and don't wipe D: until the backup is confirmed complete.
npm/npx caches and temp files cleared, Recycle Bin confirmed empty: C: is up to 2.62 GB free. Still tight — if it dips again, the staged TO_DELETE_STAGING cleanup is the next lever.