+
Connect the issue to the code that closed it
Connect GitHub and Linear to one company memory, and a single question reads both.
Planning lives in the tracker and the work lives in the repository, joined by a branch name somebody remembered to type. Asking what actually shipped against an issue means reading both and trusting the convention.
Questions that need both
Each of these is unanswerable inside either product on its own. Agent mode reads both, resolves the customer to one entity, and ends with a line per system it consulted.
- ›Which Linear issues from this cycle have merged PRs, and which do not?
- ›What changed in the code for the billing migration issue?
- ›Who reviewed the PRs behind last week's closed issues?
What each side brings
GitHub
Issues, pull requests, code and commits, searchable by anyone who can ask a question.
- Search issues and pull requests across your repositories
- Read an issue or PR with its comments
- Search code and read files at a ref
- List repositories and recent commits
Linear
Issues, projects and teams, synced hourly into memory.
- Search issues with filters
- Read an issue with comments
- Teams and projects
- Hourly sync of recent issues
Who this is for
- EngineeringKeep decisions from evaporatingDecisions, owners and deadlines are extracted from conversations and tool results into a typed, time-aware memory. Corrections supersede old facts instead of piling up next to them.
- ProductHear what customers actually ask forFeature requests are scattered across tickets, call notes, Slack threads and issues. Memtro reads them where they live, links them to the customers who raised them, and remembers which decision closed each one.
- OperationsMonitors and digests that run themselvesJobs are prompts the agent runs on a schedule with the same tools as their owner. Create them in plain language, get the report in a chat, pause or change them in a sentence.
Other seams worth closing
Ask one question across both
Seven days free. One price per organisation, nothing metered, and model usage stays on your own provider keys.