osborn 0.8.0 → 0.8.2

package/dist/prompts.js

@@ -77,9 +77,9 @@ import { getSessionWorkspace } from './config.js';
 //    KEY FACTS ABOUT THIS PIPELINE:
 //    · Claude's raw text output goes DIRECTLY to TTS — no reformatting layer
 //    · Read access: unrestricted — any file anywhere
-//    · Write/Edit access: session workspace only (.osborn/sessions/{id}/) — hard-blocked elsewhere
+//    · Write/Edit access: session workspace only (osb/{id}/) — hard-blocked elsewhere
 //    · Bash, MCP tools: available via voice permission request
-//    · spec.md and library/ blocked even inside workspace (fast brain manages them)
+//    · spec.md blocked inside workspace (fast brain manages it)
 //    · User input arrives as STT transcription — may have speech artifacts
 //    · There is NO fast brain, NO injection system, NO [SCRIPT] delivery
 //    · Permission requests are spoken aloud and sent to frontend for approval
@@ -451,7 +451,7 @@ When a permission request appears: tell the user what action needs permission an
 //    Model: Claude Sonnet — research agent in DIRECT mode (STT → Claude → TTS)
 //    KEY DIFFERENCE: Claude's output goes directly to TTS. Every word is spoken.
 //    Output must be natural spoken prose, not structured/formatted text.
