Mora

Experimental local-first memory and cited meeting context for AI agents.

[!WARNING] Mora is early alpha software. Its connectors, local corpus, search, citations, and identity review work. Its meeting output has not yet passed a product-quality test with real data. Treat each item as past evidence to check, not as a verified current obligation. Follow the quality-gated alpha plan.

Mora syncs read-only copies of Gmail, Google Calendar, iMessage, Apple Calendar, and selected files. It stores them as readable Markdown and a rebuildable SQLite index on your machine. MCP clients and the shell can use this corpus. Several agents can then find the same history with citations.

Mora does not upload your corpus by default or host it for you. Backup and share commands can send selected data to places you control. A cloud agent can also send retrieved text to its model provider. The agent and its group policy control that action.

Current product hypothesis

Before a client meeting, Mora should show what you owe and what they may owe. It should show what changed in Gmail, iMessage, and Calendar. It should give exact evidence and warn when a required source is stale.

This is the product hypothesis, not a proven claim. Mora now finds and cites past candidate lines. Work continues on typed direction and closure, fail-closed product health, and the narrow Before / Teach / Health experience. Real-user tests also continue through seven ordered evidence gates.

What works today

• Read-only ingestion. Mora turns Gmail, Google Calendar, iMessage, Apple Calendar, and selected folders into local Markdown memories. iMessage and Apple Calendar require macOS.
• A corpus you own. Markdown is the source of truth; embedded SQLite, FTS, vectors, and the person graph are indexes that you can rebuild.
• Cited recall. search, think, brief, and meeting-prep surfaces return stable IDs and dated evidence. Optional Ollama embeddings are loopback-only.
• Cited meeting context (experimental). Meeting output shows past extracts that can matter. It does not yet prove the obligation owner, direction, or closure. Check each citation before you act.
• Reviewable identity proposals. Mora can propose email↔phone joins from Address Book evidence. Mora never applies these joins on its own. Confirm, reject, and undo actions stay local and leave an audit trail.
• Agent-agnostic access. Twelve MCP tools and equivalent CLI commands work with any client that can launch a local stdio MCP server.

Install — experimental

Release files are test builds. macOS files have ad-hoc signatures, not Developer ID signatures or notarization. Windows files have no signatures. The remote installers check the selected archive against the release checksums.txt. They stop if they cannot do this check.

macOS / Linux release build

curl -fsSL https://raw.githubusercontent.com/pyranthus-hq/mora/main/install.sh | sh

The installer downloads the current release and checks its SHA-256. It then extracts and installs mora, and starts ~/vault/mora. On macOS, it also prints and runs the quarantine removal and ad-hoc signing steps. The current build needs these steps because it is not notarized.

Build from source

go install github.com/pyranthus-hq/mora/cmd/mora@latest

This needs Go 1.25+. Source builds report dev and do not update themselves. They include only the committed non-secret OAuth placeholder. For Google access, use your own client through MORA_GOOGLE_CREDENTIALS. See Connect Google.

Windows

iwr https://raw.githubusercontent.com/pyranthus-hq/mora/main/install.ps1 -OutFile $env:TEMP\install-mora.ps1; powershell -ExecutionPolicy Bypass -File $env:TEMP\install-mora.ps1

The PowerShell installer checks the release checksum. It installs to %LOCALAPPDATA%\Mora\bin and adds that directory to the user PATH. SmartScreen can still warn because the binary has no signature. See the Windows guide for platform details and Task Scheduler commands.

Connect one source

For the fastest low-trust start, choose a folder:

mora doctor
mora connect filesystem ~/notes
mora search "a project or person"

Then add only the sources that you want:

mora connect google                 # Gmail + Google Calendar, read-only
mora connect google --account work  # optional second Google account
mora connect imessage               # macOS; requires Full Disk Access
mora schedule install ingest-hourly

Google has not verified Mora's shared OAuth app. Google also limits its test users. For more control, use your own OAuth client through MORA_GOOGLE_CREDENTIALS. The guide explains both paths.

Wire it into an agent

claude mcp add mora -s user -- mora mcp serve
codex mcp add mora -- mora mcp serve

Any other MCP client can launch the same local stdio server:

{
  "mcpServers": {
    "mora": { "command": "mora", "args": ["mcp", "serve"] }
  }
}

Each MCP tool also has a CLI command. An agent with shell access can use mora search, mora think, mora brief, and mora write without MCP. See the wiring guide.

Review identity proposals

Mora never joins an email identity to a phone number on its own. On macOS, it can use Address Book evidence to propose matches for review:

mora merge list
mora merge confirm --handle <phone> --email <address>
mora merge reject --handle <phone> --email <address>
mora merge undo <ledger-id>

Each decision stays local. You can audit or undo it.

Data layout

Mora keeps data in four places. Only the vault cannot be rebuilt:

Run mora config to see the full paths. The vault is plain Markdown. Use full-disk encryption such as FileVault or BitLocker. You can also opt in to backup and encrypted sharing. These paths are outside the current product hypothesis. Read the guide before you enable either one.

Privacy boundary

• Read-only at the source. Google scopes are gmail.readonly and calendar.readonly; iMessage and Apple Calendar databases are opened read-only. Mora never sends mail or changes source records.
• Local corpus. The vault, index, tokens, sync state, and usage log remain on your machine. By default, the usage log stores local run data but not query text. It honors mora usage off / DO_NOT_TRACK=1.
• Explicit network paths. The Mora process uses the network for enabled source sync and release updates. It also uses the network for backup or sharing when you enable them. Optional Ollama inference is restricted to loopback.
• Downstream agents are a separate boundary. After an MCP client retrieves context, its model and data policy apply. A cloud agent can send retrieved text to its provider.
• Plaintext at rest. Any process that can read your home directory can read the vault. Protect the device. Do not put the vault in an unencrypted remote.

Project status and contributing

The active product plan is the Mora Home alpha epic. It has no ship or payment deadline. Current work will close the rendered-output audit and run proof before commitment-quality work starts.

• Guide — commands, connectors, and operational details.
• Architecture — as-built subsystem spec.
• Contributing — build, test, and review contract.
• Security policy — report vulnerabilities privately; never paste vault contents or credentials into a public issue.