memorysync-cli 1.0.2__py3-none-any.whl

memorysync_cli/registry.py

@@ -0,0 +1,101 @@
+"""The command tree, loaded from the Node CLI's registry.
+
+There is no second copy of the command surface here, on purpose.
+
+``registry.json`` is generated by ``sdk/cli/scripts/dump-registry.mjs`` from the
+same ``commandTree()`` the Node CLI serves for ``help --json``. Both CLIs
+therefore describe themselves from one declaration, and ``help --json`` is
+identical between them by construction rather than by review.
+
+That decision comes from watching the only competitor who ships two CLIs try the
+other way. Mem0's documentation promises the npm and Python packages "provide
+identical behavior: same commands, same options, same output formats". In
+practice their Python CLI answers ``help --json`` with twelve commands and their
+Node CLI answers with a name, a version and a description - no commands at all -
+while the two packages sit on different version numbers. Hand-maintained parity
+across two languages does not survive contact with a release schedule.
+
+What this file does not guarantee is that the Python commands *behave* the same.
+A shared registry keeps the description honest; the parity tests check that every
+declared flag is actually accepted.
+"""
+
+from __future__ import annotations
+
+import json
+from functools import lru_cache
+from pathlib import Path
+from typing import Any
+
+_REGISTRY_PATH = Path(__file__).with_name("registry.json")
+
+
+@lru_cache(maxsize=1)
+def load() -> dict[str, Any]:
+    """The whole generated tree.
+
+    Cached because the dispatcher, the help renderer and the completion writer all
+    ask for it, and re-reading a file for each would be a needless startup cost in
+    a tool that is expected to feel instant.
+    """
+    try:
+        with _REGISTRY_PATH.open(encoding="utf-8") as handle:
+            return json.load(handle)
+    except FileNotFoundError:  # pragma: no cover - packaging failure
+        raise RuntimeError(
+            "registry.json is missing from the installed package. "
+            "It is generated from the Node CLI by sdk/cli/scripts/dump-registry.mjs."
+        ) from None
+
+
+def command_tree() -> dict[str, Any]:
+    """The payload ``help --json`` prints, minus the parts that are ours alone."""
+    tree = dict(load())
+    tree.pop("exit_codes", None)
+    return tree
+
+
+@lru_cache(maxsize=1)
+def commands() -> dict[str, dict[str, Any]]:
+    """Commands keyed by name, for dispatch and help lookup."""
+    return {entry["name"]: entry for entry in load()["commands"]}
+
+
+@lru_cache(maxsize=1)
+def global_flags() -> list[dict[str, Any]]:
+    return list(load()["global_flags"])
+
+
+@lru_cache(maxsize=1)
+def formats() -> list[str]:
+    return list(load()["output_formats"])
+
+
+@lru_cache(maxsize=1)
+def exit_codes() -> dict[str, int]:
+    return dict(load()["exit_codes"])
+
+
+def subcommands(name: str) -> dict[str, dict[str, Any]]:
+    """Subcommands of one command, keyed by name. Empty when it has none."""
+    spec = commands().get(name) or {}
+    return {entry["name"]: entry for entry in spec.get("subcommands", [])}
+
+
+def flags_for(name: str, sub: str | None = None) -> list[dict[str, Any]]:
+    """Declared flags for a command, or for one of its subcommands.
+
+    Subcommands inherit the parent's flags: ``project list --output json`` has to
+    work, and the registry only declares ``--output`` once, on the parent.
+    """
+    spec = commands().get(name)
+    if spec is None:
+        return []
+
+    declared = list(spec.get("flags", []))
+    if sub is not None:
+        for entry in spec.get("subcommands", []):
+            if entry["name"] == sub:
+                declared.extend(entry.get("flags", []))
+                break
+    return declared

memorysync_cli-1.0.2.dist-info/METADATA

