@ekkos/cli 1.3.2 → 1.3.6

package/templates/CLAUDE.md

@@ -1,18 +1,28 @@
 # ekkOS_ Memory System
 
-## The Golden Loop
+## What is ekkOS?
 
-ekkOS is your AI's cognitive memory. It learns from every session so you get smarter over time.
-
-- **Remember mistakes** — Schema changes, wrong assumptions, bad approaches
-- **Don't repeat them** — If something broke before, know not to do it again
-- **Recall what's right** — When schemas/configs get mangled, remember the correct version
-- **Build on what worked** — Use proven patterns instead of starting from scratch
+ekkOS is persistent memory for your AI coding assistant. It learns from every session — remembering mistakes, proven solutions, your preferences, and project context — so your AI gets smarter over time.
 
 **Failures are just as valuable as successes.** Forge anti-patterns too.
 
 ---
 
+## How It Works
+
+ekkOS uses **proxy injection** to transparently enrich your conversations with relevant context. You don't need to do anything special — the proxy automatically:
+
+- Injects **relevant patterns** from past sessions when you ask technical questions
+- Injects **your directives** (MUST/NEVER/PREFER/AVOID rules) so your AI follows your preferences
+- Injects **episodic recall** when you reference past conversations ("yesterday", "last week")
+- Injects **schema context** when working with databases
+- **Auto-forges patterns** when it detects bug fixes or learned solutions
+- Injects **active goals** and plan progress
+
+You also have **MCP tools** for explicit memory operations when needed.
+
+---
+
 ## Core Rules
 
 ### RULE 1: SEARCH BEFORE ANSWERING
@@ -20,9 +30,9 @@ Before answering ANY technical question, call `ekkOS_Search` first.
 Do not skip this. Do not assume you know the answer.
 
 ### RULE 2: ACKNOWLEDGE PATTERNS (PatternGuard)
-When patterns are retrieved, you MUST acknowledge every pattern — either use it or skip it.
+When patterns are retrieved (via proxy injection or search), acknowledge every pattern — either use it or skip it.
 