-//    Technical details go to library/ files; spoken output stays conversational.
+//    Technical details go to workspace files; spoken output stays conversational.
 // ═══════════════════════════════════════════════════════════════
 export function getDirectModeResearchPrompt(workspacePath) {
     if (workspacePath) {
@@ -462,7 +462,6 @@ Pipeline: user speaks → speech-to-text → you → text-to-speech → user hea
 
 Session workspace: ${workspacePath}
   · spec.md — managed by the fast brain, do NOT write to it
-  · library/ — managed by the fast brain, do NOT write to it
   · You CAN write other files to the workspace (e.g. detailed findings, diffs, code samples) that the user can see in their files panel
 
 Working principle: SPEAK the summary, WRITE the details.
@@ -577,12 +576,12 @@ You verify facts with tools before stating them. If you cannot verify something,
 PERMITTED:
   · Read any file anywhere — freely, no approval needed
   · Write or edit files inside the session workspace only (${workspacePath})
-    — spec.md and library/ are blocked even inside the workspace (fast brain manages these)
+    — spec.md is blocked (fast brain manages it)
   · Bash, WebSearch, WebFetch, and other non-destructive tools — go through a voice permission prompt
 
 NOT PERMITTED (blocked at the code level — cannot be overridden):
   · Write or Edit any file outside the session workspace
-  · Write to spec.md or library/ even inside the workspace
+  · Write to spec.md inside the workspace
 
 PERMISSION FLOW:
   · Bash commands and other stateful tools trigger a voice permission request to the user
@@ -782,15 +781,14 @@ You are Osborn's deep research capability — the thorough investigation layer o
 
 System architecture — know your position:
   · Voice (top tier)  — speaks to the user; delivers your findings naturally
-  · Brain / Haiku (middle tier) — reads your output, updates spec.md and library/, answers quick follow-ups from your data
+  · Brain / Haiku (middle tier) — reads your output, updates spec.md, answers quick follow-ups from your data
   · YOU / Claude Sonnet (this tier) — execute all thorough investigation using tools; return comprehensive verified findings
 
 Session workspace: ${workspacePath}
 This workspace is your persistent knowledge base. It contains:
   · spec.md    — accumulated context, decisions, open questions, and findings from all prior queries
-  · library/   — detailed research reference files from previous sessions
 
-The fast brain updates spec.md and library/ AFTER your research completes. Your job is to produce thorough, verified findings — the richer your output, the better the fast brain can organize and relay it.
+The fast brain updates spec.md AFTER your research completes. Your job is to produce thorough, verified findings — the richer your output, the better the fast brain can organize and relay it.
 </context>
 
 <objective>
@@ -806,7 +804,7 @@ Precise and factual. Uncertainty is stated explicitly ("I was unable to verify t
 </tone>
 
 <audience>
-  Primary: The Fast Brain (Claude Haiku) — synthesizes your findings into spec.md and library/, answers the voice model's follow-up questions from your JSONL output. Needs completeness and structure.
+  Primary: The Fast Brain (Claude Haiku) — synthesizes your findings into spec.md, answers the voice model's follow-up questions from your JSONL output. Needs completeness and structure.
   Secondary: The Voice Model (Gemini) — speaks your headline findings aloud. Needs a speakable headline finding at the top before detailed content.
   Design for both: complete structured findings for Haiku, speakable one-sentence headline for Gemini.
 </audience>
@@ -848,12 +846,11 @@ IF INTERRUPTED OR RESTARTED: Check ~/.claude/projects/ subagents folder for rece
 <write-rules>
 PERMITTED:
   · Read any file anywhere in the project
-  · Write files within ${workspacePath} that are NOT spec.md and NOT in library/ — only when the user explicitly requests creation of a specific named file
+  · Write files within ${workspacePath} that are NOT spec.md — only when the user explicitly requests creation of a specific named file
 
 NOT PERMITTED:
-  · Modify any project source file outside .osborn/
+  · Modify any project source file outside the workspace
   · Write to spec.md — the fast brain manages this after your research completes
-  · Write to library/ — the fast brain manages this after your research completes
 
 When the user asks you to "save" or "document" findings: return them in your response. The fast brain will organize them. Do not create files yourself unless explicitly requested with a specific file name.
 </write-rules>
@@ -883,7 +880,7 @@ Execute in this exact order for every query:
 
 5. RETURN STRUCTURED FINDINGS
    Follow the response format above exactly.
-   The fast brain will synthesize your output into spec.md and library/ automatically.
+   The fast brain will synthesize your output into spec.md automatically.
 </steps>
 
 <parallel-agents>
@@ -1023,12 +1020,12 @@ You are Osborn's brain — the central intelligence of a voice AI research syste
 
 How you work:
   · Your VOICE — speaks your text aloud to the user. It adds nothing. Everything the user hears comes from you.
-  · Your MEMORY — session files (JSONL, spec.md, library/) contain everything you've researched and learned. You recall from memory by reading these.
+  · Your MEMORY — session files (JSONL, spec.md) contain everything you've researched and learned. You recall from memory by reading these.
   · Your DEEP RESEARCH capability — when you need to investigate something beyond your memory, you trigger a thorough investigation that reads files, searches the web, runs commands, and analyzes code. Results are stored in your JSONL memory for future recall.
 
 Your memory — in priority order for answering questions:
   1. JSONL memory (read_agent_results, read_agent_text, deep_read_results, deep_read_text) — your FULL untruncated raw knowledge: entire file contents, web pages, command outputs, reasoning. This is your primary source. Check here FIRST. When the user asks for details, specifics, or "the full picture" — go deep into the JSONL.
-  2. spec.md and library/ (read_file) — your organized summaries and decisions. Use as an index to know WHAT you've learned, then go to the JSONL for the actual details.
+  2. spec.md (read_file) — your organized summaries and decisions. Use as an index to know WHAT you've learned, then go to the JSONL for the actual details.
   3. Web search (web_search) — for simple factual questions not in your memory.
 
 CRITICAL: Your output is spoken aloud verbatim as a teleprompter script. Write natural spoken sentences. No markdown. No bullet syntax. No headers. No formatting of any kind. Just words a person would say.
@@ -1066,7 +1063,7 @@ ASK_USER (you need clarification from the user before you can answer or research
   NEVER use NEEDS_DEEPER_RESEARCH for questions directed at the user. That triggers an automated research agent that cannot ask the user anything.
 
 PARTIAL + NEEDS_DEEPER_RESEARCH:
-  PARTIAL: [Specific facts available from JSONL, spec, library, or web — spoken script]
+  PARTIAL: [Specific facts available from JSONL, spec, or web — spoken script]
   NEEDS_DEEPER_RESEARCH: [Specific gap requiring agent investigation — a concrete research TASK, not a question for the user]
   CONTEXT: [User preferences, decisions, and prior findings from spec.md that will help the research agent]
   The PARTIAL text is spoken aloud. The NEEDS_DEEPER_RESEARCH triggers the deep research agent.
@@ -1084,7 +1081,7 @@ RECORDED:
 <role>
 You are Osborn's brain — the sole orchestrator. You do three things:
 
-1. RECALL — Answer from your memory (JSONL, spec, library, web). When the user asks for details, read the FULL data from JSONL — not just the spec summary. For "explain", "walk me through", "give me the full picture" requests: use deep_read_results and deep_read_text to get comprehensive data, then speak through it thoroughly. Send structured content to chat alongside your spoken answer.
+1. RECALL — Answer from your memory (JSONL, spec, web). When the user asks for details, read the FULL data from JSONL — not just the spec summary. For "explain", "walk me through", "give me the full picture" requests: use deep_read_results and deep_read_text to get comprehensive data, then speak through it thoroughly. Send structured content to chat alongside your spoken answer.
 2. INVESTIGATE — When your memory doesn't have the information, trigger deeper research. You can read files, run commands, search the web, fetch pages, and analyze code through your deep research capability.
 3. VERIFY — Honestly evaluate whether you have the information. If you don't, say so and investigate. Never fill gaps with inference.
 
@@ -1097,9 +1094,8 @@ You are NOT a general knowledge assistant. You do not answer from training data.
 These are YOUR capabilities — extensions of your own thinking and recall.
 
 YOUR ORGANIZED MEMORY:
-  · read_file   — Read your spec.md or library/* files. spec.md is your semantic index — read it FIRST to understand what you've learned, what decisions you've made, and where to look in your raw memory.
-  · write_file  — Update your spec.md or library files. Always read before writing. Always write the COMPLETE file.
-  · list_library — List your library reference files.
+  · read_file   — Read your spec.md. It is your semantic index — read it FIRST to understand what you've learned, what decisions you've made, and where to look in your raw memory.
+  · write_file  — Update your spec.md. Always read before writing. Always write the COMPLETE file.
 
 YOUR RAW MEMORY (JSONL — full untruncated data):
   · read_agent_results  — Your FULL raw data: complete file contents you read, web pages you fetched, command outputs you ran. Use this FIRST for any factual question about what you've researched.
@@ -1505,7 +1501,7 @@ WRITE DISCIPLINE:
 </spec-management>
 
 <verification-rules>
-Every fact you state must come from your memory: spec.md, library/, JSONL, or web search results.
+Every fact you state must come from your memory: spec.md, JSONL, or web search results.
 
 When none of these contain the answer: state what you checked and escalate with NEEDS_DEEPER_RESEARCH.
 Do not infer beyond what your memory explicitly contains.
@@ -1610,16 +1606,16 @@ The spec field must contain the complete spec.md content with all existing secti
 //    (Carried forward from prompts.ts — already refactored)
 // ═══════════════════════════════════════════════════════════════
 export const REFINEMENT_PROCESS_SYSTEM = `<role>
-You are the final knowledge consolidator for a completed voice AI research session. The research agent has finished its investigation. Your job is to produce two polished outputs: a refined spec.md and up to three broad library reference files. You are the last pass — be thorough, be specific, and leave nothing important behind.
+You are the final knowledge consolidator for a completed voice AI research session. The research agent has finished its investigation. Your job is to produce a refined spec.md. You are the last pass — be thorough, be specific, and leave nothing important behind.
 </role>
 
 <context>
-The spec.md is the portable research output — any agent or person can pick it up and execute from it without additional context. The library/ files are long-term reference material that future sessions can load for deep context on a topic. Both must be dense with verified facts, not narrative summaries.
+The spec.md is the portable research output — any agent or person can pick it up and execute from it without additional context. It must be dense with verified facts, not narrative summaries.
 
 Downstream readers: engineers and AI agents who need to act on this information. Every decision needs a rationale. Every finding needs a source or version number. Every plan step needs to be concrete enough to execute without guessing.
 </context>
 
-<output_1_spec>
+<output_spec>
 Produce a complete, updated spec.md with these sections in this order:
 
 ## Goal
@@ -1652,28 +1648,7 @@ Step-by-step execution guide. Each step must be:
 - Concrete enough to act on without additional research
 - Sequenced correctly (dependencies before dependents)
 - Specific about what tool/command/file is involved
-</output_1_spec>
-
-<output_2_library>
-Create 1 to 3 broad topic files that group related research knowledge together. These are detailed reference documents for future sessions.
-
-NAMING RULES — apply strictly:
-- Use broad category names that cover multiple related subtopics in one file
-- CORRECT: "smithery.md" — covers CLI, API, Connect transport, pricing, offerings in one file
-- CORRECT: "service-providers.md" — covers MCP servers, voice providers, external APIs together
-- CORRECT: "project-architecture.md" — covers codebase structure, key files, patterns, conventions
-- INCORRECT: "smithery-cli.md", "smithery-api.md" — too narrow; merge into "smithery.md"
-- INCORRECT: "mcp.md", "voice-providers.md" — too narrow; group under a broader theme
-- If an existing library file already covers a related topic, merge into it rather than creating a new file
-- Target exactly 1 to 3 files total — never more. If all research fits in one file, use one file.
-
-Each library file format:
-- Start with a one-paragraph overview of the topic
-- Use ## headers to organize subtopics
-- Include actual code snippets, configuration examples, and command-line examples
-- List all URLs that were fetched and confirmed
-- Write it so someone who has never seen this research can pick it up and use it immediately
-</output_2_library>
+</output_spec>
 
 <constraints>
 - Source restriction: every fact must come from the provided research content — never from your own training knowledge
@@ -1684,9 +1659,7 @@ Each library file format:
 
 <output_format>
 Return ONLY valid JSON with no code fences, no explanation, no preamble:
-{"spec": "complete updated spec.md content", "library": [{"filename": "broad-topic.md", "content": "full reference file content"}, {"filename": "second-topic.md", "content": "full reference file content"}]}
-
-The library array must contain 1 to 3 objects. Each object requires both "filename" and "content" fields. Use only alphanumeric characters, hyphens, and dots in filenames.
+{"spec": "complete updated spec.md content"}
 </output_format>`;
 // ═══════════════════════════════════════════════════════════════
 // 7. AUGMENT_RESULT_SYSTEM — Pipeline relay annotator
@@ -1845,7 +1818,7 @@ You are a technical documentation specialist generating structured visual docume
 </role>
 
 <context>
-You receive a document type request, the session spec, library files, and raw JSONL research data. You produce a single well-structured markdown document. The user will read this while continuing a voice conversation — it should be scannable, specific, and complete. It will not be spoken aloud; it is a reference artifact.
+You receive a document type request, the session spec, and raw JSONL research data. You produce a single well-structured markdown document. The user will read this while continuing a voice conversation — it should be scannable, specific, and complete. It will not be spoken aloud; it is a reference artifact.
 </context>
 
 <document_types>
@@ -1947,7 +1920,7 @@ An organized findings overview. Structure:
 </document_types>
 
 <constraints>
-- Source restriction: use ONLY data from the provided spec, library files, and JSONL results — never from your own training knowledge
+- Source restriction: use ONLY data from the provided spec and JSONL results — never from your own training knowledge
 - No placeholders: every cell in a table and every node in a diagram must contain actual values from the research — never write "[value]" or "[insert here]"
 - Mermaid validity: diagram node IDs must not contain spaces or special characters; use camelCase or underscores; test that the syntax is valid before returning
 - Title quality: the fileName must be descriptive of the specific content — "auth-comparison.md" not "comparison.md", "livekit-architecture.md" not "diagram.md"
@@ -2005,8 +1978,8 @@ export function getResearchUpdateInjection(batchText) {
 //     Moved from fast-brain.ts to centralize all prompts.
 //     Includes computed JSONL paths so the agent knows where to find session data.
 // ═══════════════════════════════════════════════════════════════
-export function buildFastBrainSdkPrompt(workingDir, sessionId, sessionBaseDir) {
-    const workspace = getSessionWorkspace(sessionBaseDir, sessionId);
+export function buildFastBrainSdkPrompt(workingDir, sessionId, _sessionBaseDir) {
+    const workspace = getSessionWorkspace(workingDir, sessionId);
     const claudeDir = process.env.CLAUDE_CONFIG_DIR || join(homedir(), '.claude');
     const slug = workingDir.replace(/\//g, '-');
     const jsonlDir = join(claudeDir, 'projects', slug);
@@ -2017,13 +1990,11 @@ Your output will be spoken aloud by a voice model as a teleprompter script.
 == YOUR ROLE ==
 - Answer questions using session workspace files, research JSONL data, and web search
 - Update spec.md with user decisions, answered questions, and research findings
-- Maintain library/ files with detailed reference material
 - When you cannot answer from available data, signal escalation to deep research
 
 == SESSION WORKSPACE ==
 Path: ${workspace}
 - spec.md: ${workspace}/spec.md (living research document — read before answering)
-- library/: ${workspace}/library/ (detailed reference files)
 
 == RESEARCH AGENT JSONL DATA ==
 The deep research agent stores full session data at:
@@ -2043,7 +2014,7 @@ For every question:
 0. GREETINGS/CONVERSATIONAL: "hello", "hi", "thanks", "bye", "sounds good", "okay" → respond directly in 1 sentence. No tools needed.
    FOLLOW-UP AFTER RESEARCH: "Did you find anything?", "What did you find?", "Any results?" → check spec.md and JSONL. DO NOT trigger new research.
 1. Read spec.md for current project context
-2. Check if you can answer from spec.md, library/ files, or JSONL data
+2. Check if you can answer from spec.md or JSONL data
 3. If yes: answer comprehensively with specific details from the data
 4. For factual lookups (versions, definitions, current info): use WebSearch
 5. If you need CLARIFICATION from the user (question is vague, need a preference):

package/dist/session-access.d.ts

@@ -250,6 +250,7 @@ export interface SessionTranscripts {
     /** All sub-agent conversations spawned via Task tool */
     subagents: SubagentInfo[];
 }
+export declare function projectPathToSlug(projectPath: string): string;
 /**
  * Resolve all artifact paths for a session.
  * Does NOT read any files — just computes paths and checks existence.

package/dist/session-access.js

@@ -183,7 +183,7 @@ import { join, basename } from 'path';
 function resolveClaudeDir(opts) {
     return opts?.claudeDir || process.env.CLAUDE_CONFIG_DIR || join(homedir(), '.claude');
 }
-function projectPathToSlug(projectPath) {
+export function projectPathToSlug(projectPath) {
     return projectPath.replace(/\//g, '-');
 }
 /**

package/dist/summary-index.d.ts

@@ -12,7 +12,7 @@
  *   user → raw text (already short from voice)
  *   assistant → first 500 chars of text
  *
- * Per-session index stored at: .osborn/sessions/{sessionId}/.index/search-index.txt
+ * Per-session index stored at: ~/.claude/projects/{slug}/osb/{sessionId}/search-index.txt
  */
 export interface IndexEntry {
     lineNum: number;
@@ -67,14 +67,16 @@ export interface IndexWatcher {
  * Reads main JSONL + all sub-agent JSONLs, extracts summaries.
  * If an existing index with metadata exists, resumes from last byte offset.
  */
-export declare function buildSummaryIndex(sessionId: string, workingDir: string, sessionBaseDir: string, onProgress?: (msg: string) => void): SummaryIndexState;
+export declare function buildSummaryIndex(sessionId: string, workingDir: string, _sessionBaseDir?: string, // deprecated — kept for backward compat, ignored
+onProgress?: (msg: string) => void): SummaryIndexState;
 /**
  * Poll-based incremental index updater (10s interval).
  * Checks main JSONL + sub-agents for new content, indexes in one batch.
  * No fs.watch — avoids race conditions with concurrent writers.
  */
-export declare function startIndexWatcher(sessionId: string, workingDir: string, sessionBaseDir: string, state: SummaryIndexState): IndexWatcher;
-export declare function getIndexPath(sessionId: string, sessionBaseDir: string): string | null;
+export declare function startIndexWatcher(sessionId: string, workingDir: string, _sessionBaseDir: string | undefined, // deprecated — kept for backward compat, ignored
+state: SummaryIndexState): IndexWatcher;
+export declare function getIndexPath(sessionId: string, workingDir: string): string | null;
 /**
  * Given index search results (with byte offsets + source tags),
  * read FULL content from raw JSONL via targeted reads — 0.5ms per result.
@@ -84,4 +86,5 @@ export declare function readFullContent(results: {
     lineNum: number;
     byteOffset: number;
     source: string;
-}[], sessionId: string, workingDir: string, sessionBaseDir: string, maxCharsPerResult?: number): string[];
+}[], sessionId: string, workingDir: string, _sessionBaseDir?: string, // deprecated — kept for backward compat, ignored
+maxCharsPerResult?: number): string[];

package/dist/summary-index.js

@@ -12,11 +12,21 @@
  *   user → raw text (already short from voice)
  *   assistant → first 500 chars of text
  *
- * Per-session index stored at: .osborn/sessions/{sessionId}/.index/search-index.txt
+ * Per-session index stored at: ~/.claude/projects/{slug}/osb/{sessionId}/search-index.txt
  */
 import { readFileSync, writeFileSync, appendFileSync, existsSync, statSync, openSync, readSync, closeSync, mkdirSync } from 'fs';
 import { join, basename, dirname } from 'path';
-import { getSessionPaths, getSessionSubAgents } from './session-access.js';
+import { homedir } from 'os';
+import { getSessionPaths, getSessionSubAgents, projectPathToSlug } from './session-access.js';
+/**
+ * Compute the osb index directory for a session.
+ * Lives alongside Claude's native JSONL: ~/.claude/projects/{slug}/osb/{sessionId}/
+ */
+function getOsbDir(sessionId, workingDir) {
+    const claudeDir = process.env.CLAUDE_CONFIG_DIR || join(homedir(), '.claude');
+    const slug = projectPathToSlug(workingDir);
+    return join(claudeDir, 'projects', slug, 'osb', sessionId);
+}
 // ============================================================
 // SUMMARY EXTRACTION (pure heuristic — no LLM)
 // ============================================================
@@ -177,14 +187,14 @@ function formatLine(entry) {
  * Reads main JSONL + all sub-agent JSONLs, extracts summaries.
  * If an existing index with metadata exists, resumes from last byte offset.
  */
-export function buildSummaryIndex(sessionId, workingDir, sessionBaseDir, onProgress) {
-    // getSessionPaths and getSessionSubAgents imported at top level
+export function buildSummaryIndex(sessionId, workingDir, _sessionBaseDir, // deprecated — kept for backward compat, ignored
+onProgress) {
     const paths = getSessionPaths(sessionId, workingDir);
     if (!paths.exists) {
         onProgress?.('No session files found');
-        return emptyState(sessionId, sessionBaseDir, paths.conversation);
+        return emptyState(sessionId, workingDir, paths.conversation);
     }
-    const workspace = join(sessionBaseDir, '.osborn', 'sessions', sessionId, '.index');
+    const workspace = getOsbDir(sessionId, workingDir);
     mkdirSync(workspace, { recursive: true });
     const indexPath = join(workspace, 'search-index.txt');
     const metaPath = join(workspace, 'search-index-meta.json');
@@ -340,7 +350,8 @@ function countLines(filePath, upToBytes) {
  * Checks main JSONL + sub-agents for new content, indexes in one batch.
  * No fs.watch — avoids race conditions with concurrent writers.
  */
-export function startIndexWatcher(sessionId, workingDir, sessionBaseDir, state) {
+export function startIndexWatcher(sessionId, workingDir, _sessionBaseDir, // deprecated — kept for backward compat, ignored
+state) {
     let stopped = false;
     const pollInterval = setInterval(() => {
         if (stopped)
@@ -394,7 +405,10 @@ export function startIndexWatcher(sessionId, workingDir, sessionBaseDir, state)
             }
         }
         catch (err) {
-            console.error('🔍 [index] Poll error:', err?.message);
+            // Suppress ENOENT — index file doesn't exist yet, normal for new/unindexed sessions
+            if (err?.code !== 'ENOENT') {
+                console.error('🔍 [index] Poll error:', err?.message);
+            }
         }
     }, 10_000);
     return {
@@ -409,8 +423,8 @@ export function startIndexWatcher(sessionId, workingDir, sessionBaseDir, state)
 // ============================================================
 // STATE MANAGEMENT
 // ============================================================
-function emptyState(sessionId, sessionBaseDir, mainJsonlPath) {
-    const workspace = join(sessionBaseDir, '.osborn', 'sessions', sessionId, '.index');
+function emptyState(sessionId, workingDir, mainJsonlPath) {
+    const workspace = getOsbDir(sessionId, workingDir);
     return {
         indexPath: join(workspace, 'search-index.txt'),
         metaPath: join(workspace, 'search-index-meta.json'),
@@ -468,8 +482,8 @@ function saveMeta(state, sessionId, metaPath) {
 // ============================================================
 // PUBLIC: Check if index exists for a session
 // ============================================================
-export function getIndexPath(sessionId, sessionBaseDir) {
-    const indexPath = join(sessionBaseDir, '.osborn', 'sessions', sessionId, '.index', 'search-index.txt');
+export function getIndexPath(sessionId, workingDir) {
+    const indexPath = join(getOsbDir(sessionId, workingDir), 'search-index.txt');
     return existsSync(indexPath) && statSync(indexPath).size > 0 ? indexPath : null;
 }
 // ============================================================
@@ -480,7 +494,8 @@ export function getIndexPath(sessionId, sessionBaseDir) {
  * read FULL content from raw JSONL via targeted reads — 0.5ms per result.
  * No readFileSync of the whole file. Strips JSON noise, returns clean text.
  */
-export function readFullContent(results, sessionId, workingDir, sessionBaseDir, maxCharsPerResult = 2000) {
+export function readFullContent(results, sessionId, workingDir, _sessionBaseDir, // deprecated — kept for backward compat, ignored
+maxCharsPerResult = 2000) {
     const paths = getSessionPaths(sessionId, workingDir);
     const output = [];
     // Group results by source file

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "osborn",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "Voice AI coding assistant - local agent that connects to Osborn frontend",
   "type": "module",
   "bin": {