A private chief of staff for one operator. It captures context, holds your business memory, runs scheduled routines, and proposes the work — then asks before it acts.
Three follow-ups went quiet, two drafts are ready for your eyes, and one routine wants your attention before it runs.
Three threads need a moment of you. The afternoon is yours.
Cites your March memo and last week’s call notes. One outbound. No CC.
Conflicts with the Mikhail intro. Two drafts staged.
Vault-backed memory. People, projects, commitments, decisions.
The assistant reads first. You see the six that need a human.
Scheduled playbooks ran while you slept. Every run inspectable.
Every outbound action waits behind an approval object.
Each cell is a real run. Each run is replayable. No work happens off-book.
Transcript-first ingest — Zoom, Meet, Teams, or system audio. Anamora doesn’t just summarize; it extracts commitments, decisions, risks, and next steps, each one tied back to the line in the transcript that proves it.
30 minutes before every recurring meeting, Anamora drafts a brief from your memory: who you’re meeting, the last three things you said you’d do, the open commitments, the risks worth raising. Source notes attached.
Bot, system audio, or a voice memo for the meetings you couldn’t record. Offline recollections are tagged with lower confidence, so the assistant knows which facts to lean on. Nothing leaves your machine until you say so.
Decisions and commitments land in your vault as entities, not bullet points. Drafts for Gmail, Slack, and HubSpot stage themselves for one-button approval. If nobody proposed a next step, Anamora drafts the email that asks for one.
Anamora is built like a desk you own, not a service you rent. The runtime, the vault, the routines — all run wherever you choose to keep them. Nothing leaves unless you send it.
The default. Everything — runtime, memory, runs — lives in your user folder. Closes when you close the lid. The simplest possible deployment.
For operators who want routines running while the laptop sleeps. Run Anamora on a Mac mini and reach it from anywhere — same memory, same approvals, same four walls.
For teams sharing one operator pack, or operators who want a fixed home for the runtime. Bring your own VPS, NAS, or self-hosted box. One binary, your keys, your network.
The vault never leaves the device unless you say so. The model is the only thing that talks to a network — and you choose which model, which provider, and on which key.
The vault never leaves your machine unless you approve a send. The model is the only thing that talks to a network — and it’s your provider, your key, your bill.
Your vault is plain Markdown. Your routines are YAML. Your runs are append-only logs. The export is the directory you already have — and the runtime can keep working without us.
Yes — through the always-on tier. Run on a Mac mini, share the vault, reach the board over Tailscale. Approvals stay per-operator; memory is shared. Up to ~3 people works well.
Every drafted message, every external call, every state change is staged as an approval object with the reasoning attached. Approve. Decline. Or open a thread and discuss it.
You flagged this for send earlier. The draft cites your March memo and last week’s call notes. One outbound message. No CC.
Conflicts with Mikhail intro. Two reschedule drafts prepared, neither sent.
Routines are the unit of proactivity. They have a schedule, a scope, a policy, and a trace. Add your own from a YAML pack, or use the four that come with the app.
Memory is structured around the things your business is actually made of — people, companies, projects, commitments, decisions, risks. Not a notebook. A graph you own.
The board is the front door. Chat is where you and the assistant think together — scoped to a person, a thread, an approval, or the whole business.
Every assistant turn cites its sources. Every action it offers is staged for your eyes first.
open the relationship view →Aiyana asked about pacing on March 18, and the thread quieted after you said you’d “send the revised invoice on Friday.”
I drafted it on Mar 22 and held it — you wanted to confirm the discount with Carla first. Carla never replied.
Each routine declares its schedule, its scope, its policy, and its outputs. It runs against a snapshot of your vault, leaves a typed trace, and never side-effects without an approval object.
Build a new one in YAML, or borrow from the workspace pack.
browse the standard pack →07:30 · daily · workdays only
vault · last 7d · people + projects
read-only · no outbound · staging only
needs-you entries · open-loop digest
Each kind of action sits on a ladder. You decide where the line lives, per skill, per surface. The assistant never quietly steps over it.
The assistant suggests. Nothing is staged. Pure conversation.
all skills · default for new packsIt writes the message, schedules the call, builds the doc — and waits in your inbox.
replies · briefs · summariesIt performs every step except the last, irreversible one. Approval is a single button.
sends · payments · cal invitesIt executes inside a policy and reports the trace. You can rewind any of the last 30.
triage · labeling · note filingReserved for read-only routines and internal memory work. Never reaches the outside world.
memory consolidation onlyEvery Anamora workspace is a small folder of files: the skills it should know, the routines it should run, the policies it must respect. Version it. Share it. Fork it.
Start from a standard pack — solo founder, agency lead, executive — or assemble your own. Switch packs per client and the assistant becomes a different person, with a different memory, in the same window.
Each operator’s install is shaped by hand — to your stack, your tools, the routines you already keep, the language your team uses. Eight stages, about four to six weeks end-to-end, and a real person on the other side of every one.
you tell us how you work and what you'd want held
we read it, then we talk — desk to desk
what's in scope, what's not, the price, the calendar
gmail, slack, calendar, notion — whatever's on your desk
the assistant learns your team's words and your weekly cadence
runtime, vault, model keys — where you choose
daily check-in, every morning's read reviewed together
we stay reachable, but the desk is yours
An hour for the fit call. Two hours scattered across the build for stack walkthrough and pack review. A pilot week where you actually use it and tell us what’s wrong. That’s it.
The agent runtime ships inside the desktop app. No extra CLI to install. No service to depend on.
Memory and runs live in a vault you own. The app never accumulates state we don't show you.
The control plane sits between intent and action. The default is always: ask first.
Customize per client with files, not code. Skills, routines, policies — all under version control.
Routines are bounded and scheduled. There is no zoo of permanent personalities running in the background.
Every routine, every draft, every approval can be replayed and inspected. Trust by visibility, not by promise.
Tell us a little about how you work, what you wish was being held, and which tools the assistant would have to know. We read every application; the fit call follows within a week.
Privacy, models, meetings, deployment, money — the things you’d ask on the fit call, written down.
The vault, the routine traces, the meeting transcripts, the staged drafts — all stay on your device. The only thing that talks to a network is the model, and you choose which model, which provider, and which key.
When you approve a send, that one outbound message goes through your own integration (Gmail, Slack, etc.) — also keyed to your account, not ours.
Crash reports if you opt in (off by default). The license check, which is a single signed token call. That’s it. No telemetry, no usage analytics, no “anonymized” memory. We don’t have a database that mirrors your work.
Yes — bring your own key is the default. Anamora speaks to Anthropic, OpenAI, or any OpenAI-compatible endpoint. The recommended model for the assistant turn is Claude Opus 4.7 or GPT-5.4; routines and triage default to a smaller, cheaper model.
Your keys live in the OS keychain on your install. They never reach our servers.
Three ways, your call. Bot mode — Anamora joins your Zoom, Meet, or Teams call as a named participant and records on its own. System audio — Anamora records the audio of whatever’s playing on your machine, no bot needed. Voice memo — for the meetings you couldn’t record, dictate the recall and Anamora tags it with lower confidence.
Yes. Every extracted item carries a timestamp, a speaker, and the exact line in the transcript. Click any commitment in the post-meeting view and you walk back to the moment that produced it.
You move the vault folder to a Mac mini in your office or a small Linux box you own. Same binary, same memory, same approvals — the runtime doesn’t care where the files live. Most operators stay on the laptop forever; the always-on tier is for the few who want routines firing while the lid is closed.