feat: Mode system with inheritance and multilingual support (#412)

* feat: add domain management system with support for multiple domain profiles - Introduced DomainManager class for loading and managing domain profiles. - Added support for a default domain ('code') and fallback mechanisms. - Implemented domain configuration validation and error handling. - Created types for domain configuration, observation types, and concepts. - Added new directory for domain profiles and ensured its existence. - Updated SettingsDefaultsManager to include CLAUDE_MEM_DOMAIN setting. * Refactor domain management to mode management - Removed DomainManager class and replaced it with ModeManager for better clarity and functionality. - Updated types from DomainConfig to ModeConfig and DomainPrompts to ModePrompts. - Changed references from domains to modes in the settings and paths. - Ensured backward compatibility by maintaining the fallback mechanism to the 'code' mode. * feat: add migration 008 to support mode-agnostic observations and refactor service layer references in documentation * feat: add new modes for code development and email investigation with detailed observation types and concepts * Refactor observation parsing and prompt generation to incorporate mode-specific configurations - Updated `parseObservations` function to use 'observation' as a universal fallback type instead of 'change', utilizing active mode's valid observation types. - Modified `buildInitPrompt` and `buildContinuationPrompt` functions to accept a `ModeConfig` parameter, allowing for dynamic prompt content based on the active mode. - Enhanced `ModePrompts` interface to include additional guidance for observers, such as recording focus and skip guidance. - Adjusted the SDKAgent to load the active mode and pass it to prompt generation functions, ensuring prompts are tailored to the current mode's context. * fix: correct mode prompt injection to preserve exact wording and type list visibility - Add script to extract prompts from main branch prompts.ts into code.yaml - Fix prompts.ts to show type list in XML template (e.g., "[ bugfix | feature | ... ]") - Keep 'change' as fallback type in parser.ts (maintain backwards compatibility) - Regenerate code.yaml with exact wording from original hardcoded prompts - Build succeeds with no TypeScript errors * fix: update ModeManager to load JSON mode files and improve validation - Changed ModeManager to load mode configurations from JSON files instead of YAML. - Removed the requirement for an "observation" type and updated validation to require at least one observation type. - Updated fallback behavior in the parser to use the first type from the active mode's type list. - Added comprehensive tests for mode loading, prompt injection, and parser integration, ensuring correct behavior across different modes. - Introduced new mode JSON files for "Code Development" and "Email Investigation" with detailed observation types and prompts. * Add mode configuration loading and update licensing information for Ragtime - Implemented loading of mode configuration in WorkerService before database initialization. - Added PolyForm Noncommercial License 1.0.0 to Ragtime directory. - Created README.md for Ragtime with licensing details and usage guidelines. * fix: add datasets directory to .gitignore to prevent accidental commits * refactor: remove unused plugin package.json file * chore: add package.json for claude-mem plugin with version 7.4.5 * refactor: remove outdated tests and improve error handling - Deleted tests for ChromaSync error handling, smart install, strip memory tags, and user prompt tag stripping due to redundancy or outdated logic. - Removed vitest configuration as it is no longer needed. - Added a comprehensive implementation plan for fixing the modes system, addressing critical issues and improving functionality. - Created a detailed test analysis report highlighting the quality and effectiveness of the current test suite, identifying areas for improvement. - Introduced a new plugin package.json for runtime dependencies related to claude-mem hooks. * refactor: remove parser regression tests to streamline codebase * docs: update CLAUDE.md to clarify test management and changelog generation * refactor: remove migration008 for mode-agnostic observations * Refactor observation type handling to use ModeManager for icons and emojis - Removed direct mappings of observation types to icons and work emojis in context-generator, FormattingService, SearchManager, and TimelineService. - Integrated ModeManager to dynamically retrieve icons and emojis based on the active mode. - Improved maintainability by centralizing the logic for observation type representation. * Refactor observation metadata constants and update context generator - Removed the explicit declaration of OBSERVATION_TYPES and OBSERVATION_CONCEPTS from observation-metadata.ts. - Introduced fallback default strings for DEFAULT_OBSERVATION_TYPES_STRING and DEFAULT_OBSERVATION_CONCEPTS_STRING. - Updated context-generator.ts to utilize observation types and concepts from ModeManager instead of constants. * refactor: remove intermediate error handling from hooks (Phase 1) Apply "fail fast" error handling strategy - errors propagate and crash loud instead of being caught, wrapped, and re-thrown at intermediate layers. Changes: - Remove try/catch around fetch calls in all hooks - let errors throw - Add try/catch ONLY around JSON.parse at entry points - Delete error-handler.ts and hook-error-handler.ts (no longer needed) - Update worker-utils.ts: functions now throw instead of returning null - Update transcript-parser.ts: throw on missing path, empty file, malformed JSON - Remove all handleWorkerError, handleFetchError imports Philosophy: If something breaks, we KNOW it broke. No silent failures. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * refactor: remove intermediate error handling from worker service (Phase 2) Apply "fail fast" error handling strategy to worker service layer. Changes: - worker-service.ts: Remove try/catch from version endpoint, cleanup, MCP close, process enumeration, force kill, and isAlive check - SessionRoutes.ts: Remove try/catch from JSON.stringify calls, remove .catch() from Chroma sync and SDK agent calls - SettingsRoutes.ts: Remove try/catch from toggleMcp() - DatabaseManager.ts: Remove .catch() from backfill and close operations - SDKAgent.ts: Keep outer try/catch (top-level), remove .catch() from Chroma sync operations - SSEBroadcaster.ts: Remove try/catch from broadcast and sendToClient Philosophy: Errors propagate and crash loud. BaseRouteHandler.wrapHandler provides top-level catching for HTTP routes. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * refactor: remove error swallowing from SQLite services (Phase 3) Apply "fail fast" error handling strategy to database layer. SessionStore.ts migrations: - ensureWorkerPortColumn(): Remove outer try/catch, let it throw - ensurePromptTrackingColumns(): Remove outer try/catch, let it throw - removeSessionSummariesUniqueConstraint(): Keep inner transaction rollback, remove outer catch - addObservationHierarchicalFields(): Remove outer try/catch - makeObservationsTextNullable(): Keep inner transaction rollback, remove outer catch - createUserPromptsTable(): Keep inner transaction rollback, remove outer catch - getFilesForSession(): Remove try/catch around JSON.parse SessionSearch.ts: - ensureFTSTables(): Remove try/catch, let it throw Philosophy: Migration errors that are swallowed mean we think the database is fine when it's not. Keep only inner transaction rollback try/catch blocks. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * refactor: remove error hiding from utilities (Phase 4) Apply "fail fast" error handling strategy to utility layer. logger.ts: - formatTool(): Remove try/catch, let JSON.parse throw on malformed input context-generator.ts: - loadContextConfig(): Remove try/catch, let parseInt throw on invalid settings - Transcript extraction: Remove try/catch, let file read errors propagate ChromaSync.ts: - close(): Remove nested try/catch blocks, let close errors propagate Philosophy: No silent fallbacks or hidden defaults. If something breaks, we know it broke immediately. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat: serve static UI assets and update package root path - Added middleware to serve static UI assets (JS, CSS, fonts, etc.) in ViewerRoutes. - Updated getPackageRoot function to correctly return the package root directory as one level up from the current directory. * feat: Enhance mode loading with inheritance support - Introduced parseInheritance method to handle parent--override mode IDs. - Added deepMerge method for recursively merging mode configurations. - Updated loadMode method to support inheritance, loading parent modes and applying overrides. - Improved error handling for missing mode files and logging for better traceability. * fix(modes): correct inheritance file resolution and path handling * Refactor code structure for improved readability and maintainability * feat: Add mode configuration documentation and examples * fix: Improve concurrency handling in translateReadme function * Refactor SDK prompts to enhance clarity and structure - Updated the `buildInitPrompt` and `buildContinuationPrompt` functions in `prompts.ts` to improve the organization of prompt components, including the addition of language instructions and footer messages. - Removed redundant instructions and emphasized the importance of recording observations. - Modified the `ModePrompts` interface in `types.ts` to include new properties for system identity, language instructions, and output format header, ensuring better flexibility and clarity in prompt generation. * Enhance prompts with language instructions and XML formatting - Updated `buildInitPrompt`, `buildSummaryPrompt`, and `buildContinuationPrompt` functions to include detailed language instructions in XML comments. - Ensured that language instructions guide users to keep XML tags in English while writing content in the specified language. - Modified the `buildSummaryPrompt` function to accept `mode` as a parameter for consistency. - Adjusted the call to `buildSummaryPrompt` in `SDKAgent` to pass the `mode` argument. * Refactor XML prompt generation in SDK - Updated the buildInitPrompt, buildSummaryPrompt, and buildContinuationPrompt functions to use new placeholders for XML elements, improving maintainability and readability. - Removed redundant language instructions in comments for clarity. - Added new properties to ModePrompts interface for better structure and organization of XML placeholders and section headers. * feat: Update observation prompts and structure across multiple languages * chore: Remove planning docs and update Ragtime README Remove ephemeral development artifacts: - .claude/plans/modes-system-fixes.md - .claude/test-analysis-report.md - PROMPT_INJECTION_ANALYSIS.md Update ragtime/README.md to explain: - Feature is not yet implemented - Dependency on modes system (now complete in PR #412) - Ready to be scripted out in future release 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * fix: Move summary prompts to mode files for multilingual support Summary prompts were hardcoded in English in prompts.ts, breaking multilingual support. Now properly mode-based: - Added summary_instruction, summary_context_label, summary_format_instruction, summary_footer to code.json - Updated buildSummaryPrompt() to use mode fields instead of hardcoded text - Added summary_footer with language instructions to all 10 language modes - Language modes keep English prompts + language requirement footer This fixes the gaslighting where we claimed full multilingual support but summaries were still generated in English. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * chore: Clean up README by removing local preview instructions and streamlining beta features section * Add translated README files for Ukrainian, Vietnamese, and Chinese languages * Add new language modes for code development in multiple languages - Introduced JSON configurations for Code Development in Greek, Finnish, Hebrew, Hindi, Hungarian, Indonesian, Italian, Dutch, Norwegian, Polish, Brazilian Portuguese, Romanian, Swedish, Turkish, and Ukrainian. - Each configuration includes prompts for observations, summaries, and instructions tailored to the respective language. - Ensured that all prompts emphasize the importance of generating observations without referencing the agent's actions. * Add multilingual support links to README files in various languages - Updated README.id.md, README.it.md, README.ja.md, README.ko.md, README.nl.md, README.no.md, README.pl.md, README.pt-br.md, README.ro.md, README.ru.md, README.sv.md, README.th.md, README.tr.md, README.uk.md, README.vi.md, and README.zh.md to include links to other language versions. - Each README now features a centered paragraph with flags and links for easy navigation between different language documents. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-22 20:14:18 -05:00
parent db02da148f
commit 3ea0b60b9f
141 changed files with 11834 additions and 6699 deletions
@@ -30,26 +30,19 @@ async function cleanupHook(input?: SessionEndInput): Promise<void> {

  const port = getWorkerPort();

-  try {
-    // Send to worker - worker handles finding session, marking complete, and stopping spinner
-    const response = await fetch(`http://127.0.0.1:${port}/api/sessions/complete`, {
-      method: 'POST',
-      headers: { 'Content-Type': 'application/json' },
-      body: JSON.stringify({
-        claudeSessionId: session_id,
-        reason
-      }),
-      signal: AbortSignal.timeout(HOOK_TIMEOUTS.DEFAULT)
-    });
+  // Send to worker - worker handles finding session, marking complete, and stopping spinner
+  const response = await fetch(`http://127.0.0.1:${port}/api/sessions/complete`, {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/json' },
+    body: JSON.stringify({
+      claudeSessionId: session_id,
+      reason
+    }),
+    signal: AbortSignal.timeout(HOOK_TIMEOUTS.DEFAULT)
+  });

-    if (!response.ok) {
-      // Non-fatal - session might not exist
-      console.error('[cleanup-hook] Session not found or already cleaned up');
-    }
-  } catch (error: any) {
-    // Worker might not be running - that's okay (non-critical)
-    // But we should still log it for visibility
-    console.error('[cleanup-hook] Failed to notify worker of session end:', error.message);
+  if (!response.ok) {
+    throw new Error(`Session cleanup failed: ${response.status}`);
  }

  console.log('{"continue": true, "suppressOutput": true}');
@@ -64,7 +57,12 @@ if (stdin.isTTY) {
  let input = '';
  stdin.on('data', (chunk) => input += chunk);
  stdin.on('end', async () => {
-    const parsed = input ? JSON.parse(input) : undefined;
+    let parsed: SessionEndInput | undefined;
+    try {
+      parsed = input ? JSON.parse(input) : undefined;
+    } catch (error) {
+      throw new Error(`Failed to parse hook input: ${error instanceof Error ? error.message : String(error)}`);
+    }
    await cleanupHook(parsed);
  });
 }
@@ -9,8 +9,6 @@
 import { stdin } from "process";
 import { ensureWorkerRunning, getWorkerPort } from "../shared/worker-utils.js";
 import { HOOK_TIMEOUTS } from "../shared/hook-constants.js";
-import { handleWorkerError } from "../shared/hook-error-handler.js";
-import { handleFetchError } from "./shared/error-handler.js";
 import { getProjectName } from "../utils/project-name.js";

 export interface SessionStartInput {
@@ -30,24 +28,14 @@ async function contextHook(input?: SessionStartInput): Promise<string> {

  const url = `http://127.0.0.1:${port}/api/context/inject?project=${encodeURIComponent(project)}`;

-  try {
-    const response = await fetch(url, { signal: AbortSignal.timeout(HOOK_TIMEOUTS.DEFAULT) });
+  const response = await fetch(url, { signal: AbortSignal.timeout(HOOK_TIMEOUTS.DEFAULT) });

-    if (!response.ok) {
-      const errorText = await response.text();
-      handleFetchError(response, errorText, {
-        hookName: 'context',
-        operation: 'Context generation',
-        project,
-        port
-      });
-    }
-
-    const result = await response.text();
-    return result.trim();
-  } catch (error: any) {
-    handleWorkerError(error);
+  if (!response.ok) {
+    throw new Error(`Context generation failed: ${response.status}`);
  }
+
+  const result = await response.text();
+  return result.trim();
 }

 // Entry Point - handle stdin/stdout
@@ -62,7 +50,12 @@ if (stdin.isTTY || forceColors) {
  let input = "";
  stdin.on("data", (chunk) => (input += chunk));
  stdin.on("end", async () => {
-    const parsed = input.trim() ? JSON.parse(input) : undefined;
+    let parsed: SessionStartInput | undefined;
+    try {
+      parsed = input.trim() ? JSON.parse(input) : undefined;
+    } catch (error) {
+      throw new Error(`Failed to parse hook input: ${error instanceof Error ? error.message : String(error)}`);
+    }
    const text = await contextHook(parsed);

    console.log(
@@ -1,8 +1,6 @@
 import { stdin } from 'process';
 import { STANDARD_HOOK_RESPONSE } from './hook-response.js';
 import { ensureWorkerRunning, getWorkerPort } from '../shared/worker-utils.js';
-import { handleWorkerError } from '../shared/hook-error-handler.js';
-import { handleFetchError } from './shared/error-handler.js';
 import { getProjectName } from '../utils/project-name.js';

 export interface UserPromptSubmitInput {
@@ -29,72 +27,48 @@ async function newHook(input?: UserPromptSubmitInput): Promise<void> {
  const port = getWorkerPort();

  // Initialize session via HTTP - handles DB operations and privacy checks
-  let sessionDbId: number;
-  let promptNumber: number;
+  const initResponse = await fetch(`http://127.0.0.1:${port}/api/sessions/init`, {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/json' },
+    body: JSON.stringify({
+      claudeSessionId: session_id,
+      project,
+      prompt
+    }),
+    signal: AbortSignal.timeout(5000)
+  });

-  try {
-    const initResponse = await fetch(`http://127.0.0.1:${port}/api/sessions/init`, {
-      method: 'POST',
-      headers: { 'Content-Type': 'application/json' },
-      body: JSON.stringify({
-        claudeSessionId: session_id,
-        project,
-        prompt
-      }),
-      signal: AbortSignal.timeout(5000)
-    });
-
-    if (!initResponse.ok) {
-      const errorText = await initResponse.text();
-      handleFetchError(initResponse, errorText, {
-        hookName: 'new',
-        operation: 'Session initialization',
-        project,
-        port
-      });
-    }
-
-    const initResult = await initResponse.json();
-    sessionDbId = initResult.sessionDbId;
-    promptNumber = initResult.promptNumber;
-
-    // Check if prompt was entirely private (worker performs privacy check)
-    if (initResult.skipped && initResult.reason === 'private') {
-      console.error(`[new-hook] Session ${sessionDbId}, prompt #${promptNumber} (fully private - skipped)`);
-      console.log(STANDARD_HOOK_RESPONSE);
-      return;
-    }
-
-    console.error(`[new-hook] Session ${sessionDbId}, prompt #${promptNumber}`);
-  } catch (error: any) {
-    handleWorkerError(error);
+  if (!initResponse.ok) {
+    throw new Error(`Session initialization failed: ${initResponse.status}`);
  }

+  const initResult = await initResponse.json();
+  const sessionDbId = initResult.sessionDbId;
+  const promptNumber = initResult.promptNumber;
+
+  // Check if prompt was entirely private (worker performs privacy check)
+  if (initResult.skipped && initResult.reason === 'private') {
+    console.error(`[new-hook] Session ${sessionDbId}, prompt #${promptNumber} (fully private - skipped)`);
+    console.log(STANDARD_HOOK_RESPONSE);
+    return;
+  }
+
+  console.error(`[new-hook] Session ${sessionDbId}, prompt #${promptNumber}`);
+
  // Strip leading slash from commands for memory agent
  // /review 101 → review 101 (more semantic for observations)
  const cleanedPrompt = prompt.startsWith('/') ? prompt.substring(1) : prompt;

-  try {
-    // Initialize SDK agent session via HTTP (starts the agent!)
-    const response = await fetch(`http://127.0.0.1:${port}/sessions/${sessionDbId}/init`, {
-      method: 'POST',
-      headers: { 'Content-Type': 'application/json' },
-      body: JSON.stringify({ userPrompt: cleanedPrompt, promptNumber }),
-      signal: AbortSignal.timeout(5000)
-    });
+  // Initialize SDK agent session via HTTP (starts the agent!)
+  const response = await fetch(`http://127.0.0.1:${port}/sessions/${sessionDbId}/init`, {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/json' },
+    body: JSON.stringify({ userPrompt: cleanedPrompt, promptNumber }),
+    signal: AbortSignal.timeout(5000)
+  });

-    if (!response.ok) {
-      const errorText = await response.text();
-      handleFetchError(response, errorText, {
-        hookName: 'new',
-        operation: 'SDK agent start',
-        project,
-        port,
-        sessionId: String(sessionDbId)
-      });
-    }
-  } catch (error: any) {
-    handleWorkerError(error);
+  if (!response.ok) {
+    throw new Error(`SDK agent start failed: ${response.status}`);
  }

  console.log(STANDARD_HOOK_RESPONSE);
@@ -104,6 +78,11 @@ async function newHook(input?: UserPromptSubmitInput): Promise<void> {
 let input = '';
 stdin.on('data', (chunk) => input += chunk);
 stdin.on('end', async () => {
-  const parsed = input ? JSON.parse(input) : undefined;
+  let parsed: UserPromptSubmitInput | undefined;
+  try {
+    parsed = input ? JSON.parse(input) : undefined;
+  } catch (error) {
+    throw new Error(`Failed to parse hook input: ${error instanceof Error ? error.message : String(error)}`);
+  }
  await newHook(parsed);
 });
@@ -11,8 +11,6 @@ import { STANDARD_HOOK_RESPONSE } from './hook-response.js';
 import { logger } from '../utils/logger.js';
 import { ensureWorkerRunning, getWorkerPort } from '../shared/worker-utils.js';
 import { HOOK_TIMEOUTS } from '../shared/hook-constants.js';
-import { handleWorkerError } from '../shared/hook-error-handler.js';
-import { handleFetchError } from './shared/error-handler.js';

 export interface PostToolUseInput {
  session_id: string;
@@ -48,37 +46,26 @@ async function saveHook(input?: PostToolUseInput): Promise<void> {
    throw new Error(`Missing cwd in PostToolUse hook input for session ${session_id}, tool ${tool_name}`);
  }

-  try {
-    // Send to worker - worker handles privacy check and database operations
-    const response = await fetch(`http://127.0.0.1:${port}/api/sessions/observations`, {
-      method: 'POST',
-      headers: { 'Content-Type': 'application/json' },
-      body: JSON.stringify({
-        claudeSessionId: session_id,
-        tool_name,
-        tool_input,
-        tool_response,
-        cwd
-      }),
-      signal: AbortSignal.timeout(HOOK_TIMEOUTS.DEFAULT)
-    });
+  // Send to worker - worker handles privacy check and database operations
+  const response = await fetch(`http://127.0.0.1:${port}/api/sessions/observations`, {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/json' },
+    body: JSON.stringify({
+      claudeSessionId: session_id,
+      tool_name,
+      tool_input,
+      tool_response,
+      cwd
+    }),
+    signal: AbortSignal.timeout(HOOK_TIMEOUTS.DEFAULT)
+  });

-    if (!response.ok) {
-      const errorText = await response.text();
-      handleFetchError(response, errorText, {
-        hookName: 'save',
-        operation: 'Observation storage',
-        toolName: tool_name,
-        sessionId: session_id,
-        port
-      });
-    }
-
-    logger.debug('HOOK', 'Observation sent successfully', { toolName: tool_name });
-  } catch (error: any) {
-    handleWorkerError(error);
+  if (!response.ok) {
+    throw new Error(`Observation storage failed: ${response.status}`);
  }

+  logger.debug('HOOK', 'Observation sent successfully', { toolName: tool_name });
+
  console.log(STANDARD_HOOK_RESPONSE);
 }

@@ -86,6 +73,11 @@ async function saveHook(input?: PostToolUseInput): Promise<void> {
 let input = '';
 stdin.on('data', (chunk) => input += chunk);
 stdin.on('end', async () => {
-  const parsed = input ? JSON.parse(input) : undefined;
+  let parsed: PostToolUseInput | undefined;
+  try {
+    parsed = input ? JSON.parse(input) : undefined;
+  } catch (error) {
+    throw new Error(`Failed to parse hook input: ${error instanceof Error ? error.message : String(error)}`);
+  }
  await saveHook(parsed);
 });
@@ -1,37 +0,0 @@
-import { logger } from '../../utils/logger.js';
-import { getWorkerRestartInstructions } from '../../utils/error-messages.js';
-
-export interface HookErrorContext {
-  hookName: string;
-  operation: string;
-  project?: string;
-  sessionId?: string;
-  toolName?: string;
-  port?: number;
-}
-
-/**
- * Standardized error handler for hook fetch failures.
- *
- * This function:
- * 1. Logs the error with full context to worker logs
- * 2. Throws a user-facing error with restart instructions
- *
- * Use this for all fetch errors in hooks to ensure consistent error handling.
- */
-export function handleFetchError(
-  response: Response,
-  errorText: string,
-  context: HookErrorContext
-): never {
-  logger.error('HOOK', `${context.operation} failed`, {
-    status: response.status,
-    ...context
-  }, errorText);
-
-  const userMessage = context.toolName
-    ? `Failed ${context.operation} for ${context.toolName}: ${getWorkerRestartInstructions()}`
-    : `${context.operation} failed: ${getWorkerRestartInstructions()}`;
-
-  throw new Error(userMessage);
-}
@@ -14,8 +14,6 @@ import { STANDARD_HOOK_RESPONSE } from './hook-response.js';
 import { logger } from '../utils/logger.js';
 import { ensureWorkerRunning, getWorkerPort } from '../shared/worker-utils.js';
 import { HOOK_TIMEOUTS } from '../shared/hook-constants.js';
-import { handleWorkerError } from '../shared/hook-error-handler.js';
-import { handleFetchError } from './shared/error-handler.js';
 import { extractLastMessage } from '../shared/transcript-parser.js';

 export interface StopInput {
@@ -54,56 +52,23 @@ async function summaryHook(input?: StopInput): Promise<void> {
    hasLastAssistantMessage: !!lastAssistantMessage
  });

-  let summaryError: Error | null = null;
+  // Send to worker - worker handles privacy check and database operations
+  const response = await fetch(`http://127.0.0.1:${port}/api/sessions/summarize`, {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/json' },
+    body: JSON.stringify({
+      claudeSessionId: session_id,
+      last_user_message: lastUserMessage,
+      last_assistant_message: lastAssistantMessage
+    }),
+    signal: AbortSignal.timeout(HOOK_TIMEOUTS.DEFAULT)
+  });

-  try {
-    // Send to worker - worker handles privacy check and database operations
-    const response = await fetch(`http://127.0.0.1:${port}/api/sessions/summarize`, {
-      method: 'POST',
-      headers: { 'Content-Type': 'application/json' },
-      body: JSON.stringify({
-        claudeSessionId: session_id,
-        last_user_message: lastUserMessage,
-        last_assistant_message: lastAssistantMessage
-      }),
-      signal: AbortSignal.timeout(HOOK_TIMEOUTS.DEFAULT)
-    });
-
-    if (!response.ok) {
-      const errorText = await response.text();
-      handleFetchError(response, errorText, {
-        hookName: 'summary',
-        operation: 'Summary generation',
-        sessionId: session_id,
-        port
-      });
-    }
-
-    logger.debug('HOOK', 'Summary request sent successfully');
-  } catch (error: any) {
-    summaryError = error;
-    handleWorkerError(error);
-  } finally {
-    // Stop processing spinner (non-critical operation, errors are logged but don't block)
-    try {
-      const spinnerResponse = await fetch(`http://127.0.0.1:${port}/api/processing`, {
-        method: 'POST',
-        headers: { 'Content-Type': 'application/json' },
-        body: JSON.stringify({ isProcessing: false }),
-        signal: AbortSignal.timeout(2000)
-      });
-      if (!spinnerResponse.ok) {
-        logger.warn('HOOK', 'Failed to stop spinner', { status: spinnerResponse.status });
-      }
-    } catch (error: any) {
-      logger.warn('HOOK', 'Could not stop spinner', { error: error.message });
-    }
+  if (!response.ok) {
+    throw new Error(`Summary generation failed: ${response.status}`);
  }

-  // Re-throw summary error after cleanup to ensure it's not masked by finally block
-  if (summaryError) {
-    throw summaryError;
-  }
+  logger.debug('HOOK', 'Summary request sent successfully');

  console.log(STANDARD_HOOK_RESPONSE);
 }
@@ -112,6 +77,11 @@ async function summaryHook(input?: StopInput): Promise<void> {
 let input = '';
 stdin.on('data', (chunk) => input += chunk);
 stdin.on('end', async () => {
-  const parsed = input ? JSON.parse(input) : undefined;
+  let parsed: StopInput | undefined;
+  try {
+    parsed = input ? JSON.parse(input) : undefined;
+  } catch (error) {
+    throw new Error(`Failed to parse hook input: ${error instanceof Error ? error.message : String(error)}`);
+  }
  await summaryHook(parsed);
 });
@@ -9,57 +9,32 @@
 import { basename } from "path";
 import { ensureWorkerRunning, getWorkerPort } from "../shared/worker-utils.js";
 import { HOOK_EXIT_CODES } from "../shared/hook-constants.js";
-import { getWorkerRestartInstructions } from "../utils/error-messages.js";

-try {
-  // Ensure worker is running
-  await ensureWorkerRunning();
+// Ensure worker is running
+await ensureWorkerRunning();

-  const port = getWorkerPort();
-  const project = basename(process.cwd());
+const port = getWorkerPort();
+const project = basename(process.cwd());

-  // Fetch formatted context directly from worker API
-  const response = await fetch(
-    `http://127.0.0.1:${port}/api/context/inject?project=${encodeURIComponent(project)}&colors=true`,
-    { method: 'GET', signal: AbortSignal.timeout(5000) }
-  );
+// Fetch formatted context directly from worker API
+const response = await fetch(
+  `http://127.0.0.1:${port}/api/context/inject?project=${encodeURIComponent(project)}&colors=true`,
+  { method: 'GET', signal: AbortSignal.timeout(5000) }
+);

-  if (!response.ok) {
-    throw new Error(getWorkerRestartInstructions({ includeSkillFallback: true }));
-  }
-
-  const output = await response.text();
-
-  console.error(
-    "\n\n📝 Claude-Mem Context Loaded\n" +
-    "   ℹ️  Note: This appears as stderr but is informational only\n\n" +
-    output +
-    "\n\n💡 New! Wrap all or part of any message with <private> ... </private> to prevent storing sensitive information in your observation history.\n" +
-    "\n💬 Community https://discord.gg/J4wttp9vDu" +
-    `\n📺 Watch live in browser http://localhost:${port}/\n`
-  );
-
-} catch (error) {
-  // Context not available yet - likely first run or worker starting up
-  console.error(`
---
-🎉  Note: This appears under Plugin Hook Error, but it's not an error. That's the only option for
-   user messages in Claude Code UI until a better method is provided.
---
-
-⚠️  Claude-Mem: First-Time Setup
-
-Dependencies are installing in the background. This only happens once.
-
-💡 TIPS:
-   • Memories will start generating while you work
-   • Use /init to write or update your CLAUDE.md for better project context
-   • Try /clear after one session to see what context looks like
-
-Thank you for installing Claude-Mem!
-
-This message was not added to your startup context, so you can continue working as normal.
-`);
+if (!response.ok) {
+  throw new Error(`Failed to fetch context: ${response.status}`);
 }

+const output = await response.text();
+
+console.error(
+  "\n\n📝 Claude-Mem Context Loaded\n" +
+  "   ℹ️  Note: This appears as stderr but is informational only\n\n" +
+  output +
+  "\n\n💡 New! Wrap all or part of any message with <private> ... </private> to prevent storing sensitive information in your observation history.\n" +
+  "\n💬 Community https://discord.gg/J4wttp9vDu" +
+  `\n📺 Watch live in browser http://localhost:${port}/\n`
+);
+
 process.exit(HOOK_EXIT_CODES.USER_MESSAGE_ONLY);