Metadata-Version: 2.4
Name: vivary-memory-cognee
Version: 0.1.2
Summary: Optional Cognee adapter for Vivary typed memory recall.
Author: Jeff Kazzee
License-Expression: MIT
Project-URL: Homepage, https://vivary.vercel.app/
Project-URL: Documentation, https://vivary.vercel.app/
Project-URL: Repository, https://github.com/vivary-dev/vivary
Project-URL: Issues, https://github.com/vivary-dev/vivary/issues
Project-URL: Changelog, https://github.com/vivary-dev/vivary/blob/dev/CHANGELOG.md
Keywords: agents,memory,knowledge-graph,cognee,vivary
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Requires-Python: >=3.11
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: vivary-core>=0.2.7
Requires-Dist: vivary-tropo>=0.5.2
Requires-Dist: cognee>=1.2.2
Dynamic: license-file

# 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`](pyproject.toml); published-version reference:
[PyPI](https://pypi.org/project/vivary-memory-cognee/); verified: 2026-08-09.

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

```bash
pip install vivary-memory-cognee
```

Useful commands:

```bash
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.
