An AI assistant that remembers, and follows through.

Open source, and built for one person: you. Edward runs on your Mac, knows where he heard what he knows, keeps the promises he makes, and works in a sandboxed computer of his own.

Meet Edward, in five minutes. The people and pets are invented; the screens are the real app on test data. Download the MP4

Capabilities

More than a chatbot.

Memory with provenance

Every memory records who said it, what it is about and how sure he is. Ask how he knows something and he shows you. Only your own words become his standing instructions.

A computer of his own

A persistent shell, a file editor and a headless browser, sandboxed on your Mac: he can’t touch his own running code, read his keys or reach your database.

Follow-through, with a journal

When he says he’ll check back, he schedules it and comes back. Whatever he does on his own gets a journal entry you can mark right or wrong.

Speaks up once, or not at all

Opt-in noticing reads your messages for what matters (a deadline closing, someone waiting on you) and says it once, through one door, outside your quiet hours.

@Edward in iMessage

Write @Edward in any chat and he answers there, from your own account. Friends can ask too, inside limits; unknown numbers wait for you.

Limits you set

A daily spend cap in dollars, a cap per turn, a secret scan on everything that leaves, and approvals when you want them.

How it works

Three steps. Nothing hidden.

1

You talk

In the app, by voice, or with @Edward in iMessage. The same Edward, with the same memory, everywhere.

2

Edward works

He recalls what he knows, searches the web, works in his own shell, and shows you every step as he goes.

3

Edward follows through

He answers, files what he learned with where it came from, and comes back when he said he would.

Where he shows up

Your phone, your desk, your kitchen.

An app you can install on your phone, live voice, an iPhone widget he fills himself, and push notifications that wait out your quiet hours.

Today — The front door: what needs you, with the action on the card, and what he did on his own.
Chat, with the work rail — Every memory search, page and tool call, live, then folded into a receipt.
The Edward tab — What he knows, watches and does, in five rooms.
His screen — A stage on the Mac’s display that he arranges himself.
The household hub — Optional: pets’ feeding and meds, the calendar, lists and voice on a kitchen touchscreen.

Open Source

Run Edward on your Mac.

You need a Mac with Apple silicon that stays on, Homebrew and an Anthropic API key. Edward keeps what he knows in your own Postgres; the one outside service he needs is the Claude API.

git clone https://github.com/ben4mn/meet-edward.git
cd meet-edward
./setup.sh        # asks your name, API key and time zone
bash scripts/install-launchagents.sh

# then, on this Mac, open http://localhost:3000
cat backend/.setup_code   # the code for your first password

Under the Hood

Built to be trusted.

Edward is a long-running service on your Mac that can read your messages and act as you, so he comes with rails, receipts and limits.

Hybrid memory

pgvector and keyword search, blended 70/30, over a small embedding model that runs on your Mac. Provenance on every row, and upkeep that never deletes.

One tool loop, fourteen tools

The same tools in chat, voice, pings and wakes. What a turn may do is its policy, and a refusal comes back as an honest error, never a hidden tool.

Seatbelt rails

His shell can’t read his keys, write his own code, reach his API or databases, or script your apps. It is not a containment boundary, and the docs say so.

A mind that wakes for a reason

Follow-through on promises, a silent nightly, one small budgeted run of free time a day, and a journal of what he chose to do, instead of a timetable.

Claude, by purpose

Sonnet for chat and wakes, Haiku for memory work, Opus for evaluations. Every call priced and counted against a daily cap.

Notice, then speak

A cheap noticer reads what arrives, a gate in plain code decides, a verified speaker says it once. Quiet hours are enforced in code.

Runs like a service

LaunchAgents, a bottom-up watchdog, verified nightly backups, and staged frontend deploys with a one-command rollback.

Docs written for AI

CLAUDE.md and a page per subsystem, kept honest by a doc lint, so Claude Code can help you set him up, run him and change him.

Frequently Asked Questions