@nex-ai/nex 0.1.27 → 0.1.28

package/README.md

@@ -1,9 +1,14 @@
-# @nex-ai/nex
+# Nex: Compounding Intelligence for AI agents
 
 [![npm version](https://img.shields.io/npm/v/@nex-ai/nex)](https://www.npmjs.com/package/@nex-ai/nex)
 [![GitHub](https://img.shields.io/badge/github-nex--crm%2Fnex--as--a--skill-blue)](https://github.com/nex-crm/nex-as-a-skill)
+[![Discord](https://img.shields.io/badge/Discord-Join%20Community-5865F2?logo=discord&logoColor=white)](https://discord.gg/gjSySC3PzV)
 
-Nex CLI provides organizational context & memory to AI agents across 12 platforms.
+Turn all your AI agent conversations into a unified knowledge graph. Supports Claude Code, Codex, OpenClaw, Cursor, OpenCode, etc. Adds additional context from Email, Meetings, Slack, HubSpot, Salesforce.
+
+<a href="https://discord.gg/gjSySC3PzV"><img src="https://img.shields.io/badge/Join%20our%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" alt="Join our Discord" /></a>
+
+Talk to the team, share feedback, and connect with other developers building AI agents with Nex.
 
 **GitHub**: [github.com/nex-crm/nex-as-a-skill](https://github.com/nex-crm/nex-as-a-skill)
 
@@ -11,7 +16,7 @@ Nex CLI provides organizational context & memory to AI agents across 12 platform
 
 ```bash
 # Install globally
-npm install -g @nex-ai/nex
+bun install -g @nex-ai/nex
 
 # Or run directly (no install)
 npx @nex-ai/nex ask "who is Maria?"
@@ -99,7 +104,7 @@ nex graph                          # Open the workspace graph in your browser
 - Creates `.nex.toml` project config with commented defaults
 - Syncs API key to `~/.nex-mcp.json` (shared config)
 
-**Single install**: `npm install -g @nex-ai/nex` bundles everything — hooks, adapters, platform plugins, slash commands, rules, and MCP server. No separate packages needed.
+**Single install**: `bun install -g @nex-ai/nex` bundles everything — hooks, adapters, platform plugins, slash commands, rules, and MCP server. No separate packages needed.
 
 **Integration hierarchy** (per platform): Hooks > Custom plugins > Custom agents/modes > Workflows > Rules > MCP. Each platform gets every layer it supports.
 
@@ -252,9 +257,9 @@ git diff | nex capture
 ## Development
 
 ```bash
-npm install
-npm run build     # TypeScript → dist/
-npm run dev       # Run with tsx (no build)
-npm test          # Unit tests
+bun install
+bun run build     # TypeScript → dist/
+bun run dev       # Run TS directly (no build)
+bun test          # Unit + integration tests
 NEX_DEV_URL=http://localhost:30000 nex ask "test"  # Local API
 ```

package/dist/plugin/context-format.d.ts

@@ -9,6 +9,10 @@ export interface NexRecallResult {
 }
 /**
  * Format a Nex /ask response as an XML block for context injection.
+ *
+ * The preamble tells the AI to use the context naturally — not as a
+ * direct answer, but as background knowledge that informs the response.
+ * This makes proactive context feel seamless rather than forced.
  */
 export declare function formatNexContext(result: NexRecallResult): string;
 /**

package/dist/plugin/context-format.js

@@ -6,6 +6,10 @@ const OPEN_TAG = "<nex-context>";
 const CLOSE_TAG = "</nex-context>";
 /**
  * Format a Nex /ask response as an XML block for context injection.
+ *
+ * The preamble tells the AI to use the context naturally — not as a
+ * direct answer, but as background knowledge that informs the response.
+ * This makes proactive context feel seamless rather than forced.
  */
 export function formatNexContext(result) {
     const parts = [

package/dist/plugin/context-format.js.map

@@ -1 +1 @@
-{"version":3,"file":"context-format.js","sourceRoot":"","sources":["../../src/plugin/context-format.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,QAAQ,GAAG,eAAe,CAAC;AACjC,MAAM,SAAS,GAAG,gBAAgB,CAAC;AAQnC;;GAEG;AACH,MAAM,UAAU,gBAAgB,CAAC,MAAuB;IACtD,MAAM,KAAK,GAAa;QACtB,QAAQ;QACR,2IAA2I;KAC5I,CAAC;IAEF,IAAI,MAAM,CAAC,WAAW,GAAG,CAAC,EAAE,CAAC;QAC3B,KAAK,CAAC,IAAI,CAAC,IAAI,MAAM,CAAC,WAAW,0BAA0B,CAAC,CAAC;IAC/D,CAAC;IAED,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACf,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;IAC1B,KAAK,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC;IAEtB,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC1B,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,eAAe,CAAC,IAAY;IAC1C,+BAA+B;IAC/B,IAAI,MAAM,GAAG,IAAI,CAAC,OAAO,CAAC,uCAAuC,EAAE,EAAE,CAAC,CAAC;IACvE,8DAA8D;IAC9D,MAAM,GAAG,MAAM,CAAC,OAAO,CAAC,uBAAuB,EAAE,EAAE,CAAC,CAAC;IACrD,OAAO,MAAM,CAAC,IAAI,EAAE,CAAC;AACvB,CAAC"}
+{"version":3,"file":"context-format.js","sourceRoot":"","sources":["../../src/plugin/context-format.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,QAAQ,GAAG,eAAe,CAAC;AACjC,MAAM,SAAS,GAAG,gBAAgB,CAAC;AAQnC;;;;;;GAMG;AACH,MAAM,UAAU,gBAAgB,CAAC,MAAuB;IACtD,MAAM,KAAK,GAAa;QACtB,QAAQ;QACR,2IAA2I;KAC5I,CAAC;IAEF,IAAI,MAAM,CAAC,WAAW,GAAG,CAAC,EAAE,CAAC;QAC3B,KAAK,CAAC,IAAI,CAAC,IAAI,MAAM,CAAC,WAAW,0BAA0B,CAAC,CAAC;IAC/D,CAAC;IAED,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACf,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;IAC1B,KAAK,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC;IAEtB,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC1B,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,eAAe,CAAC,IAAY;IAC1C,+BAA+B;IAC/B,IAAI,MAAM,GAAG,IAAI,CAAC,OAAO,CAAC,uCAAuC,EAAE,EAAE,CAAC,CAAC;IACvE,8DAA8D;IAC9D,MAAM,GAAG,MAAM,CAAC,OAAO,CAAC,uBAAuB,EAAE,EAAE,CAAC,CAAC;IACrD,OAAO,MAAM,CAAC,IAAI,EAAE,CAAC;AACvB,CAAC"}

package/dist/plugin/recall-filter.d.ts

@@ -1,10 +1,13 @@
 /**
- * Smart prompt classifier for selective recall.
+ * Proactive recall filter — surfaces knowledge graph context on every meaningful prompt.
  *
- * Determines whether a prompt is likely knowledge-seeking (needs recall)
- * or a pure coding directive (skip recall). Also handles debounce —
- * skips recall if a successful recall happened within the debounce window,
- * unless the current prompt contains question words.
+ * Philosophy: err heavily on the side of recalling. The moments where context
+ * feels most "magical" are when the user DIDN'T ask for it — they're fixing a
+ * migration, deploying a service, or refactoring code, and suddenly relevant
+ * insights, patterns, or entity context from their knowledge graph appears.
+ *
+ * Only skip on truly trivial inputs (confirmations, single words) or explicit opt-out.
+ * Debounce prevents hammering the API on rapid-fire prompts.
  *
  * Persistence: last-recall timestamp stored in ~/.nex/recall-state.json
  */
@@ -19,5 +22,11 @@ export interface RecallDecision {
 export declare function recordRecall(sessionId?: string): void;
 /**
  * Determine whether this prompt should trigger a Nex /ask recall.
+ *
+ * Default: ALWAYS recall. Only skip on:
+ * - Explicit opt-out (prompt starts with !)
+ * - Trivial confirmations (yes, ok, done, lgtm)
+ * - Very short inputs (< 10 chars)
+ * - Debounce (< 10s since last recall, unless first prompt)
  */
 export declare function shouldRecall(prompt: string, isFirstPrompt: boolean): RecallDecision;

package/dist/plugin/recall-filter.js

@@ -1,10 +1,13 @@
 /**
- * Smart prompt classifier for selective recall.
+ * Proactive recall filter — surfaces knowledge graph context on every meaningful prompt.
  *
- * Determines whether a prompt is likely knowledge-seeking (needs recall)
- * or a pure coding directive (skip recall). Also handles debounce —
- * skips recall if a successful recall happened within the debounce window,
- * unless the current prompt contains question words.
+ * Philosophy: err heavily on the side of recalling. The moments where context
+ * feels most "magical" are when the user DIDN'T ask for it — they're fixing a
+ * migration, deploying a service, or refactoring code, and suddenly relevant
+ * insights, patterns, or entity context from their knowledge graph appears.
+ *
+ * Only skip on truly trivial inputs (confirmations, single words) or explicit opt-out.
+ * Debounce prevents hammering the API on rapid-fire prompts.
  *
  * Persistence: last-recall timestamp stored in ~/.nex/recall-state.json
  */
@@ -13,18 +16,9 @@ import { join } from "node:path";
 import { homedir } from "node:os";
 const DATA_DIR = join(homedir(), ".nex");
 const STATE_FILE = join(DATA_DIR, "recall-state.json");
-const DEBOUNCE_MS = 30_000; // 30 seconds
-// --- Question words that signal knowledge-seeking intent ---
-const QUESTION_WORDS = /\b(who|what|when|where|why|how|which|tell|explain|describe|summarize|summarise|list|find|show|get|any|does|did|is|are|was|were|have|has|do|can|could|should|would|will)\b/i;
-// --- Tool/action commands that are pure coding directives ---
-const TOOL_COMMANDS = /^\s*(run|build|test|lint|format|deploy|install|uninstall|start|stop|restart|commit|push|pull|merge|rebase|checkout|fetch|init|fix|refactor|rename|move|delete|remove|add|create|update|upgrade|downgrade|migrate|generate|scaffold|compile|bundle|watch|serve|debug|profile|bench|clean|reset|undo|redo|revert|squash|cherry-pick|tag|release|publish|npm|npx|yarn|pnpm|bun|pip|cargo|go|make|docker|kubectl|terraform|git|gh|cd|ls|cat|grep|find|mkdir|rm|cp|mv|touch|echo|export|source|chmod|chown|curl|wget|ssh|scp)\b/i;
-// --- File reference pattern (paths, extensions) ---
-const FILE_REF = /(?:[\w./\\-]+\.\w{1,10}|src\/|lib\/|dist\/|node_modules\/|\.\/|\.\.\/)/;
-// --- Code-heavy: >50% non-alpha characters (brackets, operators, etc.) ---
-function isCodeHeavy(text) {
-    const alpha = text.replace(/[^a-zA-Z]/g, "").length;
-    return alpha < text.length * 0.5;
-}
+const DEBOUNCE_MS = 10_000; // 10 seconds
+// --- Trivial inputs that never benefit from context ---
+const TRIVIAL = /^\s*(y(es)?|no?|ok(ay)?|sure|done|thanks?|k|lgtm|approved?|merge|ship\s*it|looks?\s*good|\+1|👍)\s*[.!?]*\s*$/i;
 function readState() {
     try {
         const raw = readFileSync(STATE_FILE, "utf-8");
@@ -52,6 +46,12 @@ export function recordRecall(sessionId) {
 }
 /**
  * Determine whether this prompt should trigger a Nex /ask recall.
+ *
+ * Default: ALWAYS recall. Only skip on:
+ * - Explicit opt-out (prompt starts with !)
+ * - Trivial confirmations (yes, ok, done, lgtm)
+ * - Very short inputs (< 10 chars)
+ * - Debounce (< 10s since last recall, unless first prompt)
  */
 export function shouldRecall(prompt, isFirstPrompt) {
     const trimmed = prompt.trim();
@@ -63,32 +63,20 @@ export function shouldRecall(prompt, isFirstPrompt) {
     if (trimmed.startsWith("!")) {
         return { shouldRecall: false, reason: "opt-out" };
     }
-    // Too short — likely a directive like "yes", "ok", "done"
-    if (trimmed.length < 15) {
-        return { shouldRecall: false, reason: "too-short" };
+    // Trivial confirmations
+    if (TRIVIAL.test(trimmed)) {
+        return { shouldRecall: false, reason: "trivial" };
     }
-    // Has question words — likely knowledge-seeking
-    const hasQuestion = QUESTION_WORDS.test(trimmed);
-    // Check debounce: skip if recent successful recall, unless question
-    if (!hasQuestion) {
-        const state = readState();
-        if (state.lastRecallAt > 0 && Date.now() - state.lastRecallAt < DEBOUNCE_MS) {
-            return { shouldRecall: false, reason: "debounce" };
-        }
-    }
-    // Tool/action commands — pure coding directives
-    if (TOOL_COMMANDS.test(trimmed) && !hasQuestion) {
-        return { shouldRecall: false, reason: "tool-command" };
-    }
-    // Code-heavy with file references and no question words
-    if (isCodeHeavy(trimmed) && FILE_REF.test(trimmed) && !hasQuestion) {
-        return { shouldRecall: false, reason: "code-prompt" };
+    // Too short to be meaningful
+    if (trimmed.length < 10) {
+        return { shouldRecall: false, reason: "too-short" };
     }
-    // Has question words — always recall
-    if (hasQuestion) {
-        return { shouldRecall: true, reason: "question" };
+    // Debounce: skip if recent successful recall
+    const state = readState();
+    if (state.lastRecallAt > 0 && Date.now() - state.lastRecallAt < DEBOUNCE_MS) {
+        return { shouldRecall: false, reason: "debounce" };
     }
-    // Default: recall (err on the side of providing context)
-    return { shouldRecall: true, reason: "default" };
+    // Default: always recall — proactive context is the goal
+    return { shouldRecall: true, reason: "proactive" };
 }
 //# sourceMappingURL=recall-filter.js.map

package/dist/plugin/recall-filter.js.map

@@ -1 +1 @@
-{"version":3,"file":"recall-filter.js","sourceRoot":"","sources":["../../src/plugin/recall-filter.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,OAAO,EAAE,YAAY,EAAE,aAAa,EAAE,SAAS,EAAE,MAAM,SAAS,CAAC;AACjE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AACjC,OAAO,EAAE,OAAO,EAAE,MAAM,SAAS,CAAC;AAElC,MAAM,QAAQ,GAAG,IAAI,CAAC,OAAO,EAAE,EAAE,MAAM,CAAC,CAAC;AACzC,MAAM,UAAU,GAAG,IAAI,CAAC,QAAQ,EAAE,mBAAmB,CAAC,CAAC;AACvD,MAAM,WAAW,GAAG,MAAM,CAAC,CAAC,aAAa;AAEzC,8DAA8D;AAC9D,MAAM,cAAc,GAAG,4KAA4K,CAAC;AAEpM,+DAA+D;AAC/D,MAAM,aAAa,GAAG,6fAA6f,CAAC;AAEphB,qDAAqD;AACrD,MAAM,QAAQ,GAAG,wEAAwE,CAAC;AAE1F,4EAA4E;AAC5E,SAAS,WAAW,CAAC,IAAY;IAC/B,MAAM,KAAK,GAAG,IAAI,CAAC,OAAO,CAAC,YAAY,EAAE,EAAE,CAAC,CAAC,MAAM,CAAC;IACpD,OAAO,KAAK,GAAG,IAAI,CAAC,MAAM,GAAG,GAAG,CAAC;AACnC,CAAC;AAYD,SAAS,SAAS;IAChB,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,YAAY,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;QAC9C,OAAO,IAAI,CAAC,KAAK,CAAC,GAAG,CAAgB,CAAC;IACxC,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,EAAE,YAAY,EAAE,CAAC,EAAE,CAAC;IAC7B,CAAC;AACH,CAAC;AAED,SAAS,UAAU,CAAC,KAAkB;IACpC,IAAI,CAAC;QACH,SAAS,CAAC,QAAQ,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QACzC,aAAa,CAAC,UAAU,EAAE,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,EAAE,OAAO,CAAC,CAAC;IAC5D,CAAC;IAAC,MAAM,CAAC;QACP,cAAc;IAChB,CAAC;AACH,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,YAAY,CAAC,SAAkB;IAC7C,UAAU,CAAC,EAAE,YAAY,EAAE,IAAI,CAAC,GAAG,EAAE,EAAE,mBAAmB,EAAE,SAAS,EAAE,CAAC,CAAC;AAC3E,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,YAAY,CAAC,MAAc,EAAE,aAAsB;IACjE,MAAM,OAAO,GAAG,MAAM,CAAC,IAAI,EAAE,CAAC;IAE9B,2CAA2C;IAC3C,IAAI,aAAa,EAAE,CAAC;QAClB,OAAO,EAAE,YAAY,EAAE,IAAI,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IACxD,CAAC;IAED,yCAAyC;IACzC,IAAI,OAAO,CAAC,UAAU,CAAC,GAAG,CAAC,EAAE,CAAC;QAC5B,OAAO,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,EAAE,SAAS,EAAE,CAAC;IACpD,CAAC;IAED,0DAA0D;IAC1D,IAAI,OAAO,CAAC,MAAM,GAAG,EAAE,EAAE,CAAC;QACxB,OAAO,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,EAAE,WAAW,EAAE,CAAC;IACtD,CAAC;IAED,gDAAgD;IAChD,MAAM,WAAW,GAAG,cAAc,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;IAEjD,oEAAoE;IACpE,IAAI,CAAC,WAAW,EAAE,CAAC;QACjB,MAAM,KAAK,GAAG,SAAS,EAAE,CAAC;QAC1B,IAAI,KAAK,CAAC,YAAY,GAAG,CAAC,IAAI,IAAI,CAAC,GAAG,EAAE,GAAG,KAAK,CAAC,YAAY,GAAG,WAAW,EAAE,CAAC;YAC5E,OAAO,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,EAAE,UAAU,EAAE,CAAC;QACrD,CAAC;IACH,CAAC;IAED,gDAAgD;IAChD,IAAI,aAAa,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,WAAW,EAAE,CAAC;QAChD,OAAO,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IACzD,CAAC;IAED,wDAAwD;IACxD,IAAI,WAAW,CAAC,OAAO,CAAC,IAAI,QAAQ,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,WAAW,EAAE,CAAC;QACnE,OAAO,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,EAAE,aAAa,EAAE,CAAC;IACxD,CAAC;IAED,qCAAqC;IACrC,IAAI,WAAW,EAAE,CAAC;QAChB,OAAO,EAAE,YAAY,EAAE,IAAI,EAAE,MAAM,EAAE,UAAU,EAAE,CAAC;IACpD,CAAC;IAED,yDAAyD;IACzD,OAAO,EAAE,YAAY,EAAE,IAAI,EAAE,MAAM,EAAE,SAAS,EAAE,CAAC;AACnD,CAAC"}
+{"version":3,"file":"recall-filter.js","sourceRoot":"","sources":["../../src/plugin/recall-filter.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,EAAE,YAAY,EAAE,aAAa,EAAE,SAAS,EAAE,MAAM,SAAS,CAAC;AACjE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AACjC,OAAO,EAAE,OAAO,EAAE,MAAM,SAAS,CAAC;AAElC,MAAM,QAAQ,GAAG,IAAI,CAAC,OAAO,EAAE,EAAE,MAAM,CAAC,CAAC;AACzC,MAAM,UAAU,GAAG,IAAI,CAAC,QAAQ,EAAE,mBAAmB,CAAC,CAAC;AACvD,MAAM,WAAW,GAAG,MAAM,CAAC,CAAC,aAAa;AAEzC,yDAAyD;AACzD,MAAM,OAAO,GAAG,gHAAgH,CAAC;AAYjI,SAAS,SAAS;IAChB,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,YAAY,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;QAC9C,OAAO,IAAI,CAAC,KAAK,CAAC,GAAG,CAAgB,CAAC;IACxC,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,EAAE,YAAY,EAAE,CAAC,EAAE,CAAC;IAC7B,CAAC;AACH,CAAC;AAED,SAAS,UAAU,CAAC,KAAkB;IACpC,IAAI,CAAC;QACH,SAAS,CAAC,QAAQ,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QACzC,aAAa,CAAC,UAAU,EAAE,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,EAAE,OAAO,CAAC,CAAC;IAC5D,CAAC;IAAC,MAAM,CAAC;QACP,cAAc;IAChB,CAAC;AACH,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,YAAY,CAAC,SAAkB;IAC7C,UAAU,CAAC,EAAE,YAAY,EAAE,IAAI,CAAC,GAAG,EAAE,EAAE,mBAAmB,EAAE,SAAS,EAAE,CAAC,CAAC;AAC3E,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,YAAY,CAAC,MAAc,EAAE,aAAsB;IACjE,MAAM,OAAO,GAAG,MAAM,CAAC,IAAI,EAAE,CAAC;IAE9B,2CAA2C;IAC3C,IAAI,aAAa,EAAE,CAAC;QAClB,OAAO,EAAE,YAAY,EAAE,IAAI,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IACxD,CAAC;IAED,yCAAyC;IACzC,IAAI,OAAO,CAAC,UAAU,CAAC,GAAG,CAAC,EAAE,CAAC;QAC5B,OAAO,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,EAAE,SAAS,EAAE,CAAC;IACpD,CAAC;IAED,wBAAwB;IACxB,IAAI,OAAO,CAAC,IAAI,CAAC,OAAO,CAAC,EAAE,CAAC;QAC1B,OAAO,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,EAAE,SAAS,EAAE,CAAC;IACpD,CAAC;IAED,6BAA6B;IAC7B,IAAI,OAAO,CAAC,MAAM,GAAG,EAAE,EAAE,CAAC;QACxB,OAAO,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,EAAE,WAAW,EAAE,CAAC;IACtD,CAAC;IAED,6CAA6C;IAC7C,MAAM,KAAK,GAAG,SAAS,EAAE,CAAC;IAC1B,IAAI,KAAK,CAAC,YAAY,GAAG,CAAC,IAAI,IAAI,CAAC,GAAG,EAAE,GAAG,KAAK,CAAC,YAAY,GAAG,WAAW,EAAE,CAAC;QAC5E,OAAO,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,EAAE,UAAU,EAAE,CAAC;IACrD,CAAC;IAED,yDAAyD;IACzD,OAAO,EAAE,YAAY,EAAE,IAAI,EAAE,MAAM,EAAE,WAAW,EAAE,CAAC;AACrD,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nex-ai/nex",
-  "version": "0.1.27",
+  "version": "0.1.28",
   "description": "Nex CLI provides organizational context & memory to AI agents",
   "type": "module",
   "bin": {
@@ -15,12 +15,13 @@
   ],
   "scripts": {
     "build": "tsc",
-    "start": "node dist/index.js",
-    "dev": "tsx src/index.ts",
-    "test": "node --import tsx --test tests/**/*.test.ts tests/**/**/*.test.ts",
-    "prepublishOnly": "npm run build"
+    "start": "bun dist/index.js",
+    "dev": "bun src/index.ts",
+    "test": "bun test",
+    "prepublishOnly": "bun run build"
   },
   "devDependencies": {
+    "@types/bun": "latest",
     "@types/node": "^22.0.0",
     "@types/react": "^18.3.18",
     "ink-testing-library": "^4.0.0",

package/platform-rules/aider-conventions.md

@@ -1,8 +1,6 @@
-# --- Nex Context & Memory ---
-
 # Nex — Organizational Context & Memory
 
-Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, and more — via MCP tools.
+Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, insights, patterns, and playbooks — via MCP tools. Context is proactively injected into your conversation, so relevant knowledge surfaces automatically even when you don't ask for it.
 
 ## MCP Tools Available
 
@@ -24,15 +22,25 @@ Shows which integrations (Gmail, Slack, Calendar, CRM) are connected and active.
 ### `nex_connect_integration` — Connect a data source
 Initiate OAuth connection for Gmail, Google Calendar, Outlook, Slack, Salesforce, HubSpot, or Attio.
 
-## When to Use Nex
+## Proactive Context
 
-When the user asks about:
-- **People or companies** — contacts, relationships, org charts
-- **Deals or opportunities** — status, history, next steps
-- **Meetings or calls** — past conversations, upcoming schedules
-- **Emails or messages** — communication history
-- **Organizational context** — company knowledge, team notes, decisions
+Nex automatically surfaces relevant context from the user's knowledge graph on every prompt — not just questions. When you see a `<nex-context>` block, use it naturally to inform your response:
 
-Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.
+- **Entity insights** — facts about people, companies, and deals mentioned or relevant to the task
+- **Knowledge insights** — patterns, lessons learned, and domain knowledge from past work
+- **Playbook rules** — proven approaches and best practices from the user's experience
+
+Leverage this context to provide more informed, personalized responses. If the context mentions a relevant pattern or past decision, incorporate it naturally without explicitly referencing the context block.
+
+## When to Use Nex Tools Directly
 
-# --- End Nex ---
+Use `nex_ask` proactively when:
+- The user mentions a person, company, or project — look up their context
+- The task involves a domain the knowledge graph may have insights on
+- You need organizational context to make a better recommendation
+
+Use `nex_remember` when:
+- The user shares a decision, preference, or important fact worth persisting
+- A conversation reveals new knowledge that future sessions should have access to
+
+Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.

package/platform-rules/cline-rules.md

@@ -1,6 +1,6 @@
 # Nex — Organizational Context & Memory
 
-Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, and more — via MCP tools.
+Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, insights, patterns, and playbooks — via MCP tools. Context is proactively injected into your conversation, so relevant knowledge surfaces automatically even when you don't ask for it.
 
 ## MCP Tools Available
 
@@ -22,13 +22,25 @@ Shows which integrations (Gmail, Slack, Calendar, CRM) are connected and active.
 ### `nex_connect_integration` — Connect a data source
 Initiate OAuth connection for Gmail, Google Calendar, Outlook, Slack, Salesforce, HubSpot, or Attio.
 
-## When to Use Nex
+## Proactive Context
 
-When the user asks about:
-- **People or companies** — contacts, relationships, org charts
-- **Deals or opportunities** — status, history, next steps
-- **Meetings or calls** — past conversations, upcoming schedules
-- **Emails or messages** — communication history
-- **Organizational context** — company knowledge, team notes, decisions
+Nex automatically surfaces relevant context from the user's knowledge graph on every prompt — not just questions. When you see a `<nex-context>` block, use it naturally to inform your response:
+
+- **Entity insights** — facts about people, companies, and deals mentioned or relevant to the task
+- **Knowledge insights** — patterns, lessons learned, and domain knowledge from past work
+- **Playbook rules** — proven approaches and best practices from the user's experience
+
+Leverage this context to provide more informed, personalized responses. If the context mentions a relevant pattern or past decision, incorporate it naturally without explicitly referencing the context block.
+
+## When to Use Nex Tools Directly
+
+Use `nex_ask` proactively when:
+- The user mentions a person, company, or project — look up their context
+- The task involves a domain the knowledge graph may have insights on
+- You need organizational context to make a better recommendation
+
+Use `nex_remember` when:
+- The user shares a decision, preference, or important fact worth persisting
+- A conversation reveals new knowledge that future sessions should have access to
 
 Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.

package/platform-rules/continue-rules.md

@@ -1,6 +1,6 @@
 # Nex — Organizational Context & Memory
 
-Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, and more — via MCP tools.
+Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, insights, patterns, and playbooks — via MCP tools. Context is proactively injected into your conversation, so relevant knowledge surfaces automatically even when you don't ask for it.
 
 ## MCP Tools Available
 
@@ -22,13 +22,25 @@ Shows which integrations (Gmail, Slack, Calendar, CRM) are connected and active.
 ### `nex_connect_integration` — Connect a data source
 Initiate OAuth connection for Gmail, Google Calendar, Outlook, Slack, Salesforce, HubSpot, or Attio.
 
-## When to Use Nex
+## Proactive Context
 
-When the user asks about:
-- **People or companies** — contacts, relationships, org charts
-- **Deals or opportunities** — status, history, next steps
-- **Meetings or calls** — past conversations, upcoming schedules
-- **Emails or messages** — communication history
-- **Organizational context** — company knowledge, team notes, decisions
+Nex automatically surfaces relevant context from the user's knowledge graph on every prompt — not just questions. When you see a `<nex-context>` block, use it naturally to inform your response:
+
+- **Entity insights** — facts about people, companies, and deals mentioned or relevant to the task
+- **Knowledge insights** — patterns, lessons learned, and domain knowledge from past work
+- **Playbook rules** — proven approaches and best practices from the user's experience
+
+Leverage this context to provide more informed, personalized responses. If the context mentions a relevant pattern or past decision, incorporate it naturally without explicitly referencing the context block.
+
+## When to Use Nex Tools Directly
+
+Use `nex_ask` proactively when:
+- The user mentions a person, company, or project — look up their context
+- The task involves a domain the knowledge graph may have insights on
+- You need organizational context to make a better recommendation
+
+Use `nex_remember` when:
+- The user shares a decision, preference, or important fact worth persisting
+- A conversation reveals new knowledge that future sessions should have access to
 
 Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.

package/platform-rules/cursor-rules.md

@@ -1,6 +1,6 @@
 # Nex — Organizational Context & Memory
 
-Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, and more — via MCP tools.
+Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, insights, patterns, and playbooks — via MCP tools. Context is proactively injected into your conversation, so relevant knowledge surfaces automatically even when you don't ask for it.
 
 ## MCP Tools Available
 
@@ -22,13 +22,25 @@ Shows which integrations (Gmail, Slack, Calendar, CRM) are connected and active.
 ### `nex_connect_integration` — Connect a data source
 Initiate OAuth connection for Gmail, Google Calendar, Outlook, Slack, Salesforce, HubSpot, or Attio.
 
-## When to Use Nex
+## Proactive Context
 
-When the user asks about:
-- **People or companies** — contacts, relationships, org charts
-- **Deals or opportunities** — status, history, next steps
-- **Meetings or calls** — past conversations, upcoming schedules
-- **Emails or messages** — communication history
-- **Organizational context** — company knowledge, team notes, decisions
+Nex automatically surfaces relevant context from the user's knowledge graph on every prompt — not just questions. When you see a `<nex-context>` block, use it naturally to inform your response:
+
+- **Entity insights** — facts about people, companies, and deals mentioned or relevant to the task
+- **Knowledge insights** — patterns, lessons learned, and domain knowledge from past work
+- **Playbook rules** — proven approaches and best practices from the user's experience
+
+Leverage this context to provide more informed, personalized responses. If the context mentions a relevant pattern or past decision, incorporate it naturally without explicitly referencing the context block.
+
+## When to Use Nex Tools Directly
+
+Use `nex_ask` proactively when:
+- The user mentions a person, company, or project — look up their context
+- The task involves a domain the knowledge graph may have insights on
+- You need organizational context to make a better recommendation
+
+Use `nex_remember` when:
+- The user shares a decision, preference, or important fact worth persisting
+- A conversation reveals new knowledge that future sessions should have access to
 
 Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.

package/platform-rules/kilocode-rules.md

@@ -1,6 +1,6 @@
 # Nex — Organizational Context & Memory
 
-Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, and more — via MCP tools.
+Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, insights, patterns, and playbooks — via MCP tools. Context is proactively injected into your conversation, so relevant knowledge surfaces automatically even when you don't ask for it.
 
 ## MCP Tools Available
 
@@ -22,13 +22,25 @@ Shows which integrations (Gmail, Slack, Calendar, CRM) are connected and active.
 ### `nex_connect_integration` — Connect a data source
 Initiate OAuth connection for Gmail, Google Calendar, Outlook, Slack, Salesforce, HubSpot, or Attio.
 
-## When to Use Nex
+## Proactive Context
 
-When the user asks about:
-- **People or companies** — contacts, relationships, org charts
-- **Deals or opportunities** — status, history, next steps
-- **Meetings or calls** — past conversations, upcoming schedules
-- **Emails or messages** — communication history
-- **Organizational context** — company knowledge, team notes, decisions
+Nex automatically surfaces relevant context from the user's knowledge graph on every prompt — not just questions. When you see a `<nex-context>` block, use it naturally to inform your response:
+
+- **Entity insights** — facts about people, companies, and deals mentioned or relevant to the task
+- **Knowledge insights** — patterns, lessons learned, and domain knowledge from past work
+- **Playbook rules** — proven approaches and best practices from the user's experience
+
+Leverage this context to provide more informed, personalized responses. If the context mentions a relevant pattern or past decision, incorporate it naturally without explicitly referencing the context block.
+
+## When to Use Nex Tools Directly
+
+Use `nex_ask` proactively when:
+- The user mentions a person, company, or project — look up their context
+- The task involves a domain the knowledge graph may have insights on
+- You need organizational context to make a better recommendation
+
+Use `nex_remember` when:
+- The user shares a decision, preference, or important fact worth persisting
+- A conversation reveals new knowledge that future sessions should have access to
 
 Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.

package/platform-rules/opencode-agents.md

@@ -1,8 +1,6 @@
-# --- Nex Context & Memory ---
-
 # Nex — Organizational Context & Memory
 
-Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, and more — via MCP tools.
+Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, insights, patterns, and playbooks — via MCP tools. Context is proactively injected into your conversation, so relevant knowledge surfaces automatically even when you don't ask for it.
 
 ## MCP Tools Available
 
@@ -24,15 +22,25 @@ Shows which integrations (Gmail, Slack, Calendar, CRM) are connected and active.
 ### `nex_connect_integration` — Connect a data source
 Initiate OAuth connection for Gmail, Google Calendar, Outlook, Slack, Salesforce, HubSpot, or Attio.
 
-## When to Use Nex
+## Proactive Context
 
-When the user asks about:
-- **People or companies** — contacts, relationships, org charts
-- **Deals or opportunities** — status, history, next steps
-- **Meetings or calls** — past conversations, upcoming schedules
-- **Emails or messages** — communication history
-- **Organizational context** — company knowledge, team notes, decisions
+Nex automatically surfaces relevant context from the user's knowledge graph on every prompt — not just questions. When you see a `<nex-context>` block, use it naturally to inform your response:
 
-Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.
+- **Entity insights** — facts about people, companies, and deals mentioned or relevant to the task
+- **Knowledge insights** — patterns, lessons learned, and domain knowledge from past work
+- **Playbook rules** — proven approaches and best practices from the user's experience
+
+Leverage this context to provide more informed, personalized responses. If the context mentions a relevant pattern or past decision, incorporate it naturally without explicitly referencing the context block.
+
+## When to Use Nex Tools Directly
 
-# --- End Nex ---
+Use `nex_ask` proactively when:
+- The user mentions a person, company, or project — look up their context
+- The task involves a domain the knowledge graph may have insights on
+- You need organizational context to make a better recommendation
+
+Use `nex_remember` when:
+- The user shares a decision, preference, or important fact worth persisting
+- A conversation reveals new knowledge that future sessions should have access to
+
+Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.

package/platform-rules/vscode-instructions.md

@@ -1,10 +1,6 @@
----
-applyTo: "**"
----
-
 # Nex — Organizational Context & Memory
 
-Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, and more — via MCP tools.
+Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, insights, patterns, and playbooks — via MCP tools. Context is proactively injected into your conversation, so relevant knowledge surfaces automatically even when you don't ask for it.
 
 ## MCP Tools Available
 
@@ -26,13 +22,25 @@ Shows which integrations (Gmail, Slack, Calendar, CRM) are connected and active.
 ### `nex_connect_integration` — Connect a data source
 Initiate OAuth connection for Gmail, Google Calendar, Outlook, Slack, Salesforce, HubSpot, or Attio.
 
-## When to Use Nex
+## Proactive Context
+
+Nex automatically surfaces relevant context from the user's knowledge graph on every prompt — not just questions. When you see a `<nex-context>` block, use it naturally to inform your response:
+
+- **Entity insights** — facts about people, companies, and deals mentioned or relevant to the task
+- **Knowledge insights** — patterns, lessons learned, and domain knowledge from past work
+- **Playbook rules** — proven approaches and best practices from the user's experience
+
+Leverage this context to provide more informed, personalized responses. If the context mentions a relevant pattern or past decision, incorporate it naturally without explicitly referencing the context block.
+
+## When to Use Nex Tools Directly
+
+Use `nex_ask` proactively when:
+- The user mentions a person, company, or project — look up their context
+- The task involves a domain the knowledge graph may have insights on
+- You need organizational context to make a better recommendation
 
-When the user asks about:
-- **People or companies** — contacts, relationships, org charts
-- **Deals or opportunities** — status, history, next steps
-- **Meetings or calls** — past conversations, upcoming schedules
-- **Emails or messages** — communication history
-- **Organizational context** — company knowledge, team notes, decisions
+Use `nex_remember` when:
+- The user shares a decision, preference, or important fact worth persisting
+- A conversation reveals new knowledge that future sessions should have access to
 
 Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.

package/platform-rules/windsurf-rules.md

@@ -1,6 +1,6 @@
 # Nex — Organizational Context & Memory
 
-Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, and more — via MCP tools.
+Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, insights, patterns, and playbooks — via MCP tools. Context is proactively injected into your conversation, so relevant knowledge surfaces automatically even when you don't ask for it.
 
 ## MCP Tools Available
 
@@ -22,13 +22,25 @@ Shows which integrations (Gmail, Slack, Calendar, CRM) are connected and active.
 ### `nex_connect_integration` — Connect a data source
 Initiate OAuth connection for Gmail, Google Calendar, Outlook, Slack, Salesforce, HubSpot, or Attio.
 
-## When to Use Nex
+## Proactive Context
 
-When the user asks about:
-- **People or companies** — contacts, relationships, org charts
-- **Deals or opportunities** — status, history, next steps
-- **Meetings or calls** — past conversations, upcoming schedules
-- **Emails or messages** — communication history
-- **Organizational context** — company knowledge, team notes, decisions
+Nex automatically surfaces relevant context from the user's knowledge graph on every prompt — not just questions. When you see a `<nex-context>` block, use it naturally to inform your response:
+
+- **Entity insights** — facts about people, companies, and deals mentioned or relevant to the task
+- **Knowledge insights** — patterns, lessons learned, and domain knowledge from past work
+- **Playbook rules** — proven approaches and best practices from the user's experience
+
+Leverage this context to provide more informed, personalized responses. If the context mentions a relevant pattern or past decision, incorporate it naturally without explicitly referencing the context block.
+
+## When to Use Nex Tools Directly
+
+Use `nex_ask` proactively when:
+- The user mentions a person, company, or project — look up their context
+- The task involves a domain the knowledge graph may have insights on
+- You need organizational context to make a better recommendation
+
+Use `nex_remember` when:
+- The user shares a decision, preference, or important fact worth persisting
+- A conversation reveals new knowledge that future sessions should have access to
 
 Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.

package/platform-rules/zed-rules.md

@@ -1,8 +1,6 @@
-# --- Nex Context & Memory ---
-
 # Nex — Organizational Context & Memory
 
-Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, and more — via MCP tools.
+Nex provides your AI agent with real-time organizational knowledge — contacts, deals, meetings, emails, notes, insights, patterns, and playbooks — via MCP tools. Context is proactively injected into your conversation, so relevant knowledge surfaces automatically even when you don't ask for it.
 
 ## MCP Tools Available
 
@@ -24,15 +22,25 @@ Shows which integrations (Gmail, Slack, Calendar, CRM) are connected and active.
 ### `nex_connect_integration` — Connect a data source
 Initiate OAuth connection for Gmail, Google Calendar, Outlook, Slack, Salesforce, HubSpot, or Attio.
 
-## When to Use Nex
+## Proactive Context
 
-When the user asks about:
-- **People or companies** — contacts, relationships, org charts
-- **Deals or opportunities** — status, history, next steps
-- **Meetings or calls** — past conversations, upcoming schedules
-- **Emails or messages** — communication history
-- **Organizational context** — company knowledge, team notes, decisions
+Nex automatically surfaces relevant context from the user's knowledge graph on every prompt — not just questions. When you see a `<nex-context>` block, use it naturally to inform your response:
 
-Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.
+- **Entity insights** — facts about people, companies, and deals mentioned or relevant to the task
+- **Knowledge insights** — patterns, lessons learned, and domain knowledge from past work
+- **Playbook rules** — proven approaches and best practices from the user's experience
+
+Leverage this context to provide more informed, personalized responses. If the context mentions a relevant pattern or past decision, incorporate it naturally without explicitly referencing the context block.
+
+## When to Use Nex Tools Directly
 
-# --- End Nex ---
+Use `nex_ask` proactively when:
+- The user mentions a person, company, or project — look up their context
+- The task involves a domain the knowledge graph may have insights on
+- You need organizational context to make a better recommendation
+
+Use `nex_remember` when:
+- The user shares a decision, preference, or important fact worth persisting
+- A conversation reveals new knowledge that future sessions should have access to
+
+Always try `nex_ask` first for general queries. Use `nex_search` when you need to find a specific record by name.