Product and engineering

The PR, its reviews, the ticket, and the discussion behind it.

Leon indexes the history around your code: why a decision was made, who reviewed it, what is still open. Your coding assistant queries it over MCP and opens each session with the morning briefing.

Create a workspace Sign in

is this PDF export bug already known?

Leon’s answer3 sources

Yes. Three customers have reported it since Monday source 1. Engineering reproduced it on invoices longer than 50 lines source 2, and the fix is in review source 3.

[1]Empty PDF export
Conversation · Support · Oct 20, 2026
The customer gets a blank PDF when exporting the October invoice.
[2]PDF export: blank page past 50 lines
Ticket · Thomas Girard · Oct 21, 2026
Reproduced: past 50 lines, rendering stops without an error.
[3]fix(export): paginate PDF rendering
PR · Thomas Girard · Oct 22, 2026
Renders page by page instead of in one pass. Review requested.

Fictional example · Leon’s Search screen

Search syntax

What this team asks.

Written the way people type them. Leon searches every connected tool and answers with citations.

01the PR that changed the refresh token
02tool:github type:ticket
03why did we drop the Redis queue?
04before:2026-10-01 "migration"

In practice

What Leon does on an ordinary workday.

What Leon does for this team today. Fictional examples.

Monday, 9 a.m.
Resume where you left off
Developer, 25-person SaaS company
where was I on the billing repo?
She left a migration half done on Friday. When her session starts, the repo’s morning briefing is already in her coding assistant: what she did, the review that came in since, the reopened issue, what is still open.
Impact: She and her assistant start from the right place, without reopening three tabs.
Her coding sessions
Before rewriting a module
Check what the team already decided
Developer, 12-person startup
have we already tried generating PDFs in the browser?
He has his coding assistant query Leon over MCP. Leon returns the PR closed in March, the review explaining why it was dropped (broken rendering of accented characters) and the decision record in Notion.
Impact: The assistant doesn’t repeat a dead end the team already paid for, or it flags what has changed since.
Rerunning an analysis from last month
Retrieve what you worked out with your AI assistant
Product manager, 40-person company
the cohort retention query without the test accounts
In September he built the query with his AI assistant, edge cases included. The conversation, captured by the extension, comes back in one search next to the ticket that requested the chart. Only he can see it.
Impact: The final, corrected query, with the reasoning that led to it.
His AI conversations
10 p.m., an error in an unfamiliar module
Find out whether the incident has happened before
On-call developer, 30-person SaaS company
has this import error happened before?
Leon returns the Sentry issue from March, the PR that fixed it, the incident ticket and the postmortem. The next day, a chat turns them into a first draft of the new postmortem.
Impact: She applies the known workaround instead of paging the module’s author.

Impact

What changes for this team.

01
The why behind every change
Reviews, tickets and design meetings surface next to the PR they explain.
02
Native to your assistant
Leon’s MCP server gives your coding assistant the team’s history, scoped to your permissions.
03
The morning briefing
What you did, what changed, what is still open: 250 words, ready when your session starts.