A leaner layout for writing and presenting — trims the chrome around the outline and tunes Presenter mode for showing your work. Accent color and node text color are left untouched.
Also runnable from Quick Assist ("apply editor's choice") — same effect as clicking Apply. Applying always leaves an Undo that restores every setting it touched, until you use it or apply again.
Built for long-form structured documentation rather than presenting — full toolbar, full status bar, Decision Log and Tags front and center. The opposite instinct from Editor's Choice.
Also runnable from Quick Assist ("apply documentation mode"). Applying always leaves an Undo that restores every setting it touched, until you use it or apply again.
gist scope — create one here. Stored in this browser only, the same way your AI provider keys are.
added as an authorized JavaScript origin.
added as a redirect URI and Calendars.Read delegated permission granted.
_note attribute is written. Off: excluded from all of the above entirely, including the small "has a note/code" indicator dots — nothing in the PDF hints that a hidden note exists. Preview itself is unaffected; this only changes what an exported file actually contains.models:read scope. This is a fixed list — Sakura doesn't support adding another API endpoint, so a Content-Security-Policy can restrict outbound requests to these known providers rather than staying open to anywhere.
Turns off every optional feature above in one click, all at once — a stripped-down outliner with just the tree, nothing else competing for attention. This is the same on/off state as toggling each row above individually; it's a shortcut for all eleven, not a separate mode.
No separate Undo here — Restore Full flips every one of the above back on in one click. If you'd only turned a few of them off by hand before going minimal, Restore Full turns all eleven back on rather than reproducing that exact partial state, so re-toggle any you want off again afterward.
models:read scope; model IDs in the dropdown already include the required vendor prefix (e.g. openai/gpt-4o)horizontal (or row) to lay those stages out left to right instead — same idea as the numbered-leaf case above, just for stages that still have their own sub-detail, where structure alone can't tell "these are still parallel enough to sit in a row" apart from "these are sequential phases, stack them" (a top-level phase sequence and a same-shaped row of sub-steps look identical on paper). Each stage keeps its own subtree laid out normally beneath it either way — the tag only changes whether stages sit side by side or stacked. All-or-nothing: every sibling in the group has to be numbered for this to kick in, so one numbered aside among ordinary children doesn't pull the whole group into sequence mode by accident. Numbering style is flexible — "1.", "1)", "1:", "1 · ", "1 - " all count, since people number lists differently and the character itself isn't the meaningful partdecision, database (or db/datastore), excluded, ui, service, middleware, backend, external, actor, or note (a few spelling variants work too — see the source for the full list) sets that node's box type directly, the same shapes AI classification can produce — worth having even when AI didn't run at all, or when AI's own guess should be overridden for a specific node. An explicit tag always wins over whatever AI separately classified that node as. decision only sticks if the node genuinely has 2+ children, same structural guard AI's own decision classification uses, so a stale tag can't produce a diamond with no actual fork under itedge-label, placed as a sibling directly between two other nodes at the same outline level, contributes its own text as a label on the arrow connecting those two neighbors instead of becoming a box itself — useful for annotating a transition ("Passes: freight group & qty", "Returns: pricing values") the way a real system-integration diagram would. It never counts toward the 60-node cap and never gets its own layout slot; delete it (or remove the tag) to drop the label again.json export from another Sakura session or shared by a colleague — adding its tasks to the end of your list with its own Undo toast; any task whose text matches one you already have is flagged (not skipped) in that toast, since text alone can't tell a real duplicate from two tasks that just happen to read the same. Export opens a small menu with two formats: PDF prints the full list — Open then Completed — regardless of any active priority/status/due filter, so a filtered view never silently shortens the printout; Sakura To-Dos saves the same full list as a shareable .json file for a colleague to Import the same waytodo: scope still does thattodo: milk — and clicking a result opens the panel and flashes the match.json file — send it to a colleague and they bring it in with the header's Import button below, the same "share/import between Sakura users" pattern To-Dos and whole documents also use.json file exported by another Sakura user (the whole-list export below, or a single shared note) — unlike the .ics path, this doesn't skip likely duplicates, it imports everything and flags matches (same title and date as a note you already have) in the confirmation toast, so you decide what to do with them. Export saves every dated meeting note as one .ics calendar file — undated notes are skipped, since there's nothing to put on a calendar without a date. Each event gets a 30-minute default length (meeting notes don't track an end time) and lists attendees in the description rather than as real calendar invitees, since Sakura doesn't collect attendee email addressesPick how you want to get familiar. You can always revisit both from the Help menu.
Think of an outliner as turning your notes into a family tree, instead of a messy pile of paragraphs. Instead of writing left to right, you write in points that tuck inside one another. Here's why that makes life easier:
These are the only emoji that get swapped for a matching SVG line icon on section-header rows. Anything not shown here stays as plain emoji — that's the mix "Render section icons as SVG" warns about.
Every node ending in "?" — uncheck any you don't want. Only your outline selection starts checked if you had question nodes selected.
Paste text below — Q: / A: pairs (this also reads Sakura's own Q&A export format back in), or just a list of questions ending in "?" if there's nothing else to go on.
Shape, container, and flow direction for each node — adjust anything that guessed wrong, then generate. This never touches this document's own tags.
todo: milk