Early access for software teams on GitHub and Slack
Team memory that gets people unstuck.
MemoAgent watches your GitHub pull requests for work that's stuck. Each weekday morning it tells each person in Slack what's blocked, which reviews they owe and what they need to fix, with a link to every pull request.
- 9:30by default
- when your Brief arrives on weekdays, in your own time zone. We can set a different time for anyone.
- 1full working day
- before a waiting review counts as stalled. Weekends don't count, and days follow the reviewer's time zone.
- 15minutes
- from a stall to a private alert for the pull request's author, inside their working hours and at most 3 a day.
- 1nudge a day
- at most, per reviewer and pull request, and only when the author asks for it.
The questions your team stops asking each other
Each weekday morning, the Daily Brief answers them for the person asking, with a link to the pull request.
- Asked on GitHub
Ada
Are you still reviewing #17?
- Asked on GitHub
Linus
Who should I nudge about my pull request?
- Asked on GitHub
Grace
Why can't #58 merge?
- Asked on GitHub
Alan
Is anyone waiting on changes from me?
- Asked on GitHub
Margaret
Is my review request still waiting?
- Asked in Slack
Katherine
Who's holding up my pull request?
- Asked in Slack
Dennis
Am I holding anyone up?
- Asked in Slack
Barbara
Which pull request should I look at first?
- Asked in Slack
Ken
Is my pull request stuck, or just slow?
- Asked in Slack
Frances
Which reviews do I owe?
How it works
Connect GitHub and Slack, then let MemoAgent watch
A review waits for days, or a pull request can't merge and nobody says so. MemoAgent notices, and tells the people who can move it.
1. Connect GitHub and Slack
Install the GitHub App on the repositories you choose, and add MemoAgent to your Slack workspace. It reads only what you give it access to.
2. It notices what's stuck
Plain rules: a review waiting a full working day, requested changes left for two working days, or a merge conflict. Before anyone hears about it, MemoAgent reads the pull request from GitHub again, so anything fixed since drops out.
3. A Brief for each person
A short Slack message on weekday mornings, at 9:30 in their own time zone by default, sent only when something needs them and skipped while their Slack status says they're away. Open PR goes straight to GitHub; Nudge reviewer and Not a blocker ask you to confirm first.
The Daily Brief
What lands in Slack on weekday mornings
Each person gets their own list: blocked pull requests first, then the reviews they owe, then what they need to fix. When a review stalls during working hours, its author hears within 15 minutes.
MemoAgent
MemoAgentAPP9:30 AM
Your Daily Brief for Thursday, October 1
Blocked
1. Add rate limits to the public API
acme/api#42 has waited 1 working day for review from Grace.
Waiting on you
2. Cache the pricing table
Ada has waited 2 working days for your review on acme/web#17.
Your priorities
3. Rename the billing events
GitHub says acme/api#58 can't be merged cleanly: it conflicts with its base branch.
Only visible to you
MemoAgentAPP9:41 AM
Sent a reminder to Grace.
A day with MemoAgent
From stalled to reviewed, before lunch
The author hears first, the reviewer gets one reminder, and the blocker clears itself once the review is in.
MemoAgent
Your Daily Brief arrives
Three items: a blocked pull request, a review you owe, and a merge conflict to fix.
MemoAgent
A review stalls
acme/api#61 has now waited a full working day for Grace. The alert goes only to you.
You
You tap Nudge reviewer and confirm
Grace gets one reminder with the link. MemoAgent won't remind her about this pull request again for a day.
Grace
The review is done
The blocker clears on its own, and tomorrow's Brief doesn't mention it.
Features
What MemoAgent does today, and what comes next
- Available
Daily Brief
Each weekday morning, when something needs you: what's blocked, which reviews you owe, and what you need to fix.
- Available
Instant stall alerts
When a review on your pull request stalls, you hear within 15 minutes, inside your working hours and at most 3 times a day. Anything else waits for your next Brief.
- Available
Author-only nudges
Only the pull request's author can nudge a reviewer, and only after confirming. At most once a day per reviewer and pull request, and never automatically.
- Available
Respects time off
Follows each person's Slack time zone, and skips their Brief and stall alerts while their Slack status says they're on vacation, out sick or out of office.
- Coming in October
Cited answers
Ask in Slack what was decided. Every sentence of the answer links to the message or pull request it came from.
- Coming in October
Promises kept
Commitments made in Slack are remembered, and raised in the Brief when they slip.
Coming in October
Answers you can check
Ask MemoAgent in Slack what the team decided. Every sentence carries a number, and every number opens the pull request or message it came from. Anything it can't cite, it leaves out.
What did we decide about webhook retries?
Webhooks are retried up to five times with backoff1. Anything that still fails goes to the dead-letter queue, which Grace agreed in #platform on Tuesday2.
- 1GitHub · acme/api#36Retry failed webhooks with backoff: merged Tuesday
- 2Slack · #platform, Grace, Tuesday 14:02“Five retries with backoff is fine. Anything longer goes to the dead-letter queue.”
For companies
Built for software companies on GitHub and Slack
MemoAgent works across every team and repository you connect, and each person hears only about what needs them.
The whole team, from day one
One setup covers the repositories you choose, and everyone who works in them gets their own Brief in Slack.
Work keeps moving
Stalled reviews, unanswered change requests and merge conflicts reach the person who can act, without a manager asking around.
Set up in one call
During early access we set MemoAgent up with you in 30 minutes, on your own repositories and Slack.
Your data stays yours
Each company's data is kept apart from every other's, the tokens that connect your tools are stored encrypted, and your data never trains a model.
Principles
Four rules we build by
- Proven
- Every sentence in an answer cites its source, and a sentence without one is left out.
- Fresh
- Before it tells you anything, MemoAgent reads the live state from GitHub again.
- Private
- You only ever see what you can already see in the tool it came from.
- Minimal
- It stores only what its job needs, like pull request titles, states and links, and keeps no archive of your messages. Your data never trains a model.
Questions
Before you connect anything
What MemoAgent reads, who sees what, and what happens to your data.
What does MemoAgent read?
In GitHub: pull requests, reviews and review requests in the repositories you install it on. In Slack: who people are, and their time zone and status, so Briefs arrive at the right moment. Reading conversations is coming in October, and only in the channels you invite it to.
Who sees what?
Each person's Brief is about their own work: their pull requests and the reviews they owe. Answers will only draw on what the person asking can already see in the tool it came from.
Do you train AI models on our data?
No. We never train or fine-tune models on customer data, and the model providers we'll use don't train on API data.
What do you store?
Pull request titles, states and links; who was asked to review what, and when; a log of GitHub events (type, person, pull request and time); people's names, emails, time zones and account IDs; what's stuck; and the Briefs we've sent. Webhook payloads are processed and dropped within minutes, and we keep no archive of your messages.
Where is it hosted?
In the United States: the database and servers in AWS US East (Ohio), and the job queue in N. Virginia. Every team's data is kept apart by row-level security in the database, and the tokens that connect your tools are stored encrypted.
How do we start?
Book a 30-minute demo. During early access we set MemoAgent up with you, on your own repositories and Slack.
See it on your own pull requests
A 30-minute call: how MemoAgent would work for your team, and exactly what it needs access to.