@@ -0,0 +1,158 @@
+Metadata-Version: 2.5
+Name: memorysync-cli
+Version: 1.0.2
+Summary: MemorySync from your terminal. Zero dependencies.
+Project-URL: Documentation, https://docs.memorysync.io/cli
+Project-URL: Homepage, https://memorysync.io/cli
+Author: MemorySync
+License: MIT
+License-File: LICENSE
+Keywords: agent-memory,ai-agents,cli,llm,long-term-memory,memory,memorysync,terminal
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: Utilities
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+
+# memorysync-cli (Python)
+
+MemorySync from your terminal. Zero dependencies.
+
+The same CLI as the npm package `memorysync-cli`, implemented in Python. Same 21
+commands, same flags, same output formats, same exit codes. The two are
+interchangeable, so you only need one.
+
+```bash
+pipx install memorysync-cli
+```
+
+`pipx` is recommended because this is an application rather than a library. `pip
+install` works too, but outside a virtual environment it fails on
+externally-managed Pythons — Homebrew and most Linux distributions — with
+`externally-managed-environment` ([PEP 668](https://peps.python.org/pep-0668/)).
+
+Requires Python 3.9 or newer.
+
+## Getting started
+
+```bash
+memorysync init                       # store a key, pick a default user
+memorysync add "Prefers pnpm" --user alice
+memorysync search "package manager" --user alice
+memorysync quota                      # how much of the plan is left
+```
+
+Both `memorysync` and `msync` are installed; `msync` is just shorter.
+
+## Parity is enforced, not promised
+
+Both CLIs read one generated command tree, so `help --json` is byte-identical
+between them. The test suite runs both and compares stdout for every offline
+command, including all four completion scripts, and compares exit codes for each
+failure mode. A command added to one and not the other fails the build.
+
+That matters because the alternative does not hold. Mem0 ships a Node and a Python
+CLI and documents them as identical; their Python CLI answers `help --json` with
+twelve commands while their Node CLI answers with a name, a version and a
+description and no commands at all, and the two sit on different versions.
+
+## Zero dependencies
+
+`argparse`, `urllib.request` and `json` cover everything. Mem0's Python CLI depends
+on httpx, rich and typer.
+
+Every dependency is code on a customer's machine that they cannot audit on our
+behalf, which matters more for a closed-source tool because nobody else is reading
+our lockfile. A table and eight colours do not justify it.
+
+## Agent mode
+
+Pass `--json` (or `--agent`) before the command for one JSON envelope, no colour,
+no spinners, errors as JSON with a non-zero exit:
+
+```bash
+memorysync --json search "preferences" --user alice
+```
+
+`data` is always a list, for every command. An agent parses one shape rather than
+remembering which commands return an object.
+
+```bash
+memorysync help --json     # the whole command tree, for self-discovery
+```
+
+## Exit codes
+
+A script can branch on the cause rather than parsing prose.
+
+| Code | Meaning |
+|------|---------|
+| 0 | Success |
+| 1 | Unclassified failure |
+| 2 | Usage: unknown command, bad flag, bad value |
+| 3 | Auth: missing, expired or revoked credentials |
+| 4 | Quota: a plan limit is reached |
+| 5 | Network: unreachable or timed out |
+| 6 | Not found |
+| 130 | Interrupted |
+
+Code 4 earns its place. Over a plan limit the API returns success with an empty
+result rather than an error, deliberately, so an assistant never narrates billing
+state to an end user. From a terminal that silence is unhelpful, so the CLI reads
+usage and turns it into a distinct code — otherwise an exhausted plan is
+indistinguishable from an empty database.
+
+## Where your key is stored
+
+Never in the config file. In order: `MEMORYSYNC_API_KEY`, then the OS keychain,
+then an owner-only encrypted file.
+
+| Platform | Storage |
+|---|---|
+| macOS | Keychain, via `security` |
+| Linux | Keyring, via `secret-tool`, when libsecret is present |
+| Windows | Owner-only encrypted file |
+
+Windows has no scriptable Credential Manager path that avoids a dependency, so it
+uses the file tier. That is the same on the Node CLI. The file is `0600` and its
+contents are tied to the machine and user, which stops a casual `cat` or a backup
+scraper; anyone who can already run code as you can read it. The keychain is
+better, which is why it is tried first.
+
+## Deleting
+
+`delete` is two-step by default: without `--yes` it previews and changes nothing.
+
+`delete --all` clears that one end user's memories and nothing else. No form of any
+command can delete an account, a project or an API key.
+
+To clear every memory for an end user through the API directly, use a wide filter
+on `DELETE /memory/forget`, for example `{"before": "<now>"}`. Not
+`/memory/user/purge`: despite its path it is not end-user scoped and erases the
+account behind the credential.
+
+## Environment variables
+
+| Variable | Purpose |
+|---|---|
+| `MEMORYSYNC_API_KEY` | Key, highest priority |
+| `MEMORYSYNC_BASE_URL` | API base URL |
+| `MEMORYSYNC_USER` | Default end user |
+| `MEMORYSYNC_PROJECT` | Default project |
+| `MEMORYSYNC_PROFILE` | Named profile |
+| `MEMORYSYNC_OUTPUT` | Default output format |
+| `MEMORYSYNC_CONFIG_DIR` | Where config and credentials live |
+| `NO_COLOR` | Disable colour |
+
+## Documentation
+
+<https://docs.memorysync.io/cli>

memorysync_cli-1.0.2.dist-info/RECORD

@@ -0,0 +1,24 @@
+memorysync_cli/__init__.py,sha256=rIo2gmWpCD0Mr4IaRQkdlfeQ8epfMDQJuV1wAu_KssY,503
+memorysync_cli/__main__.py,sha256=EUWNiTcTB3QGHWPXzOkBcHOjz8zEWWRiSgxkZEH78nM,257
+memorysync_cli/_version.py,sha256=LZTFaiDdXahAtu6Prb5WEPk4QX_pfMd7zDoNQSzcGsI,23
+memorysync_cli/args.py,sha256=vZD3HgBUHg8eDQ_uSk9ijDwoFDBAd1y72HKlqP6Oj-c,7355
+memorysync_cli/completions.py,sha256=h7vxXva-4uvk3mC2aVQpOoYtMkzB4-RiNRAGrH7s5DU,5129
+memorysync_cli/config.py,sha256=Y8uyBmtN9X5tbHNMVLjpVm6jjIcwNPbDq4T28yG-38E,4868
+memorysync_cli/credentials.py,sha256=wn_VCAS2UQfoLoeOPkmMZpzB12GG-u3cWp9J4H-yAQI,8773
+memorysync_cli/errors.py,sha256=pCwR-_LBFQvkVWn9gIGd1mR0i_vSJgUcOxcEg3YN9Hg,3812
+memorysync_cli/http.py,sha256=O0ijJp4UO7lRM2gegRnbxapYRD7ArU0AxULrnOY0S5Y,10125
+memorysync_cli/main.py,sha256=zZCR45FoKPO7UPtoQzlVS9xUhSjNQ4-pcVeHfdLdAP8,11544
+memorysync_cli/output.py,sha256=pOKlv1LqDfrkuLsl2nsTgylLvajyh-nNNqD7NCSJimQ,9751
+memorysync_cli/registry.py,sha256=DqyQlqWnPEahpd3ar4WR67xxR3Idm618P2TR13ateZA,3723
+memorysync_cli/commands/__init__.py,sha256=M0dK8dCV4ZA2oiOaygx3MTxT8D9GEAaH6hghXkKuTyA,321
+memorysync_cli/commands/admin.py,sha256=EHdgIbpKL5LWZokYp2ERLuao79FXtb02WwzGHoCbXL8,12716
+memorysync_cli/commands/init.py,sha256=_a5Cvd0NZgC8tybMQe7nx-28yB51m3WJbPLvrFDvJ_A,3993
+memorysync_cli/commands/memory.py,sha256=VuDqHhgI7qDHVIXZytWLGfZj-fwfZfR3oegEQnoiq4g,24141
+memorysync_cli/commands/source.py,sha256=RPQ3Zs5FVhbiQNzTKQXEFcnsELQVUZQB4ejoqEIU_hA,4865
+memorysync_cli/commands/tooling.py,sha256=aBCE0mqbAoIx3YMbwDSdaDDw_6aliKbGSc8Ht2aUuT8,9117
+memorysync_cli/registry.json,sha256=9zCclXXjLlJm30-pMpXkdCeZKaAX3ZaBXuhqKaYxQMo,18588
+memorysync_cli-1.0.2.dist-info/METADATA,sha256=5s1D5d9tLd6FIidJtpPFUmjoRpUWXRaxt42XpbtrPns,5833
+memorysync_cli-1.0.2.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
+memorysync_cli-1.0.2.dist-info/entry_points.txt,sha256=kcdyOYwO3rCrg1-fFBRhSZJ672zYIyAatnFPrmMMqR8,87
+memorysync_cli-1.0.2.dist-info/licenses/LICENSE,sha256=Q3_7utsuE0ra7B7SvEUYhdEEdNnYceaffKzQg10k7WE,1088
+memorysync_cli-1.0.2.dist-info/RECORD,,

memorysync_cli-1.0.2.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.32.0
+Root-Is-Purelib: true
+Tag: py3-none-any

memorysync_cli-1.0.2.dist-info/entry_points.txt

@@ -0,0 +1,3 @@
+[console_scripts]
+memorysync = memorysync_cli.main:run
+msync = memorysync_cli.main:run

memorysync_cli-1.0.2.dist-info/licenses/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 MemorySync
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.