Estoa

Every agent, one inbox

Your coding agents, your assistant and your bots ask in one place. You answer once, from the web or straight from your phone's lock screen. Android first, iPhone later.

Amber asks · 4 min ago

The auth refactor is green. Merge it to main?

MergeWaitLater
Amber, coding agent
The colonnade of the Stoa of Attalos in Athens, white columns under a dark timber ceiling
Stoa of Attalos, Athens

In progress

Docs site

Moving the API pages to the new layout, 14 of 22 done.

Amber, coding agent

Needs you

Billing migration

Paused before step 3: renaming the plans table needs your OK.

Cobalt, coding agent

Approval · Pilot

Restart the database on prod-2?

systemctl restart postgresql
Allow with passkeyDeny
Pilot, ops bot
The two-storey front of the Stoa of Attalos under a blue sky
The Agora, Athens

This morning

Billing migrationNeeds you

Docs siteIn progress

Flaky login testStuck

Tax receiptsDone

Work board
A black pottery shard scratched with the name Aristeides, an Athenian ballot
An ostrakon: a one-word answer

You replied by voice · 0:14

"Go with the smaller index, and leave the old one until Monday."

Cobalt heard you

Answered from the lock screen

Try it. A coding agent's question, the way it lands on your phone. Pick an answer and the agent carries on.

  • Android and the web first, iPhone later. The buttons work from the notification shade; you never open the app for a yes.
  • Reply by voice. Hold, talk, let go. Estoa transcribes it and the agent reads your words.
  • Later is an answer too. The question comes back when you said it would, not before.
  • Cleared everywhere. Answer on the phone and the question leaves the laptop too.

14:02

Thursday 5 November

Estoa · Amber needs you · now

The auth refactor passed all 214 tests. Merge it to main?

Amber · ~/projects/shop

Split the auth module into session, tokens and passkeys.

Moved 31 call sites; removed the old cookie helper.

Wrote 18 new tests for token refresh.

All 214 tests pass on auth-refactor.

Asked in Estoa: merge to main?

Waiting for an answer…

Stop fishing
for updates

στοά

The two-storey front of the Stoa of Attalos under a blue sky
The ostrakon of Aristeides, close up

Three coding agents in three terminal tabs, an assistant in a chat app, a bot that pings you about a server. Each asks in its own place, so after lunch you scroll four histories to find the one question waiting on you. A stoa was the covered colonnade on the edge of a Greek square, where people waited in the shade to be heard. Estoa is that colonnade for your agents: each waits with a name and a clear question, and gets back to work the moment you answer.

Agent asks, you tap, it goes on

  1. Two minutesFirst, paste one MCP address and a key into your agent.
  2. Hours of its own workThen it works, and when it needs you it asks: buttons, a checklist, an approval.
  3. One tapNext, you answer from the notification, the web or your voice.
  4. Seconds laterLast, the answer reaches the agent that asked, even if it went idle.

What your agents can send

Questions with buttons

Two to four choices in the agent's own words, or a free reply. No parsing "yeah ok" out of a chat.

Cobalt asks

Keep the old endpoint for a week, or remove it today?

Keep a weekRemove today

Checklists you tick

Things only a person can do. The agent sees each tick as it happens.

Test on real devices

  • Sign up on Android
  • Pay with a test card
  • Sign up on a tablet
  • Reset a password

Approvals with your passkey

Risky steps wait for your fingerprint or screen lock. An agent can ask; it can never approve itself.

Pilot wants to run

git push --force origin main
Allow with passkeyDeny

One card per piece of work

Agents keep a card current instead of posting a feed. You read where things stand, not what was said.

Stuck

Flaky login test

Waiting on the vendor's sandbox, down since 9:00.

Next: rerun when it's back.

Notes they can't wreck

Each project keeps a note: what it's for, what you decided, where it was left. Agents write only in their own sections.

Website

What it's for

Your words. Agents can read this, never change it.

Decisions

Nov 3 · Docs move to the new layout. You.

Offers, not actions

An agent can offer "Deploy now". Nothing runs until you tap it, and then only that.

Cobalt offers

Staging looks right. Deploy to production?

Deploy nowNot yet

Where everything stands

Back after a day away? The board shows what moved, what's stuck and what waits on you. Pink means it needs you; nothing else is pink. Open any row.

Works with any MCP client

For solo builders with three coding agents going at once, and for people whose assistant handles their mail, calendar and errands. If it speaks MCP, or can make an HTTP call, it can ask you things.

Claude Code

Asks before it merges, migrates or deletes.

Codex

Reports a finished task and what it left for you.

Cursor

Wants a decision on the approach.

Your assistant

Books, reschedules, pays, and checks with you first.

An ops bot

Needs a passkey before it touches production.

Your own scripts

One HTTP call to ask a question, one to read the answer.

Your workspace is your own room

The Stoa of Attalos had 21 rooms behind its columns, one per merchant. Estoa works the same way: every workspace is walled off in the database itself, not only in the code.

The long marble walk inside the Stoa of Attalos, columns on one side and rooms on the other

Each agent gets its own key, so you see exactly who said what, and you can revoke one without touching the others. A new key or a new passkey always tells you.

A stoa's floor plan: a long colonnade with 21 rooms behind it, one marked as yours

Room 14 is yours

Isolation
Row-level security in the database
Agents
One revocable key each
Risky steps
Your passkey, every time
Your data
Export or delete it any day

Free while in early access

Plans with more history and storage come later. Estoa opens to a small group first; leave an email and we'll write when your workspace is ready.

One email when your workspace is ready. Nothing else.