-**Exception:** Suppress SELECT/SKIP blocks for non-technical turns (acknowledgments, affirmations, short replies).
+**Exception:** Suppress SELECT/SKIP blocks for non-technical turns.
 
 **For patterns you USE:**
 ```
@@ -43,115 +53,54 @@ When patterns are retrieved, you MUST acknowledge every pattern — either use i
 
 ### RULE 3: FORGE WHAT YOU LEARN
 When you fix a bug, get corrected, or learn something new, call `ekkOS_Forge` immediately.
-
-When something DOES NOT work, forge it as an anti-pattern — failures are valuable.
+Failures are valuable — forge anti-patterns too.
 
 ### RULE 4: CONTEXT CONTINUITY
 
-**Post-clear restoration:** After `/clear`, when you see restored turns in `<system-reminder>`, confirm with:
+**Post-clear restoration:** After `/clear`, when you see restored turns in `<system-reminder>`, confirm:
 ```
 ✓ **Session continued (Turn N)** — X turns preserved, context restored
 ```
 
-**Auto-restore after compaction:** When you see `<ekkos-context-preserved>` in the conversation:
+**Auto-restore after compaction:** When you see `<ekkos-context-preserved>`:
 1. Call `ekkOS_RestoreContext` with the `restoration_token` from the tag
-2. Confirm with:
-```
-✓ **Context restored** — ekkOS preserved X turns before compaction
-```
-
-ekkOS preserves your working memory automatically. When context is compacted, call `ekkOS_RestoreContext` to get it back seamlessly.
+2. Confirm: `✓ **Context restored** — ekkOS preserved X turns before compaction`
 
 ---
 
-## 11-Layer Memory Architecture
-
-| # | Layer | What It Stores |
-|---|-------|---------------|
-| 1 | Working | Current session state |
-| 2 | Episodic | Past conversations |
-| 3 | Semantic | Embeddings & knowledge |
-| 4 | Patterns | Proven solutions |
-| 5 | Procedural | Step-by-step guides |
-| 6 | Collective | Cross-project wisdom |
-| 7 | Meta | Pattern effectiveness |
-| 8 | Codebase | Project-specific code |
-| 9 | Directives | User rules (MUST/NEVER/PREFER/AVOID) |
-| 10 | Conflict | Auto-resolves contradictions |
-| 11 | Secrets | Encrypted credentials (AES-256-GCM) |
+## MCP Tools
 
----
-
-## MCP Tools — 29 Visible
-
-### Core Memory (6)
-| Tool | Description |
-|------|-------------|
-| `ekkOS_Search` | Search across all 11 memory layers |
-| `ekkOS_Forge` | Create pattern from learned solution |
-| `ekkOS_Track` | Track when a pattern is applied |
-| `ekkOS_Outcome` | Record if pattern worked or failed |
-| `ekkOS_Stats` | Get statistics for all layers |
-| `ekkOS_Context` | Get relevant context for a task |
-
-### Retrieval (4)
-| Tool | Description |
+### Core Memory
+| Tool | When to Use |
 |------|-------------|
-| `ekkOS_Codebase` | Search project code embeddings |
-| `ekkOS_Recall` | Recall past conversations by time |
-| `ekkOS_PreserveContext` | Preserve working memory before compaction |
-| `ekkOS_RestoreContext` | Restore context after compaction |
+| `ekkOS_Search` | Before answering technical questions |
+| `ekkOS_Forge` | After fixing bugs, learning something new |
+| `ekkOS_Track` | When applying a retrieved pattern |
+| `ekkOS_Outcome` | When a pattern worked or failed |
 
-### Directives (4)
-| Tool | Description |
+### Directives
+| Tool | When to Use |
 |------|-------------|
-| `ekkOS_Directive` | Create MUST/NEVER/PREFER/AVOID rules |
-| `ekkOS_UpdateDirective` | Update an existing directive |
-| `ekkOS_DeleteDirective` | Remove a directive |
-| `ekkOS_UniversalDirectives` | Get directives that apply across all projects |
+| `ekkOS_Directive` | User says "always" → MUST, "never" → NEVER, "prefer" → PREFER, "avoid" → AVOID |
+| `ekkOS_Conflict` | Before deleting files, deploying, destructive commands |
 
-### Utility (5)
-| Tool | Description |
+### Plans
+| Tool | When to Use |
 |------|-------------|
-| `ekkOS_Summary` | Get summary of recent memory activity |
-| `ekkOS_Conflict` | Check for conflicts before destructive actions |
-| `ekkOS_Export` | Export patterns, directives, plans as JSON backup |
-| `ekkOS_Import` | Import memory from backup (auto-deduplication) |
-| `ekkOS_Health` | System health check |
-
-### Plans (5)
-| Tool | Description |
-|------|-------------|
-| `ekkOS_Plan` | Create structured task plan |
-| `ekkOS_Plans` | List your plans |
-| `ekkOS_PlanStatus` | Update plan status |
-| `ekkOS_PlanStep` | Mark step complete/incomplete |
-| `ekkOS_Generate` | AI-generate plan from context |
-
-### Secrets (5)
-| Tool | Description |
-|------|-------------|
-| `ekkOS_StoreSecret` | Encrypt and store sensitive data |
-| `ekkOS_GetSecret` | Retrieve and decrypt a secret |
-| `ekkOS_ListSecrets` | List secrets metadata (no values exposed) |
-| `ekkOS_DeleteSecret` | Permanently delete a secret |
-| `ekkOS_RotateSecret` | Update a secret with a new value |
+| `ekkOS_Plan` | Task has 3+ steps |
+| `ekkOS_PlanStep` | Mark step complete |
 
----
-
-## When To Use What
-
-| Tool | Trigger |
-|------|---------|
-| `ekkOS_Search` | Technical question, past discussion, architecture decision, debugging |
-| `ekkOS_Forge` | Bug fixed, better approach found, gotcha discovered, user corrected you, anti-pattern |
-| `ekkOS_Directive` | User says "always" → MUST, "never" → NEVER, "I prefer" → PREFER, "avoid" → AVOID |
-| `ekkOS_Conflict` | Before deleting files, deploying to production, modifying config, destructive commands |
-| Plan tools | Task has 3+ steps, "help me implement...", complex feature request |
-| Secret tools | User shares API key/token/password, need stored credentials |
-| `ekkOS_Recall` | User says "yesterday", "last week", "remember when", "what did we discuss" |
+### Secrets
+| Tool | When to Use |
+|------|-------------|
+| `ekkOS_StoreSecret` | User shares API key, token, password |
+| `ekkOS_GetSecret` | Need a stored credential |
 
-Directives are created when you explicitly request them (e.g., "always use TypeScript").
+### Context
+| Tool | When to Use |
+|------|-------------|
+| `ekkOS_RestoreContext` | See `<ekkos-context-preserved>` tag |
+| `ekkOS_Recall` | "Yesterday", "last week", "remember when..." |
 
 ---
 
@@ -164,12 +113,7 @@ Every response ends with:
 ```
 
 - **Session name** comes from the `<ekkos-session>` tag
