1. Discuss
“Use SQLite for the local prototype so contributors do not need a database service. Revisit it before multi-user hosting. Add a migration test before changing the schema.”
Turn the conversation you can see into a project archive. Keep a local Markdown copy, upload it to your Kireo account, and search for the decisions when you need them.
Free to try during beta · Your account, your memories
Decisions, next steps, and the reasons behind them.
Install the plugin and configure your key before running compact
Sample walkthrough · no account needed
This is a fixed, illustrative example. It does not run AI, upload anything, or search your data.
“Use SQLite for the local prototype so contributors do not need a database service. Revisit it before multi-user hosting. Add a migration test before changing the schema.”
my-app.md
We chose SQLite for the local prototype so contributors can run it without a database service. Revisit this before multi-user hosting.
With the installed plugin, you ask your assistant to search your saved archive. It does not automatically restore a previous chat.
Try it with your own project →Summarize the visible discussion into a Markdown archive named after your project directory.
Ask your connected assistant to search saved decisions. New chats do not load archives automatically.
Run kireo index and semantically search your own codebase from Claude Code or Cursor.
Choose Claude Code or Codex and install its plugin.
Configure a key for your own Kireo account.
Archive the discussion, then ask your assistant to find a decision.
The plans below describe standard limits. During beta, allowances may be higher; check Usage in your account for your current limits.
Your personal memory layer across every AI tool.
Start freeEverything in Free, plus semantic search over your own code.
Get startedRun kireo index locally — your repo becomes searchable in Claude Code & Cursor.
14-day no-questions refund on any paid plan.
Try one archive, then tell us what got in your way.
Share feedback