Guide

Using ekkOS with Claude Code

What ekkOS does for you, what you'll see, and how to get the most out of persistent memory.

How It Works

Once ekkOS is connected, Claude automatically gets enriched with context from your memory before every response. You don't need to do anything — it just works.

1You ask a question or make a request

2ekkOS finds relevant patterns, directives, and context from your memory

3Claude sees your memory alongside your question — and responds smarter

4If Claude fixes a bug or learns something, ekkOS saves it for next time

What Happens Automatically

These features work without you doing anything. ekkOS detects what you need and provides the right context.

Pattern Memory

When you ask a technical question, ekkOS searches your memory for relevant patterns — past solutions, gotchas, architectural decisions — and gives them to Claude before it answers.

This means Claude won't repeat mistakes you've already solved. If you fixed an auth bug last month, Claude knows the fix next time you hit a similar issue.

Directives

Your personal rules — things Claude should always do, never do, prefer, or avoid. ekkOS applies them to every conversation automatically.

MUST Run tests before deploying

NEVER Push directly to main

PREFER Functional over imperative style

AVOID Class-based React components

Schema Awareness

When you write SQL queries, use Supabase, or work with Prisma, ekkOS automatically provides the correct table and column names. No more "column does not exist" errors from Claude guessing field names wrong.

Auto-Learning

When Claude fixes a bug or solves a non-trivial problem, ekkOS detects the fix and saves it as a pattern. Next time you (or anyone on your team) hits the same issue, Claude already knows the solution.

Safety Checks

Before destructive actions (deleting files, deploying, dropping tables), Claude checks your directives for conflicts. If you set a NEVER rule, it will be enforced — even across sessions.

Recalling Past Sessions

ekkOS can bring context from previous sessions into your current conversation. This only happens when you explicitly ask — there's no automatic cross-session bleed.

Phrases that trigger recall

"What did we discuss yesterday?"

"Remember when we worked on auth?"

"Last session we fixed a bug..."

"Bring back context from last week"

"What did we do last time?"

"Last month we decided to..."

Privacy note: Normal conversation words like "earlier" or "previously" do not trigger cross-session recall. Only explicit references to past sessions, time periods, or memory do.

Things You Can Tell Claude

Setting Directives

Tell Claude your preferences and they become permanent rules:

"Always use TypeScript strict mode"

"Never delete files without asking me first"

"I prefer Tailwind over styled-components"

"Avoid using class components in React"

Searching Memory

Ask Claude to search what it knows:

"What do you know about our auth setup?"

"Search for patterns about deployment"

"What did we decide about the database schema?"

Storing Secrets

Share API keys and they're encrypted with AES-256-GCM:

"Store this API key: sk-abc123..."

"What's my OpenAI key?"

Plans & Tasks

For multi-step work, create tracked plans:

"Help me implement user authentication"

"Create a plan for migrating to PostgreSQL"

Plans persist across sessions. Come back tomorrow and pick up where you left off.

Session Continuity

ekkOS preserves your working context even when Claude Code's context window fills up. When the conversation gets too long:

•ekkOS saves your current working state before compaction
•Claude Code compresses the conversation
•ekkOS restores the context — you experience zero knowledge loss

You can also type /clear and then /continue to start a fresh conversation without losing memory context.

The ekkOS Footer

Every response from an ekkOS-enabled session ends with a footer like this:

Claude Code (Opus 4.6) · 🧠 ekkOS_™ · cosmic-penguin-runs · 📅 2026-03-03 4:50 PM EST

IDE + Model — which tool and model you're using

Session Name — a human-readable identifier for your session (e.g., "cosmic-penguin-runs")

Timestamp — when the response was generated

If you see the footer, ekkOS is active and working.

PatternGuard

When Claude retrieves patterns from memory, it acknowledges each one with a SELECT or SKIP block. This is transparency — you can see exactly which patterns influenced the response.

[ekkOS_SELECT]
- id: pat_abc123
  reason: directly relevant to this auth bug
  confidence: 0.9
[/ekkOS_SELECT]

[ekkOS_SKIP]
- id: pat_def456
  reason: about database migrations, not auth
[/ekkOS_SKIP]

You don't need to do anything with these blocks — they're informational. They only appear on technical responses, not casual conversation.