Project Scoping
Each project gets its own AI brain. Patterns, directives, and learning stay isolated per repository while universal knowledge carries across all of them.
When you work on multiple projects, ekkOS automatically detects which repository you're in and scopes all memory operations to that project. Patterns learned in a Python API won't bleed into your React app. Directives set for one project stay in that project. But universal knowledge — like "never commit .env files" — stays global across everything.
How It Works
Automatic Detection
When you open your IDE in a git repository and start coding with ekkOS, the CLI automatically detects your git remote and sends it to the proxy. A project is auto-created the first time a new repository is seen. You never need to manually create or configure projects.
Memory Isolation
All 12 memory layers respect project boundaries. Patterns, episodic recall, schemas, goals, plans, and learning pipelines are filtered by project. When you ask "what did we fix last week?", you only get results from the current project — not every project you've worked on.
Global + Project
Every piece of memory has a scope: global or project. Global patterns (like "always use TypeScript strict mode") apply everywhere. Project-specific patterns (like "this API uses Prisma") only appear in that project. Directives work the same way.
What Gets Scoped
| Layer | Scoped? | How |
|---|---|---|
| Patterns | Per-project + global | Project patterns + NULL (global) patterns both returned |
| Directives | Per-project + global | Rules are tagged by project scope and merged with global rules |
| Episodic Recall | Per-project | "Last week" only returns current project's sessions |
| Schema Guards | Per-project | Different DB schemas per project |
| Goals & Plans | Per-project | Plans scoped to the project they were created in |
| Auto-Forge | Per-project | Auto-detected patterns inherit the session's project |
| Learning Pipeline | Per-project | Fast-loop and slow-loop isolated per project |
| Collective Patterns | Always global | Cross-model validated patterns apply everywhere |
| Secrets Vault | Optional | Secrets can be global or project-specific |
| Working Memory | Session-scoped | Already isolated per session (ephemeral) |
Zero Configuration
You don't need to do anything. Projects are detected from your git remote URL the moment you start coding. No setup, no configuration, no project creation screens. Just open your IDE in a repo and ekkOS handles the rest.
Managing Projects
Project Switcher
The platform dashboard has a project switcher in the sidebar. Select a project to view its patterns, directives, and growth metrics. Select "All Projects" to see everything.
Archiving Projects
When you archive a project, its patterns are moved to global scope (not deleted). The project disappears from your list, but all learned knowledge is preserved and becomes available across all projects.
Existing Users
If you were using ekkOS before project scoping was added, all your existing patterns and directives are global. They'll continue to work everywhere. New patterns will be automatically scoped to whichever project you're working in when they're created.