eminiar 0.13.0 → 0.13.1

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "eminiar",
   "displayName": "Eminiar",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "description": "Local-first context, memory and knowledge graph for Claude Code: sandboxed execution, FTS5 + vector search, session continuity, code graph.",
   "author": {
     "name": "Ryan Dick"

package/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "eminiar",
   "displayName": "Eminiar",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "description": "Local-first context, memory and knowledge graph for coding agents: sandboxed execution, FTS5 + vector search, session continuity, code graph.",
   "author": {
     "name": "Ryan Dick"

package/README.md

@@ -17,11 +17,11 @@
 <br/>
 
 <picture>
-  <source media="(prefers-color-scheme: dark)" srcset="docs/images/dashboard-explore-dark.webp">
-  <img alt="The eminiar dashboard: source explorer with file impact, dependents and linked memories" src="docs/images/dashboard-explore-light.webp" width="900">
+  <source media="(prefers-color-scheme: dark)" srcset="docs/images/dashboard-swarm-dark.webp">
+  <img alt="The eminiar Swarms dashboard: progress rings, run stats and the live topology of a swarm run" src="docs/images/dashboard-swarm-light.webp" width="900">
 </picture>
 
-<sub>The local dashboard: source, file impact and the memories linked to the file.</sub>
+<sub>The Swarms dashboard: progress rings, run stats and the live topology of a run.</sub>
 
 </div>
 
@@ -88,6 +88,11 @@ Recall matches a memory when the prompt names it, one of its tags, a file it men
 symbol from that file. A memory can come back later in a long session. To see why a memory did
 or did not appear, run `eminiar recall --explain "<prompt>"`.
 
+| | |
+|:---:|:---:|
+| [<img alt="Memory: the list of memories by kind, and one decision with its tags, linked files and text" src="docs/images/dashboard-memory-dark.webp" width="430">](docs/dashboard.md#memory) | [<img alt="Memory graph: memories linked to the files, tags and topics they are about" src="docs/images/dashboard-memory-graph-dark.webp" width="430">](docs/dashboard.md#memory) |
+| **Memory:** read and edit every memory | **Memory graph:** what each memory is about |
+
 ### 🕸️ Code knowledge graph — a map before an edit
 
 tree-sitter parses TypeScript, JavaScript, Python, Go and PHP into files, symbols, imports, calls,
@@ -100,6 +105,11 @@ Memories and documentation share the same graph. Each memory links to the files
 mentions, and each doc source links to the code that uses it. One graph answers *"what do we
 know about this file?"*
 
+| | |
+|:---:|:---:|
+| [<img alt="Galaxy: the knowledge graph of files and symbols around a file, by imports, calls and references" src="docs/images/dashboard-galaxy-dark.webp" width="430">](docs/dashboard.md#galaxy) | [<img alt="Explore: the source of a file with its impact, dependents and linked memories" src="docs/images/dashboard-explore-dark.webp" width="430">](docs/dashboard.md#explore) |
+| **Galaxy:** the knowledge graph | **Explore:** source, impact and linked memories |
+
 ### 📜 Git history, read for Claude
 
 `em_history` classifies every commit (feat, fix, refactor, perf …). It traces each fix back to
@@ -110,12 +120,19 @@ The history graph connects branches to their commits, commits to the files they
 those files to the memories and docs about them. Merged and deleted branches keep their commits.
 A fix points at the commit it repairs.
 
+| | |
+|:---:|:---:|
+| [<img alt="History: commits classified by kind, with the branch graph" src="docs/images/dashboard-history-dark.webp" width="430">](docs/dashboard.md#history) | [<img alt="History graph: branches, their commits, and the files, memories and docs they touched" src="docs/images/dashboard-history-graph-dark.webp" width="430">](docs/dashboard.md#history) |
+| **History:** classified commits and fix tracing | **History graph:** branches to files and memories |
+
 ### 📚 Documentation knowledge base
 
 `em_docs` finds your local docs (READMEs, ADRs, OpenAPI, Postman) and the libraries, services
 and third-party APIs your code calls. It indexes their documentation locally. OpenAPI specs are
 split into one section per endpoint, so a lookup returns the exact operation.
 
+[<img alt="Docs: discovered local docs, catalog libraries and registry packages, ready to index" src="docs/images/dashboard-docs-dark.webp" width="640">](docs/dashboard.md#docs)
+
 ### 💸 Usage insights — what each session really costs
 
 `em_usage` reads the transcripts Claude Code keeps on your machine and records tokens, cache
@@ -125,14 +142,25 @@ session with its compactions, which tools fill the context, insights with recomm
 what eminiar's own tools saved in dollars. Everything stays local; cost is an estimate at list
 price ([details](docs/usage.md)).
 
+[<img alt="Usage: cost per day by model, cache hit rate, burn rate and session scores" src="docs/images/dashboard-usage-dark.webp" width="640">](docs/dashboard.md#usage)
+
 ### 🐝 Agent swarms (opt-in)
 
 Declare worker roles in `.eminiar/swarm.yaml`, with their prompts, models, tools, skills and
 hooks. eminiar generates a Claude Code agent file per role. `/eminiar:em-swarm <swarm> <goal>`
 makes the main session the coordinator: it plans small tasks, fans workers out in parallel and
 reviews what comes back. Every worker starts with the memories, history risk and hot files for
-its task. Capacity limits, a shared blackboard and a live Swarms tab in the dashboard come with
-it. Nothing changes until you run `eminiar swarm init` ([details](docs/swarms.md)).
+its task. Capacity limits, a shared blackboard and a Swarms tab in the dashboard (a live run
+monitor, plus a visual editor for the swarm file) come with it. Nothing changes until you run `eminiar swarm init` ([details](docs/swarms.md)).
+
+The run monitor shows progress, workers and the topology as a run happens. The configuration
+studio edits roles, models and topology without hand-written YAML
+([monitor](docs/dashboard.md#swarms), [studio](docs/swarms.md#edit-in-the-dashboard)).
+
+| | |
+|:---:|:---:|
+| [<img alt="Swarm run: progress rings, task and worker counts, and the live topology of a run" src="docs/images/dashboard-swarm-dark.webp" width="430">](docs/dashboard.md#swarms) | [<img alt="Swarm configuration studio: swarms, topology picker and the swarm file" src="docs/images/dashboard-swarm-config-dark.webp" width="430">](docs/dashboard.md#configure) |
+| **Run monitor:** progress, workers, topology | **Configuration studio:** edit the swarm file visually |
 
 ### ⚖️ Adjudicator (opt-in)
 
@@ -146,17 +174,10 @@ off: `eminiar adjudicator enable` ([details](docs/adjudicator.md)).
 ### 📊 Local dashboard
 
 `eminiar ui` opens a local web app with token savings, usage and cost, a source explorer with
-impact analysis, a graph "galaxy", an architecture map, a history explorer with a history
-graph, a memory editor with a memory graph, and a docs manager.
+impact analysis, a graph "galaxy", a history explorer with a history graph, a memory editor with a
+memory graph, a docs manager, and a swarm monitor with a configuration studio.
 
-| | |
-|:---:|:---:|
-| [<img alt="Galaxy: the knowledge graph around a file" src="docs/images/dashboard-galaxy-dark.webp" width="430">](docs/dashboard.md#galaxy) | [<img alt="Usage: cost per day by model, cache hit rate, burn rate and session scores" src="docs/images/dashboard-usage-dark.webp" width="430">](docs/dashboard.md#usage) |
-| **Galaxy:** the knowledge graph | **Usage:** cost, cache and burn rate |
-| [<img alt="History graph: branches, their commits, and the files, memories and docs they touched" src="docs/images/dashboard-history-graph-dark.webp" width="430">](docs/dashboard.md#history) | [<img alt="Memory graph: memories linked to the files, tags and topics they are about" src="docs/images/dashboard-memory-graph-dark.webp" width="430">](docs/dashboard.md#memory) |
-| **History graph:** branches to files and memories | **Memory graph:** what each memory is about |
-| [<img alt="History: commits classified by kind, with the branch graph" src="docs/images/dashboard-history-dark.webp" width="430">](docs/dashboard.md#history) | [<img alt="Hotspots: fan-in, churn and complexity per file" src="docs/images/dashboard-hotspots-dark.webp" width="430">](docs/dashboard.md#architecture) |
-| **History:** classified commits and fix tracing | **Hotspots:** where change is risky |
+[<img alt="Overview: tokens kept out of context, savings per session, project and lifetime, the active swarm run and savings by tool" src="docs/images/dashboard-overview-dark.webp" width="640">](docs/dashboard.md#overview)
 
 ## What Claude sees
 
@@ -272,6 +293,13 @@ Your code, tool output and memories stay on your machine. eminiar uses the netwo
 
 The dashboard listens on `127.0.0.1` only.
 
+## About
+
+eminiar is for people who use Claude Code or Cursor on a real codebase and want it to remember
+decisions, see the structure of the code and stop filling its context with raw output. It is
+local-first: one SQLite database per project, no cloud service, and the dashboard listens on
+`127.0.0.1` only. It is open source under the MIT license, written by Ryan Dick.
+
 ## License
 
 MIT © Ryan Dick

package/bin/_resolve.sh

@@ -7,7 +7,7 @@
 # but no node_modules/, so dist/*.js cannot import better-sqlite3 and friends. The
 # installer pins the stable copy (~/.eminiar/plugin/node_modules/eminiar, with its
 # dependencies beside it) in $EMINIAR_HOME/root-path; when the directory this shim
-# lives in cannot resolve its dependencies, we run the pinned copy's dist/ instead.
+# lives in cannot run (see em_runnable), we run the pinned copy's dist/ instead.
 EM_HOME="${EMINIAR_HOME:-$HOME/.eminiar}"
 # EM_SELF: the shim's real path when it was reached through a symlink (bin/eminiar).
 DIR="$(cd "$(dirname "${EM_SELF:-$0}")/.." && pwd)"
@@ -28,9 +28,12 @@ if [ ! -x "$NODE" ]; then
   NODE="$(command -v node 2>/dev/null)"
 fi
 
-# A package root is runnable when its dependencies resolve: node_modules/ inside it
-# (dev checkout, npm -g) or beside it (stable copy inside ~/.eminiar/plugin/node_modules).
+# A package root is runnable when the dist/ entry this shim runs (EM_ENTRY) is built and its
+# dependencies resolve: node_modules/ inside it (dev checkout, npm -g) or beside it (stable copy
+# inside ~/.eminiar/plugin/node_modules). A copy Claude Code makes from a git marketplace has
+# node_modules/ (Claude Code installs the dependencies) but no dist/, which is gitignored.
 em_runnable() {
+  [ -f "$1/dist/${EM_ENTRY:-server}.js" ] || return 1
   [ -e "$1/node_modules/better-sqlite3/package.json" ] || [ -e "$1/../better-sqlite3/package.json" ]
 }
 
@@ -39,7 +42,7 @@ if ! em_runnable "$DIR"; then
   RUN=""
   if [ -f "$EM_HOME/root-path" ]; then
     ALT="$(cat "$EM_HOME/root-path" 2>/dev/null)"
-    if [ -n "$ALT" ] && [ -f "$ALT/dist/server.js" ] && em_runnable "$ALT"; then
+    if [ -n "$ALT" ] && em_runnable "$ALT"; then
       RUN="$ALT"
       # Point version/grammar lookups at the code that actually runs; keep the
       # launch directory for diagnostics (em_doctor shows "launched from").

package/bin/em-hook

@@ -1,6 +1,7 @@
 #!/bin/sh
 # Hook entry shim. Node and package-root resolution live in _resolve.sh.
 # A hook must never block Claude: if nothing can run, print an empty JSON object.
+EM_ENTRY=hook
 . "$(dirname "$0")/_resolve.sh"
 # Swarm enforcement fails closed: when nothing can run, an Agent/Task call in a project whose
 # .eminiar/swarm.yaml says `enforce: true` is denied. Reads stdin only here; every other call
@@ -80,7 +81,7 @@ if [ ! -x "$NODE" ]; then
   exit 0
 fi
 if [ -z "$RUN" ]; then
-  echo "eminiar hook: $DIR has no node_modules and no stable copy is pinned (run: npx eminiar install)" >&2
+  echo "eminiar hook: $DIR cannot run (no dist/hook.js or node_modules) and no stable copy is pinned (run: npx eminiar install)" >&2
   [ -n "$EM_GATE" ] && exit 1
   swarm_gate "$@" && echo '{}'
   exit 0

package/bin/em-server

@@ -1,12 +1,13 @@
 #!/bin/sh
 # MCP server shim (stdio). Node and package-root resolution live in _resolve.sh.
+EM_ENTRY=server
 . "$(dirname "$0")/_resolve.sh"
 if [ ! -x "$NODE" ]; then
   echo "eminiar: no node binary found (run: npx eminiar install)" >&2
   exit 1
 fi
 if [ -z "$RUN" ]; then
-  echo "eminiar: $DIR has no node_modules and no stable copy is pinned in $EM_HOME/root-path (run: npx eminiar install)" >&2
+  echo "eminiar: $DIR cannot run (no dist/server.js or node_modules) and no stable copy is pinned in $EM_HOME/root-path (run: npx eminiar install)" >&2
   exit 1
 fi
 exec "$NODE" "$RUN/dist/server.js" "$@"

package/bin/eminiar

@@ -10,13 +10,14 @@ while [ -L "$EM_SELF" ]; do
     *) EM_SELF="$(dirname "$EM_SELF")/$EM_LINK" ;;
   esac
 done
+EM_ENTRY=cli
 . "$(dirname "$EM_SELF")/_resolve.sh"
 if [ ! -x "$NODE" ]; then
   echo "eminiar: node >= 22.12 is required" >&2
   exit 1
 fi
 if [ -z "$RUN" ]; then
-  echo "eminiar: $DIR has no node_modules and no stable copy is pinned in $EM_HOME/root-path (run: npx eminiar install)" >&2
+  echo "eminiar: $DIR cannot run (no dist/cli.js or node_modules) and no stable copy is pinned in $EM_HOME/root-path (run: npx eminiar install)" >&2
   exit 1
 fi
 exec "$NODE" "$RUN/dist/cli.js" "$@"