@tpsdev-ai/flair 0.25.2 → 0.25.4

package/README.md

@@ -126,11 +126,11 @@ Every agent has an Ed25519 key pair. Requests are signed with `agentId:timestamp
 Memories are automatically embedded on write using [nomic-embed-text](https://huggingface.co/nomic-ai/nomic-embed-text-v1.5-GGUF) (768 dimensions). Search by meaning:
 
 ```bash
-# Write a memory
-flair memory write "Harper v5 sandbox blocks node:module but process.dlopen works"
+# Write a memory (--agent is your registered agent id)
+flair memory add --agent myagent "Harper v5 sandbox blocks node:module but process.dlopen works"
 
 # Find it later by concept, not exact words
-flair memory search "native addon loading in sandboxed runtimes"
+flair memory search --agent myagent "native addon loading in sandboxed runtimes"
 # → [0.67] Harper v5 sandbox blocks node:module but process.dlopen works
 ```
 

package/dist/cli.js

@@ -8018,7 +8018,15 @@ program
         {
             name: "@tpsdev-ai/flair",
             kind: "bin",
-            probe: () => probeBinVersion(execFileSync, "flair"),
+            // Same PATH-independence fix as flair-mcp below: when `flair` isn't on
+            // PATH (a custom npm prefix — mise/fnm/nvm/volta, or the sudo-less
+            // user-prefix install the README recommends), the bin probe returns
+            // null even though the package IS globally installed, and `flair
+            // upgrade` mis-reports "not detected → run npm install -g". Fall back
+            // to the lib probe, which require.resolves the package.json regardless
+            // of PATH or `--version` support. (Canary's 0.25.3 dogfooding caught
+            // this — the fallback existed for flair-mcp but not for flair itself.)
+            probe: () => probeBinVersion(execFileSync, "flair") ?? probeLibVersion("@tpsdev-ai/flair"),
         },
         {
             name: "@tpsdev-ai/flair-mcp",
@@ -12767,6 +12775,14 @@ program
 // its Node-version check passes. The shim imports this module, so import.meta.main
 // is false there — without this explicit entry point the CLI would load but never run.
 async function runCli() {
+    // A bare `flair` (no command) is a help request, not a usage error — show
+    // help and exit 0, rather than commander's default (help + exit 1). Flags
+    // like -h/--help/-v have argv beyond the binary and fall through to
+    // commander, which already exits 0 for them.
+    if (process.argv.length <= 2) {
+        program.outputHelp();
+        process.exit(0);
+    }
     await program.parseAsync();
 }
 // Run CLI directly when this file is the entry point — covers `node dist/cli.js`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tpsdev-ai/flair",
-  "version": "0.25.2",
+  "version": "0.25.4",
   "packageManager": "bun@1.3.10",
   "description": "Identity, memory, and soul for AI agents. Cryptographic identity (Ed25519), semantic memory with local embeddings, and persistent personality — all in a single process.",
   "type": "module",