NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro
Start for free
Feature

Action items that get checked, not just listed

Every meeting ends with promises and most of them are never written down anywhere that gets read again. Memtro reads the commitments out of meeting notes, team chat and conversations, records who owes what and by when, and checks the other connected systems for evidence that it landed. The ones that did are settled; the ones that did not are listed, overdue first.

The problem

  • Action items are typed into a document at the end of the call and never opened again.
  • The person who promised remembers it differently from the person who was promised.
  • Nobody knows whether the thing was done without asking, and asking is the awkward part.
  • The same promise is made in two meetings and tracked as two things, or as none.

How it works

  • Commitments are read nightly from meeting notetakers (Granola, Fireflies, Google Meet, Zoom, Gong), Slack and what the assistant learns in conversation.
  • Each one is an entity in the memory graph with an owner, a due date and the source it came from, listed under Memory → Commitments with Open, Overdue, Landed and Cancelled filters.
  • The nightly check looks for evidence in every other connected system: the invoice in Xero, the merged pull request, the closed ticket. What it finds settles the commitment with the evidence attached.
  • A commitment can be sent to GitHub, Linear, Jira or Twenty as a ticket; when the ticket closes, the commitment settles itself.
  • Ask for your commitments in Slack and settle them with a button; a duplicate of one already marked done is not recreated.

Ask it like this

  • › What did I promise in last week's customer calls?
  • › Which of Will's commitments are overdue, and what were they based on?
  • › Send the migration commitment to Linear
  • › my commitments

Setting it up

  1. 01Turn Commitments on under Organisation → Features. Like the other registers it is off to begin with, because it writes to shared memory and spends model calls every night.
  2. 02Connect a notetaker — Granola, Fireflies, Google Meet, Zoom or Gong — and Slack if promises get made in channels. Only channels the connected account belongs to are read, public and private; direct messages never are.
  3. 03Grant Settle and record commitments to whoever should be able to settle them. Reading the register needs no grant.
  4. 04Optionally connect GitHub, Linear, Jira or Twenty, so a promise that is really a piece of work can be sent to the tracker and settle itself when the ticket closes.

The tools behind it

  • memtro_commitmentsThe register, with each verdict and the evidence behind it, and the systems it could not see because nothing is connected to them.
  • memtro_record_commitmentRecords a promise made in this conversation, or one somebody reports from a call Memtro cannot see.
  • memtro_update_commitmentSettles, cancels, reopens or corrects an entry when somebody says it is done, dropped or moved — with a note saying what that rests on.

Available wherever Memtro answers: the Chat page, the API and any MCP client. Every input is in the tools reference.

What it does not do

  • It reads meetings and chat, not every system. A promise made in an email, a ticket or another chat tool is not picked up yet.
  • In chat it needs the agreement in writing. A thumbs-up reaction is not a message, so a promise accepted with one is invisible to it.
  • It sees what a notetaker wrote down. If the notes do not mention the commitment, neither will Memtro.
  • Nothing is ever marked missed. Finding no evidence means none of your systems recorded anything, which is not the same as the work not happening, so the entry stays open and says what was looked for.
  • The overnight verdict is only as fresh as the last sync. Ask in chat and the agent goes and looks for real.

Questions

Where does it read commitments from?+

From the meeting notetakers, chat systems and conversations you connect. The summary a notetaker writes is enough; a full transcript is better.

Does it decide on its own that something is done?+

It settles a commitment when another connected system shows evidence, and keeps the evidence on the record. Anything it is unsure about stays open for a person to settle, and a person can always reopen one.

Who can settle them?+

Members with the Settle and record commitments permission, on the dashboard or from the Slack buttons. Everyone can read them.

Does it read my direct messages?+

No. Only channels the connected Slack account belongs to, public and private. Direct messages are never read, so nothing said in private reaches a page the whole organisation can see.

What happens when the person is not one of ours?+

The graph learns what everybody in a meeting undertook, customers and suppliers included, which is useful in a conversation. The register itself lists the organisation's own people, because a list of who owes what is noise otherwise.

Other things it does