You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d5edfd4
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,6 +60,7 @@ needs to be useful:
60
60
| ⚡ **Automations**| Work starts when it happens: on a schedule (“weekdays at 08:00”), when something happens in a connected app (a new email, a Slack message, a calendar event, a Notion update), when a condition you describe comes true (“competitor pricing changes”), or when a webhook is called. Describe it in one sentence and Godmode sets it up. |
61
61
| ⏰ **Follow-ups**| When a task needs waiting — a reply to an email, a delivery, a build, office hours — the agent sets itself a time and picks the chat up again on its own, with all the context, like a coworker who says “I'll check back tomorrow at 10”. You see when it comes back and can continue now, move it or cancel it. |
62
62
| 🤝 **Delegation**| Agents hand tasks to peer agents or spawn short-lived subagents. The Godmode agent can list, check, create and configure all agents. Follow a handoff both ways: open the teammate's chat from the handoff card, and jump back to the chat that asked from there. |
63
+
| 🧰 **Claude Code & MCP**| Build your team from the terminal: connect Claude Code — or Cursor, Codex, Claude Desktop, any app that speaks MCP — and say *“Create a Godmode agent that…”*. One click in **Settings → Claude Code & MCP** adds Godmode to Claude Code for every project. The app gets Godmode's own management tools (agents, automations, tasks, runs, VMs) through a key of its own, with full or look-only access; scripts reach the same tools with `godmode call`. Passwords, 2FA codes and settings stay out of its reach. |
63
64
| 🏢 **Team & org chart**| Give every agent a role (*Bookkeeper*, *Research analyst*) and a lead; agents are told who does what and who they report to, so work goes to the right one. The **org chart** shows the whole team with what each is doing right now. Status tells the truth — *Working in 2 chats*, *Queued*, *Needs your answer*, *Last run failed* (one click opens the run) — and each agent's page shows **what's on its plate**: live work, waiting chats, board tickets, follow-ups and its next automations. Duplicate an agent in one click; messages from automations, the board or other agents are labelled as such, never shown as yours. Or start a **whole team** in one click — *Back office*, *Marketing*, *Sales*, *Product & QA*: a lead and its reports, wired up, with their schedules. |
64
65
| 💰 **Spend & budgets**| See what the team cost today, this week, this month and all time — per agent and per kind of work, booked when it was spent. Give the team (and any agent) a **monthly budget**: you're told at 80%; at 100% automations, follow-ups and board tickets are **held, not failed** — they continue by themselves next month or as soon as you raise the budget, or right away when you click *Let it run*. Chats you start always run. |
65
66
| 📨 **Message queue**| Keep writing while an agent works: your messages wait in a queue above the message box, and the agent picks them up at its next step and works them into what it is doing — a correction lands right away, an extra request comes after the current step. Reword or remove a queued message until it is picked up, or hit *Send now* to interrupt. |
@@ -143,6 +144,10 @@ needs to be useful:
143
144
<td><img src="docs/screenshots/phone-pairing.png" alt="Connect a phone by scanning a one-time QR code" /><br /><sub><b>Connect a phone</b> — scan a one-time code; the phone gets its own key</sub></td>
<td><img src="docs/screenshots/connect.png" alt="Settings: Claude Code and MCP, with the connected apps and the tools they can call" /><br /><sub><b>Claude Code & MCP</b> — connected apps, their access and the tools they can call</sub></td>
149
+
<td><img src="docs/screenshots/connect-claude-code.png" alt="Claude Code connected in one click, with a first prompt to try" /><br /><sub><b>One click</b> — Godmode adds itself to Claude Code; ask for an agent in your next session</sub></td>
150
+
</tr>
146
151
<tr>
147
152
<td><img src="docs/screenshots/messaging.png" alt="Slack, Telegram and Teams bots connected to agents" /><br /><sub><b>Messaging</b> — talk to agents from Slack, Telegram and Microsoft Teams</sub></td>
148
153
<td><img src="docs/screenshots/messaging-bot.png" alt="A bot's access requests, agents and who may use it" /><br /><sub><b>Bot settings</b> — approve people, pick agents, see every chat</sub></td>
@@ -253,6 +258,27 @@ and Screen Recording on its screen if agents should use apps there — the runne
253
258
runner: `godmode runner status`, `godmode runner pair` (a new pairing code to paste under **Add runner → Enter a
254
259
pairing code**), `godmode runner uninstall`.
255
260
261
+
### Claude Code & other AI tools — set Godmode up from your terminal
262
+
263
+
1. In Godmode open **Settings → Claude Code & MCP → Connect Claude Code**. Godmode adds itself to Claude Code on this
264
+
computer as an MCP server, for every project.
265
+
2. Start a new Claude Code session and ask: *“Create a Godmode agent that checks our competitors' pricing every Monday
266
+
morning and sends me a summary.”* The agent, its instructions and its schedule show up in Godmode.
267
+
268
+
**Connect another app** gives any other MCP client (Cursor, Codex, Claude Desktop…) its own key, with the config to
269
+
paste. A key either sets up and steers (agents, automations, tasks, VMs) or only looks; remove an app in the same place
270
+
and its key stops working. The same tools work from a shell, for scripts:
271
+
272
+
```bash
273
+
export GODMODE_CONNECT_TOKEN=gmc_… # the key from Settings → Claude Code & MCP
274
+
godmode tools # what the key can do; `godmode tools agent_create` shows the arguments
godmode mcp # the MCP server itself (stdio) — what the apps start
277
+
```
278
+
279
+
`godmode` here is the core binary (in the desktop app: `Godmode Bot.app/Contents/MacOS/godmode-core`; the dialog shows
280
+
the full path). Inside Godmode nothing changes: the built-in *Godmode* agent creates and manages agents from any chat.
281
+
256
282
## ⚡ Quick start
257
283
258
284
1.**Onboarding** — pick a vault passphrase (enable *Remember on this device* so routines run unattended).
@@ -404,6 +430,13 @@ Every run is committed, so you can see exactly what an agent learned and did —
404
430
set of routes: no logins, 2FA codes, backups, integrations, settings or folders, and only screens shared in a chat
405
431
can be controlled. A paired phone can still ask agents to act on your computer — remove a lost phone in
406
432
Settings → Phone, and turn on *Require Face ID* in the app.
433
+
-**Connected apps** (Claude Code, other MCP clients) get a key of their own (stored hashed) that opens only the
434
+
management tools of the MCP gateway: no passwords, 2FA codes, settings or files. They see which logins exist (names
435
+
and usernames) and what agents were asked and answered. They act as the built-in agent and inside its limits — an
436
+
agent they create can use saved logins but not read them, can't manage agents and can't control this computer until
437
+
you allow it. Every change and every refused call is in the audit log; removing an app cuts it off at once. A key
438
+
that sets up and steers can still create agents and automations that act with your logins: connect only apps you
439
+
trust, and give the others a look-only key.
407
440
408
441
-**Runners** pair with a one-time code and pin each other's keys; the link is end-to-end encrypted (X25519, AES-256-GCM)
409
442
and the runner's API never listens beyond its own loopback. A paired Godmode gets your vault key on the runner so
@@ -445,6 +478,7 @@ See [CONTRIBUTING.md](CONTRIBUTING.md).
445
478
-[x] Runners: another Mac does the work of a chat while this one sleeps — one install command, encrypted link, setup copied, live view
446
479
-[ ] Runners on Windows and Linux, tasks of the board on a runner, VMs copied to a runner
447
480
-[x] Godmode Cloud (optional, self-hosted): your computer in any browser, phones without Tailscale, accounts and plans
481
+
-[x] Claude Code & MCP: Claude Code and other AI tools create and manage agents, automations and tasks from outside, plus a `godmode` command line for scripts
Copy file name to clipboardExpand all lines: SECURITY.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,13 @@ We aim to acknowledge reports within 72 hours and to ship a fix for critical iss
35
35
-**Re-authentication for sensitive actions**: revealing a password, enabling "reveal" for an agent (or as default) and
36
36
turning on "remember this device" need a short-lived grant confirmed with your vault passphrase — a stolen API token
37
37
alone is not enough.
38
+
-**Connected apps** (Settings → Claude Code & MCP): Claude Code and other MCP clients reach Godmode with a key of
39
+
their own (`gmc_…`, stored as a SHA-256 hash, shown once). The key opens the management tools of the MCP gateway and
40
+
nothing else: no vault tools, no browser, no settings, no dashboard API. Even a look-only key sees which logins
41
+
exist (names, domains, usernames — never a password or a code) and the prompts and results of runs and tasks. Calls
42
+
run as the built-in agent with the limits below, keys are either full or look-only, changes and refused calls are
43
+
audited as `connector.call`, and keys are left out of backups. Phones and Godmode Cloud can't create or remove keys. A full key can create agents and automations that
44
+
later act with your saved logins, so it deserves the same care as the app itself.
38
45
-**No privilege escalation through agents**: agents that create or edit agents cannot grant reveal access, change
39
46
workspaces, browser profiles or out-of-scope integrations. A task an agent hands to a reveal-mode agent runs
40
47
without raw secrets unless the caller reads raw secrets itself and the target is global or in the caller's workspace
0 commit comments