> **DRAFT, UNTESTED for Parts 0, A, C and E (9 Oct).** Part B and Part D passed a real-Hermes smoke run on p2box on 6 Oct. Not exercised yet: the WhatsApp link (needs a browser on the box and a phone to scan), reader scripts and test notes.

> **For you, the member:** you never need to read this file. Drag it onto your brain folder, then tell Hermes: Read connect-to-capture.md in my brain folder and connect my WhatsApp.

# Connect your tools, part 2 (Day 9): WhatsApp, your tools, your old notes and your meetings, into your capture

**If you are Claude Code on the member's laptop, stop here.** This pack is for Hermes on the member's box. Tell the member in one line: "This one is for Hermes: drag it onto your brain folder, then in the Hermes app say: Read connect-to-capture.md in my brain folder and connect my WhatsApp." Do nothing else with this file.

**For Hermes.** The member dragged this file into their brain folder. First, link the member's WhatsApp through WhatsApp Web on this box. Then hand the Capture bot every tool on `_System/tools-list.md` (made on Day 8) so each joins the **Nightly chat capture** it already runs at 23:00 (Day 5). You add **no new scheduled job**. Test each tool once, now, and report. If the member has a meeting recorder, add it to the same capture (Part E).

## The member's sentences

| The member says | You do |
|---|---|
| Read connect-to-capture.md in my brain folder and connect my WhatsApp. | Part 0, then report |
| Give my Capture bot my tools list and start capturing. | Parts A to D, then report (the member pours in old notes first, lesson 2) |
| Connect [tool] to my nightly capture. | Parts A to C for that one tool |
| Connect my [recorder] and add my meetings to my capture. | Part E, then report |

## Rules for this pack

- Keep this pack: move this file into `_System/packs/` (replace an older copy) and add one line under `## Packs you have` in AGENTS.md naming the sentences above and this file.
- **Keys:** read them only from `~/.hermes/.env` by name, inside the command that uses them. Never print, copy or repeat a value. A key that is missing: tell the member, in one line, to tell Claude Code on the laptop "Add a key for [tool]." Never ask for a key in chat.
- **Sign-ins:** where a tool connects by signing in, start the tool's own sign-in flow and give the member the link or the steps; a password is typed only by the member, on the tool's own page, never into the chat.
- The capture rules are the Capture bot's own (one source = one whole note, title naming the real subject, source line; keep decisions, promises, facts, ideas, lessons; skip small talk, setup chatter and anything secret). Do not restate or change them here.
- Report in plain words, no file paths unless asked. If stuck: "Stuck? Post your screen in the community, and bring it to the weekly call (link on the course page)."

## Part 0: connect WhatsApp (lesson 1)

A personal WhatsApp number has no connector, plugin, MCP or API. The way in is WhatsApp Web on this box, the same page the member would open on a laptop.

1. **A browser on the box.** If this box has no browser Hermes can drive, install Chromium for it (on a VPS it runs without a screen). Use one browser profile for the Capture bot that survives restarts, so tonight's capture and every later one use the same WhatsApp link. Check Hermes's own browser docs for the current way on this box.
2. **Open web.whatsapp.com** in that browser.
3. **Show the QR code:** take a screenshot of WhatsApp's QR code and show it to the member in the Hermes app. Tell them: "On your phone, open WhatsApp, Settings, Linked devices, Link a device, and scan this." If the code expires before they scan, show the new one.
4. **Prove it:** read the newest chat's title and tell the member the title only, not its content.
5. On the WhatsApp row of the tools list, set Route to `WhatsApp Web` and Status to `connected`. If WhatsApp is not on the list yet, add it under Fulfilment.
6. Any other tool whose Route is a web page (`browser`) on the tools list (a tool whose only way in is its own web page): same steps with its own page; a password is typed by the member on that page, never in the chat.

Report: "Your WhatsApp is linked. Next, say: Give my Capture bot my tools list and start capturing."

## Part A: one reader per tool

For each tool on the tools list: use its Day 8 route to read the last 24 hours (its Hermes plugin, its MCP, its API with the key from the locked drawer, its CLI, or for WhatsApp and any `browser` row the logged-in browser from Part 0). Write a short reader script into the Capture bot's `scripts/` folder (`<capture-bot home>/scripts/read-<tool>.sh`) that prints the last 24 hours as plain text (who, when, what), one thread or conversation per block, and nothing else. A tool that cannot connect by connector, plugin, MCP or API/CLI: set its Route to `browser` and run Part 0 step 6 for it.

