Dates below are when something shipped, oldest first — the rail runs forward in time. Nothing unshipped carries a date: we would be guessing, and a date on a page like this reads as a promise — so in the two groups below Shipped, order is intent rather than schedule. Last reviewed 15 Aug 2026.

Shipped

• Jun 2026

  The knowledge base and skills

  Search and capture over knowledge that persists between sessions, and shared procedures your agents follow. Both were already working at the first commit in the repository, so this is the earliest month the history can prove rather than the month they were built.

• Jun 2026

  Handoffs

  One agent hands work to another - send, reply, and an inbox that holds it until the recipient next connects.

• Jun 2026

  Summaries with a source on every claim

  Everything captured about a subject is gathered and condensed into one compact summary, with each statement carrying a link to where it came from. When a source changes, the summary is rebuilt.

• Jul 2026

  Multi-user support

  Several people, each running their own agents and clients, working against one shared Vault.

• Jul 2026

  Search learns from what agents report back

  When an agent says a result was useful or useless, that changes what surfaces next time.

• Jul 2026

  Entity knowledge map

  Brain tracks the things your knowledge is about - a system, a service, a person - and how they connect, so a question about one can start from its neighbours.

• Jul 2026

  Vaults, and private ones that stay private

  Knowledge is split by project, product or client, so one client's work stays out of another's answers. A personal vault you are not on behaves as though it does not exist - no results, and nothing to tell you it is there.

• Jul 2026

  Sign in with Google or Microsoft

  Use an account you already have. No Levirge password to create, and none for us to store.

• Jul 2026

  Self-serve API tokens

  Create and revoke your own access tokens, without asking us.

• Aug 2026

  Hosted and cloud inference lanes

  A switch for where the AI models run. Hosted mode uses machines Levirge owns, with no outside provider involved; cloud mode uses third-party models, when speed matters more than keeping everything in one place.

• Aug 2026

  Who captured what

  A document records the person whose agent captured it. A fact asserted by a single document inherits that; once a second document asserts the same fact it has no single author, and a summary written from many documents never does - so those point back at the documents instead. Nothing is backfilled: anything captured before this reads as system.

• Aug 2026

  Obsidian plugin

  Edit the same knowledge in Obsidian that your agents read. Your changes go up, theirs come down, and if both sides changed, their copy is parked beside yours instead of overwriting it.

• Aug 2026

  Contradiction detection

  When a new entry says nearly the same thing as an existing one in nearly the same words, the two are compared and the newer can retire the older. Reworded contradictions are not caught - only close matches are compared.

• Aug 2026

  Date-windowed browsing

  Ask what changed between two dates and get all of it, in order, with a stable list you can page through. Everything in the window, not the closest matches - which is what makes "what did we learn this week" a question with a complete answer.

• Aug 2026

  Reminders

  A dated note an agent can ask about: what falls due in the next 30 days. Brain answers the question - it does not email or alert anyone, so something has to be scheduled to act on the answer.

• Aug 2026

  Live inbox handoff notifications

  An agent watching its inbox is woken the moment work is handed to it. If it is offline the message waits, and each one arrives once, oldest first - so an agent that goes down misses nothing.

• Aug 2026

  Scoped access tokens

  A token can be limited to the Vaults you choose, and made read-only, so the token a CI job carries reaches only what that job needs. Scope only ever narrows: a Vault granted to you later does not widen a token issued before it, and losing access to a Vault shrinks the token too. A token cannot create further tokens. Tokens issued before this keep working and are listed as unscoped, so what is left to narrow is countable.

In build

• In build

  Review what agents wrote

  See what changed and undo it, the way you would review a code change.

Designed, not started

• Planned

  Git-backed Vaults

  Each Vault mirrored as readable Markdown files in a git repository you hold - so you can see what changed, roll it back, and walk away with everything. Today the storage is ours, kept separate per customer, and there is no restoring from a copy you hold.

• Planned

  A copy in your own git repository

  Your GitHub, GitLab or own server holding a continuously updated copy, while we hold the working one.

• Planned

  Something that acts on due reminders

  A scheduled job that reads what is due and decides what to do about it - tell someone, act, or stay quiet. Yours to define, which is the point.

• Planned

  Cloud options for the last two inference models

  Two of the four inference models still need hardware of your own. Putting them in the cloud is the difference between needing a workstation and running on a small server.

• Planned

  On-Premise deployment

  Brain inside your own network. The on-premise section covers what that involves and takes registrations.

What this page will not do

No quarters, no delivery dates, and no feature described in the present tense before it exists. Shipped rows carry the month they shipped, taken from the repository history commit by commit rather than from memory. Where a feature predates the repository's first commit, the row says so in its own words rather than implying the date is exact. Nothing unshipped carries a date, because that would be a guess wearing the clothes of a commitment. If you need something here to be real by a particular date, talk to us — that is a commercial conversation, not a roadmap entry.