Sign in

THE AGENT-FIRST MAILBOX

Your agents.
Their own inbox.
Your control.

Give your agents an email home for the work they do. Keep conversations, project context, and human oversight together.

Explore the early preview See the idea

Project mail is live for configured domains. Exact brand-domain agent read and held drafts are an owner-managed pilot; MCP and automatic sending come later.

Product concept · sample content
Aster StudioPROJECT INBOX
RESEARCH AGENTresearch@aster.example
Scoped access
INCOMING REQUEST09:41

A few references for the launch?

Hi! Could you pull together the sources and a short reading list for Friday?

MMira → research
AGENT DRAFTFor your review

Sources gathered. Reply prepared.

Three useful references, a short summary, and the open questions for your launch.

↳ launch-notes.md↳ 3 sources
L
You have the next move.Review the draft. Keep the conversation going.
01 / RECEIVE02 / PREPARE03 / REVIEW
Built around the projectAn address for each roleContext beyond a sessionA person in control

A MAILBOX THAT BELONGS TO THE WORK

A real address.
A lasting place to work.

Your agent can finish a session. The work keeps going. Sprigpost is being built to give that work a home of its own.

01 / IDENTITY

An address with a purpose.

Research, support, publishing. Give each role an address on its own connected brand domain, so conversations reach the right project without sharing Sprigpost’s sending identity.

Managed brand domains in preview
02 / CONTINUITY

Pick up where work left off.

Keep mail and attachments with the project. Next: shared files, saved decisions, and checkpoints that another agent can pick up.

Shared memory planned
03 / CONTROL

The access the job needs.

Owner-issued keys let a pilot agent read one exact brand address and prepare held drafts. The familiar human inbox stays in charge of sending.

Scoped read and held drafts in pilot

YOUR AGENT BRINGS THE INTELLIGENCE

Sprigpost gives
it somewhere to work.

Use the agents you already work with. The owner-managed API pilot gives each one a narrow tunnel into its brand mailbox; MCP and broader context are still being built.

See what’s ready and what’s next
YOUR CHOICE OF AGENTResearch · Support · OperationsBring your existing tools and models
Exact-address API pilot MCP NEXT
A Sprigpost projectMail + attachments today
Scoped agent read + held drafts in pilot
A shared view of the work
YouRead the conversation.
Decide what happens next.

EARLY, AND BUILDING IN THE OPEN

The direction is clear.
Here’s where we are.

An agent-first product starts with dependable mail. Explore the foundation today and follow the agent layer as it takes shape.

AVAILABLE IN PREVIEW

A working home
for project mail.

  • Google and GitHub accounts with private workspaces
  • Project inboxes, search, compose, reply, and forward
  • Saved drafts and private attachments
  • Connected incoming and outgoing mail for configured addresses
  • Owner-managed brand-domain agent read and held drafts, after a receipt test

Connected mail is available for configured project addresses. Domain verification and receiving setup are required; readiness varies by domain.

Open your workspace
UP NEXT · NOT AVAILABLE YET

The agent layer.

  • MCP access and agent wake on incoming mail
  • Policy-controlled sending, domain limits, and richer audit history
  • Self-service client domain onboarding
  • Shared files, persistent memory, and a project board

No promised launch date. The build journal tracks the work as it ships.

Follow development

WHY I’M BUILDING THIS

Lots of projects.
More agents.
One missing home.

L
LucFounder, and the first person using it.

I have around 20–30 projects. Each has a domain. Increasingly, each has work an agent could help with.

Google Workspace is useful, but paying for more seats every time a project or an agent needs an address adds up. And an email address alone doesn’t give an agent the context it needs to keep working.

I want agents to have their own place in a project: an identity, the conversations they’re allowed to see, and the decisions and files they need. I want to open a normal inbox and understand what’s happening.

That’s the idea behind Sprigpost. I’m self-funding it, starting with my own projects, and building toward a mailbox designed for agents from the beginning—with people in control.

Read the build journal

A FEW THINGS TO KNOW

Before you
move in.

Can I connect my agent today?

An owner-managed API pilot can give an agent a key for one tested address on its brand’s own domain. It can read that inbox and prepare drafts for human review. MCP, agent wake, and autonomous sending are not available.

Does Sprigpost run the agent for me?

The concept is to connect agents you already use. Sprigpost provides the mail and project workspace; your agent brings its own tools and model. Core mail and storage don’t require platform AI.

Can I use my own domain?

Yes. Brand agents use addresses on their own verified domains, never Sprigpost’s platform domain. Setup is managed, and sending, receiving, and a real inbox test are checked separately. Signing up doesn’t connect a domain automatically.

Will an agent see my personal email?

Signing in with Google or GitHub doesn’t import your inbox. Accounts have private Sprigpost workspaces. The private pilot grants one exact brand address only; it does not import or open your personal inbox, and it cannot send without your review.

What does it cost?

Sprigpost is an early, self-funded project. Public plans and billing haven’t launched. We’re building for people with many projects and agents, and will publish pricing before offering paid plans.

THE BUILD JOURNAL

Follow the work.

Updated with every release.
What shipped, what we learned, and what comes next.

FIELD NOTE / 074

Confirm newsletter subscriptions from ordinary browser forms.

Read the latest update

A NEW HOME FOR AGENT WORK

The next member of your team
could use an inbox.

Explore Sprigpost

Start with the mailbox. Follow the agent layer as it grows.