wicked-brain 0.4.5 → 0.4.7

package/README.md

@@ -159,10 +159,33 @@ Brains can link to other brains. A personal research brain can reference a team
 
 When you search, wicked-brain dispatches parallel search agents across all accessible brains and merges the results. Access control is filesystem permissions — if you can read the directory, you can search it.
 
-## What's on Disk
+## Per-Project Brains
+
+**Each project gets its own brain.** `wicked-brain:init` creates a brain under
+`~/.wicked-brain/projects/{project-name}/` by default, where `{project-name}`
+is the basename of your current working directory. This keeps unrelated
+codebases, clients, and research domains from crowding a single index — and
+makes federated search across projects meaningful.
 
 ```
 ~/.wicked-brain/
+  projects/
+    my-app/              # one brain per project
+    client-site/
+    personal-research/
+```
+
+Multiple agents can work on different projects simultaneously without stepping
+on each other. A supervising "meta-brain" can watch `~/.wicked-brain/projects/*`
+and federate queries across all of them via `brain.json` links.
+
+If you really want one brain for everything, you can pass a custom path to
+`wicked-brain:init` — but you'll fight the index as it grows.
+
+## What's on Disk
+
+```
+~/.wicked-brain/projects/{project-name}/
   brain.json              # Identity and brain links
   raw/                    # Your source files
   chunks/
@@ -171,6 +194,7 @@ When you search, wicked-brain dispatches parallel search agents across all acces
   wiki/                   # Synthesized articles with [[backlinks]]
   _meta/
     log.jsonl             # Append-only event log
+    config.json           # Server port, source path
   .brain.db               # SQLite search index (auto-managed)
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wicked-brain",
-  "version": "0.4.5",
+  "version": "0.4.7",
   "type": "module",
   "description": "Digital brain as skills for AI coding CLIs — no vector DB, no embeddings, no infrastructure",
   "keywords": [

package/server/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wicked-brain-server",
-  "version": "0.4.5",
+  "version": "0.4.7",
   "type": "module",
   "description": "SQLite FTS5 search server for wicked-brain digital knowledge bases",
   "keywords": [

package/skills/wicked-brain-init/SKILL.md

@@ -18,9 +18,34 @@ Commands in this skill work on macOS, Linux, and Windows. When a command has
 platform differences, alternatives are shown. Your native tools (Read, Write,
 Grep, Glob) work everywhere — prefer them over shell commands when possible.
 
+## Per-project brains (important)
+
+**Each project gets its own brain under `~/.wicked-brain/projects/{project-name}/`.**
+Do NOT initialize a single monolithic brain at `~/.wicked-brain/` — that overwhelms
+the index, mixes unrelated content across clients/codebases, and makes federated
+search useless.
+
+The structure is:
+```
+~/.wicked-brain/                          # parent directory (not a brain)
+  projects/
+    my-app/                               # one brain per project
+      brain.json
+      chunks/
+      _meta/
+    client-site/                          # another project's brain
+      brain.json
+      ...
+```
+
+Project name defaults to the basename of the current working directory
+(lowercase, hyphens for spaces). A supervising "meta-brain" agent can watch
+`~/.wicked-brain/projects/*` and federate across all of them via
+`brain.json` links.
+
 For the brain path default:
-- macOS/Linux: ~/.wicked-brain
-- Windows: %USERPROFILE%\.wicked-brain
+- macOS/Linux: `~/.wicked-brain/projects/{project_name}`
+- Windows: `%USERPROFILE%\.wicked-brain\projects\{project_name}`
 
 ## When to use
 
@@ -31,12 +56,18 @@ For the brain path default:
 
 ### Step 1: Ask the user
 
-Ask these questions (provide defaults):
+Compute the default project name from the current working directory basename
+(lowercase, replace non-alphanumerics with hyphens). Then ask:
+
+1. "What should this project's brain be called?" — Default: `{cwd_basename}`
+2. "Where should it live?" — Default:
+   - macOS/Linux: `~/.wicked-brain/projects/{project_name}`
+   - Windows: `%USERPROFILE%\.wicked-brain\projects\{project_name}`
 
-1. "Where should your brain live?"
-   - Default (macOS/Linux): `~/.wicked-brain`
-   - Default (Windows): `%USERPROFILE%\.wicked-brain`
-2. "What should this brain be called?" — Default: directory name
+If the user supplies a path that is exactly `~/.wicked-brain` (the parent
+directory, not a project subdirectory), push back: explain the per-project
+convention and suggest `~/.wicked-brain/projects/{project_name}` instead.
+Only accept the flat path if the user explicitly insists.
 
 ### Step 2: Check for existing brain
 

package/skills/wicked-brain-lsp/SKILL.md

@@ -43,6 +43,71 @@ whether the language server process is running and review its stderr logs.
 Read `_meta/config.json` for brain path and server port.
 If it doesn't exist, trigger wicked-brain:init.
 
+## Prerequisites — Source Path
+
+**LSP operates on the source project, not the brain directory.** The server must know where the ingested project lives to initialize language servers correctly. Without this, LSP calls will fail with "No Project" errors or return empty results.
+
+### Check if source_path is configured
+
+Read `{brain_path}/_meta/config.json`. Look for a `source_path` key:
+
+```json
+{
+  "brain_path": "/Users/me/.wicked-brain",
+  "server_port": 4243,
+  "source_path": "/Users/me/Projects/my-project"
+}
+```
+
+If `source_path` is **present** — LSP is configured. Proceed with calls.
+
+If `source_path` is **missing** — LSP will fail. Fix it before continuing.
+
+### Fix: set source_path
+
+**Option A** — Re-ingest the project directory (recommended, sets source_path automatically):
+```
+wicked-brain:ingest source=/path/to/project
+```
+
+**Option B** — Write it manually to `_meta/config.json`, then restart the server:
+```bash
+# Read current config, add source_path, write back
+python3 -c "
+import json
+path = '{brain_path}/_meta/config.json'
+with open(path) as f: cfg = json.load(f)
+cfg['source_path'] = '/absolute/path/to/project'
+with open(path, 'w') as f: json.dump(cfg, f, indent=2)
+print('source_path set')
+" 2>/dev/null || python -c "
+import json
+path = '{brain_path}/_meta/config.json'
+with open(path) as f: cfg = json.load(f)
+cfg['source_path'] = '/absolute/path/to/project'
+with open(path, 'w') as f: json.dump(cfg, f, indent=2)
+print('source_path set')
+"
+# Then restart the server with --source:
+npx wicked-brain-server --brain {brain_path} --port {port} --source /absolute/path/to/project &
+```
+
+**Option C** — Restart server with `--source` flag (does not persist to config):
+```bash
+npx wicked-brain-server --brain {brain_path} --port {port} --source /absolute/path/to/project &
+```
+
+Wait 2 seconds after restarting, then verify with `lsp-health`.
+
+### Diagnosing "No Project" / empty results
+
+Symptoms that indicate missing or wrong `source_path`:
+- `lsp-workspace-symbols` returns `{"symbols":[]}` for any query
+- `lsp-health` shows `{"typescript":{"status":"error","message":"No Project"}}` or similar
+- Any LSP call returns an error about workspace or project not found
+
+Check `source_path` in config. If it points at the brain directory (e.g., `~/.wicked-brain/...`) instead of the source project, that is wrong — the brain dir has no `tsconfig.json` or language config. Set it to the project root and restart.
+
 ## When to Use
 
 | You want to... | Action | Example |
@@ -130,7 +195,7 @@ If installation fails, report to the user:
 | `language_server_crashed` | The server crashed 3 times. Report to user, suggest checking the language server logs. |
 | `unsupported_language` | No known language server for this file extension. |
 | `lsp_timeout` | The language server took too long. May be initializing a large project. Retry once. |
-| `file_outside_workspace` | The file isn't in a registered project. Use `wicked-brain:onboard` to register the project first. |
+| `file_outside_workspace` | The file isn't under `source_path`. Check `_meta/config.json` — `source_path` must be the project root that contains the file. Set it and restart the server with `--source`. |
 
 ### Step 5: Use results