Perseus
Cited codebase search for coding agents at perseus speeds
Perseus fills a real gap for teams that depend on coding agents: fast, accurate code context with citations. Multi-hop search and impact analysis are genuinely useful for complex, multi-file edits. Pricing is fair for teams but steep for individual devs; start with the Demo week.
Verified 1d ago · liveness 71/100 · cite: rightaichoice.com/tools/perseus
- Developers using AI coding agents who need accurate code context
- Teams working on large monorepos with many modules
- Engineers who want to reduce agent hallucinations from stale state
- Agent tool builders looking for a fast retrieval backend
- Complete beginners who need a full IDE replacement
- Teams that require offline-only operation (Perseus is cloud-based)
- Users who only need simple file-level search (grep may suffice)
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 Perseus if you only need simple grep-style file search, work offline or in air-gapped environments, or if your team is new to coding agents and doesn't yet need precise code citations.
The Demo week costs $5 one-time, but if you don't cancel before it renews, you'll be charged for a Developer seat.
Perseus pricing starts at $20/seat/month for developers, which is competitive with other coding agent context tools, though some open-source alternatives are free. The Scale plan at $100/seat/month targets larger teams needing more memory and queries; compare with enterprise search tools that often cost more per seat.
In short
Perseus — Cited codebase search for coding agents at perseus speeds. Best for Developers using AI coding agents who need accurate code context, Teams working on large monorepos with many modules, Engineers who want to reduce agent hallucinations from stale state. Plans from $5/mo.
What's new in Perseus
Checked yesterdayAcross the latest 5 updates: 3 changelog entries and 2 news mentions.
Search under constraints — Blog post explores search under constraints, discussing how Perseus handles constrained retrieval scenarios.
Blog post on constrained retrieval scenarios.
Perseus puts gpt-5.5 on top of the DeepSWE leaderboard — Perseus with gpt-5.5 tops DeepSWE leaderboard, demonstrating retrieval grounds coding agents effectively.
Perseus with gpt-5.5 tops DeepSWE leaderboard.
Multi-hop search follows threads across files with tighter citations — Multi-hop search now spans multiple files in one pass; citations point to exact supporting lines. Warm starts settle in about a s
Improved multi-hop search and citation precision.
Incremental re-indexing and CLI --json output — Working tree re-indexes only changed files; CLI gains --json mode for piping ranked hits.
Adds incremental indexing and JSON output.
HTTP API for querying indexed repositories — New HTTP API returns ranked, cited results, enabling editor and agent integrations to ground coding agents in code.
Exposes query results via HTTP API.
What people actually say about Perseus — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
40 mentions across 2 sources (Hacker News, Lemmy) · researched Jul 3, 2026.
- +Promises sub-second cited code search with exact line ranges.
- +Indexes uncommitted edits without re-indexing the whole tree.
- +Supports multi-hop search and research packets across files.
- +Includes impact analysis to warn before editing shared symbols.
- +CLI and HTTP API enable integration with editors and agents.
- −No real user reviews exist — all community data is off-topic.
- −Private access limits independent evaluation before purchase.
- −Name confusion with other projects reduces discoverability.
- −Language support limited to Go, Rust, Ruby for deep parsing.
- −Pricing is paid with no free tier beyond a demo week.
- • No information on overage charges for indexing large repos
- • Potential per-seat or per-repo pricing not specified
Viability Score
How well maintained and how widely used is Perseus? 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: August 2026
How we score →Key Features
- Semantic code search by meaning and structure
- Cited results with exact file and line range
- Multi-hop search across files in one pass
- Constrained search to narrow queries with additional conditions
- Research packets combining multiple questions
- Impact analysis before editing shared symbols
- Incremental re-indexing of uncommitted edits
- Warm start settles in about one second
- CLI with --json output for piping ranked hits
- HTTP API endpoint for querying indexed repositories
- Diff search modes: changed, impacted, regression
- Automatic indexing of GitHub repositories via URL
- Indexing of local working tree including uncommitted files
- Structural parsing for Go, Rust, Ruby
- Large monorepo handling with generated file exclusion
About Perseus
Perseus is a retrieval engine built specifically for coding agents. It indexes your working tree—including uncommitted edits—and returns ranked, cited results in about a second. You can ground Claude Code, Cursor, Codex, or your own agents in real code with exact file and line citations, reducing hallucinations and stale context. Key features include semantic code search by meaning and structure, multi-hop search that follows threads across files in one pass, constrained search for narrowing queries with additional conditions, impact analysis that shows the dependency surface before editing shared symbols, and research packets combining multiple questions. Structural parsing for Go, Rust, and Ruby, large monorepo handling with generated file exclusion, incremental re-indexing of uncommitted edits, and a warm start that settles in about a second round out the feature set. The Perseus console provides live query monitoring, while CLI with --json output and an HTTP API support scripting and agent integrations. Notably, Perseus with gpt-5.5 tops the DeepSWE leaderboard (June 2026), proving real-world effectiveness. Compared to generic code search tools or grep, Perseus is specialized for agent-driven workflows, offering low-latency queries with precise, actionable citations.
Behind the Verdict
Perseus addresses a specific pain point that many developers face when using AI coding agents: the agent often hallucinates or works with stale context because it lacks precise, up-to-date knowledge of the codebase. Perseus solves this by providing a retrieval layer that indexes both committed and uncommitted code, then returns cited results—exact file paths and line ranges—that agents can trust. The multi-hop search is particularly valuable for tracing logic across multiple files in a single pass, and impact analysis helps you understand the blast radius of a change before you make it. The CLI's --json mode and the HTTP API make it easy to integrate into your own scripts or agent pipelines. However, Perseus is not a replacement for an IDE or a general-purpose code search tool; it's specialized for agent-driven workflows. The cloud dependency might be a concern for teams with strict data residency or air-gapped requirements. For individual developers, the pricing—$20/month per seat—may feel steep, but the Demo week is a low-cost way to evaluate. Overall, if you're building or using coding agents in a serious way, Perseus is worth a look.
Researching Perseus? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Perseus actually fits — and what changes day-one when you adopt it.
You're implementing a feature that touches a shared auth module. Before editing, you run 'perseus impact requireUser' to see which files depend on it.
Outcome: Perseus lists callers, tests, and risks, so you can patch safely without breaking other routes.
You're building a custom coding agent that needs to navigate a large monorepo. You integrate the HTTP API to let it query indexed code.
Outcome: Your agent gets cited, ranked results in ~1 second, reducing hallucinations and speeding up edits.
You have a shared billing plan catalog used across services. You run 'perseus research' with questions about checkout, plan limits, and tests.
Outcome: Perseus returns a combined reading list, so your agent sees the full contract before editing any billing code.
Use Cases
- Ask your coding agent to find where authentication is enforced on a query route, returning cited file and line numbers.
- Before editing a shared function, run impact analysis to see which files depend on it and what tests cover it.
- Index a large monorepo and have your agent query for specific error strings or UI labels across the entire codebase.
- Combine multiple related questions (e.g., billing route, pricing plan catalog, billing tests) into a research packet for holistic understanding.
- Use the CLI's json mode to pipe ranked search results into custom scripts or CI pipelines.
Models Under the Hood
as of 2026-08-19
Limitations
- Queries are limited by plan-based caps (e.g., 5,000 queries/month on the Scale plan, 2,000 on Developer, 250 on Demo week).
- Indexing supports local working trees with uncommitted edits and GitHub URLs; the docs do not mention other VCS support.
- The service is cloud-dependent, as there is no mention of self-hosting.
- The CLI docs recommend using short noun phrases for queries, but the context window for queries is not documented.
as of 2026-08-23
Verification history
We have re-verified Perseus 5 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.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Free to cite with attribution — this page re-verifies continuously.
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.
Plans compared
For each published Perseus tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Demo week
$5 one-time
Ideal for
Individual developers or teams wanting to try Perseus on a real repository before committing; good for evaluating citation quality and latency.
What this tier adds
Starting tier: one-time $5 for 7 days, 250 queries, 1 repo, 100k LOC, 20 ask calls, 7-day memory.
Developer
$20/seat/month
Ideal for
Solo developers or small teams using coding agents daily; fits up to 2M LOC and moderate query volume.
What this tier adds
Adds monthly subscription: 2,000 queries/mo, 3 repos, 2M LOC, 200 ask calls/mo, 90-day memory.
Scale
$100/seat/month
Ideal for
Teams with large monorepos and heavy agent usage; for those needing more queries, repos, and memory retention.
What this tier adds
Adds 5,000 queries/mo, 15 repos, 25M LOC, 1,500 ask calls/mo, unbounded memory.
Where the pricing makes sense
The company stage and team size where Perseus's pricing actually pencils out — and where peers do it cheaper.
Perseus pricing starts at $20/seat/month for developers, which is competitive with other coding agent context tools, though some open-source alternatives are free. The Scale plan at $100/seat/month targets larger teams needing more memory and queries; compare with enterprise search tools that often cost more per seat.
Setup time & first value
How long it actually takes to get something useful out of Perseus — broken out by persona, not the marketing-page minute.
For an individual developer: sign up and install CLI in under 5 minutes; index a repository in about a minute for typical repos. For teams: allow ~30 minutes to onboard members and index multiple repos; the Demo week can be used for a quick trial.
Switching to or from Perseus
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From grep/ripgrep: Start using Perseus queries to find code by meaning; index your repo once, then query with natural language.
- →From other code search tools like Sourcegraph: Index the same repositories in Perseus and point your agents to it via CLI or API.
- →From no tool: Simply install the CLI, run 'perseus index' on your checkout, and start querying—no migration needed.
- ↗To another tool like Sourcegraph: Keep your code in GitHub and use Sourcegraph's native integration; Perseus's indexed data is proprietary.
- ↗To open-source alternatives: You can continue using grep or build a custom retriever, but you'll lose the cited relevance ranking.
- ↗To self-hosted search: Export your codebase and use an open-source indexer; Perseus is cloud-only.
- ↗To enterprise AI platforms: Many have built-in code context; export your indexed data via the API (if available) or re-index from scratch.
Resources & Guides
Tutorials & Learning
Official links
Tools that pair well with Perseus
Common stack mates teams adopt alongside Perseus, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Perseus vs Spider Cloud
Spider Cloud and Perseus solve completely different problems: one fetches live web data for AI agents, the other indexes code for coding agents. Choose Spider Cloud if you need fast, cheap web scraping with AI extraction and browser automation. Choose Perseus if you need accurate, cited code search for your agentic workflows. No direct competition.
Perseus vs Voyage Ai
If you're building enterprise RAG pipelines requiring high-accuracy retrieval on domain-specific text—especially finance, legal, or code—Voyage AI offers superior embedding and reranking models with long-context and low-dimensional options. However, if your focus is grounding AI coding agents in real code with cited, multi-hop search, Perseus is the specialized tool, especially with its recent speed and citation improvements. Choose based on your primary need: document retrieval versus code-native search.
Perseus vs Temporal Ai
Temporal AI and Perseus serve completely different needs: Temporal is for building reliable, long-running AI agents and workflows with automatic failure recovery, while Perseus is a code search engine that grounds coding agents in accurate context. If you need to orchestrate multi-step agentic workflows that survive crashes, choose Temporal. If you want your coding agent to retrieve precise, cited code snippets quickly, go with Perseus. They are complementary – you could even use both together.
Alternatives to Perseus
View allFrequently Asked Questions
Best-of guides
Used Perseus? Help shape our editorial sentiment research.