br8n
Context-capture and resume engine — captures developer intent on interruption and replays it as a resume card, so picking work back up costs seconds instead of minutes.
This package is the br8n backend: the FastAPI service, the MCP server that Claude Code talks to, and the local/cloud storage tiers behind them.
Most people should install br8n as a Claude Code plugin rather than by hand — the plugin bootstraps this package for you:
/plugin marketplace add anthonysuherli/br8n
/plugin install br8n@br8n
Direct install
pip install br8n
Two entry points are installed:
br8n-mcp— the MCP server (stdio), for wiring into an MCP client by hand.br8n-server— the local HTTP API. Binds127.0.0.1:8002; on the local tier it refuses any non-loopback host, because that tier runs without API auth.
Check the install with:
python -m br8n.api.main --check
Tiers
br8n ships one engine with two storage backends, selected by BR8N_BACKEND:
- local (default when no Supabase credentials are present) — SQLite +
sqlite-vecat~/.br8n/brain.db, single user, loopback only, no auth. - cloud — Supabase (pgvector + GoTrue), multi-user, per-request JWT tenancy.
Capture and resume work with no API keys at all. Semantic search needs an
embedding key (AI_GATEWAY_API_KEY or OPENAI_API_KEY); the explore/gap-fill
pipeline additionally needs TAVILY_API_KEY. See .env.example in the repository
for the full matrix.
Source, issues, and documentation: https://github.com/anthonysuherli/br8n
MIT licensed.
1 maintainer
Metadata
1 maintainer
Release files for br8n 1.1.2
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 | |
|---|---|---|---|---|
| br8n-1.1.2.tar.gz | 162.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| br8n-1.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 315.3 kB
Release files / br8n-1.1.2.tar.gz
| Download URL | br8n-1.1.2.tar.gz |
|---|---|
| Size | 162.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b5f837ec8b7f79e1e202dd4aff004470c884237c59f846375f0d92434f6262e
|
|
BLAKE2b-256 checksum How to use checksums |
d3d93a990c0324551d3b94f63dc25467b660ab6bf93be81c81ada2aea8203af8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / br8n-1.1.2-py3-none-any.whl
| Download URL | br8n-1.1.2-py3-none-any.whl |
|---|---|
| Size | 152.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fe931625e2e76ca91e1e3789b436463da26948efb780e0847bca8abc18ef27ce
|
|
BLAKE2b-256 checksum How to use checksums |
e91ad8f2cc55abfac000e21cb812f1ce65bf8f97aefe456ae9bacfa593750181
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for br8n 1.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.
