Thread
Log inWaitlist

Early access · waitlist open

The inbox where you and your agents run the company.

Read and send email, direct Claude Code or Codex on your own machines, and approve what agents do, from web or iPhone. For founders running one product or several.

Join the waitlistSee an exampleInvites go out in small batches.
Illustrative walkthrough of the Thread Inbox. Sample names and data; timing condensed.

Works with what you already run. Connect it once; every agent can use it.

Your mail and calendar

  • Gmail
  • Microsoft 365
  • Google Calendar

Your agents and code

  • Claude Code
  • Codex
  • GitHub

Your machines

  • macOS
  • Linux
  • iPhone

Also connects: Stripe · Twilio · Sentry · Outlook

Why Thread

A new kind of company. One founder. Agents that hold the tools. One leader that keeps the context.

01

Agents do the work

Claude Code and Codex work in your projects, on your machines, with the mail, browser, calendar and secrets you grant them. They investigate, build, verify and reply.

Claude CodeCodexyour Macyour mail
02

The work stays connected

Instructions, progress, questions and results return to the same conversation. Thread supplies the memory, schedules, hosts and records around it.

memoryscheduleshostsrecords
03

You make the decisions

Review drafts, answer questions and choose what agents may do next. Attention is not execution: nothing ships because you looked at it.

Needs youDraft for approvalDoneUndo

An example

From customer email to verified fix, in one thread.

  1. 01

    A customer emails

    Mia’s message lands in your Inbox, filed as Support. You answer in the same thread: have Claude Code reproduce it and fix it.

    Mia LarsenSupport09:40

    Invoice download fails — Hi — clicking Download invoice on our October invoice gives an error page. Could you take a look?

    YouPrivate09:41

    Have Claude Code reproduce this and fix it. Open a PR and merge when CI is green.

    Private discussion stays private. Mia never sees this thread of the conversation.

  2. 02

    An agent investigates

    Ada starts Claude Code in the connected project on your own machine. Every step shows in the thread, and you can steer it.

    WorkingFix invoice downloadbimmi · kvist · hulda/3f9a21cWorktree
    Claude CodeAgentWorking for 48s
    Searched "download_invoice" in backend/app/billing
    Read backend/app/billing/pdf.py
    pytest tests/billing -q1 failed, 41 passed
    Editing backend/app/billing/pdf.py

    Type into the thread to steer the running turn, or queue a message for the next one.

  3. 03

    Review the fix

    Changed files and test results arrive in the conversation. CI goes green, the PR merges because you said so, and the deploy is verified.

    2 files changed+37 −4
    backend/app/billing/pdf.py+19 −4
    backend/tests/billing/test_pdf.py+18
    #214 fix(billing): regenerate the invoice PDF when the cached file is missing
    Deployed
    Lint
    Tests
    Build

    Merged because you asked for it. Deploy verified by the health check. Ada watched the checks for you; no model or shell stayed running just to wait.

  4. 04

    Approve the reply

    Ada drafts the answer from your address. Under draft-for-approval you press Send; automatic sending needs a policy you enabled.

    Email · as youDraft for approvalNot sent
    Re: Invoice download fails

    Hi Mia — fixed. Your October invoice downloads again; the cached PDF had gone missing and we now regenerate it on the fly. Sorry for the hassle, and shout if anything else is off.

    Send email Edit
    Support replies to this sender:DisabledAlways queueDraft for approvalAuto-act
  5. 05

    Keep the result

    The fix, the checks, the sent reply and the cost stay with the customer conversation. You mark it Done; nothing is marked for you.

    Invoice download failsDoneWorked for 2m 14s · $0.31
    Fixed · PR #214 merged and deployed, health check passed
    Answered · Reply sent from your address at 09:47, receipt recorded
    Recorded · 2 files changed by Claude Code · task 3f9a21c · before and after kept
    Done · Marked by you. Done is attention, never execution.

    Morning, Ronny — 2 things need you.

    2
    needs you
    7
    ada today
    $4.12
    spend
    14:00
    next

Trust

You choose what agents can do.

  • New automation policies default to draft for approval

    Connecting a mailbox grants nothing on its own. Ada surfaces drafts and questions until you say otherwise; coding agents do what you instruct, within the permissions their sessions were given.

  • More autonomy is proposed, never taken

    After a run of approvals without edits for one kind of action, Ada proposes auto-act for it. You accept or decline, and one tap takes it back.

  • Every recorded change carries its author

    Agent, task and before-and-after values on every change Thread records, with a rewind that previews before it rolls Thread’s own records back. One master switch disables autonomous actions.

Connected to the work

Email, agents and decisions. Together.

Needs you3Ada asks1Working2
  • Mia LarsenSupport09:40Invoice download fails — clicking Download invoice gives an error page…
  • AdaAda asks08:02Allow auto-send for receipt replies? — Your last 12 decisions here were approvals.
  • Claude CodeWorking08:31Add retry to the SES sender — bimmi · kvist · Working for 6m
  • Jonas BergMeeting09:12Thursday demo? — Could we do 14:00 CET instead?
  • StripeReceipt08:55Payout of kr 48 200 — sent to •••• 4411
  • Lena HoffHot prospectYesterdayRe: pilot for Nordlys — We'd like to start in November.

Inbox

See what needs your decision and what agents are working on. Mail, Ada, agents and results in one timeline, with private discussion kept apart from customer mail.

Hosts3 working
  • ronny-macbookmacOS · code · Xcode1 session
  • bimmiLinux · control + code2 sessions
  • alinLinux · code · CI runneridle
  • appsproduction · commands only—
$ hulda-agent setup # outbound only

