Skip to content

Kolibri

Projects, tasks and pages that never wait for the network. This is the manual for using them.

Looking for one thing

Press / or use the search box above. The four reference pages — shortcuts, the quick-add syntax, the filter language and the glossary — are where the tables live.

Running the instance

This site is about using Kolibri. Installing it, backing it up, wiring up mail and reading the threat model live in the repository, under docs/. Getting an instance points at each.

Three things worth knowing before anything else

Section titled “Three things worth knowing before anything else”

Nothing here waits for the network. Every screen reads from a copy of the workspace on your own device. Opening a board, filtering it, typing a comment and dragging a card all happen at the speed of the machine in front of you, and they happen the same way with the wifi off. What you changed queues up and merges when you are back. Working offline explains what that means when two people edited the same thing.

Colour means status, not decoration. Overdue, blocked, done. If something in the interface is coloured, it is telling you something — which is why so little of the rest is.

An assistant can be a member of the workspace. Kolibri speaks the Model Context Protocol, so a model can read the backlog, file issues and move them through the workflow with exactly the permissions you hand it — including a read-only token, which is refused by every tool that writes. See connecting an assistant.