🛠️ Contest: Build a custom agent and win a trip to San Francisco

Your Move: what you owe and what you’re owed, across email, chat and meetings

Imagine starting each day with one list of what you owe people and what they owe you, across your email, chat and meetings, that already knows what you’ve finished. With Superhuman Go, that’s possible.

“Your Move” is an AI agent that does exactly that. Every morning it reads the places where you do most of your work, finds every ask and commitment, and checks which ones are already done.

One line from a list looks like this:

Using it is simple: you receive one list every day. But - building it was harder than it sounds. “Next week” has to become a real date. A question asked in a meeting can get answered in an email thread. Sometimes the only proof something’s done is an invite on your calendar.

I tested the agent against two weeks of my real email and meetings (plus a Slack workspace I set up with test conversations), and checked every result manually. After more than 100 test runs, I learned how to steer the way Go works through a plan: what order to put the steps in, how to stop it from skipping one, and how to make it show what it actually read. I’ve written up the key lessons in the accompanying doc, so you can use them in your own agents.

Without “Your Move”, you’d either have to note down every commitment as it comes up, or scroll back through your inbox, chat and meeting notes to find anything you missed. That’s how most of us have done it for years, but it’s tedious and takes time. Go can do that tracking for you, so you can focus on the work that needs your judgment, creativity, expertise, or ambition.

The Agent

Agent name: Your Move

What it does: Each morning it tells you:

  • Your move: what you owe others, and messages still waiting on your reply.
  • Waiting on others: what others owe you, or asks with no answer yet.

It also checks whether each one is already complete, searching your mail, chat and calendar, and takes it off the list when it can tell it’s done.

Anything with a stated deadline shows the date. Each line quotes the exact words, who said them, and names the email / chat message / meeting, with a link when there is one. Anything it isn’t sure about goes under “Judgment calls” for you to decide.

The list also lives in a Superhuman Doc, so open items carry over from one morning to the next and drop off once they’re done. You can open the doc anytime to review or edit it.

The recurring problem: Commitments get made everywhere: on calls, in email threads, in chat. Keeping track of all of them takes effort, and some slip through the cracks.

How it works: The first time you run it, it sets itself up with you. It checks which tools you’ve connected (email, Slack or Teams, and a meeting notetaker, ideally Fathom), tells you what’s missing and how to connect it, and creates its list in a Superhuman Doc.

After that, it runs on a schedule every weekday morning at 8am. In order, it:

  1. Opens its list and reads what’s still open.
  2. Reads every meeting transcript, email thread and chat conversation since its last run (the last 14 days on the first run), noting every ask and commitment word for word.
  3. Decides which ones count: asks and commitments to or from you, not cold pitches or commitments between other people.
  4. Checks whether each one is already done, searching your mail, chat and calendar.
  5. Updates the doc and writes the list, starting with a line that says how many meetings, email threads and chat conversations it read.

Who it’s for: most digital-native workers today: anyone whose day is a mix of meetings, email and chat, and who makes and receives commitments in all three.

Apps and connectors: This Go agent reads your Mail, your chat (Slack or Teams), your calendar (to check what’s already done) and your meeting notetaker (ideally Fathom :wink: ; it works with whichever one you’ve connected, and I tested with Wispr Flow). It keeps its list in Superhuman Docs.

How to try it: Community agents can’t be shared through Go’s Agent directory yet, so you build your own copy. A have a walkthrough on how to set it up in my accompanying Coda doc.

How it Stacks Up

Solves a clear, recurring problem: Every day, commitments pile up across email, chat and meetings. Keeping track of them by hand or with other tools takes time. Your Move does this for you every weekday morning.

Fits naturally into a real workflow: It reads the places these things already happen: your email, your chat (Slack or Teams) and your meeting transcripts, and it checks your calendar. The list arrives each morning and also lives in a Superhuman Doc you can open anytime. It also doesn’t ask you to start a new habit. You don’t have to remember to run it, prompt it or tag anything for it. It runs on its own every weekday, so the list is waiting when you open Go.

Gives someone better context, focus, or momentum: Task trackers are a whole industry, and most of them need you to type every item in. Your Move skips that: it pulls asks and commitments straight from your email, chat and meetings, and drops what’s done, so you start the day on what’s next instead of rebuilding your list. Each line also carries the quote and its source, so you have the context to act.

Is easy for another person to understand and adapt: Anyone can see why each item is on the list: every line quotes the exact words, who said them and where, with a link when there is one, and the list opens by saying what it read. The first run walks them through connecting their own email, chat (Slack or Teams) and notetaker. Everything also ends up in a Superhuman Doc, so they can check any item and refer back to it anytime.

Keeps people in control of important decisions and actions: It only reads, and writes only to its own list: it never sends, replies or accepts an invite for you. Close calls go under “Judgment calls” with the exact quote, so you decide what counts. If you mark a row Done or Dismissed, it stays that way.

What I Learned While Building It

You can’t talk about building reliable AI agents without talking about evals, or in other words: testing the agent’s responses against answers you already know.

Before each test, I worked out the correct list myself from two weeks of my real email and meetings, plus a Slack workspace I set up with fake conversations written to be tricky: 16 asks and commitments, 6 of them already finished. Then I checked each run against that list, one item at a time. Early versions handled about half. The latest handles about 13 of the 16 (missing mostly the tricky ones). All 30+ versions, what changed and why, and every test conversation are in the companion doc.

Lessons on Building Reliable Go Agents

I learned a ton of things that would be valuable to anyone trying to build a reliable go agent; I’ll only address a few of them here:

1. Give it a plan. Go has a planning mode, where it lays out its steps before starting, but it decides on its own when to use it. Every run where no plan appeared stopped early. When I had it write out my plan first, with each job as its own step, runs read more and found more, possibly because each step gets its own context window (or its own sub-agent; Go doesn’t show which). For example, a step that clears wrong rows from the list removed 0 of 7 when it was buried inside another step, and 6 of 7 as its own step.

2. Make it go in order, and tell it what to do when stuck. Even with a plan, Go doesn’t always run its steps in order. In one run, its step list showed two steps in progress at once and a later step already checked off. It was as if I’d asked it to bake a cake and it started frosting before the cake was in the oven. So I told it to work strictly one step at a time. Then, when a step got stuck, like a transcript that wouldn’t load, Go stopped the whole run right there: no email, no Slack, no list. Since I added “write down what you couldn’t do, move on, and always finish the list,” no run has stopped.

3. Give it memory. Go starts every run from scratch. Keeping the list in a Superhuman Doc means each morning reads only what’s new since the last run, not the whole two weeks. Less to read means more gets read: on three weeks of mail, runs ran out partway; on two, Go mostly read everything.

4. Make it say what it read
Every list now opens with how many meetings, email threads and chat conversations it read. Agents fail silently, and this one line shows you when one did.

You can find the remaining lessons in my accompanying Superhuman Doc.

And again, instructions how to use it are here!

Edit: Here’s my course completion certificate.

2 Likes