Notion in Your Coven, and the Comments Waiting on You

A comment that mentions you is a request with excellent manners and no deadline. It sits in a document you won't open again until someone asks, in a meeting, whether you saw it. AICoven now connects to Notion, and gathers the comments addressed to you, from Notion, Google Drive, and GitHub, into one place where you can't pretend you didn't see them.

Available in AICoven 3.1.0, out next week.

---

Connecting Notion

Notion sits in Settings → Connected Apps, described as Pages you choose, and that description is literal. When you sign in, Notion's own screen asks which pages AICoven may see, and those are the pages it can use. To change them, change AICoven's access in Notion.

Each coven can narrow that set under Pages in its Connections. Choose some and the footer says "Agents in Field Notes can use only these pages and the pages inside them." A coven with none chosen can't use any Notion page, which is how client work stays in the client's coven.

What agents can do with those pages

With Read, an agent can search pages by title and read them. A page outside what the coven allows is refused before it is read.

With Read and make changes, an agent can also create pages, add to the end of a page, and comment, as you, without asking first. The settings footer says as much, so nobody finds out by accident. No agent tool replaces or deletes text a page already holds. The one way to rewrite existing text is to edit a memory you saved from that page, below.

Every request goes through AICoven's API and is sent only while the coven's choice still allows it. When a run ends, AICoven reads back what the agent made and says when it couldn't check. These tools are offered on BYOK cloud providers and on Hermes and OpenClaw in compatibility mode; native Hermes runs and Workspace MCP clients don't get them.

Saving a page into memory

Every page a coven lists has Save to Memory. Before you confirm, it says how many memories the page makes, that a copy of its text is stored in AICoven, split by heading and encrypted as all memory is, and, in a shared coven, that every member can read it, including members who can't open it in Notion. Include the Pages Inside It, off by default, saves up to 50 sub-pages and picks up ones added later. When the page changes, opening the coven saves it again.

In a coven on Read and make changes, whoever saved a page can edit one of its memories, and the edit is written to that section in Notion first. If the section changed there meanwhile, nothing is written, and the app shows "This section changed in Notion. Nothing was saved. It says now:" with the current text. Agents edit under the same rules.

Two limits. A page Notion cuts short is refused rather than saved in part. And an agent can propose saving a Google Doc it has read, but not a Notion page; that one is yours to do.

Comments that mention you

On me and each coven's Tasks now have Comments in Notion, Comments in Google Drive, and Mentions in GitHub:

• Notion: open comments that @-mention you, on pages the coven reaches, up to 20 pages per check.
• Google Drive: comments that mention you or are assigned to you, on the files chosen for the coven, up to 20 per check.
• GitHub: issues and pull requests in the coven's repositories that mention you without being assigned to you.

A comment row shows who wrote it, where, and its words, with Mine, Not Mine, and Open in Notion (or Google Drive). The words are read for that screen and kept nowhere. Not Mine is remembered. Mine checks the comment is still open and addressed to you, then makes a personal task: "Comment from Maya on Launch plan", author and page, never the words. Task titles are stored as plain text, as every task title in AICoven is, so that name and title are too.

When a check can't read everything, the section says "Some Notion items may be missing: not everything could be checked this time." and removes nothing it already showed. Comments on a block inside a page aren't listed by Notion for the page, so they don't appear at all.

The post on GitHub and Linear tasks listed @-mentions as not gathered yet. That list is one item shorter.

Do it for me, and Talk it through

A comment task has Do it for me… and Talk it through, like any task. Do it for me… asks which agent should take it, then says what the work is. For a comment or a mention it asks: "Please tell me what this asks of me and draft a reply I could send". Talk it through opens a thread that starts with the task.

The caveat: the agent gets the task's title and link, not the comment's words, and no agent tool reads Notion or Google Drive comments. It can read the page around it; for the exact wording, paste it into the thread. And "draft a reply" is a request, not a lock. In a coven on Read and make changes, an agent can comment in Notion without asking first. If you want every reply to stay a draft until you send it, keep that coven on Read.