Archive a folder and everything in it

Archiving a folder used to hide the folder but leave every note inside it active, still showing up in your dashboard, recents, and search. Retiring a big import meant sweeping the notes up yourself with multi-select, list by list, and an AI assistant over MCP had it worse: one update call per note, each one echoing the full note body back. A thousand-note import from another notes app is a real case that landed in our feedback, and it was stuck exactly there.

Now archiving a folder means retiring it, contents included:

• On the web, the archive action sweeps the folder, its sub-folders, and all their notes together. Restore brings them back the same way, and if a restored folder sits inside an archived parent, the parent comes back too, so nothing ends up stranded.
• Over MCP, your AI can do it in one call: containers-update with archived: true, plus include_notes and include_nested to sweep the contents. The response returns how many folders and notes changed instead of streaming note bodies, so retiring a thousand-note import costs one tool call instead of a thousand.
• Over the REST API, PATCH /containers/:id/archive takes the same include_notes and include_nested options. Existing integrations keep the old flag-only behavior unless they opt in.

The sweep is deliberately gentle with your data. Archived notes keep their content, history, links, and attachments. Nothing about the sweep counts as an edit, so timestamps and version history stay exactly as they were, and everything is reversible from the Archive page.

Why this matters: a second brain accumulates finished projects and old imports. Retiring them should be one action, not an afternoon, and what your AI reads as "current" should actually be current.

Live now. No setup required.