Demo
Screenshots
This release in the UX fixture harness, with invented data: the owner Ellis, their partner Rowan and the dog Biscuit aren't real.
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
This release in the UX fixture harness, with invented data: the owner Ellis, their partner Rowan and the dog Biscuit aren't real.
Open-source AI assistant for your Mac with long-term memory: chat, voice and iMessage pings, a mind that notices and follows through, and his own sandboxed computer. Next.js, FastAPI, Postgres/pgvector, LangGraph and Claude. Your data stays on your machine.
Most assistants start every conversation from nothing and wait to be asked. Edward is built the other way round:
This release is a snapshot of a build that ran every day for one person for months. The parts that were bespoke to that setup are marked ADAPT: in the code and collected in docs/ADAPTING.md.
Memory
Talking to him
@Edward in any chat, message yourself, or reply to his message, and he answers in that chat in his own turn. Friends can ping him too, inside limits (a few turns an hour per chat, no new conversations with people who did not ask, unknown numbers held for you, and no shell, file editor, Chrome or screens in their turns unless you set EDWARD_FRIENDS_FULL_TOOLSET=on). His messages go out from your own iMessage account on the host Mac, signed as Edward.Doing things on his own
EDWARD_PROACTIVITY on, he reads incoming messages and mail for what matters to you and decides to stay silent, leave a note, or push. Off by default.bash in a persistent sandboxed shell (macOS Seatbelt) in ~/edward-home, a file editor, web search and fetch, a headless browser of his own (Playwright's shell, never your Chrome), and look for images and PDFs. Fourteen tools in total, the same on every surface.EDWARD_CHROME_HANDS=on, he can use your logged-in Chrome. Typing outside a search box or pressing send/post acts as you and runs only when you asked in that turn; payments are refused in every turn. Off by default.Where he shows up
scriptable/): he decides what it shows./screen): a stage he arranges on the host Mac's display, with what he is thinking while he works./hub): a touchscreen page for a kitchen or a pet station — pets' feeding and meds, the family calendar, lists, timers, voice, a photo screensaver. Built so alerts stay rare: only timed doses ever go overdue.companion/EdwardBar).Integrations
whatsapp-mcp).Guard rails
EDWARD_TAINT_APPROVALS=on holds their outward calls for your Approve/Deny..env); and can't reach Edward's own API, his databases or the WhatsApp bridge. It stops accidents and a command he was talked into, but it is not a containment boundary: the shell runs as your macOS user and can write the rest of your home (shell startup files, ~/Library/LaunchAgents) and Homebrew, from which programs run outside the sandbox. For strong isolation, run Edward as a separate macOS user (docs/ADAPTING.md; the full list is in computer.md).@Edward gets no shell, file editor, Chrome or screens, and look only at what they sent or a link, because their message is someone else's text driving a turn on your Mac. EDWARD_FRIENDS_FULL_TOOLSET=on gives them everything. Their turns can still read what Edward reads (your chats, memories and calendar) and answer with the discretion his prompt asks for, which is a prompt, not a wall.You need: a Mac with Apple silicon that can stay on, the Xcode command-line tools (xcode-select --install), Homebrew, and an Anthropic API key. A Mac mini makes a good always-on host.
1. Install.
git clone https://github.com/ben4mn/meet-edward.git && cd meet-edward
./setup.sh # installs everything, asks for your name, API key and time zone
2. Start Edward, one of two ways. Pick one; you don't need both.
Always on (the usual choice for the Mac that hosts him). launchd starts him now and at every login, and restarts him if he stops:
bash scripts/install-launchagents.sh
./setup.sh --launchagents does the same at the end of setup. If you already started Edward by hand from this checkout, the installer stops that copy first.
By hand. He runs until you stop him or the Mac restarts:
./restart.sh # backend :8000, frontend :3000
The first start takes a few minutes: the backend downloads its small embedding model and sets up the database, and the frontend runs its first build. ./restart.sh waits for each (up to 2 minutes for the backend, 4 for the frontend); if one is still busy after that, it says "still starting", leaves it running and exits 0. Watch it with tail -f /tmp/edward-backend.log.
3. Choose a password, on the Mac itself. Open http://localhost:3000 on the Mac that runs Edward. The first visit asks for a password and a one-time setup code. Read the code in a terminal on that Mac, from your checkout:
cat backend/.setup_code
The backend makes the code when it starts and no password exists yet. Only your macOS user can read the file, and it is deleted once the password is set. The log and the scripts say only where the code is, never what it is. Case and dashes don't matter. After 10 wrong codes in 15 minutes, setup pauses until the oldest ages out; wrong codes never count against signing in.
Until a password is set, the API answers nothing but the sign-in pages. The setup request also has to come from a page at localhost on this Mac, so a phone or another computer on your network is told to use the Mac. That check reads request headers, though, and a device on your network can forge them; the code is what keeps someone else from claiming your Edward first. If the Mac has no screen, forward the port from your own computer (ssh -L 3000:localhost:3000 [email protected]), open http://localhost:3000 there, and read the code over ssh (ssh [email protected] cat <your checkout>/backend/.setup_code).
./setup.sh is safe to run again; each step checks what is already there. It stops before installing anything on an Intel Mac or in a Rosetta shell (Platform support). It installs [email protected], postgresql@16 and node with Homebrew, builds pgvector from source for Postgres 16, creates the edward database, makes backend/.venv with pinned dependencies, installs Playwright's headless shell, runs npm ci, builds two small Swift helpers (media and EventKit), and writes .env from .env.example.
scripts/install-launchagents.sh installs the backend, the frontend, a health check every five minutes (plus a deeper one at 08:00), a nightly backup at 03:30 (to ~/edward-backups unless EDWARD_BACKUP_DIR says otherwise; the dumps are readable by you alone) and a daily memory report, labelled com.meet-edward.* (EDWARD_LAUNCHD_PREFIX). It takes --with-graph, --without-backup, --dry-run and --uninstall. With the agents loaded, ./restart.sh (or ./restart.sh backend|frontend) restarts through launchd. It only ever restarts its own checkout's Edward: in a second clone or a worktree it refuses (exit 78) to touch agents that run another checkout. Logs are in /tmp/edward-backend.log and /tmp/edward-frontend.log.
After you sign in:
Settings → Mind → Skills. Every skill starts off on a fresh install, so Edward can use none of them until you turn them on here. Turn on what Edward may use: Shell/Bash (his computer: bash and the editor), Web Search, iMessage, Push Notifications, iOS Widget.
Settings → House → Locale. Check your time zone: reminders, quiet hours and "today" follow it.
macOS permissions (System Settings → Privacy & Security), only for what you use:
setup.sh prints at the end. Edward reads iMessage, Mail, Contacts, Calendar and Reminders from their databases through it. If you start Edward by hand with ./restart.sh rather than the LaunchAgents, macOS charges your terminal app instead, so grant that too.bash backend/scripts/eventkit_request_access.sh while sitting at the Mac.docs/ADAPTING.md has the full list, and what to redo after brew upgrade [email protected].
Reaching him from your phone. Installing the PWA, push notifications and the microphone all need HTTPS. Put a tunnel (Cloudflare Tunnel, Tailscale, ngrok) or a reverse proxy in front of port 3000, set EDWARD_PUBLIC_BASE_URL to that address, and name the tunnel's LaunchAgent in EDWARD_TUNNEL_LABEL so the health check watches it. The backend listens on every interface so devices on your network (a hub) can reach it; EDWARD_BACKEND_HOST=127.0.0.1 keeps it to this Mac. Sign-in allows 5 failed tries per client in 15 minutes, and 100 from all clients together (past that, signing in pauses for everyone until the oldest failures age out; changing your password is limited per signed-in session instead, and never by that ceiling); behind a tunnel the client is read from the tunnel's own headers, so leave uvicorn's FORWARDED_ALLOW_IPS unset (auth-and-pwa.md).
Everything lives in .env at the repo root; .env.example describes every setting with its default. The backend loads it itself (a value set in its environment wins), and the start scripts never export it. Most values are read on every call; restart the backend to be sure (./restart.sh backend).
About you (backend/services/owner.py):
This Mac (backend/services/host_config.py): EDWARD_PUBLIC_BASE_URL (where you open Edward; links in pushes and texts use it), EDWARD_TUNNEL_LABEL, EDWARD_BACKEND_HOST, EDWARD_LAUNCHD_PREFIX, EDWARD_BACKUP_DIR. The frontend bakes its public origin (NEXT_PUBLIC_BASE_URL, default EDWARD_PUBLIC_BASE_URL, used for link previews) into the build, so after changing it run bash frontend/deploy-build.sh and restart the frontend. The session cookie is Secure, which assumes HTTPS (browsers generally make an exception for http://localhost). If signing in at a plain-HTTP address keeps sending you back to the login page, and it is a network you trust, set EDWARD_COOKIE_SECURE=off.
The model and the money. EDWARD_LLM_PROVIDER=anthropic is the default: every call goes to the Claude API, one route per purpose (Sonnet for chat, wakes and the screens, Haiku for background memory work, Opus for evaluations), each overridable with EDWARD_CLAUDE_<PURPOSE>_MODEL and friends. EDWARD_DAILY_SPEND_CAP_USD (default 5), EDWARD_TURN_MAX_USD (3.00) and EDWARD_AUTONOMOUS_TURN_MAX_USD (1.00) bound the spend.
Off by default, and how to turn it on:
docs/ADAPTING.md lists every default, including what is on (the spend cap, quiet hours, the two daily wakes, the nightly backup).
The iPhone widget: copy scriptable/edward-widget.js into Scriptable and fill in your public address and your widget token (open /api/widget/token on your Edward while signed in). Treat the token like your password: besides the widget, it can chat with Edward as you (POST /api/widget/chat). Put it only on your own devices, and if it leaks, replace it with POST /api/widget/token/regenerate while signed in.
Next.js PWA (:3000) ──/api──▶ FastAPI (:8000) ──▶ PostgreSQL 16 + pgvector (:5432)
Today · Chat · Voice │
Edward tab · /screen · /hub │
├─ a turn (LangGraph): preprocess → retrieve_memory → respond (tool loop) → extract_memory
├─ one toolset of 14 tools; bash runs in a Seatbelt sandbox in ~/edward-home
├─ listeners: iMessage (chat.db), Mail, Gmail → the mind (wakes, noticing, pings)
├─ scheduler (every 30 s), consolidation (hourly), the screens' pulse
└─ the Claude API: ChatClaude, one route per purpose, a daily dollar cap
The backend runs natively on macOS, not in Docker: it reads Apple's databases, talks to Messages over AppleScript, and sandboxes Edward's shell with Seatbelt. Every subsystem has its own page in docs/architecture/.
macOS on Apple silicon only. Intel Macs are not supported: setup.sh stops before installing anything on an Intel Mac, in a Rosetta (x86_64) shell, or with an x86_64 Python, because the pinned PyTorch behind the local embedding model has no x86_64 macOS wheel. The EventKit helper (changing Calendar and Reminders) needs macOS 14 or later; on an older macOS setup.sh warns and Edward runs without it. Linux and Windows (WSL) are not supported: setup.sh stops on anything but macOS, Edward's bash tool needs macOS Seatbelt and fails closed without it, and the Apple integrations (iMessage, Mail, Calendar, Reminders, Contacts) have nothing to read. If you want to try a port, docs/ADAPTING.md lists the macOS-specific seams.
This release replaces the March 2026 public version. Self-evolution, the Lightpanda browser, the Python/JavaScript/SQL sandboxes, LangSmith and the morning briefing are gone; your memories, conversations, documents, files and scheduled events are kept and migrated in place on first start. Back up first, then follow docs/UPGRADING.md.
Contributions are welcome. CONTRIBUTING.md covers setup, the test database, the checks a change must pass and the privacy rules. Open an issue first to talk about what you would like to change.
To cchen362 for the orchestrator fix (worker tools reported "Error: None" on success, #5), which this release carries.
Open-source AI assistant for your Mac with long-term memory: chat, voice and iMessage pings, a mind that notices and follows through, and his own sandboxed computer. Next.js, FastAPI, Postgres/pgvecto
Visão geral
Open-source AI assistant for your Mac with long-term memory: chat, voice and iMessage pings, a mind that notices and follows through, and his own sandboxed computer. Next.js, FastAPI, Postgres/pgvector, LangGraph and Claude. Your data stays on your machine.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Meet Edward roda localmente via stdio.
Última verificação: 2026-10-28. Open-source AI assistant for your Mac with long-term memory: chat, voice and iMessage pings, a mind that notices and follows through, and his own sandboxed computer. Next.js, FastAPI, Postgres/pgvector, LangGraph and Claude. Your data stays on your machine.