How aiperson works — set up your AI memory in minutes

Two things, projected everywhere

aiperson keeps two things about you and pushes them into every AI surface you open:

Your persona

How you work: voice, the values you hold, conventions you've agreed, things you refuse, how you sign off. It lives in a private git repo you own.

Your corpus

What you've done: git commits, plans, tasks, sessions, calendar, notes — indexed locally so any AI can answer "what was I working on?" with sourced specifics.

Both are read by a single connector that speaks the Model Context Protocol (MCP), so the same persona and corpus show up in Claude Code, Cursor, VS Code, your browser, and your desktop — without you re-explaining yourself each time.

1

Install the CLI

One command. It drops the personkit binary onto your machine — no account needed yet.

terminal

$ curl -fsSL https://aiperson.one/install.sh | sh

▸ downloading personkit (universal)…
▸ installed to ~/.local/bin/personkit
✓ ready — run `personkit setup` to begin

Windows users: irm https://aiperson.one/install.ps1 | iex.

2

Sign in and name your AI

personkit setup opens aiperson.one in your browser. Sign in with GitHub — that binds a private my-persona repo to your account — then give your AI a name. Kairos is the default.

3

Pick a voice

Choose a register — warm, direct, formal, technical. The model interpolates between presets, and you can retune it anytime from Persona → Voice in the dashboard. This is the seed of your persona; it grows from here.

4

Wire every AI tool on your machine

Back in the terminal, personkit setup finishes the job: it detects every supported AI tool you have installed and wires your persona into all of them in one pass — connect, then build your corpus, seed it from your recent git history, and verify.

personkit setup

$ personkit setup

▸ connect wired 6 tools (claude-code, cursor, vscode, windsurf, zed, gemini-cli)
▸ corpus init ~/.dotperson/corpus.db ready (vec + fts live)
▸ seed 312 events from 4 repos · last 30 days
▸ verify 6/6 surfaces OK

✓ done in 4m 12s — open Claude Code and ask "what was I working on?"

5

Use it — in any tool you already have

That's setup done. Now open any wired editor and just ask. Your AI calls aiperson over MCP, pulls the matching events from your local corpus, and answers with specifics — commit SHAs, dates, sources.

Claude Code MCP

you ▸ what was I working on last week?

kairos ▸ calling corpus.query(text: "last week", limit: 20)

Last week you shipped the aiperson UI level-up. Three threads:

• Dashboard SPA + settings — 11 pages exposing every knob [git a0e8641 · 6d ago]
• Docs portal — /docs with seven pages [git 9531d78 · 5d ago]
• Relay cutover — retired the old HTML, added preferences [git ec1cec1 · 5d ago]

Want me to pick up the Chrome Web Store submission you flagged?

The same question works in Cursor, VS Code, Windsurf, Zed — anywhere you wired aiperson. The answer is drawn from your machine, not ours.

◆

The dashboard — every control in one place

aiperson.one/dashboard is mission control. A live view of your corpus, an editor for your persona, and a settings surface for every knob — privacy per kind, embedder choice, sync cadence, notifications, per-tool toggles. Press ⌘K anywhere to jump.

Dashboard overview — stats and recent activity — Overview: your persona at a glance, plus a live feed of recent corpus events.

Persona editor — voice tab — Persona → Voice. Edit inline; changes commit to your git repo.

Corpus search with results — Corpus search. Each hit shows how it matched and where it came from.

Advanced settings — embedder, sync, thresholds — Advanced: the knobs that used to be environment variables, now a form.

◆

Editors and CLIs — thirteen of them

personkit connect writes the right file in the right place for each tool, and registers the MCP server where the tool expects it. It's idempotent — run it again anytime to re-sync. Here's a slice of what it writes:

~/.claude/CLAUDE.md

## Who you're working with
Voice: warm-direct, en-GB, measured cadence.
Values: precision over verbosity; reversibility;
British English; confirm before irreversible ops.
Refuses: force-push to main; committing secrets.

.cursor/rules/dotperson.mdc

---
alwaysApply: true
---
# Your collaborator's persona
Voice: warm-direct, en-GB.
Conventions: numbered migrations; cyan accent;
comments only when the WHY is non-obvious.

Every wired surface, and the file it owns:

Claude Code

~/.claude/CLAUDE.md + settings.json

MCP + Stop hook

Cursor

.cursor/rules/dotperson.mdc

MCP + always-apply rule

VS Code (Copilot)

User/mcp.json + instructions

Native MCP

Windsurf

.windsurfrules

MCP + rules

Zed

assistant settings

Agent config

JetBrains AI

guidelines.md

Markdown rules

Continue.dev

.continue/rules

MCP + rules

Cline

.clinerules

Rules file

Aider

CONVENTIONS.md

Conventions

Augment

AGENTS.md

Agent guide

Antigravity

AGENTS.md

MCP + agent guide

Gemini CLI

GEMINI.md

Context file

◆

In the browser — 21 cloud chat surfaces

The aiperson browser extension brings your persona into every major cloud chat surface — Western and Chinese frontier — that doesn't speak MCP. Open any of them, click the extension, and it injects your persona into the prompt; with opt-in capture per surface, every turn (yours and the assistant's) flows back into your corpus.

aiperson · signed in Detected surface: ChatGPT

Bring your AI into this chat

Capture this conversation

Open dashboard

Chrome, Edge and Brave. Per-surface capture toggles, master kill switch, regex redactor, and traffic-light health dots all live in the popup. An in-page indicator shows when aiperson is recording — one click pauses for a single chat.

All twenty-one supported chat surfaces:

ChatGPT

OpenAI

Verified

Claude

Anthropic

Verified

Gemini

Google

Verified

Microsoft Copilot

Microsoft

Verified

Grok

xAI

Verified

Meta AI

On the desktop — Quick Capture

The desktop app sits in your menu bar. The main window is the dashboard; the real win is Quick Capture — a floating panel on a global hotkey (⌘⇧P) for dropping a thought, decision, or commitment straight into your corpus, from anywhere.

Desktop Quick Capture panel — Type, press ⌘⏎, and it's an event in your corpus with provenance.

◆

Where your data actually lives

aiperson is local-first. We host almost nothing.

my-persona.git

Your persona, in a private GitHub repo you own. Every change is a signed commit.

~/.dotperson/corpus.db

Your corpus, a SQLite file on your machine. Mirroring to our relay is opt-in, per event.

signed snapshots

Export a portable, Ed25519-signed snapshot anytime. Secrets are redacted before anything is written.

Get started Read the technical docs

Sign in to aiperson

Two things, projected everywhere

Your persona

Your corpus

Install the CLI

Sign in and name your AI

Pick a voice

Wire every AI tool on your machine

Use it — in any tool you already have

The dashboard — every control in one place

Editors and CLIs — thirteen of them

In the browser — 21 cloud chat surfaces

On the desktop — Quick Capture

Where your data actually lives