The Praxos Inbox
A list of everything that’s waiting on you. Built from your conversations, calls and AI sessions.
Contents
What is the Praxos Inbox?
The Praxos Inbox is a list of everything that’s waiting on you. Praxos builds it from your conversations, calls and AI sessions.
Praxos will fill it from work that’s already happening. This is automatic. You don’t need to add to it manually.
What can it do for me?
The Inbox catches work you or your team said you’d do and haven’t done yet. The goal is to tell you things before someone (or yourself) has to chase you later.
Work and important things often get dropped because someone said them out loud, but nobody wrote them down. “I’ll send you the deck.” “I’ll review the contract and get back to you.” “Can you review the PR?” “Can you take a look at my blog post draft?” You say them, don’t write them down, and two weeks later, as you are about to sleep, remember them. Then you scramble to make time for them the next day.
The Inbox holds four kinds of items:
- What you said you’d do.
- What others said they’d do for you.
- What your agents want to do. If an agent is about to send an email or run a command that your Space requires approval for, it waits here until you say yes.
- Changes a teammate made that your work depends on.
Each item shows who said it and where. You can check and mark it as Done, Wrong or Forget.
Example: the agreement I said I’d send
This one happened to me. In October 2026, a customer told me he needed a business associate agreement (BAA) with Praxos. I had said we’d send ours over. Then the thread went quiet.
Sent the draft. Its margin comments “must be addressed before this can be sent over.”
Three weeks later, my cofounder Soheil asked Praxos: “Did Lucas ever send a BAA to the customer? He thinks not, but let’s check the evidence.” Praxos went through my email and answered with the full chronology. No BAA had gone to the customer, and the last email said the draft wasn’t ready to send. It also said where it couldn’t look, like Slack and text messages.
That answer only existed because Soheil asked. The Inbox puts the same finding in front of you before anyone has to ask:
Send Marcus the BAA
Promised Oct 14 · open 6 days · Linden Law sent the draft today
Marcus Hale at Kestrel Billing needs a BAA before he can work with you. On Oct 14 you told him you'd send yours. Linden Law sent the draft today, with comments to resolve before it can go to him.
- 1Ask Linden Law to resolve their commentsSends as you · email to Linden LawLucas Urbisaiato Linden Law · Email
Thanks for the draft. Could you resolve the margin comments and send me a clean copy? Marcus at Kestrel is waiting on it.
- 2Send the clean BAA to MarcusWaits for step 1 · Praxos drafts it when the clean copy arrives
Sources 6
In date order- You to Marcus Hale· Oct 14Your words
Asked how Kestrel is classified, “before we send our BAA over.”
- You to Linden Law· Oct 14
Asked for a template BAA.
- Marcus Hale to you· Oct 15
Kestrel is a medical billing service. It needs an sBAA with an added amendment.
- You to Linden Law· Oct 16
Sent Marcus's requirements.
- Linden Law and you· Oct 19
They asked for the customer's name for a conflict check. You sent it.
- Linden Law to you· Oct 20
Sent the draft. Its margin comments “must be addressed before this can be sent over.”
Example: the promise you can't get to
In November 2026, I promised a customer, Quillmoor AI, Slack automation import. They can’t join until it exists. Then my availability changed: my calendar filled up with calls.
Soheil is already building tools to connect to Slack.
Someone else should take this on. But nobody has pressed on this topic, because everyone assumes I am working on it.
Praxos notices. It sees my promise, no work on it since, and that Soheil is already building tools to connect to Slack. So it brings this to my attention in my Inbox. When I agree, Praxos prepares the full handoff: Soheil gets my promise, where I made it, and a link to his own Slack work.
Slack automation import
- Your email· Nothing since Nov 5
- Your chats· Nothing since Nov 5
- Your coding sessions· Nothing since Nov 5
Soheil is already working on the Slack integration.
What can it access to do these things?
The Inbox can access only what you connect to Praxos. This means messages and calls on Praxos, your AI sessions in Claude Code, Codex and the other tools you link, and apps such as Gmail, Calendar, Dropbox and GitHub.
Praxos reads these sources for two things: when someone commits to something, and whether it happened.
There are three limits:
- You see only your own items. Your Inbox doesn’t show a teammate’s private commitments. No one can see your Inbox.
- Nothing that needs approval runs without it. If your Space requires approval for an action, the agent waits until you decide.
- You choose what each Space can read. You can turn off any connection for any Space.
What do you mean that it’s proactive?
Proactive means Praxos looks for unfinished work on its own and tells you about it. You don’t have to ask.
Most software waits for you. For example, a to-do list needs you to write the task; a search box needs a query. But searching for something you’ve forgotten is impossible. Likewise, you can’t write down or work on a task that you forgot about.
Praxos’s Inbox takes care of this problem. When someone says “I’ll do X,” Praxos records this commitment. Later it looks for evidence that X happened. Evidence could be a sent email, a message saying it’s done, a commit or a file. If Praxos finds evidence, the item gets moved out of your Inbox. If not, the item stays there until you take action.
If a teammate is already doing related work, Praxos suggests handing the item to them. You decide, and they get the original promise and its context.
Company names in the examples are made up.
