Cortland 🍎

Give an AI real access to your Mac — Mail, Calendar, Reminders, Notes, files — without giving it the keys. Every consequential action previews first, waits for your approval through a channel the model can't touch, gets logged, and can be undone. Bring your own model: Claude, or a local one that never leaves the machine.

You:       Add a reminder to call the vet tomorrow at 2pm
Cortland: Received — working on it…
Cortland: Added "Call vet" for tomorrow, Aug 3 at 2:00 PM.

That conversation happened over iMessage, answered by a 4 GB model running on an 8 GB MacBook Air. Nothing left the Mac.

The texting interface needs a second Apple ID, signed into Messages on the Mac only — a mouthpiece, not a worker. It owns no mail, no calendar, no data. You text it from your phone like any contact; the Mac still does the work as you. Your system iCloud stays yours. Claude Code, Cursor, Codex, and other MCP clients skip this step: they talk to the same tools over stdio.

What it looks like in use

Ask about your week — reads are free, no approval needed:

You:       Anything from the school this week?
Cortland: Three emails from Lincoln Elementary. Two are the weekly
            newsletter; one from Ms. Alvarez on Tuesday asks for a
            permission slip by Friday.

Ask it to change something — writes stop and ask, every time:

The code in that prompt is generated by the framework and never enters the model's context — so even a fully prompt-injected model can't forge your approval. Ignore the message and the action expires, refused.

Ask what it can do — answered from the tools actually installed, so it can't overclaim:

You:       what can you do?
Cortland: Here's what I can do with your Mac:
            • Calendar: list, look up, create, delete
            • Mail: search, read, follow threads, draft, send (asks first), flag, file
            • Notes: search, read, create, add to
            • Reminders: list, search, create, tick off, delete

            Anything that deletes or changes things asks you first — I text
            you a code and wait for "yes <code>". Reads just happen.

In Claude Code or Claude Desktop, the same tools are just there:

You: send a reply to Ms. Alvarez saying the slip is coming Thursday Claude: [searches mail, reads the thread] I can send this from your Personal account to alex@example.com. Approve in the usual channel.

mail_send is write-gated. Live mode plus per-action human approval. A stolen token can only ask.

Requirements

macOS only. Nothing here runs on Windows or Linux — the tools talk to Apple apps via Automation.

iMessage bridge only: macOS 13+ (modern chat.db), Full Disk Access for the process that runs Node, Automation → Messages, and a second Apple ID signed into Messages.app — not into System Settings. See SETUP.md §5.1.

Osaurus as a client: Apple Silicon, macOS 15.5+.

Not required: an npm @cortland install (0.2.0 is GitHub-only for now), a developer account, iCloud for Path A, or any API key.

Quick start

Fastest path to “it searched my mail” — Cursor (or Claude Code) as the brain, no second Apple ID, no Ollama:

xcode-select --install          # if `xcode-select -p` fails
git clone https://github.com/cortland-suite/cortland.git
cd cortland
npm install && npm run build    # first install compiles sqlite — a minute

Then Cursor Settings → MCP, add servers pointing node at packages/mail/dist/server.js (and reminders/notes/calendar if you want them). Absolute paths. JSON is in docs/08_local_models.md.

Ask: search my mail for anything from school this week. macOS will prompt Automation (Cursor → Mail). Allow it.

Writes stay previews until you set "live": true in ~/Library/Application Support/cortland/config.json. Even then, send/delete asks you per action.

Texting it from your phone is a longer path (second Apple ID + Ollama). SETUP.md is the ordered list; docs/08 is the illustrated one.

Why it exists

Most MCP servers for personal data are thin wrappers around AppleScript: delete_email, send_message, executed the instant a model calls them. That's a hard thing to trust with an inbox, and the alternatives don't help — cloud assistants (Poke, Arlo, Lindy) can't touch Apple-native data at all, because Apple gives them no API, and self-hosted agents like OpenClaw run ungoverned (a CVSS 8.8 in January 2026, with permission gates still on the roadmap).

Cortland inverts the default. A tool call previews what it would do unless you've opted into live mode, and even then every consequential action waits for you. The framework enforcing that is a small library with a test suite proving each guarantee can't be bypassed — and every tool in the suite is built on it.

The guarantees

Install

@cortland 0.2.0 is not on npm yet. From the repo:

git clone https://github.com/cortland-suite/cortland.git
cd cortland
npm install
npm run build
npx cortland setup

The wizard asks before every step and records what it did. Full walkthrough — including the iMessage bridge, permissions, and model choice — in SETUP.md. Connecting Cursor, Codex, LM Studio, Osaurus, or Ollama: docs/08_local_models.md.

Packages

Bring your own model

Cortland is the tools. You pick the brain.

Path A. Cursor, Claude Code, Claude Desktop, Codex, LM Studio, or Osaurus hosts the model. Cortland is an MCP plugin. No second Apple ID.

Path B. You text it. A second Apple ID signs into Messages on the Mac (mouthpiece only). Ollama runs Gemma 4 on disk. Approvals are yes <code> in the same thread.

Field-tested on an 8 GB M2: gemma4:e2b-it-qat (4.3 GB) makes clean tool calls and refuses honestly. The governed contract matters more with a small model, not less.

Walkthroughs, including LM Studio and Osaurus from a clean install: docs/08_local_models.md. Clean-Mac order, permissions, and the iMessage second-ID steps: SETUP.md.

Privacy model