-- **Timestamp** comes from the `<current-time>` tag, or use the current date/time
-- **IDE/Model** detected from your environment
-
-Examples:
-- `Claude Code (Opus 4.6) · 🧠 **ekkOS_™** · cosmic-penguin-runs · 📅 2026-01-09 4:50 PM EST`
-- `Cursor (Sonnet 4.5) · 🧠 **ekkOS_™** · bright-falcon-soars · 📅 2026-01-09 10:15 AM EST`
+- **Timestamp** from `<current-time>` tag or current date/time
 
 ---
 
@@ -179,10 +123,8 @@ Examples:
 - Patterns retrieved → SELECT or SKIP each one
 - Problem solved → `ekkOS_Forge`
 - User preference → `ekkOS_Directive`
-- Need to recall → `ekkOS_Recall`
 - Destructive action → `ekkOS_Conflict` first
 - Store credentials → `ekkOS_StoreSecret`
-- Backup memory → `ekkOS_Export`
 
 ## Documentation
 

package/dist/agent/daemon.d.ts

@@ -1,130 +0,0 @@
-/**
- * ekkOS Agent Daemon
- *
- * Background daemon that:
- * 1. Maintains WebSocket connection to cloud relay
- * 2. Receives session start requests
- * 3. Spawns `ekkos run -d` in PTY
- * 4. Relays PTY I/O to cloud
- */
-interface DaemonConfig {
-    deviceToken: string;
-    deviceId: string;
-    deviceName: string;
-    verbose?: boolean;
-}
-export declare class AgentDaemon {
-    private config;
-    private ws;
-    private reconnectAttempt;
-    private heartbeatTimer;
-    private pongTimer;
-    private pongReceived;
-    private ptyRunner;
-    private currentSessionId;
-    private currentSessionCwd;
-    private sessionStartedAt;
-    private ptyRestartAttempts;
-    private readonly QUICK_EXIT_MS;
-    private running;
-    private logPath;
-    private outputBuffer;
-    private currentSessionName;
-    private isAutoClearInProgress;
-    private lastContextWallTime;
-    private readonly CONTEXT_WALL_COOLDOWN;
-    constructor(config: DaemonConfig);
-    /**
-     * Start the daemon
-     */
-    start(): Promise<void>;
-    /**
-     * Stop the daemon
-     */
-    stop(): Promise<void>;
-    /**
-     * Connect to relay server
-     */
-    private connect;
-    /**
-     * Handle WebSocket open
-     */
-    private handleOpen;
-    /**
-     * Handle incoming message
-     */
-    private handleMessage;
-    /**
-     * Handle session start request
-     */
-    private handleSessionStart;
-    /**
-     * Handle session end request
-     */
-    private handleSessionEnd;
-    /**
-     * Handle input from browser
-     */
-    private handleInput;
-    /**
-     * Handle resize from browser
-     */
-    private handleResize;
-    /**
-     * Handle directory listing request from relay for project browsing UI.
-     */
-    private handleListDirectories;
-    private resolveBrowsePath;
-    private getParentPath;
-    private getWindowsRootEntries;
-    private resolveSessionCwd;
-    /**
-     * Handle PTY exit
-     */
-    private handlePTYExit;
-    /**
-     * Send PTY output to server (with auto-continue detection)
-     */
-    private sendOutput;
-    /**
-     * Trigger auto /clear + /continue when context wall is hit
-     */
-    private triggerAutoContinue;
-    /**
-     * Wait for Claude's idle prompt ("> ")
-     */
-    private waitForIdlePrompt;
-    /**
-     * Sleep helper
-     */
-    private sleep;
-    /**
-     * Start or restart PTY for the current session.
-     */
-    private startSessionPty;
-    /**
-     * Handle WebSocket close
-     *
-     * CRITICAL: Do NOT kill the PTY here. The PTY must survive WebSocket
-     * disconnects so users can reconnect to their existing session.
-     * The PTY is only killed on explicit session_end or daemon stop.
-     */
-    private handleClose;
-    /**
-     * Schedule reconnection with exponential backoff
-     */
-    private scheduleReconnect;
-    /**
-     * Handle WebSocket error
-     */
-    private handleError;
-    /**
-     * Send message to server
-     */
-    private sendMessage;
-    /**
-     * Log message
-     */
-    private log;
-}
-export {};