Your machines

Connect a Mac or Linux box with hulda-agent. Sessions run there and report back to the Inbox. Outbound only, no inbound ports.

Email · as youSent · 09:47
Re: Invoice download fails
FromRonny <ronny@kvist.app>
ToMia Larsen <mia@nordlys.studio>

Hi Mia — fixed. Your October invoice downloads again; the cached PDF had gone missing and we now regenerate it on the fly…

Receipt recordedGmail Edited before sending

Email as you

Read, draft and send through your connected Gmail or Microsoft 365 mailbox. The recorded send status lives in the conversation.

This week Google + Outlook synced
Mon
Nordlys
Tue
Jonas demo
Wed
Deep work
Thu
Booked
Fri
Payroll
Booked through your public page · Meet link attached.

Calendar and booking

Two-way sync with Google Calendar and Outlook, plus public booking pages that attach Meet or Teams links.

Live · AirPods · wake word oncontinues in your Inbox
Ada

“Mia’s invoice fix is deployed and the reply went out. Jonas wants Thursday at two — shall I confirm?”

“Yes, confirm it.”

Voice

Talk to Ada by voice, with a wake word on AirPods, and pick the conversation up again in your Inbox.

Combined 4 companies · one inbox
  • HQchief of staff · morning brief
  • Kvist3 need you · 2 working
  • Lumen1 needs you · 1 working
  • Atlas Labsall clear
Morning brief at 07:30 across all four.

Several products

One place to direct the work across your companies: a combined inbox, calendar and activity feed, and a morning brief.

Changes · billing/pdf.pyView diff
before
return cached_pdf(path)
after
return cached_pdf(path) or render_pdf(inv)
by Claude Code · task 3f9a21c · merge approved by you
Nordlys Studio · Swedish entitypays quarterlyprefers emailpilot since March

Memory and record

Thread keeps business context close to the work. Recorded changes carry the agent, the task and the before and after.

  • Morning briefran 2h ago
  • Sentry alert → propose fixdraft for approval
  • Receipt → bookkeepingauto-act
  • Pilot follow-upsdraft
Spend today $4.12 of $25 cap

Automations

Schedule recurring work and react to webhooks under the same approval rules. Spend caps pause work and tell you why.

Code

Coding sessions that live in your inbox.

Give Claude Code or Codex a task in the Inbox. Follow its progress on your connected machine, steer the session, and review the result in the same thread.

  • Your coding agents, on your machines

    Claude Code and Codex run headless on any connected Mac or Linux host. Open the terminal when you want direct control, then hand back.

  • Review changes in the conversation

    A worktree per session and changed files on every turn. Ask for a pull request; merging and deploying happen when you say so.

  • Updates come back to you

    Ada watches CI, review and merge and brings the results to the thread. No model or shell stays running just to wait.

  • Inspect the work together

    A shared headless browser both of you can drive, and a spoken digest when a session finishes.

iPhone · early access

Your Inbox and your agents, in your pocket.

Review results, approve drafts and steer sessions when you step away from your desk. The app mirrors your working set, so what you do lands fast even on a bad connection.

  • Approve a draft on the train

    Read the draft, edit it if you like, and send it from your connected mailbox in one tap.

  • Steer a running session from the sofa

    Send a follow-up to a running agent, or queue it for the next turn. Queued cards show exactly what is pending.

  • Talk with your hands in your pockets

    Voice mode with a wake word on AirPods. Ada reads the Inbox; you answer.

Dictation in the composer. A spoken digest when a session finishes.

Built the way it works

Built by one founder, working with agents.

“I run my own products through Thread every day, and I used it to build Thread. This page is the latest example: one instruction in my Inbox, one coding session on my Linux box, a second agent’s critique, a pull request and CI. I still make every call that matters; the agents do the hours.”

Ronny Bruknapp, founder

1,200+
commits since April 2026
4,400+
tests across web, iPhone, host daemon and backend
1
instruction in the Inbox started this page; a second agent reviewed it

Questions

Before you connect anything.

Straight answers about what Thread needs, what it may do, and what it will not do without you.

How does the waitlist work?

Tell us about your company below. We read every application and invite founders in small batches, newest products and sharpest use cases first. You hear from us by email; nothing is charged to join.

What do I need to start?

A Gmail or Microsoft 365 mailbox, and a Mac or Linux machine with Claude Code or Codex installed. The hulda-agent daemon connects your machine outbound; there are no inbound ports to open.

What can act without me?

Nothing until you allow it. New automation policies default to draft-for-approval, and coding agents only do what you instruct them to. After a run of approvals without edits, Ada proposes auto-act for that kind of action; you accept or decline, and you can revoke it in a tap. A master switch disables autonomous actions.

Where does the work run, and where does my data live?

Coding sessions run on your own machines, one Git worktree per session. Thread stores the conversations, drafts, send receipts and change records that make the Inbox work, isolated per company.

Is there an iPhone app?

Yes. Web and iPhone open together when your invite arrives: the same Inbox, the same agents, with voice and dictation built in.

What does it cost?

Early-access pricing is not published yet; you will know before your invite, and joining the waitlist costs nothing. You use your own Claude and Codex subscriptions; Thread pools them and parks work until a quota resets instead of failing.

Early access

Give your next task to an agent. Keep it in your Inbox.

Thread is in early access for founders running one product or several. Tell us about your company and we will invite you when your batch opens.

  • Early access opens in small batches. We read every application.
  • Invites arrive by email, for web and iPhone together.
  • Nothing to pay and nothing to set up until your batch opens.

No card, no commitment. We only use this to decide who to invite next and to send your invite. Privacy