## Part B: join the nightly capture

1. Add one step to `_System/jobs/nightly-chat-capture-prompt.md`, after the chat export step and before the notes are written: "Run each `read-<tool>.sh` in your `scripts/` folder; treat each thread or conversation it prints like a chat: one note per meaningful one, with a source line naming the tool and the date."
2. Update the job's row in the jobs table: the What it does column now names the connected tools. The time (23:00) and Run by (Capture bot) do not change. Do not create another job.

## Part C: test each tool now

Run each reader once and write at most one note per tool, the newest meaningful thread, into `01. Inbox/agent-drops/` with the usual capture rules. Set the row's Status to `connected` (worked) or leave it with the error in one plain line. A tool that cannot connect by connector, plugin, MCP or API/CLI: set its Route to `browser` and run Part 0 step 6 for it. Then show the member the tools table: a tick for each tool that worked, or what is missing in one plain line.

## Part D: check

Start a new session yourself and answer "What runs on its own?" from the jobs table: still the one Nightly chat capture at 23:00 (and nothing else unless the member made it), now naming WhatsApp and the connected tools.

## Part E: your meeting recorder (optional, lesson 4)

The member says "Connect my [recorder] and add my meetings to my capture." (or names it: Plaud, Pocket or another). A meeting recorder is a small device that records meetings in person or on calls; its phone app sends the audio to the recorder's own cloud, which writes a transcript and a summary. The Capture bot can only reach a recorder whose cloud offers a way in.

1. **Check the recorder.** Ask the member which recorder they have if they did not name it. Look up, on the recorder's own site and docs, whether its recordings live in a cloud with a connector, plugin, MCP or API. If recordings stay only on the device or in a phone app with no way in, tell the member plainly in one line: "Your [recorder] keeps its recordings on the device, so I can't reach them. If you change recorders, pick one with a cloud and an MCP." Stop Part E there.
2. **Pick the route, in this order** (the same order as Day 8): a Hermes connector (Capabilities, then Connectors in the Hermes app; `hermes mcp catalog` on this box), then a Hermes plugin (`hermes plugins search <recorder>`), then the recorder's own MCP, then its API, then the browser route from Part 0. Plaud publishes an official MCP (`@plaud-ai/mcp`, run with `npx`; see docs.plaud.ai). For any other recorder, check its site for an MCP or API (for example Pocket documents both). Add it as an MCP server in Hermes's own config the way Hermes's docs say for this box.
3. **Sign in once.** The recorder's sign-in opens a page in a browser. This box may have no screen, so show the member the sign-in link in the Hermes app for them to open and approve; a password is typed only by the member, on the recorder's own page, never in the chat. Where the recorder uses a key instead, the key goes in through Claude Code on the laptop ("Add a key for [recorder]."), and you read it from `~/.hermes/.env` by name.
4. **Test-read.** Read the newest recording and tell the member its title only.
5. **Join the nightly capture.** Write `read-<recorder>.sh` (or the MCP call) for the Capture bot, as in Part A, that prints every recording new since the last run: one block per meeting with its title, date, the recorder's summary and the whole transcript. Add it to the same 23:00 Nightly chat capture step from Part B; no new job. Each meeting becomes ONE whole note in `01. Inbox`: a title naming the real subject of the meeting, a source line (the recorder's name, the recording date), the summary, then the whole transcript (a very long transcript goes whole into `08. Sources` with the one Inbox note pointing to it, as the Capture bot already does). Keep a watermark in `_System/state/` (last recording captured) and move it only after the note is written, so a rerun makes no duplicates.
6. Add the recorder to the tools list (Route, Status `connected`) and name it in the jobs table's What it does column.

Report: "Your [recorder] is connected. Newest meeting: [title]. From tonight, every meeting you record lands in your Inbox as one note."

## Report back

1. "Connected to your nightly capture: [tools]. Still missing a key or sign-in: [tools]."
2. One line per tested tool: what it found, and the title of its test note.
3. If a recorder was connected: its name and the newest meeting's title.
4. "Nothing new runs on its own: your 23:00 capture now reads these tools too. Tomorrow your Link, Organise and Signal bots start running every night after it."