Knowledge scribes

A scribe is a conversation you own that Knowledge starts for you. It follows a skill that ships with Knowledge, once or on a schedule, and saves what it finds to the viewed agent's store. Part of the Knowledge plugin guide.

Open Knowledge in the Control UI and select the Scribes tab. Scribes that are starting, on, paused, failing, or whose conversation is not found are listed under On. The rest are under Available, including a once scribe that is done, which can be started again.

The scribes

• Knowledge Consolidation files claims that maintenance left unlinked, creates pages for subjects that deserve one, supersedes status snapshots by their outcome, and records outcomes in page State. It runs on its own schedule: weekly on Sundays at 3:45 AM in your time zone by default, or nightly at 3:45 AM, after maintenance links what it can. Each run is an agent turn over every unlinked claim, so nightly uses more tokens. Maintenance itself never starts it.
• Learn from conversations saves the decisions, preferences, commitments, and lessons in your conversations. Ongoing runs check for newly finished conversations daily at 4:00 AM in your time zone. Conversations already learned from are skipped. Defaults are active conversations from the last 30 days.
• Learn from Granola turns each Granola meeting into a meeting page, updates the people, companies, and projects it discusses, and saves its decisions and commitments, through the Granola plugin. Ongoing runs check for finished meetings on weekdays at 10 AM, 2 PM, and 6 PM in your time zone. Meetings already in Knowledge are skipped, and a meeting still being recorded waits for a later run. It keeps a checkpoint page, Knowledge scribe checkpoint · Learn from Granola, so an interrupted run resumes. Defaults are your meetings (recorded by you or with you invited) from the last 7 days.
• Learn from Memory brings memory-core notes into Knowledge once. Memory itself is not changed.

The Granola plugin

Learn from Granola reads meetings with the tools of the Granola plugin, which connects to your Granola account through Granola's MCP server. The Scribes tab checks the plugin and shows one of:

Each control opens the plugin's page under Plugins, where you install it, turn it on, or sign in. Set up… stays disabled until Granola is connected. If the page cannot read the plugin's state (for example, without operator.read), it shows nothing and lets you start; a run without the plugin stops with Scribe status: failed and says the plugin is not connected.

The scribe keeps the meeting's Granola ID (the UUID in its notes.granola.ai/d/… link) on the meeting page. It retains the meeting notes and the full transcript as originals; a meeting without a transcript is not ingested.

Start a scribe

Select Set up…, Import…, or Turn on…, choose options, and start. Starting needs a connection with write access (operator.write).

The dialog's Prompt area shows the full message the page sends. It is generated from your choices; expand it to read or edit it before starting. Once you edit it by hand, changing a choice no longer regenerates it (the dialog says which it is), and Use generated prompt discards your edits. Start sends the text shown.

1. Knowledge creates a conversation titled Scribe · <title> for the viewed agent, or reuses the scribe's existing conversation (restoring it if it was archived).
2. It sends that conversation the prompt: what the scribe does, its settings as plain bullets, and numbered steps. No vault content is included.
3. An ongoing scribe creates one automation for itself and reports on. The Scribes tab then runs that automation once as its first run; the setup turn never runs it. If the page is closed when setup finishes, the first run starts the next time the Scribes tab loads. A once scribe does its work and reports back. Nothing is scheduled.

Scribes run as you, with your private access to the store, and use the agent's default model. Read everything a scribe did by opening its conversation. Ongoing scribes also appear on the Automations page.

Example prompt

Turning on Knowledge Consolidation with the weekly default sends:

Set up the Knowledge scribe "Knowledge Consolidation" in this conversation. Don't ask questions: nobody is watching this turn. This scribe consolidates Knowledge claims that name no page: it files each one on the right page, creates pages for subjects that deserve one, supersedes status snapshots by their outcome, and folds the outcomes into page State. The knowledge-claim-consolidation skill does the work on each run. Settings:- Runs weekly, Sundays at 3:45 AM America/Los_Angeles (cron `45 3 * * 0`). Steps:1. Call knowledge_status. Go on when the scope is private and writes are enabled, or the store is unprovisioned (...). Otherwise stop: ...2. With the automations tool, list automations including disabled ones and take those with declaration key `knowledge:scribe:claim-consolidation`. Remove each one owned by another conversation, ...3. Add the automation with the automations tool:   - name: Knowledge scribe · Knowledge Consolidation   - declaration key: `knowledge:scribe:claim-consolidation`   - schedule: the cron expression and time zone in the settings   - session target: `session:` followed by this conversation's session key (from Runtime)   - payload: an agent turn whose message is the run message below, exactly as written inside the fence   - delivery: none; failure alert after 2 failed runs   ...4. Get the automation and check that it targets this conversation.5. Don't start a run from this turn: a run started here is skipped when the turn ends. The Scribes page starts the first run.6. Report the automation's ID and next run time. End your reply with one line: `Scribe status: on — <one sentence: the automation and its next run>`. If a step fails, stop and end with `Scribe status: failed — <why>` instead. ... Run message: ```textScheduled run of the Knowledge scribe "Knowledge Consolidation". Don't ask questions: nobody is watching this turn. Steps:1. Call knowledge_status. ...2. Follow the "Scribe runs" section of the knowledge-claim-consolidation skill: consolidate every claim that names no page until none is left to decide. ...3. End your reply with one line: `Scribe status: on — <one sentence with counts: claims examined, linked, superseded, withdrawn and left>`....```

Each scheduled run receives the automation's run message. To change what later runs do, edit the scribe's automation on the Automations page: its message is the run message, and its schedule is the scribe's schedule.

States

The Scribes tab derives an ongoing scribe's state from its automation: whether it exists and targets the scribe's conversation, whether it is enabled, and its last run. Each scribe turn also ends its reply with a plain status line, such as Scribe status: done — read 3 files, saved 12 items. The states are on, done, and failed. The tab uses that line where the automation cannot tell: whether a once scribe is Done or Failing, and whether setup succeeded before the page starts the first run. It also shows the line's sentence as the result summary.

Controls

Open a scribe for its schedule, next and last run, model, failure alert, and recent runs. Learn from Granola also shows the Granola plugin's state as its source.

Controls need write access. Pause, resume, and turn off are rejected if the automation changed since the page read it; the page shows the error, and reopening the scribe shows its current state.

Limits

• The Scribes tab rereads scribe state about every 30 seconds while it is visible, so a setup result or a finished run can take that long to appear.
• Conversation counts and the MEMORY.md size come from Gateway reads. A count the Gateway cannot provide is left out rather than estimated.
• The tab reads status lines from the conversation's last 100 messages.
• An ongoing scribe's conversation is the session its automation targets, read by session key, so renaming it is safe. A scribe without an automation is found by its Scribe · <title> name; renaming that conversation means the scribe starts a new one next time.

Related

• Ingestion workflows
• Maintenance
• Control UI