Daily Triage Agent

~2 min read

Daily Triage Agent

A common pattern: notes land in Inbox/ and you want an agent to read them, summarize, and propose where each one should live. Triage proposes, you approve, agent applies.

Setup

A top-level Inbox/ folder where new notes accumulate (the in-app New Note button defaults to “the current folder,” so quick capture from Inbox/ lands the next note next to it).
Optional but recommended: a scoped API key. lettuce keys add --label triage --scope all --allow Inbox,Areas,Projects,Reference,Archive limits the agent to your destinations, so a runaway can never write outside them.
Optional: add your canonical destination folders to AGENTS.md so the agent uses your vocabulary.

Prompt

@claude Triage every note in Inbox/. For each one:

Summarize in one sentence.

Suggest 2-3 tags from the vault’s taxonomy.

Propose a destination folder (Areas, Projects, Reference, or Archive).

Don’t move anything yet. Reply with a table.

Tools the agent will use

Tool	Why
`list_notes(path: "Inbox", recursive: true)`	Enumerate the inbox.
`read_note(path)`	Read each note’s body.
`read_outline(path)`	Cheaper than `read_note` when you only need structure.
`list_tags`	See the existing taxonomy so suggestions reuse your vocabulary.
`list_folders`	Know the destination options.

After you approve a destination plan:

Trust + safety

The first pass is read-only — no writes until you say “apply”.
Every move_note is attributed (agent: claude or similar) and revertible from the agent timeline pane.
Scoped key prevents the agent from writing outside your destinations even if you forget.

Example output

Note	Summary	Tags	Destination
`Inbox/scratch.md`	Q1 roadmap discussion	`#project/web`, `#planning`	`Projects/Active`
`Inbox/idea-7.md`	Newsletter format experiment	`#writing`, `#idea`	`Areas/Writing`

You eyeball the table, reply “Apply”, and the agent calls move_note per row.