Working with Pages
A Miki page is a document AI writes from your notes and keeps current as those notes change. You describe what you want in plain language; AI decides which notes are relevant and synthesizes them. See [1] for how pages differ from notes.
Creating a page
From Organize, create a new page and give it two things:
- A title — "Sourdough", "House renovation", "What I'm learning about Rust".
- Instructions — what this page should collect and how to present it, in ordinary language. "Everything about my sourdough experiments, newest first, with what worked and what didn't." "A chronological timeline of the renovation, one line per event."
Instructions are where the leverage is. The same set of notes produces a very different page depending on what you ask for — a summary, a timeline, a comparison table, a FAQ, a set of open questions. It's worth being specific.
A brand-new page starts empty and out of date. Nothing runs automatically: click Refresh and AI will find the relevant notes and write the page. See [2] for what that costs and the other ways to trigger it.
The two views: Page and Notes
A page leads a double life — a finished article, and the collection of notes behind it. Two tabs switch between them:
Page shows the AI-written result, rendered as an article with citations back to source notes. There's a button to copy the raw markdown if you want to take it elsewhere.
Notes shows the underlying notes as cards, in three sections:
- Pinned — notes you attached by hand. AI never removes these.
- Referenced — notes the current page text actually cites.
- Other associated — notes AI matched to this page but didn't end up quoting.
The tab you're on is part of the address, so a link to the Notes view stays on the Notes view when somebody else opens it.
Pinning notes
AI decides which notes belong to a page, and mostly it's right. When it isn't, pinning is the override.
Two ways to pin: drag a note from the notes list onto the page, or use the + next to the Pinned heading. Adding a page from the note's side pins it too.
A pinned note is permanent — no AI run will ever drop it. An unpinned note you remove by hand may be re-added by the next match run, which is exactly why the pin exists. If you keep removing the same note, pin the ones you do want instead.
Refreshing
Refresh brings a page up to date. It runs in two stages: find the relevant notes, then write the page from them. Each stage has a mode:
- Auto (the default) works incrementally — it looks at what's new or changed and adds to what's already there. Fast and cheap.
- Full refresh re-evaluates everything from scratch: re-finding every relevant note, or rewriting the whole page. Slower and costs more.
Auto is the right answer almost always. Reach for a full refresh when you've substantially changed a page's instructions, or when the page has drifted and you want a clean slate. Both modes live under Advanced Settings in the refresh dialog.
Refresh All, from the Organize page, refreshes every page in the current space in one go.
Staleness
Small amber markers appear on notes, page cards, and pages themselves. They mean "this changed since AI last processed it" — either notes underneath moved, or the page text is older than the notes it's built from. They're a hint about where a refresh is worth spending on, not a warning.
Updates are user-triggered. Nothing refreshes on a schedule today.
Layered instructions
Three levels of instruction stack, from general to specific:
- Personal AI Instructions (Account → AI Instructions) apply to every one of your personal pages. Good for standing preferences: your writing style, your timezone, the fact that "the boys" means your kids.
- A group's description does the same job for that group's pages. It's both a description for humans and instructions for AI.
- The page's own instructions are the specific brief.
The more general layers are worth filling in once — they save you repeating yourself on every page.
Editing a page
You don't, really. A page's text is AI's output, so the way to change it is to change what goes in: edit the notes underneath, or rewrite the page's title and instructions, then refresh.
When you genuinely want to take the wheel, use Save as Note. That snapshots the page's title, instructions, and current text into an ordinary note you can edit freely — and which AI will no longer maintain. You can delete the page at the same time if the note is replacing it.
Limits worth knowing
Page length. A page is generated up to roughly 16,000 tokens (about 12,000 words). Past that the text is cut off and a warning appears at the top. Three fixes, in order of how well they work:
- Narrow the page. Tighten the instructions to a specific angle rather than everything.
- Split it. Instead of one "Work Projects" page, make one per project. Notes can feed several pages, so nothing gets duplicated.
- Remove less relevant notes so AI concentrates on what matters.
About 50 pages per space. Beyond that, a page can fall outside the search AI uses to find candidates, and a legitimately related note may quietly lose its link. Pinned notes are never affected. If you're near the limit, prefer fewer, broader pages — or a separate group.
Instructions are assumed to be stable. Routine refreshes only ever add — they won't remove associations that no longer fit. So if you rewrite a page's instructions to mean something substantially different, run a Full refresh to clear out what no longer belongs, or just create a new page and delete the old one.
Publishing
A page in a public group is readable by anyone, at a friendly URL you choose. That's how this documentation is published. See [3].