---
digest: >
  v0.19.0 expands the Mirror web console from conversation organization into
  direct conversation and journey maintenance. Users can now create journeys
  from Workspace through a reviewable draft flow, delete individual
  conversations, delete selected unassigned conversations in bulk, and see a
  larger conversation trail for selected journeys. The release keeps destructive
  actions explicit, preserves extracted memories when conversations are deleted,
  and treats journey creation as an editable identity artifact rather than a
  brittle administrative form.
---

# v0.19.0 — Web Console Conversation and Journey Maintenance

**Date:** 2026-06-02

## Highlights

- Adds **New journey** in Workspace with natural-language input, generated markdown draft, editable preview, and bounded create validation.
- Adds explicit conversation deletion from conversation detail pages.
- Adds **Delete selected** beside **Assign selected** on the Unassigned conversations surface.
- Preserves extracted memories when deleting conversations by detaching their `conversation_id` instead of deleting the memory records.
- Expands selected-journey conversation visibility from a small eight-item slice to a larger bounded trail.
- Polishes maintenance controls so destructive and primary actions remain visually distinct.

## Where We Started

The previous release made unassigned conversations visible and assignable, which
surfaced the next maintenance gap immediately. Once conversations could be
organized, users also needed to remove disposable or accidental conversation
records without leaving the web console. The same Workspace surface also exposed
a second gap: journeys still had to be created through Mirror skills or direct
identity editing, even though the web console had become the place where
conversation organization happens.

Journey creation was the more delicate problem. A journey is not just a row in a
database. It is an identity artifact that the Mirror uses for routing, memory,
Builder context, and future continuity. A dry CRUD form would create valid rows
that could still be weak journeys.

## What Changed

Workspace now includes a **New journey** action. The first slice asks for the
raw material of a journey in natural language, then generates a structured
markdown draft with title, status, stage, description, current focus, scope, and
done condition. The user reviews and edits the draft before saving. Creation is
bounded by slug validation, duplicate checks, minimum content checks, required
status, and a required description section. Optional metadata such as project
path, icon, and color can be set during creation.

Conversation maintenance also became explicit. Conversation detail pages now
include a confirmed **Delete conversation** action. The Unassigned conversations
surface now supports selecting multiple conversations and deleting them as a
batch, beside the existing assignment flow. Deletion removes messages and
conversation embeddings, clears runtime-session and LLM-call references, and
preserves extracted memories by nulling their source conversation id.

The selected journey conversation list now uses a larger bounded read model so a
journey with more than eight assigned conversations does not appear artificially
short. This is still a protective limit for the browser payload, not a final
pagination model.

## Conscious Exclusions

- Journey draft generation is deterministic in this release; it does not yet use an LLM to infer richer fields from the user's description.
- Journey slug rename, journey deletion, and migration of conversations or memories between renamed slugs are not included.
- The Workspace conversation list still uses a bounded payload rather than pagination or **Load more**.
- Conversation deletion is direct web-console maintenance, not an asynchronous Operation with approval and backup.
- Deleted conversations do not delete extracted memories, even when those memories originated from the deleted conversation.

## What We Learned

The web console is becoming the maintenance home for the personal Mirror. That
changes the design standard: actions must be available where the user notices
the problem, but identity-bearing artifacts still need review and shape before
persistence. The right journey-creation form is not a replacement for the
Mirror's inference. It is a structured drafting surface that keeps the user in
control of the final identity prompt.

## Next Horizon

The visible next step is refinement, not expansion for its own sake: browser
validation of the journey-creation flow, better disclosure when a bounded list
has more items, and eventually a **Load more** or paginated conversation trail
for mature journeys with long histories.
