Everything Releap does.
Six surfaces. One indexed codebase. Every role covered.
Ask how your product works. Get cited answers.
Releap indexes your codebase — functions, classes, modules — using AST-aware chunking and pgvector retrieval. Every answer cites the exact file and line range it came from, pinned to the commit Releap read when it generated the answer.
Ask in the web UI, in Slack (with no seat required), or through your coding agent via the MCP server. Multi-turn threads maintain context across a conversation. Answers can be exported, saved to KB, or turned into tickets with one click.
Turn codebase understanding into engineering work.
From any chat answer, generate a full ticket with acceptance criteria, code references, and an engineering prompt — specific enough for a developer or coding agent to act on without asking follow-up questions.
Manage tickets in a Kanban board or table view. Verify acceptance criteria before pushing. Export to GitHub Issues, Jira, Linear, or Aha!. Two-way sync keeps external trackers in step.
One source. Every audience. On the record.
When work ships, Releap drafts release notes from your commits and tickets — different copy for different audiences (customers, CS, support KB, internal engineering) — automatically.
Review and edit in the web UI with the Releap editing panel. Send a test to your inbox before publishing. Publish via email export, hosted page, or delivery to your configured ESP. Every step is logged for audit and approval chains when you need them.
Documentation that stays current with your code.
Create KB pages from answers, tickets, and direct Releap generation. Releap flags stale sections when the source files they reference are updated — no more outdated docs sitting unnoticed.
KB articles are searchable and retrievable in chat answers. When Releap answers a question, it surfaces relevant KB context alongside the codebase citations. Export to Markdown, HTML, or PDF.
Your active ticket in your editor.
The Releap extension for VS Code surfaces your assigned ticket directly in the sidebar — AC items, related files, and Explore with Releap — all without leaving your editor.
Branch detection matches your current branch to a Releap ticket automatically. Verify acceptance criteria before you push. Compare verification status across local, test, and production environments. The MCP server lets Claude, Codex, and Cursor read and update tickets as they generate code.
No GitHub approval needed
Index your local VS Code workspace directly — no GitHub App, no admin rights, no waiting for security review.
When your organization approves the GitHub connection, switch over in one click. Your local index is superseded automatically.
Install from VS Code Marketplace →Intelligence in the tools your team already uses.
MCP Server
Expose Releap to any MCP-compatible coding agent. Claude, Codex, Cursor, and custom agents can:
- Read assigned tickets and sprint contents
- Draft tickets with a two-phase review before creation
- Run AC verification against the current codebase
- Update ticket status and assignees
- Search the codebase and KB
15+ tools. OAuth 2.1 + PKCE auth. Auto-configured by the VS Code extension.
Slack Bot
/lens queries from any channel. Answers are
visible to the whole team without requiring seats.
- Query codebase from shared channels
- Follow-up buttons (Block Kit)
- Ticket creation from Slack
- No per-user seat requirement
- Usage draws from the workspace pool
Ready to connect your codebase?
30-day free trial. No credit card. Read-only by default.