Brevi: fast, safe native builds of AI-written Python
Brevi is a compiler built for AI coding agents. The agent writes the plain Python it already writes best; Brevi builds it through Rust into a native binary that prints exactly what CPython prints and runs 1.7x to 40x faster with the default build. Anything it cannot build comes back as one short JSON line the agent can act on.
pip install brevi # or run it without installing: uvx brevi mcp
$ printf 'print(sum(i * i for i in range(10)))\n' > main.py
$ brevi run main.py # build natively (cached), then run
285
$ brevi check main.py # build without running: errors only
$ brevi build main.py -o app --release # an optimised binary to keep or ship
$ brevi mcp # MCP server for agents: check, run, test, patch, edit, show, guide
A sure mistake is reported before anything runs, as one line with a fix:
{"line":8,"msg":"name 'totl' is not defined","fix":"did you mean total?"}
Brevi compiles through rustc, so a Rust toolchain must be on the PATH (rustup.rs).
- For agents: add the MCP server as the command
breviwith the argumentmcp(Claude Code:claude mcp add brevi -- brevi mcp). Its tools sandbox by default. For AI agents - Same answers as CPython: every saved agent program and large test program matches CPython's output and exit status. Imports of installed packages (numpy, pandas, requests, ...) work; most numpy code builds natively.
- Public preview: Brevi works today and is tested against CPython on every change, but expect the CLI to change between releases.
Docs · Source · Changelog · Issues · Apache-2.0
mcp-name: io.github.ets-public/brevi
1 maintainer
Metadata
1 maintainer
Release files for brevi 0.25.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| brevi-0.25.0-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for brevi-0.25.0-py3-none-win_amd64.whl |
| brevi-0.25.0-py3-none-manylinux_2_34_x86_64.whl | Python 3 | none | Linux glibc 2.34+ x86-64 | Details for brevi-0.25.0-py3-none-manylinux_2_34_x86_64.whl |
| brevi-0.25.0-py3-none-manylinux_2_34_aarch64.whl | Python 3 | none | Linux glibc 2.34+ ARM64 | Details for brevi-0.25.0-py3-none-manylinux_2_34_aarch64.whl |
| brevi-0.25.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for brevi-0.25.0-py3-none-macosx_11_0_arm64.whl |
| brevi-0.25.0-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details for brevi-0.25.0-py3-none-macosx_10_12_x86_64.whl |
Total release size: 13.0 MB
Release files / brevi-0.25.0-py3-none-win_amd64.whl
| Download URL | brevi-0.25.0-py3-none-win_amd64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e7262aec5d8f2d4cac31fd7eab8581d1fc4b16c8a92c2f11df6f3ee3b8a3d840
|
|
BLAKE2b-256 checksum How to use checksums |
60d8815b255313e4bc7cf1211782df09a61622d5234df01d4098c628cff6dfcf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / brevi-0.25.0-py3-none-manylinux_2_34_x86_64.whl
| Download URL | brevi-0.25.0-py3-none-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Linux glibc 2.34+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
577593c00e3fb353a95bea47d22289c0c4db53eeb5540ac05ede1b3f3c0f23a4
|
|
BLAKE2b-256 checksum How to use checksums |
2224cf148c9825e8c75566728153973ec2a8e3edb12d4865547e22d5067961aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / brevi-0.25.0-py3-none-manylinux_2_34_aarch64.whl
| Download URL | brevi-0.25.0-py3-none-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | Linux glibc 2.34+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
1ce9f8c9d343493d49ac794c6abc0609b2297eaa2011619e8f64ea34bfd66f7b
|
|
BLAKE2b-256 checksum How to use checksums |
e897f41a15ed7c028634d16f273ebf0fc034dfcf0d283a51cb31e50be5aea9b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / brevi-0.25.0-py3-none-macosx_11_0_arm64.whl
| Download URL | brevi-0.25.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
395db1809d70dbce93051c5009741048433a8b86eb4674290c7d8262fae2fa1b
|
|
BLAKE2b-256 checksum How to use checksums |
925c4ce2b47497efc4590a41d4a7272db5469cb89a7ce5a07dcd070e1daed78a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / brevi-0.25.0-py3-none-macosx_10_12_x86_64.whl
| Download URL | brevi-0.25.0-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
584c3f17bfb4ee901a72dfabf68bceb9676df445114546fa410ad2c4bb560e3a
|
|
BLAKE2b-256 checksum How to use checksums |
5e70f26f05387051b397f1e49f7e56d6d19a7440152a15159ca9cfc265510b3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logSecurity for brevi 0.25.0
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.
Full provenance
All 5 files in this release have been uploaded with provenance metadata.
Attestation for brevi-0.25.0-py3-none-win_amd64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logA 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.
