Beaker: the AI-first coding notebook
Beaker is a next-generation coding notebook built for the AI era. Beaker seamlessly integrates a Jupyter-like experience with an AI agent that can generate and run code on your behalf. The agent has access to the entire notebook environment as its context, allowing it to make smart decisions about the code it generates and runs. It can even read tracebacks and fix its own errors, and install missing libraries automatically when it needs them.
Beaker also lets you swap effortlessly between a notebook-style coding interface and a chat-style interface, giving you the best of both worlds. Since everything is interoperable with Jupyter, you can always export your notebook and use it in any other Jupyter-compatible environment.
Beaker is built on top of Archytas, our framework for building AI agents that can interact with code. Advanced users can build their own custom agents with custom ReAct toolsets to support any number of use cases.
We like to think of Beaker as a (much better!) drop-in replacement for workflows where you'd normally rely on Jupyter notebooks, and we hope you'll give it a try and let us know what you think.
Getting Started
Getting Beaker up and running is easy. Install Beaker with:
pip install beaker-notebook
Next, run beaker config update to set up your configuration. This creates a beaker.conf configuration file (you can find its location at any time with beaker config find). You can leave most fields at their defaults, but you'll need to set LLM_SERVICE_TOKEN to your OpenAI API key — or the API key for whichever LLM provider you've selected.
Once installed and configured, start a notebook with:
beaker notebook
Your notebook server will start up and Beaker will be ready to use at localhost:8888.
Quick demo
Here is a quick demo of using Beaker to interact with a free weather API, fetch some data, perform some data transformations and a bit of analysis. This is really just scratching the surface of what you can do with Beaker, but it gives you a sense of the kinds of things it can do.
Want to know more?
There is a lot more to Beaker than what we've covered here. The full documentation covers how to customize and extend Beaker — building your own custom contexts, agents, subkernels, and integrations to make Beaker fit your specific needs. It also covers using the beaker-ts TypeScript library to embed Beaker into your own front-end application.
Metadata
Release files for beaker-notebook 2.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 | |
|---|---|---|---|
| beaker_notebook-2.1.2.tar.gz | 3.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beaker_notebook-2.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 MB
Release files / beaker_notebook-2.1.2.tar.gz
| Download URL | beaker_notebook-2.1.2.tar.gz |
|---|---|
| Size | 3.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3463c6b82870c1ccea7eed7b3d7e4e613e76a91d11984647ec5c36709b188173
|
|
BLAKE2b-256 checksum How to use checksums |
b29eb850fcc7319b9fce70f82b2deb3112f81e8eaeda7ec2468eb8abe8875578
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 15, 2026.
Transparency logRelease files / beaker_notebook-2.1.2-py3-none-any.whl
| Download URL | beaker_notebook-2.1.2-py3-none-any.whl |
|---|---|
| Size | 3.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb6783f5929100b6488ab5438e8ee95822a4dcb801df9a1b5a0e9c7c535f0635
|
|
BLAKE2b-256 checksum How to use checksums |
9ab2a36b688f9937a14a961533f6b52af91d5f7bab2a7f4723fa044aaaf49546
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 15, 2026.
Transparency log