---
digest: >
  v0.42.0 lets a host read and edit a persona. `mirror-mind/desktop` gains three calls:
  `listPersonas`, `readPersona` and `updatePersona`. The update writes only the fields it is
  given (name, prompt, description, routing keywords), keeps every other metadata key, refuses
  a stale edit and goes behind the front door's verified snapshot. Additive: the Desktop API
  version stays 1. No schema change, no migration, no model change.
---

# v0.42.0 — A Persona the Host Can Read and Edit

**Date:** 2026-11-08

## Highlights

- **Three persona calls in `mirror-mind/desktop`**
  ([CR205](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr205-let-the-host-read-and-edit-a-persona.md)).
  `listPersonas(dbPath)` answers each persona's `id`, `name` and `description`, by id.
  `readPersona(dbPath, { persona })` answers it whole: `prompt`, `name`, `description`,
  `routingKeywords`, `defaultModel`, `inheritsFrom` and `updatedAt`.
  `updatePersona(dbPath, { persona, expectedUpdatedAt, ... })` changes its `name`, `prompt`,
  `description` or `routingKeywords` and answers the persona as `readPersona` reads it.
- **Only what you give is written.** Every metadata key the call does not write is kept in
  place, `persona_id` and `briefing` included. `null` removes a name or a description; an
  empty list removes the keywords. An update that changes nothing writes nothing.
- **A refusal writes nothing and names the field.** Refusals are `PersonaCallRejectedError`s
  with a `reason`: `invalid_name`, `invalid_prompt`, `invalid_description`,
  `invalid_routing_keywords`, `unknown_persona`, `persona_changed`, `metadata_unreadable` or
  `invalid_request`.
- No schema change, no migration. `DESKTOP_API_VERSION` stays 1.

## Where We Started

Nautilus for Mirror shows a persona's name beside each answer (CR204) and is building a
screen that opens the persona from that name. The Desktop API had no persona call: a host
could not list the personas, read one or change one without writing the identity table
itself, which no host may do. The CLI's `identity set` writes only a persona's content.

## What Changed

**Shaped like the Journey calls.** `ts/src/persona/personaCalls.ts` takes an explicit
database path, refuses a database that is not `current` with `DatabaseNotCurrentError`, and
checks the whole request before it opens the database for writing. The reads open
read-only. The update writes in one immediate transaction, behind the verified snapshot the
front door takes before a write.

**A stale edit is refused.** `updatePersona` takes back the `updatedAt` it read, as
`updateJourney` does, and refuses with `persona_changed` when another write came between.

**Bounds.** A name is trimmed, 1 to 80 characters, with no control character, as CR204
reads it. A description is trimmed, 1 to 2,000 characters. A prompt must not be blank and
is kept as given. Keywords: at most 200, each trimmed, 1 to 80 characters, no control
character. Metadata that is not a JSON object is refused rather than replaced, though a
prompt alone can still change.

**Read only.** `defaultModel` and `inheritsFrom` are returned and never written. A metadata
`briefing` is not offered: nothing in the Core reads it, and the seed puts a YAML briefing
into the prompt. It stays untouched.

## Conscious Exclusions

- **An edited prompt does not reach a conversation where the persona already spoke.** A
  delta delivers a persona's prompt once per session and remembers only its id; the edit
  takes effect in new conversations and after a compaction.
  CR206, "Deliver a persona again when its prompt changed" (PR #69), captures the fix.
- **An edited prompt keeps its generated descriptor**, as `mirror identity set` does. The
  router reads the descriptor only for a persona with no `description`;
  `mirror descriptor generate` refreshes it.
- **No create, delete or image.** A persona's image belongs to the host.
- **No CLI command** for the new calls: the CLI keeps `identity set` and `inspect persona`.

## Upgrading

```bash
mirror runtime update
```

Nothing to configure. A host that embeds the Core moves its pin to 0.42.0 to use the calls.

## Next Horizon

CR206, so an edit reaches the open conversation; a command and a host call to set a
Journey's `default_persona`; Nautilus for Mirror's persona screen on these calls.
