Use cases

Okto Neuron in use. Payloads included.

Each write-up follows one question from the first tool call to the answer, shows the shape of what comes back, and points at the bytes a reviewer would open to check it. Values in the payloads are illustrative; the key names are the real ones.

Use case · 01 One decision. Recalled with its byte range.

A team writes a decision into a Markdown note. Days later, an agent in Claude Code is asked about it, picks the right vault, calls ask with include_sources=true, and answers with the vault-relative path, the byte range, and the content hash of the block it read. When the note is edited, the changed fact supersedes the old claim on the next ingest. The provider-error branch is shown too.

Decision recall Byte-exact provenance Supersession synthesis_status

Tools: list_vaults · ask · remember · explore Read the walkthrough →

More walkthroughs are coming. Running Okto Neuron against a vault of your own and have a question it answered well, or badly? We would like to write it up.

Tell us about it ↗

Point it at your notes. Ask it something you already know.

Prerelease 0.3.0. Free to run locally. No account required.

Install locally See how an answer is grounded