a git-native outliner
olai
An outliner that lives in files you own.
Indent, check off, search. Markdown sits beside the outline. Git records every edit.
nix run github:juspay/olai -- web path/to/outlines
one directory. a browser. that’s the whole install.
Compared to Workflowy and Dynalist
Same outlining model — indent, move, mirror, check off. The difference is where the data lives.
| Workflowy, Dynalist | olai | |
|---|---|---|
| Storage | A hosted database | Plain files in a directory you choose |
| Sync | Their cloud | git, or anything that moves files |
| History | In-app version history | git log |
| Search | Keyword, in their app | Filter the page you’re on, or search the whole directory |
| Source | Proprietary | Open source (AGPL-3.0) |
Outlines are ordinary files. The format spec is there if you want it.
What’s due
Dated work from every outline, on one page. Late things sit above today. A birthday isn’t a task — it stays on its day and never turns red. The calendar is a plugin.
5 days ago · Fri, Aug 7
Kitchen renovation
Today · Wed, Aug 12
Kitchen renovation
Sat, Aug 15in 3 days
Kitchen renovation
two quiet weeks
Fri, Aug 28in 2 weeks
Kitchen renovation
A file named for the day — 2026-08-12.md, anywhere in the directory — is that day’s note. Open the day and the note is on top, with everything dated that day underneath it.
Weekly chores come back as a fresh row on the next date, so eleven Mondays are eleven rows, not one row whose date kept moving.
Filter the page you are on
Type in the box above the outline and the rows that don’t match are hidden. Clicking a tag does the same. The query is in the page’s address, so you can send the filtered page to someone as a link.
Matches stay where they live. Ancestors stay so a bare title still makes sense.
Done, last week, a quoted phrase — the rest of the query language is in the search docs.
Type like an outliner
Click a title to edit it in place. Enter makes the next line. Tab indents. The rest is the usual outliner muscle memory.
| Enter | commit, and open the next line |
| Enter mid-line | split the row in two, there |
| Backspace at the start | join this row onto the one above |
| Tab / Shift+Tab | indent, or out again |
| Alt+Shift+↑/↓ | move a row among its siblings |
| ⌘+Z | take back your last edit here |
| ⌘+Enter | tick it off, or take that back |
| ⌘+⇧+Enter | walk the mark on: to do, then doing, then none |
| ⌘+⇧+D | duplicate the row, and everything under it |
| ⌘+⇧+M | move it under a row you search for, anywhere |
| Shift+Enter | write the note under it |
| Esc | drop what you were typing |
Off a Mac, ⌘ is Ctrl. The full map — dragging, the palette, pins, the inbox — is in the editing docs.
How it looks
Four palettes — two by day, two by night — and an unpicked page follows your OS. Press a chip; this page follows.
A coding agent edits your outlines with you
A chat opens on the row it is about, beside that row’s page. You keep typing while it works. It ticks off tasks and rewrites Markdown files, and you watch the page change. Git records both of you.
cabinets.md+3−2
+4 more lines
The page updates because the file on disk changed.
How to point an agent at a running olai is in the chat docs.
Plugins
The outline editor, the Markdown reader, the shell, chat, git, search — they are plugins. They show on one panel. Switch one off while olai is running; the rest keep going. The runtime is Cordis, a meta-framework of spatiotemporal composability. The paper is on arXiv.
▶Needs attention1
▶Agents4 on · 2 off
▶Notes19 on
▶Connections6 on · 1 off
▶Interface10 on
▶Your plugins2 on
▶Serverlaptop
Ask for one. Press ⌘K, say in one sentence what it should do, and an agent writes it while you watch.1 Read what it does, press Turn on, and it starts drawing in the page you are on. No reload, no install, no build.2 Your settings travel with your notes.3
my-notes/ ├── plugins/ │ └── hex-swatch/ │ ├── README.md what it does, for people │ ├── server.ts what runs on the server │ └── browser.tsx what draws in the page ├── _olai/ │ └── Settings.olai hex-swatch: on, approved ├── colours.olai └── kitchen.olai
Every plugin olai ships, and what each one does
Server and transport
| ws | The connection your browser tab uses to talk to the olai server. |
| mcp | The MCP server that coding agents connect to for olai's tools, how long it runs, and its session tickets. |
| web-app | Serves the browser app's files, separately from the browser connection and the MCP server. |
| vault | The directory olai serves: the one path every write goes through, the lock that keeps a second olai out, and the format settings. |
| settings | Settings for the whole directory, read from one Settings.olai file. |
| identity | Who is looking at the page: which request headers olai trusts, and the captured-by chip. |
| git | Records commits, and holds the commit and push settings. |
| search | Matches search queries, and what still works when search is switched off. |
| vault-plugins | The plugins a directory keeps in its own plugins/ folder: reading them, approving them, and their pages. |
Integrations
| chat | How a conversation is stored as a row, the chat-agent-session property, and the services chat offers other plugins. |
| kolu | Terminals from kolu: a terminal's row, a live view of it, the feed of terminals waiting on you, and messages to a conversation. |
| browsing | A Chromium browser you and your agents share: the page that shows it, shared sign-ins, who owns it, settings and safety. |
| odu | CI runs from odu: a chip on the row naming the run, a grid of its jobs, and messages to a conversation about runs. |
| xyne-spaces | Copies the messages plugins post into a conversation to a Xyne Spaces channel. |
| Gmail: connecting an account, reading and filing mail from a conversation, and acting on threads. | |
| journal | The calendar, a page for each day, and the agenda of rows that have a date. |
Browser UI
| ui-renderer | Draws the browser app with Solid, and lets plugins add parts to named places on the page. |
| layout | The page's frame: the sidebar column, the header and its health dot, banners, and the places where file viewers sit. |
| navigation | Page addresses, Back and Forward, which pane has focus, and the command palette. |
| tabs | Several pages open as tabs above the panes, each with its own Back and Forward. |
| sidebar | The column of files on the left, the narrow rail beside it, and the places plugins can add to them. |
| outlines | Outline pages: editing a row, and the commands on a row's menu. |
| markdown | Editing Markdown documents, their front matter, and headings. |
| files | Browsing the files in the directory, and creating new files from the browser. |
| pins | The pinned pages in the sidebar: their order, and the commands to pin and unpin. |
| capture | Quick capture: typing a row straight into the inbox, and the palette's prefix for it. |
| trash | Browsing rows you threw away, restoring them, and emptying the Trash. |
| alerts | Desktop notifications: asking for permission, the sound, and the mark on the browser tab. |
| preferences | The Preferences panel: what it holds, and how far each choice reaches. |
| theme | Colours, typeface and text size, stored per browser and set under Appearance. |
| plugin-inspector | The Plugins panel: switching plugins on and off, why one failed to start, and trying again. |
| link-preview | Read-only previews, kept up to date, of the pages that links inside olai point to. |
File kinds
| outline-olai | Which files are outlines (.olai), how they are read, and the one way olai writes them. |
| hypertext | Showing saved .html pages in a locked-down preview. |
| csv | Showing a .csv file as a table, read-only, with its first row as the headings. |
| hledger | Showing hledger accounting journals as transactions, balances and source. |
| image | Showing pictures, and serving the image file to the browser. |
Showing a .pdf file in your browser's own PDF viewer, read-only. |
Test fixtures
| test-layout | A replacement page frame built only from the public navigation parts. |
| test-counter | A tiny plugin showing that olai runs with no directory served at all. |
| test-palette | Adds entries to the command palette through the public interface. |
| test-page | Adds a page that the plugin draws itself. |
Git records your edits
Every edit is written to disk at once. Commit from the panel when you are ready, or turn on Auto-commit and olai makes one commit after fifteen quiet seconds.
┌─ Changes ─────────────────────────────────┐
│ olai: Outlines as a collection done │
│ · chat agent · 12m ago · 1a2b3c4 │
│ │
│ OUTLINES ───────────────────────────── │
│ ☑ roadmap.olai │
│ ✓ Outlines as a collection done │
│ ✎ Notes: one state, same line note │
│ + Kolu integration: auto-… created │
│ │
│ OTHER FILES ────────────────────────── │
│ ☑ README.md modified │
│ ☐ notes/scratch.md untracked │
│ │
│ 2 commits not on origin/master [ Push ] │
│ [ Commit 3 changes · 1 file ] │
└───────────────────────────────────────────┘
Commit messages start with olai, so the trail is easy to find. The rest is in the git docs.
Footnotes
-
The worked example is a morning agenda: from 7 in the morning it sends the rows that are overdue or due today into each node agent's conversation, once a day. Read the morning agenda. ↩
-
What you are left with is a folder in your own directory: a README anybody can read, and the code. Git records every line of it. Copy the folder into another directory and it arrives switched off, until a person there turns it on. ↩
-
A plugin you asked for keeps its settings in the same file as the plugins olai ships. A top-level row in
_olai/Settings.olainames each plugin; its properties choose how it behaves and whether it runs. The Plugins panel writes the same file. See the settings docs. ↩