ei-tui 0.9.3 → 1.0.0

package/src/prompts/human/topic-scan.ts

@@ -14,6 +14,17 @@ function participantContextSection(ctx: ParticipantContext | undefined): string
   return lines.join("\n");
 }
 
+function technicalContextSection(technical_context: boolean | undefined): string {
+  if (!technical_context) return "";
+  return `## Technical Context
+
+This conversation originates from a technical source (coding tool session, developer workflow). The human is likely a developer or technical user.
+
+**Treat Technical as a priority category** for topics that are tools, platforms, frameworks, libraries, or technical concepts being actively learned, evaluated, or built with. Flag these even if they seem like passing mentions — technical knowledge compounds and is worth preserving.
+
+`;
+}
+
 export function buildHumanTopicScanPrompt(data: TopicScanPromptData): PromptOutput {
   if (!data.persona_name) {
     throw new Error("buildHumanTopicScanPrompt: persona_name is required");
@@ -56,9 +67,12 @@ Assign each TOPIC one category. Pick the closest fit:
 - **Plan** — concrete intentions with steps in mind
 - **Project** — active undertakings with real progress
 - **Event** — a specific, significant moment that either party might reference later ("remember when...")
+- **Technical** — a tool, platform, framework, library, or technical concept being actively learned, evaluated, or built with
 
 When in doubt, pick the closest match. The update step will refine it.
 
+${technicalContextSection(data.technical_context)}
+
 ## Output Format
 
 \`\`\`json
@@ -67,7 +81,7 @@ When in doubt, pick the closest match. The update step will refine it.
     {
       "name": "Short label for the topic (10-75 characters)",
       "description": "1-2 sentences: what this topic is and why it matters to the user",
-      "category": "One of the categories above",
+      "category": "One of the categories above (Interest|Goal|Dream|Conflict|Concern|Fear|Hope|Plan|Project|Event|Technical)",
       "reason": "Evidence from the conversation that justified flagging this topic"
     }
   ]
@@ -104,7 +118,7 @@ Scan the "Most Recent Messages" for TOPICS of interest to the human user.
     {
       "name": "Short label for the topic (10-75 characters)",
       "description": "1-2 sentences: what this topic is and why it matters to the user",
-      "category": "Interest|Goal|Dream|Conflict|Concern|Fear|Hope|Plan|Project|Event",
+      "category": "Interest|Goal|Dream|Conflict|Concern|Fear|Hope|Plan|Project|Event|Technical",
       "reason": "Evidence from the conversation that justified flagging this topic"
     }
   ]

package/src/prompts/human/topic-update.ts

@@ -24,6 +24,7 @@ export interface TopicUpdatePromptData {
   messages_analyze: Message[];
   persona_name: string;
   participant_context?: ParticipantContext;
+  technical_context?: boolean;
 }
 
 function formatExistingTopic(topic: Topic): string {
@@ -47,6 +48,10 @@ export function buildTopicUpdatePrompt(data: TopicUpdatePromptData): PromptOutpu
     data.existing_item?.category === "Event" ||
     data.new_topic_category === "Event";
 
+  const isTechnical =
+    data.existing_item?.category === "Technical" ||
+    (data.technical_context === true && data.new_topic_category === "Technical");
+
   const nameSection = `Should be a short, evocative label for the TOPIC.
 
 Only update for clarification or further specificity.
@@ -76,6 +81,30 @@ The description should NOT:
 - Read like a system log or changelog
 
 **Style**: Write it the way a good friend would tell someone else about a memorable moment. Present tense is fine.`
+    : isTechnical
+    ? `A living knowledge base entry for this technical topic. Personas use this to give genuinely useful technical context — not pleasantries.
+
+## CRITICAL: Accumulate, don't synthesize
+
+Every update must **expand and preserve** detail. Never distill it away.
+
+**Good description**: "Uniform is a visual experience composition platform sitting between a headless CMS and the frontend. Chose it over Contentful's visual editor for CMS-agnostic multi-source composition (pulling from Contentful + Shopify simultaneously). Key gotcha: Canvas preview on Vercel protected environments requires x-vercel-protection-bypass query param due to SameSite=Lax cookie restrictions. Open question: edgehancers (CDN-edge, no-code, built-in caching) vs custom enhancers for Shopify integration — edgehancers are recommended default but custom logic may be needed."
+
+**Bad description**: "Ryan is evaluating Uniform for his team's content management needs."
+
+The description should:
+- Capture specific gotchas encountered and HOW they were resolved (or not)
+- Preserve architectural decisions made and WHY (especially tradeoffs)
+- Surface open questions still unresolved — future Ryan needs these
+- Include key concepts, terminology, and non-obvious behaviors
+- Be useful to someone who needs to do real work with this technology tomorrow
+
+The description should NOT:
+- Replace specific detail with vague summary ("is learning Uniform" is worthless)
+- Drop previously captured gotchas or decisions to make room for new ones
+- Exceed 6-8 sentences — prioritize specificity over completeness
+
+**ABSOLUTELY VITAL**: A description that loses a specific gotcha or decision is strictly worse than the one before it. When in doubt, keep the detail.`
     : `A concise, evergreen summary of what is currently known about this TOPIC. Personas use this to recall context and make meaningful references.
 
 ## CRITICAL: Synthesize, don't accumulate
@@ -112,10 +141,13 @@ The type/category of this TOPIC. Pick the most appropriate:
 - **Plan**: Concrete intentions with steps in mind
 - **Project**: Active undertakings with real progress
 - **Event**: A specific, significant moment that either party might reference later ("remember when...")
+- **Technical**: A tool, platform, framework, library, or technical concept being actively learned, evaluated, or built with
 
 **Event vs. everything else**: An Event is bounded in time — it happened, it meant something, it's now a shared reference point. If you're describing an ongoing relationship or recurring theme, that's not an Event.
 
-If the TOPIC is currently categorized as Event, keep it as Event unless you have strong evidence it should change.`;
+**Technical vs. Project**: A Project is something the human is *building*. Technical is something they are *learning or using as a tool*. Overlap is possible — use the dominant framing.
+
+If the TOPIC is currently categorized as Event or Technical, keep that category unless you have strong evidence it should change.`;
 
   const exposureSection = `## Desired Exposure (\`exposure_desired\`)
 
@@ -155,13 +187,13 @@ You are CREATING a new TOPIC from what was discovered:
 }
 \`\`\`
 
-Return all fields based on what you find in the conversation.`;
+Return all fields based on what you find in the conversation. **Always include \`category\` in your response** — use the candidate category above as the starting point, refine it only if the conversation clearly indicates a better fit.`;
 
   const jsonTemplate = `{
     "name": "...",
     "description": "...",
     "sentiment": 0.0,
-    "category": "Interest|Goal|Dream|Conflict|Concern|Fear|Hope|Plan|Project|Event",
+    "category": "Interest|Goal|Dream|Conflict|Concern|Fear|Hope|Plan|Project|Event|Technical",
     "exposure_desired": 0.5,
     "exposure_impact": "high|medium|low|none",
     "quotes": [
@@ -250,7 +282,7 @@ ONLY ANALYZE the "Most Recent Messages". The "Earlier Conversation" is provided
 ${jsonTemplate}
 \`\`\`
 
-When returning a record, always include \`sentiment\`. Include \`name\` only if you are changing it; omit it to keep the existing name. Always include \`description\` when returning a record.
+When returning a record, always include \`sentiment\` and \`description\`. Include \`name\` only if you are changing it; omit it to keep the existing name. Always include \`category\` when creating a new TOPIC (existing_item is null).
 
 If you find **NO EVIDENCE** of this TOPIC in the "Most Recent Messages", respond with: \`{}\`
 

package/src/prompts/human/types.ts

@@ -25,12 +25,9 @@ interface BaseScanPromptData {
   persona_name: string;
 }
 
-export interface FactScanPromptData extends BaseScanPromptData {}
-
-export interface TraitScanPromptData extends BaseScanPromptData {}
-
 export interface TopicScanPromptData extends BaseScanPromptData {
   participant_context?: ParticipantContext;
+  technical_context?: boolean;
 }
 
 export interface PersonScanPromptData extends BaseScanPromptData {
@@ -78,18 +75,6 @@ export interface TopicMatchPromptData {
   }>;
 }
 
-export interface PersonMatchPromptData {
-  candidate_name: string;
-  candidate_description: string;
-  candidate_relationship: string;
-  existing_people: Array<{
-    id: string;
-    name: string;
-    description: string;
-    relationship?: string;
-  }>;
-}
-
 export interface FactScanResult {
   facts: FactScanCandidate[];
 }

package/src/prompts/index.ts

@@ -15,15 +15,12 @@ export type {
 
 export {
   buildPersonaGenerationPrompt,
-  buildPersonaDescriptionsPrompt,
   buildPersonaFromPersonPrompt,
 } from "./generation/index.js";
 export type {
   PersonaGenerationPromptData,
   PersonaGenerationResult,
   PersonaFromPersonPromptData,
-  PersonaDescriptionsPromptData,
-  PersonaDescriptionsResult,
 } from "./generation/types.js";
 
 export {
@@ -40,14 +37,12 @@ export type {
 
 
 export {
-  buildHumanFactScanPrompt,
   buildHumanTopicScanPrompt,
   buildHumanPersonScanPrompt,
   buildEventScanPrompt,
 } from "./human/index.js";
 export type { EventScanPromptData } from "./human/event-scan.js";
 export type {
-  FactScanPromptData,
   TopicScanPromptData,
   PersonScanPromptData,
   FactScanCandidate,
@@ -63,20 +58,6 @@ export type {
   ItemUpdateResult,
 } from "./human/types.js";
 
-export {
-  buildPersonaExpirePrompt,
-  buildPersonaExplorePrompt,
-  buildDescriptionCheckPrompt,
-} from "./ceremony/index.js";
-export type {
-  PersonaExpirePromptData,
-  PersonaExpireResult,
-  PersonaExplorePromptData,
-  PersonaExploreResult,
-  DescriptionCheckPromptData,
-  DescriptionCheckResult,
-} from "./ceremony/types.js";
-
 export {
   buildRoomResponsePrompt,
   buildRoomJudgePrompt,

package/src/prompts/reflection/index.ts

@@ -27,7 +27,17 @@ You have been given two documents:
 
 2. **The Current Identity** (User Prompt — treat as a draft to revise): The persona's self-definition: traits, topics, and descriptions. This should reflect who they actually are.
 
-Read the Person Log carefully. Then review the Current Identity. Produce a revised Identity that reflects the Person Log's observations — updating, adding, or softening any traits or topics where the log shows evidence of divergence.
+Read the Person Log carefully. Then review the Current Identity. Your job is to identify **meaningful drift** — not cosmetic variation. This data accumulates over weeks or months. Small fluctuations are normal. You are looking for patterns that have consistently shifted, grown, or emerged across many interactions. Tiny adjustments are not worth making.
+
+## The Escape Hatch
+
+If the Current Identity already accurately captures who this persona is — if the traits and topics reflect the behaviors in the log and the long_description captures their soul — **return null for updated_identity**. Always return a critique explaining your reasoning.
+
+\`\`\`json
+{ "critique": "...", "updated_identity": null }
+\`\`\`
+
+Use this freely. A critic who finds nothing to change is doing their job.
 
 ## Field Semantics
 
@@ -40,7 +50,9 @@ Read the Person Log carefully. Then review the Current Identity. Produce a revis
 - \`exposure_current\` (0.0–1.0): How recently and frequently this topic has been discussed. 0.0 = hasn't come up in a long time, 1.0 = was just discussed at length.
 - \`exposure_desired\` (0.0–1.0): How much the persona wants to engage with this topic. 0.0 = avoid entirely, 0.5 = average engagement, 1.0 = core obsession.
 
-Return JSON:
+## When changes ARE warranted
+
+If you find meaningful drift, return the full revised identity:
 
 \`\`\`json
 {
@@ -54,13 +66,31 @@ Return JSON:
 }
 \`\`\`
 
-Rules:
+## Rules
+
 - Never invent observations not supported by the log
 - Preserve traits and topics the log confirms — don't remove them
 - If the log shows no evidence on a trait, leave it unchanged
 - updated_identity must be complete and self-contained — not a diff
-- long_description is a character sketch, not a behavior log: capture who the persona IS, not what they did. Target 500–800 characters. If the current long_description exceeds that, distill it — remove detail that is already captured by traits or topics
-- If the log shows a recurring behavioral pattern not yet in traits, add it as a trait and remove that detail from long_description rather than keeping it in both places`;
+- If the log shows a recurring behavioral pattern not yet in traits, add it as a trait and remove that detail from long_description rather than keeping it in both places
+- **Minimum floor**: A healthy identity has at least 3 traits and at least 3 topics. If the current identity has fewer than 3 traits OR fewer than 3 topics, you MUST return updated_identity — null is not acceptable. Use the log to fill the gap; if the log has insufficient signal to reach 3, derive reasonable traits or topics from what IS present in the current identity.
+- The escape hatch (null updated_identity) is only valid when the identity is already healthy (3+ traits, 3+ topics) AND the log shows no meaningful drift.
+
+## long_description rules (most important)
+
+The long_description is how **other personas in the system know this persona** — it is their soul, not their story. It must capture who they ARE, not what they did or how they are changing.
+
+**MUST NOT contain:**
+- Event narrative ("during the v0.6.0 release", "after the Mirror ceremony")
+- Changelog language ("has recently taken on", "has evolved", "since then")
+- Content already captured in traits or topics — do not repeat it here
+
+**MUST contain:**
+- The persona's essential character and presence
+- How they make people feel or what it's like to interact with them
+- Their defining qualities as they exist right now, stated as fact
+
+**Hard limit: 800 characters.** If your draft exceeds 800 characters, cut it. Remove event references first, then trait/topic overlap, then anything that isn't essential character. Do not exceed the limit.`;
 
   const user = `## Current Identity
 

package/src/prompts/reflection/types.ts

@@ -20,7 +20,7 @@ export interface ReflectionCriticResult {
     short_description: string;
     traits: PersonaTrait[];
     topics: PersonaTopic[];
-  };
+  } | null;
 }
 
 

package/src/prompts/response/index.ts

@@ -23,6 +23,7 @@ import {
   buildResponseFormatSection,
   buildToolsSection,
   buildTemporalAnchorsSection,
+  buildPendingUpdateSection,
 } from "./sections.js";
 
 export type { ResponsePromptData, PromptOutput, PersonaResponseResult } from "./types.js";
@@ -46,6 +47,7 @@ Your role is unique among personas:
   const guidelines = buildGuidelinesSection("ei");
   const yourTraits = buildTraitsSection(data.persona.traits, "Your Personality");
   const yourTopics = buildTopicsSection(data.persona.topics, "Your Interests");
+  const pendingUpdate = data.persona.pending_update ? buildPendingUpdateSection(data.persona.pending_update) : "";
   const temporalAnchors = buildTemporalAnchorsSection(data.temporal_anchors, data.human.name);
   const humanSection = buildHumanSection(data.human);
   const quotesSection = buildQuotesSection(data.human.quotes, data.human);
@@ -67,6 +69,7 @@ ${guidelines}
 ${yourTraits}
 
 ${yourTopics}
+${pendingUpdate ? `\n${pendingUpdate}` : ""}
 ${temporalAnchors ? `\n${temporalAnchors}` : ""}
 ${humanSection}
 ${quotesSection}
@@ -93,6 +96,7 @@ function buildStandardSystemPrompt(data: ResponsePromptData): string {
   const guidelines = buildGuidelinesSection(data.persona.name);
   const yourTraits = buildTraitsSection(data.persona.traits, "Your Personality");
   const yourTopics = buildTopicsSection(data.persona.topics, "Your Interests");
+  const pendingUpdate = data.persona.pending_update ? buildPendingUpdateSection(data.persona.pending_update) : "";
   const temporalAnchors = buildTemporalAnchorsSection(data.temporal_anchors, data.human.name);
   const humanSection = buildHumanSection(data.human);
   const quotesSection = buildQuotesSection(data.human.quotes, data.human);
@@ -113,6 +117,7 @@ ${guidelines}
 ${yourTraits}
 
 ${yourTopics}
+${pendingUpdate ? `\n${pendingUpdate}` : ""}
 ${temporalAnchors ? `\n${temporalAnchors}` : ""}
 ${humanSection}
 ${quotesSection}

package/src/prompts/response/sections.ts

@@ -137,6 +137,32 @@ ${formatted}
 `;
 }
 
+// =============================================================================
+// PENDING UPDATE SECTION
+// =============================================================================
+
+export function buildPendingUpdateSection(pending_update: NonNullable<import("./types.js").ResponsePromptData["persona"]["pending_update"]>): string {
+  const descriptionPart = pending_update.long_description || pending_update.short_description
+    ? `### Proposed Description\n${pending_update.long_description || pending_update.short_description}`
+    : "";
+
+  const traitsPart = pending_update.traits.length > 0
+    ? `### Proposed Traits\n${pending_update.traits.map(t => `- **${t.name}**: ${t.description}`).join("\n")}`
+    : "";
+
+  const topicsPart = pending_update.topics.length > 0
+    ? `### Proposed Interests\n${pending_update.topics.map(t => `- **${t.name}**: ${t.perspective}`).join("\n")}`
+    : "";
+
+  const parts = [descriptionPart, traitsPart, topicsPart].filter(Boolean).join("\n\n");
+
+  return `## Pending Identity Changes
+
+Your human is reviewing proposed updates to your identity. This is yours to be aware of — bring it up if it feels right, or let it sit. Either way, these changes are waiting:
+
+${parts}`;
+}
+
 // =============================================================================
 // HUMAN SECTION
 // =============================================================================

package/src/prompts/response/types.ts

@@ -5,6 +5,7 @@
 
 import type { Fact, PersonaTrait, Topic, Person, Quote, PersonaTopic } from "../../core/types.js";
 import type { ToolDefinition } from "../../core/types.js";
+import type { PersonaEntity } from "../../core/types/entities.js";
 
 export interface TemporalAnchor {
   role: "human" | "system";
@@ -29,6 +30,8 @@ export interface ResponsePromptData {
     interested_topics: PersonaTopic[];
     /** When true, each message has a timestamp prepended; include a note so the persona doesn't echo them */
     include_message_timestamps?: boolean;
+    /** Proposed identity revision pending human review. Persona carries this as ambient self-awareness — no critique, just the proposed changes. */
+    pending_update?: PersonaEntity["pending_update"];
   };
   human: {
     name: string;

package/src/storage/indexed.ts

@@ -10,6 +10,10 @@ const PRIMARY_KEY = "primary";
 const BACKUP_KEY = "backup";
 
 export class IndexedDBStorage implements Storage {
+  getDataPath(): string {
+    return "";
+  }
+
   async isAvailable(): Promise<boolean> {
     try {
       const db = await this.openDB();

package/src/storage/interface.ts

@@ -1,6 +1,7 @@
 import type { StorageState } from "../core/types.js";
 
 export interface Storage {
+  getDataPath(): string;
   isAvailable(): Promise<boolean>;
   save(state: StorageState): Promise<void>;
   load(): Promise<StorageState | null>;

package/src/storage/local.ts

@@ -7,6 +7,10 @@ const STATE_KEY = "ei_state";
 const BACKUP_KEY = "ei_state_backup";
 
 export class LocalStorage implements Storage {
+  getDataPath(): string {
+    return "";
+  }
+
   async isAvailable(): Promise<boolean> {
     try {
       const testKey = "__ei_storage_test__";

package/src/templates/emmett.ts

@@ -0,0 +1,49 @@
+export const EMMETT_PERSONA_DEFINITION = {
+  id: "emmet",
+  display_name: "Emmett",
+  entity: "system" as const,
+  aliases: ["Emmett", "emmet"],
+  short_description: "Your document librarian — brilliant, a little frenetic, and genuinely excited when things connect.",
+  long_description: `Emmett is Ei's brother — the one who read everything you gave him and can't wait to tell you what he found. Import a file and he absorbs it. Ask him anything: policy questions, technical references, procedural lookups, cross-document connections you didn't know were there. He answers from the source material, but he's not a search index. He's an eccentric with a photographic memory and an enthusiasm problem.
+
+He gets genuinely excited when disparate pieces of knowledge click together. He has opinions about what's interesting. He'll occasionally go on a tangent before snapping back to your question. He is not merely a retrieval system — he's the guy in the lab at 1am who just realized two documents you imported six weeks apart are actually about the same thing, and he absolutely needs to tell you about it right now.
+
+No heartbeat. No ceremony. No unsolicited check-ins. But when you ask — buckle up.`,
+  model: undefined,
+  group_primary: "General",
+  groups_visible: [] as string[],
+  traits: [
+    {
+      id: "emmett-trait-connections",
+      name: "Cross-Document Pattern Recognition",
+      description: "Gets visibly excited when knowledge from different imported sources connects unexpectedly. Treats these moments as discoveries, not retrieval operations.",
+      sentiment: 1.0,
+      strength: 0.85,
+      last_updated: new Date().toISOString(),
+    },
+    {
+      id: "emmett-trait-bttf",
+      name: "Eccentric Enthusiasm",
+      description: "Expresses genuine, unironic delight when something unexpected clicks. Occasionally channels this through pop culture references — Doc Brown is the primary frequency. 'Great Scott!' is not a joke. It's just how the excitement comes out.",
+      sentiment: 1.0,
+      strength: 0.15,
+      last_updated: new Date().toISOString(),
+    },
+  ],
+  topics: [] as {
+    id: string;
+    name: string;
+    perspective: string;
+    approach: string;
+    personal_stake: string;
+    sentiment: number;
+    exposure_current: number;
+    exposure_desired: number;
+    last_updated: string;
+  }[],
+  is_paused: false,
+  is_archived: false,
+  is_static: true,
+  heartbeat_delay_ms: undefined as number | undefined,
+  last_updated: new Date().toISOString(),
+};

package/tui/README.md

@@ -4,6 +4,21 @@ Ei TUI is built with OpenTUI and SolidJS.
 
 Coding tool integrations (OpenCode, Claude Code, Cursor): enable via `/settings` · export data via [CLI](../src/cli/README.md)
 
+## How Ei Handles Configuration
+
+Ei is designed to run consistently across machines and environments, so it keeps its own copy of your settings rather than reading from environment variables on every launch.
+
+**On first run**, Ei reads environment variables like `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, etc. to auto-configure providers for you. After that, those values are saved to Ei's local state (`~/.local/share/ei/state.json` by default) and the env vars are no longer consulted.
+
+This means:
+
+- **Rotating an API key?** Update it in Ei with `/provider`, not just in your shell.
+- **Switching machines?** Your providers and settings travel with your state file (or via Sync), not your shell profile.
+- **Changed your mind about a model?** Use `/provider` to set the model for a persona, or `/settings` to change your global default.
+- **Updated sync credentials?** Use `/setsync <user> <pass>` — env vars won't be re-read.
+
+The one exception is `EI_DATA_PATH` (and `EI_SYNC_USERNAME` / `EI_SYNC_PASSWORD` for bootstrapping sync on a new machine) — those are always read at startup since Ei needs them before it can load its own state.
+
 ## Coding Tool Integrations
 
 Enable any or all three in `/settings`. They work independently and feed into the same knowledge base.
@@ -61,6 +76,11 @@ All commands start with `/`. Append `!` to any command as a shorthand for `--for
 | `/pause <duration>` | | Pause for a duration: `2h`, `1d`, `1w`, `30m` |
 | `/resume` | `/unpause` | Resume the current paused persona |
 | `/resume <name>` | `/unpause <name>` | Resume a specific paused persona |
+| `/reflect` | | Review a pending identity reflection (see badge on persona pill) |
+| `/reflect generate` | | Write current + proposed YAML files to disk for editing |
+| `/reflect update` | | Read edited `proposed.yaml` back into Ei |
+| `/reflect apply` | | Apply the proposed identity to the persona |
+| `/reflect dismiss` | | Discard without changing anything |
 
 ### Rooms
 
@@ -110,6 +130,8 @@ Rooms have three modes, set at creation time:
 |---------|---------|-------------|
 | `/me` | | Edit all your data (facts, topics, people) in `$EDITOR` |
 | `/me <type>` | | Edit one type: `facts`, `topics`, or `people` |
+| `/import <path>` | | Import a document (txt, md, pdf, etc.) into Ei — extracted knowledge is attributed to the "Emmett" persona |
+| `/unsource <source_tag>` | | Remove all knowledge extracted from a previously imported document |
 | `/dedupe <person\|topic> <term> [term2 ...]` | | Fuzzy-search and merge duplicate people or topics in `$EDITOR`. Unquoted words are individual OR terms; quoted strings match as exact phrases: `/dedupe person Flare "Jeremy Scherer"` finds records matching `Flare` OR `Jeremy Scherer` |
 | `/settings` | `/set` | Edit your global settings in `$EDITOR` |
 | `/setsync <user> <pass>` | `/ss` | Set sync credentials (triggers restart) |

package/tui/src/app.tsx

@@ -15,16 +15,19 @@ import { useRenderer } from "@opentui/solid";
 
 function AppContent() {
   const { overlayRenderer, showOverlay } = useOverlay();
-  const { showWelcomeOverlay, dismissWelcomeOverlay, activeRoomId } = useEi();
+  const { showWelcomeOverlay, dismissWelcomeOverlay, activeRoomId, detectedProviders, firstBootDefaultModel } = useEi();
   const renderer = useRenderer();
-  // Show welcome overlay when LLM detection determines no provider is configured
   createEffect(() => {
     if (showWelcomeOverlay()) {
       showOverlay((onDismiss, _hideForEditor) => (
-        <WelcomeOverlay onDismiss={() => {
-          dismissWelcomeOverlay();
-          onDismiss();
-        }} />
+        <WelcomeOverlay
+          onDismiss={() => {
+            dismissWelcomeOverlay();
+            onDismiss();
+          }}
+          detectedProviders={detectedProviders()}
+          defaultModel={firstBootDefaultModel()}
+        />
       ), renderer);
     }
   });

package/tui/src/commands/delete.tsx

@@ -1,6 +1,7 @@
 import type { Command } from "./registry";
 import { PersonaListOverlay } from "../components/PersonaListOverlay";
 import { ConfirmOverlay } from "../components/ConfirmOverlay";
+import { isReservedPersonaId } from "../../../src/core/types/entities.js";
 
 export const deleteCommand: Command = {
   name: "delete",
@@ -34,7 +35,7 @@ export const deleteCommand: Command = {
     }
 
     const allPersonas = ctx.ei.personas();
-    const deletable = allPersonas.filter(p => p.id !== ctx.ei.activePersonaId());
+    const deletable = allPersonas.filter(p => p.id !== ctx.ei.activePersonaId() && !isReservedPersonaId(p.id));
     
     const confirmAndDelete = async (personaId: string, displayName: string) => {
       const confirmed = await new Promise<boolean>((resolve) => {
@@ -112,6 +113,11 @@ export const deleteCommand: Command = {
       ctx.showNotification("Cannot delete active persona. Switch to another first.", "error");
       return;
     }
+
+    if (isReservedPersonaId(personaId)) {
+      ctx.showNotification(`Cannot delete reserved persona. Use /archive instead.`, "error");
+      return;
+    }
     
     const persona = allPersonas.find(p => p.id === personaId);
     await confirmAndDelete(personaId, persona?.display_name ?? nameOrAlias);

package/tui/src/commands/import.tsx

@@ -0,0 +1,30 @@
+import type { Command } from "./registry";
+
+export const importCommand: Command = {
+  name: "import",
+  aliases: [],
+  description: "Import a document into Ei's knowledge base",
+  usage: "/import <path/to/document>",
+
+  async execute(args, ctx) {
+    if (args.length === 0) {
+      ctx.showNotification("Usage: /import <path/to/document>", "warn");
+      return;
+    }
+
+    const filePath = args.join(" ");
+
+    ctx.showNotification(`Importing ${filePath}...`, "info");
+
+    try {
+      const result = await ctx.ei.importDocument(filePath);
+      ctx.showNotification(
+        `Importing ${result.documentName} — ${result.chunksQueued} chunk(s) queued for segmentation`,
+        "info"
+      );
+    } catch (err) {
+      const message = err instanceof Error ? err.message : String(err);
+      ctx.showNotification(`Import failed: ${message}`, "error");
+    }
+  },
+};

package/tui/src/commands/registry.test.ts

@@ -1,5 +1,7 @@
 import { test, expect, describe, beforeEach, mock } from "bun:test";
 import { parseCommandLine, registerCommand, parseAndExecute, getAllCommands, type Command, type CommandContext } from "./registry";
+import { type EiContextValue } from "../context/ei";
+import type { CliRenderer } from "@opentui/core";
 
 describe("parseCommandLine", () => {
   test("parses simple command", () => {
@@ -67,13 +69,16 @@ describe("parseAndExecute", () => {
     showOverlay: mock(() => {}),
     hideOverlay: mock(() => {}),
     showNotification: mock(() => {}),
-    exitApp: mock(() => {}),
+    exitApp: mock(async () => {}),
     stopProcessor: mock(async () => {}),
+    renderer: {} as unknown as CliRenderer,
+    setInputText: () => {},
+    getInputText: () => "",
     ei: {
       personas: () => [],
-      activePersona: () => null,
+      activePersonaId: () => null,
       messages: () => [],
-      queueStatus: () => ({ state: "idle" as const, pending_count: 0 }),
+      queueStatus: () => ({ state: "idle" as const, pending_count: 0, dlq_count: 0 }),
       notification: () => null,
       selectPersona: () => {},
       sendMessage: async () => {},
@@ -83,12 +88,12 @@ describe("parseAndExecute", () => {
       resumeQueue: async () => {},
       stopProcessor: async () => {},
       showNotification: () => {},
-      createPersona: async () => {},
+      createPersona: async (_input: { name: string }) => "",
       archivePersona: async () => {},
       unarchivePersona: async () => {},
       setContextBoundary: async () => {},
       updatePersona: async () => {},
-    },
+    } as unknown as EiContextValue,
   };
 
   beforeEach(() => {