Founding 500: $29 a month, locked for life. 417 machines left.
Tweety Bird
Install

A Wednesday, with Tweety Bird.

You kick off work from your phone. It runs on your Mac. Both agents share what they learn.

One command. Card is not charged until it proves it remembers. Reply "goldfish" for a full refund, any time in 60 days.

The whole thing in three sentences.

  1. A text thread on your phone reaches a small process on your own Mac that sits beside Claude Code and Codex.

  2. Both agents read from and write to one memory on every turn, so what one decides the other knows.

  3. Because the thread is on your phone and the process runs on a box that does not sleep, the laptop lid stops being the end of their workday.

Sixty seconds.

The full day.

  1. You kick off the billing migration in Claude Code, close the lid, and walk to lunch.

  2. Claude hits a permission prompt. Your phone buzzes in the taco line: the prompt, the diff, three buttons. You are not flying blind. You see the button. You tap "Show me" and read the migration on a screen you can actually read. You tap Yes. Claude keeps going. Fifty-five minutes of agent time you would have lost, kept.

  3. "how's the migration." The reply: 47 of 47 pass, and "you told me Thursday to keep Stripe customer IDs denormalized on the org row, so I left that alone." You screenshot it. Caption: "my coding agent remembered tuesday." Forty likes before you finish the taco.

  4. "codex, review what claude did on billing." Codex opens the PR already knowing the Thursday decision. It does not flag the denormalized IDs. It finds an actual bug in the retry path instead. You did not re-explain anything.

  5. Claude hits the 5-hour window. Used to be the most-hated moment of the day. "codex, take the rest of the migration." Codex takes it, mid-thought. The cap is a handoff now, not a reset.

  6. Lid closes. Laptop in the bag. The mini keeps working.

  7. Couch. Side project. "check whether the stripe webhook retry landed in prod and fix the flaky test we found tuesday." It knows which test. You never open the laptop.

  8. You kick off the long refactor before bed. At 11:22 it hits a prompt. Your phone buzzes once. You read the diff in bed, tap yes, and go to sleep. It finishes at 2:04 AM.

  9. The first thing you check is not GitHub. It is a text: "Refactor done, PR #412 open, CI green, 3 files you should eyeball: [links]." Attached: the diff as a file.

  10. The dependency audit ran. It did not "fix" the pg pin, because it remembers why you pinned it. It opened a PR for one real CVE and texted you the link.

  11. Standup. "PR's up, waiting on review." Nobody asks how your PR count doubled.

What is actually running on your Mac.

  1. the thread

    Telegram, iMessage, WhatsApp, Slack DM, or Discord. Whichever is already open on your phone. Both agents live in it. Say "codex, take it from here" and Codex takes it. Say nothing and the agent that was working keeps working. No new app, no new login, no QR code per session.

  2. the process

    One small daemon that sits beside Claude Code and Codex, not inside them. It keeps running without a terminal window, a foreground app, or a flag you forgot to pass. It pauses when the Mac sleeps and resumes when it wakes. Nothing in it lives inside either agent, so when Codex ships a new CLI your thread still answers and your 7 AM audit still fires.

  3. the memory

    Written and read on both agents' lifecycle hooks, every turn, deterministically. Decisions, the why behind them, rejected approaches, conventions, promises the agent made. Not your source. It lives outside the context window, which is why compaction cannot delete it and the 5-hour cap cannot reset it. Under the hood it is MemoryRouter, which is in production and is the reason this is not another SQLite file nobody queries.

  4. the relay

    A permission prompt on your Mac becomes a message on your phone with the diff and three buttons. Approvals require a paired device, not just a message. You set the policy per repo: reads, tests, lint, and PRs to a branch run unattended; spending money, pushing to prod, messaging anyone, and deleting anything wait for your tap.

  5. the hands

    A real Chrome on your Mac using the logins you already have, and a real cron that runs with today's memory and catches up if the Mac was asleep. Both kick off from a text or a schedule. Downloads land in the thread as files.

What it does not do.

  • It does not run your agents somewhere else. If the Mac is off, nothing runs. That is the point.
  • It does not replace Claude Code or Codex, or sit between you and the labs. You keep your plan, your login, your CLI.
  • It does not run --dangerously-skip-permissions. Unattended means you are one tap away, not that the guardrails are off.
  • It does not store your source. It stores what your agents decided and why.

Try the first ten minutes.

One command. Five minutes. Tell Claude one decision, ask Codex, and watch it answer. Your card is not touched until it does.

Install in one command

$29 a month, locked for life for the first 500 machines. 417 left. Reply "goldfish" for a full refund, any time in 60 days.

Your laptop closes at 6. Your agents don't.