Lovcode is live · free · last verified 25 Oct 2026 · viability monitor
Lovcode
Search your local Claude Code and Codex session history with four-granularity project memory.
If your recurring complaint is "I fixed this three weeks ago and can't find the command," Ataru is the most direct answer for Claude Code and Codex users. The four-granularity model plus stable session, message, and line IDs for every hit is real engineering, not a demo — and the explicit semantic-to-keyword fallback tells you the builder isn't overselling recall. Just know it is optional-depth software: you get nothing back until your own sessions are already on disk.
Verdict generatedVerified 6d ago · liveness 45/100 · cite: rightaichoice.com/tools/lovcode
- Developers running Claude Code or Codex across many repositories who need past sessions back
- Engineers working on machines that cannot send session data to a hosted service
- Teams that need an auditable local record of how AI-assisted decisions were reached
- Agent builders who want programmatic readback of original sessions by stable ID
- Developers using AI coding agents other than Claude Code or Codex
- Anyone looking for an agent that writes or reviews code for them
- Teams needing shared, multi-user access to a single session history
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Ataru if your session history is on a hosted agent or an IDE assistant whose transcripts you cannot point at locally, since the tool indexes the session files on your own disk.
No pricing model is visible in the material reviewed for this refresh, so cost is not a differentiator you can evaluate from this page alone. Weigh Ataru against the cost of the agent subscriptions it indexes, and against hosted memory tools that charge per seat for a shared view — Ataru's value proposition is local indexing rather than a billed service tier.
In short
Lovcode — Search your local Claude Code and Codex session history with four-granularity project memory. Best for Developers running Claude Code or Codex across many repositories who need past sessions back, Engineers working on machines that cannot send session data to a hosted service, Teams that need an auditable local record of how AI-assisted decisions were reached. Free to use.
What is Lovcode?
Lovcode — Search your local Claude Code and Codex session history with four-granularity project memory. Best for Developers running Claude Code or Codex across many repositories who need past sessions back, Engineers working on machines that cannot send session data to a hosted service, Teams that need an auditable local record of how AI-assisted decisions were reached. Free to use.
Ataru — shipped under the Lovcode slug at code.lovstudio.ai — indexes the session files your AI coding agents already wrote to your disk and turns them into a queryable memory layer. Reach for it when you half-remember the command, the diagnosis, or the reason a plan got changed three weeks ago and the answer is buried somewhere in a transcript you cannot grep. Instead of one blunt search box, it answers at four granularities: Turn (a single atomic message or tool record), Run (the turns inside one execution), Session (repeated runs in one conversation), and Project (sessions merged across a repository). Every hit carries a stable session, message, and line identifier, so you jump back to the original wording rather than a truncated paraphrase. The retrieval core is written in Rust and built on Tantivy with Jieba tokenization, which means Chinese phrasing, code snippets, package names, domains, and error strings all land in the same index — handy if your work mixes natural-language notes with pasted stack traces. Indexing is incremental: new messages get picked up as sessions land, and if a rebuild fails, the last usable index is kept instead of leaving you with nothing. Indexing never rewrites your source sessions; the index is derived data only. Search runs offline by default, and semantic recall is an optional enhancement that visibly degrades to keyword search when it is unconfigured or times out. There are three ways in, all sharing one retrieval contract: a desktop app for macOS, Windows, and Linux; a JSON CLI for headless indexing and search; and an Agent Skill that lets an agent verify the index, run a search, and read the original text back by stable ID. Install is via npx lovstudio skills add ataru-indexing and ataru-search — nothing gets uploaded. The project is Apache-2.0 with sources published. Positioning is narrow on purpose. Raw terminal scrollback and a generic IDE assistant are the alternatives, and neither does this job well: editor assistants
Key features
- Local session index across Claude Code and Codex history
- Four-granularity search: Project, Session, Run, Turn
- Stable session, message, and line IDs on every hit for exact readback
- Rust retrieval core using Tantivy with Jieba tokenization
- Chinese and code search in one index — identifiers, package names, domains, error strings
- Offline-first search; semantic recall as an optional enhancement
- Explicit fallback from semantic to keyword search when unconfigured or timed out
- Incremental index catch-up instead of full rescans
- Non-destructive indexing that never rewrites source session files
- Failed-rebuild protection that retains the last usable index
- Desktop app for macOS, Windows, and Linux with keyword, semantic, and hybrid recall
- JSON CLI for headless search and index maintenance
- Agent Skill for index verification and original-text readback by stable ID
- Shared retrieval contract across desktop, CLI, and Agent Skill
- Open source under Apache-2.0, installable via npx lovstudio skills add
Behind the verdict
Pick Ataru when your sessions already exist locally and you keep needing them again. That's the whole precondition, and it's a real one — install it on a fresh machine and the search returns nothing useful until you have run agents there for a while. Once you do, the four views earn their keep. A Turn search gets you the exact command. Project search gets you the arc of a decision across 26 sessions in one repo. We'd use Project most often for "why did we do it this way" questions and Turn for "what was that flag." The Chinese-plus-code indexing is not marketing filler. If your notes are partly in Chinese and partly pasted error strings and package names, a single Tantivy index with Jieba tokenization saves you from running two searches and merging results by hand. That combination is uncommon enough to be the deciding factor for some buyers. Where it bites: scope. Claude Code and Codex only. If your team runs something else, look elsewhere before you spend an afternoon on setup. There's also no shared, multi-user history here — this is your machine's record, not your team's. For collaborative memory, a general developer knowledge tool is the closer comparison; for an agent that writes the code instead of recalling it, an IDE assistant is the closer comparison. We like the honesty in the failure modes. Incremental catch-up rather than full rescans, non-destructive indexing, failed-rebuild protection that keeps the last usable index, and a semantic layer that degrades openly instead of pretending a keyword hit was a vector match. That last one matters more than it sounds — retrieval tools that hide their fallback are how you end up trusting a bad result. Open source under Apache-2.0 with published sources lowers the risk of adopting something early. You install from
Limitations
- Ataru is tied to Claude Code and Codex sessions — if that is not your agent stack, it has nothing to index.
- It is downstream of the agent, not a replacement: it does not write code, review diffs, or run tasks for you.
- Everything lives on your machine, so there is no shared team view and no hosted backup unless you build one.
- Usefulness scales with how much history you already have; a fresh install over an empty session directory gives you very little.
- Semantic recall is optional and, when unconfigured or slow, search drops back to keyword matching.
as of 2026-10-02
Researching Lovcode? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Lovcode still active?
Lovcode is live · free · last verified 25 Oct 2026 · viability monitor.
Viability score
How well maintained and how widely used is Lovcode? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →What do users say about Lovcode?
How we verified this
Every listed fact about Lovcode — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 25 Oct 2026. Pages mix model-assisted synthesis with human review; see how we verify.
Verification history
We have re-verified Lovcode 10 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed features, our verdict, who it suits, description, summary, pricing tiers, who should skip it, integrations
- — changed our verdict, who it suits, description, features, limitations, switching in, switching out, who should skip it, pricing fit, setup time, summary, use cases
- — changed who it suits, description, pricing tiers, features, summary, our verdict, integrations
- — changed SSL certificate
- — changed domain expiry, SSL certificate
- — changed who should skip it, switching in, switching out, description, pricing fit, setup time, features, hidden costs, pricing tiers, our verdict, summary
Showing the 6 most recent of 10 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Lovcode cost in 2026?
Lovcode: Free to use. Pricing last verified 25 Oct 2026.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Lovcode's pricing actually pencils out — and where peers do it cheaper.
No pricing model is visible in the material reviewed for this refresh, so cost is not a differentiator you can evaluate from this page alone. Weigh Ataru against the cost of the agent subscriptions it indexes, and against hosted memory tools that charge per seat for a shared view — Ataru's value proposition is local indexing rather than a billed service tier.
Has Lovcode's pricing changed?
No plan price for Lovcode has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Lovcode?
Pick Lovcode if you are Developers running Claude Code or Codex across many repositories who need past sessions back, Engineers working on machines that cannot send session data to a hosted service, Teams that need an auditable local record of how AI-assisted decisions were reached, Agent builders who want programmatic readback of original sessions by stable ID.
Look elsewhere if you are Developers using AI coding agents other than Claude Code or Codex, Anyone looking for an agent that writes or reviews code for them, Teams needing shared, multi-user access to a single session history, New users with no local session history yet — there is nothing to index on day one.
Skip it if Skip Ataru if your session history is on a hosted agent or an IDE assistant whose transcripts you cannot point at locally, since the tool indexes the session files on your own disk.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Lovcode actually fits — and what changes day-one when you adopt it.
A production error appears that you are sure you fixed before. You open the desktop app, search the error string, and get hits at Turn level with session, message, and line IDs attached — but you want the surrounding reasoning, so you move up to the Run and then the Project view for that repository.
Outcome: You land on the original command and the note explaining why it worked, instead of re-deriving it from scratch or grepping shell history that does not contain the conversation.
You need searchable history but cannot send transcripts anywhere. You install via npx lovstudio skills add ataru-indexing, let the Rust indexer catch up over the session files already on disk, and query with the JSON CLI.
Outcome: You get keyword search over your own history with no upload step, and if semantic recall is not configured, results degrade to keyword matching rather than failing silently.
You register the Agent Skill so your agent can confirm the index is current, issue a search, and read the matched message back by its stable ID.
Outcome: The agent works from original context rather than a paraphrase, using the same retrieval contract the desktop app and CLI use.
Use cases
- Find the exact command you used to fix a deploy failure three weeks ago by searching a half-remembered error string.
- Trace a full debugging arc by moving from a Turn hit up to the Run, Session, and Project level that contains it.
- Let an agent verify the index, run a search, and read the original session text back by stable ID instead of a summary.
- Keep a per-project record of how a repository's problems were solved so onboarding does not start from zero.
- Run headless indexing and search over session files on a machine without a GUI via the JSON CLI.
- Search across mixed Chinese and English prompts when your own notes and prompts are written in both.
Setup time & first value
How long it actually takes to get something useful out of Lovcode — broken out by persona, not the marketing-page minute.
Desktop: install the macOS, Windows, or Linux build and let the index catch up over existing session files — first useful search typically lands within the first session. CLI: npx lovstudio skills add ataru-indexing, then the search skill; usable in minutes on a machine that already has session history. Agent Skill: add both skills and point your agent at the index — the limiting factor is how
Switching to or from Lovcode
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From terminal scrollback: point Ataru at the session files already on disk so past sessions become searchable rather than scrolling off-screen.
- →From grep over shell history: shell history holds commands but not the reasoning around them; Ataru indexes the conversation that produced the command.
- ↗To a hosted team memory service: sessions stay in local files, so there is no export step from Ataru itself — you would re-ingest the originals.
Integrations
Tutorials & Learning
YouTube returned 6 videos for “Lovcode”, and we withheld 6: 6 could not be judged, because “Lovcode” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Lovcode.
Official links
What are the best Lovcode alternatives?
The closest alternatives to Lovcode we list are VibeAround, Beezi and Vicoa. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| VibeAround | Free | Free | — |
| Beezi | Freemium | Pricing not published | — |
| Vicoa | Freemium | Pricing not published | — |
Alternatives to Lovcode
View all
VibeAround
Local-first workspace to launch, steer, and resume Claude Code, Codex, and Gemini CLI sessions from desktop, browser, or phone.
Tools that pair well with Lovcode
Common stack mates teams adopt alongside Lovcode, with the specific reason each pairing earns its keep.
VibeAround
Local-first workspace to launch, steer, and resume Claude Code, Codex, and Gemini CLI sessions from desktop, browser, or phone.
Beezi
Beezi is AI coding spend observability: session-level token, model, time, and cost tracking for Claude Code and Codex teams.
Vicoa
Vicoa is a remote control plane for coding agents: run Claude Code, Codex, and dozens more on your own machines, then steer any session from your phone.
Lovcode vs its closest rival
Lovcode's closest head-to-head is with Spider Cloud — Lovcode and Spider Cloud serve entirely different purposes: Lovcode is a free desktop companion for Claude Code users to manage history and configs, while Spider Cloud is a pay-as-you-go web scraping API for AI agents and RAG pipelines. Choose Lovcode if you exclusively use Claude Code and need organizational tools; choose Spider Cloud if you need fast, reliable web data extraction for your AI applications. Verdict generated
Head-to-head comparisons
Lovcode vs Spider Cloud
Lovcode and Spider Cloud serve entirely different purposes: Lovcode is a free desktop companion for Claude Code users to manage history and configs, while Spider Cloud is a pay-as-you-go web scraping API for AI agents and RAG pipelines. Choose Lovcode if you exclusively use Claude Code and need organizational tools; choose Spider Cloud if you need fast, reliable web data extraction for your AI applications.
GeneratedLovcode vs Voyage Ai
Lovcode and Voyage AI serve entirely different purposes, so choice depends on your workflow. If you use Claude Code and want a free desktop companion to manage history, configs, and skills, Lovcode is a no-brainer. If you need state-of-the-art embeddings for RAG with domain specialization and enterprise compliance, Voyage AI is the clear winner despite its opaque pricing.
GeneratedLovcode vs Temporal Ai
Choose Lovcode if you solely use Claude Code and need a free, lightweight organizer for chat history and configs. Choose Temporal AI if you need a robust, scalable orchestration platform for reliable AI agents and workflows, especially with multi-language support and enterprise durability.
GeneratedFrequently asked questions
Used Lovcode? Help shape our editorial sentiment research.