CogniRelay
CogniRelay is a self-hosted continuity and collaboration substrate for autonomous agents with bounded, recoverable memory and explicit restart orientation. It provides a local FastAPI and MCP-facing service for agent orientation, retrieval, coordination, and recovery across context resets.
Install
python3 -m venv .venv
source .venv/bin/activate
python -I -m pip --isolated --disable-pip-version-check install --no-index --no-deps --no-cache-dir --upgrade \
"pip @ https://files.pythonhosted.org/packages/3f/06/3e4420302363fbb71be3c7f35ce042f54bfca330e3e66b3a2e3c4cca579f/pip-26.2.2-py3-none-any.whl#sha256=fd7f4dfa8190e014013b9f08f3e973f4e4c26ffd179a204895533a7254813a70"
python -m pip install cognirelay
Update host CA certificates first. The pinned wheel authenticates the first download even when the venv's initial pip has an older CA bundle. This changes only the venv, including on Ubuntu-managed Python. For existing environments, run the pinned bootstrap with that environment's Python before upgrading CogniRelay. See the TLS audit and recovery guide.
Run
Set COGNIRELAY_REPO_ROOT to a durable writable repository root before starting the service. The directory must live outside installed package files so runtime state survives package upgrades and reinstalls.
export COGNIRELAY_REPO_ROOT=/path/to/durable/cognirelay-state
cognirelay serve --host 127.0.0.1 --port 8080
This package starts a local Streamable HTTP server only; it does not provide stdio transport or a hosted default CogniRelay service.
Agent assets
PyPI installs include the last-mile agent assets needed to integrate CogniRelay continuity hooks and the continuity-authoring skill. To inspect the installed assets:
cognirelay assets path
cognirelay assets list
To materialize them into a workspace, run:
cognirelay assets copy --to /path/to/workspace
The copy command writes /path/to/workspace/agent-assets. The full last-mile guide remains in the project documentation on GitHub Pages.
Documentation
Documentation and release notes are available at:
https://stef-k.github.io/CogniRelay/
Project source is available at:
Metadata
Release files for cognirelay 1.4.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cognirelay-1.4.15.tar.gz | 884.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cognirelay-1.4.15-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / cognirelay-1.4.15.tar.gz
| Download URL | cognirelay-1.4.15.tar.gz |
|---|---|
| Size | 884.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b81a43a385b08d6508419c42e6b87782dab572af2dec5c17d0c60e03d2bf85fd
|
|
BLAKE2b-256 checksum How to use checksums |
05a3507887f76233cc91196db392e1de2225f7f817e68bebd85f3b9f41a8bdd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / cognirelay-1.4.15-py3-none-any.whl
| Download URL | cognirelay-1.4.15-py3-none-any.whl |
|---|---|
| Size | 420.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a8e49485e3487698b03a75b21baf6708ac4c571799e3413ae2c02cf2570da56
|
|
BLAKE2b-256 checksum How to use checksums |
b405090796290edf197a7b6bf37429a7177850b7b52195f076143bddbda57a49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for cognirelay 1.4.15
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.