---
title: Teach Omniscio About Me (guided personalization mission)
---
# Teach Omniscio About Me (guided personalization mission)

## What it is

A short coached mission that interviews the user for a few facts about
themselves — what to call them, their world, how they like answers, and what
they're working on — then saves a tidy "About me" block into Omniscio's global
**Custom Agent Instructions** (`defaultAgentInstructionsCustom`). Because that
field is injected into every Claude session via `.claude/amc-instructions.md`,
every future session starts out already knowing the user. Windows-only in v1.
Fully reversible.

## Where to find it

From the mission picker — the **Run a guided mission** button offered on a blank session's nudge or the Dashboard empty state. It never launches itself, and the result lands in **Settings → Agent Instructions**.

## How it behaves

### How to reach it

From the mission picker (the **Run a guided mission** button in a blank
session's nudge or the Dashboard empty state). It is never auto-launched — it
needs the user to want to share. Re-running it updates the same block in place.

### The flow

1. **Kickoff card** — "Want me to learn a little about you?" → **Yes, get to know me** / **Maybe later**.
2. **Interview** (plain chat) — four light, skippable questions.
3. **Confirm card** — "Here's what I'll remember about you:" → **Save it** / **Tweak something**.
4. **Result card** — confirms the save, points to Settings → Agent Instructions, offers **Undo**.

### Trust model

- Touches exactly one of the user's own settings — never a file, never the cloud.
- Never clobbers existing Custom Instructions: the profile is wrapped in a
  clearly-marked `<!-- Omniscio:ABOUT-ME:START -->…<!-- Omniscio:ABOUT-ME:END -->` block,
  appended or replaced in place (idempotent).
- Undo restores the exact prior value (including anything the user had typed).
- The save applies inline (no approval popup) because the mission carries a
  per-session in-app token; the in-card "Save it" is the consent.

## For agents

### How it works (for agents with repo access)

`source: 'teach-amc-about-me'` routes through `createSessionWithPrompt`.
`registry.ts` marks the mission `injectInAppToken: true`, so `session-create.ts`
mints an in-app token and writes a `about-me-conn.json` (`{ port, token }`) into
the mission's `.first-mission` manifest dir. The bundled helper
(`src/main/services/first-mission/about-me.ts`, dispatched by the mission CLI's
`about-me-read|apply|undo` subcommands) reads that file, does the marked-block
merge, snapshots the prior value to `about-me-manifest.json`, and `GET`/`PATCH`es
`/settings/defaultAgentInstructionsCustom` on the control server (inline-apply
for in-app-session tokens). Telemetry lands under the `teach_about_me` feature.
The renderer reuses the generic `confirm`/`result` mission cards unchanged.

## Related

- [default-agent-instructions.md](default-agent-instructions.md) — the Custom Instructions field this mission writes.
- [first-mission.md](first-mission.md) · [project-kickstart.md](project-kickstart.md) — the other two missions.
- [settings-patch-approval.md](settings-patch-approval.md) — the control-server settings-write path (inline for in-app sessions).