cortexdb-cli 0.5.2__py3-none-any.whl → 0.5.3__py3-none-any.whl

cortexdb_cli/__init__.py

@@ -1,3 +1,3 @@
 """CortexDB CLI - command-line interface for the v1 memory API."""
 
-__version__ = "0.5.2"
+__version__ = "0.5.3"

{cortexdb_cli-0.5.2.dist-info → cortexdb_cli-0.5.3.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: cortexdb-cli
-Version: 0.5.2
+Version: 0.5.3
 Summary: Command-line interface for CortexDB — the long-term memory layer for AI.
 Project-URL: Homepage, https://cortexdb.ai
 Project-URL: Documentation, https://cortexdb.ai/docs
@@ -62,8 +62,22 @@ cortexdb recall "Q3 revenue?"
 cortexdb
 ```
 
-The signup token has a 7-day TTL on the free tier. Re-run `cortexdb init`
-to refresh, or pass `--api-key` + `--actor` to use a token from your IdP.
+The signup token has a 7-day TTL on the free tier.
+
+**Re-running `cortexdb init` does not refresh it.** `init` reuses an existing
+identity and changes nothing; against an expired one it refuses and exits 3.
+That is deliberate: a new identity is a new *brain*, and memories written
+under the old actor stay where they are, unreachable from the new config.
+
+When a token expires you have two safe options:
+
+- `cortexdb init --api-key <token> --actor <actor>` — keep the same brain
+  with a token you already hold (e.g. from your IdP).
+- `cortexdb init --force` — deliberately start a NEW brain. The previous
+  identity is backed up to `state.json.replaced` first.
+
+For a second brain alongside the first, isolate instead of replacing:
+`cortexdb --config-dir <dir> init`, or set `CORTEXDB_HOME`.
 
 ## Commands
 
@@ -112,7 +126,9 @@ Force JSON mode any time with `--json`.
 - The v1 API requires both `Authorization: Bearer <PASETO>` and `X-Cortex-Actor`.
   The CLI stamps both on every request — you never need to pass them by hand.
 - 401s show the specific error code (`TOKEN_EXPIRED`, `actor_mismatch`, …)
-  and the remediation: usually `cortexdb init`.
+  and the remediation. Note that `TOKEN_EXPIRED` is **not** fixed by re-running
+  `cortexdb init` — see the identity note above; that would mint a different
+  brain rather than restore access to yours.
 - 403s cite the missing capability and the policy tier that denied. If a
   recall returns `diagnostics.read denied`, pass `--diagnostics none` —
   free-tier tokens don't carry the `diagnostics.read` capability.

{cortexdb_cli-0.5.2.dist-info → cortexdb_cli-0.5.3.dist-info}/RECORD

@@ -1,4 +1,4 @@
-cortexdb_cli/__init__.py,sha256=E9HyqRe9juxBYu8xwyA9tk6TUvi3rTeVOfrdIvcJFPA,90
+cortexdb_cli/__init__.py,sha256=2UYu9wmxTQpfORew0gzovY5bYQAyLW6hmnIR-bQps9E,90
 cortexdb_cli/client.py,sha256=CQwGo4Gn7cHDnfLUlJBZMsZ9-AyGVz8W6bJKxNMwlRA,2862
 cortexdb_cli/config.py,sha256=ee1qmOfqMwilL81ujaqjf6TjjlrFG7WZAHRIgeyif9U,5690
 cortexdb_cli/errors.py,sha256=xwxAWYY7KtNa-e7dyLQECnsKcciVcKC41CXFFF_-0VU,3924
@@ -34,7 +34,7 @@ cortexdb_cli/commands/scopes.py,sha256=Cx_zV-zyIrnDxwp_I4AX_Teh7UFu4EdvDOYe9hTEF
 cortexdb_cli/commands/search.py,sha256=4wsgNU47deb0x5o7xC9eWlhwdIIbz56q7ne8GIiCmYo,1953
 cortexdb_cli/commands/understanding.py,sha256=BktqOn-GloOzSSGJGK9xh5kGCpxcrwkNogtXhjj4pBI,5371
 cortexdb_cli/commands/wire.py,sha256=M3UUHScmvr_MDrX_RaMBg-YLTcHKUq9woNkT4KHJKfs,8131
-cortexdb_cli-0.5.2.dist-info/METADATA,sha256=CIgu0dksEWHPqVq3WHPmOq2kQRxkMf3U00ZlltMO620,4429
-cortexdb_cli-0.5.2.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
-cortexdb_cli-0.5.2.dist-info/entry_points.txt,sha256=h3sEbdqqvtv8LBbRLUgybYPo9N2lpU85fQUSh5ToEvs,51
-cortexdb_cli-0.5.2.dist-info/RECORD,,
+cortexdb_cli-0.5.3.dist-info/METADATA,sha256=pHC6gxm4OoeXGAaxtiJ-zDrbsuVGbbQfC_Cj2GQTmvM,5234
+cortexdb_cli-0.5.3.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
+cortexdb_cli-0.5.3.dist-info/entry_points.txt,sha256=h3sEbdqqvtv8LBbRLUgybYPo9N2lpU85fQUSh5ToEvs,51
+cortexdb_cli-0.5.3.dist-info/RECORD,,