Skip to main content

vivary-memory-cognee

Optional Cognee adapter for Vivary semantic memory.

This package keeps Vivary graph-first:

  • tropo analyzes the workspace and owns typed graph truth.
  • vivary-cognee index sends only privacy-filtered typed node packets to Cognee.
  • vivary-cognee recall accepts only hits that map back to known Vivary node ids.
  • provider state under .vivary/memory/cognee/ is rebuildable cache.
  • Cognee runtime directories are scoped to the workspace state_path.

Source candidate 0.1.2 depends directly on vivary-core>=0.2.7 and vivary-tropo>=0.5.2. It uses Vivary Core's fail-closed content-privacy policy when Git-ignore privacy is enabled. The currently published 0.1.0 package relies on memory.privacy.private_paths for .strato/private/**; generated Vivary configuration already includes it, while hand-written or older configuration must add it explicitly before indexing. Source: pyproject.toml; published-version reference: PyPI; verified: 2026-08-09.

Install this package only when a workspace explicitly opts into Cognee:

pip install vivary-memory-cognee

Useful commands:

vivary-cognee doctor --root . --json
vivary-cognee index --root . --dry-run --json
vivary-cognee index --root . --yes --json
vivary-cognee recall "where is auth handled" --root . --json
vivary-cognee forget --root . --yes --json

Indexing and forgetting require --yes because they write provider memory. Provider runtime calls also require memory.cognee.allow_network = true; the generated default is false, so dry-runs and doctor checks are safe until a human explicitly enables the Cognee/embedding provider path. If memory.cognee.api_key_env is set, that environment variable must be present before provider writes or recalls run. Local providers that intentionally need no API key must set memory.cognee.allow_without_api_key = true. Cognee telemetry is disabled by default unless memory.cognee.allow_telemetry = true is set explicitly; inherited tracing environment variables are forced off by the default policy. doctor checks package presence without importing Cognee runtime; runtime commands bind Cognee's state/cache/log roots to the workspace before import. Recall requires a current manifest fingerprint. Approved index replaces the previous workspace-bound dataset first, and forget --yes requests dataset deletion instead of a memory-only reset. Dataset names include a workspace path hash even when a label is configured, so one workspace cannot accidentally target another workspace's dataset.

The adapter never imports Cognee from core Vivary packages.

Metadata

Release files for vivary-memory-cognee 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vivary-memory-cognee 0.1.2
File Size Uploaded Provenance
vivary_memory_cognee-0.1.2.tar.gz 21.3 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for vivary-memory-cognee 0.1.2
File Interpreter ABI Platform
vivary_memory_cognee-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 34.2 kB

Release files / vivary_memory_cognee-0.1.2.tar.gz

Download URL vivary_memory_cognee-0.1.2.tar.gz
Size 21.3 kB
Tags Source
SHA-256 checksum
How to use checksums
9ad0c2e181cce37214d423efd911a61154963219557e53b7e4a797c2ff771159
BLAKE2b-256 checksum
How to use checksums
bd50ba572bffef151dec32103fafe8d0e33cea8aff74c862739cef87ddcea021
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / vivary_memory_cognee-0.1.2-py3-none-any.whl

Download URL vivary_memory_cognee-0.1.2-py3-none-any.whl
Size 13.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6ac77e57a7ea89add2599c377b8d9fdeababebaf9dadb85bfb8041187992c2f8
BLAKE2b-256 checksum
How to use checksums
eec4abfa953faa4e21cababc77ad4ef8ee32bef466bda83739c3634774aa2ca5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for vivary-memory-cognee 0.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page