Codebind
Codebind is an IPython extension that runs a model with one tool: an IPython cell executed in the active session. IPython owns execution, namespace, history, magics, tracebacks, and rich display; Codebind owns only conversation and model orchestration.
Installation
Run Codebind without installing it permanently:
uvx codebind
Or install it with any Python package installer:
pip install codebind
After installation, start ordinary IPython with the Codebind extension from any directory:
codebind
It opens standard IPython with chat and Models in the user namespace. All normal IPython command-line options remain available.
models = Models({"openai": "OPENAI_API_KEY"})
chat.send(
"Inspect this project and tell me what to implement first.",
models.chat("openai/gpt-5", reasoning_effort="medium"),
)
Codebind does not load files or construct a project prompt automatically. The user states what should be loaded as context. Pass instructions= to Session only when an application needs its own system instructions.
Jupyter
Start JupyterLab with Codebind from any directory without a permanent installation:
uvx --from jupyterlab --with codebind jupyter lab
Or install both packages into the same environment, then start JupyterLab normally:
pip install codebind jupyterlab
jupyter lab
Load Codebind in a notebook:
%load_ext codebind
Run that cell once so JupyterLab can connect to the extension, then use Codebind in later cells:
models = Models({"openai": "OPENAI_API_KEY"})
model = models.chat("openai/gpt-5")
await chat.asend("Inspect the current notebook state.", model)
The Codebind package includes a prebuilt JupyterLab extension. In JupyterLab, each model-authored IPython execution becomes a genuine code cell with its native execution count and outputs, and the assistant response becomes a rendered Markdown cell. The cells are ordinary notebook content and are saved with the notebook.
Other IPython frontends use the standard MIME display protocol instead. They still receive syntax-highlighted code, assistant Markdown, stdout, tracebacks, rich results, and native IPython history without Codebind depending on their UI.
ChatGPT account login
Models Provider can start its OpenAI browser sign-in flow directly from IPython:
import webbrowser
models = Models()
authorization = await models.sign_in("openai")
webbrowser.open(authorization.url)
await authorization.complete()
chat.send(
"Inspect this project.",
models.chat("openai/gpt-5", authorization=authorization),
)
The authorization remains in memory for this session. Persistent credential storage belongs to the host application.
OpenAI officially supports ChatGPT subscription sign-in for Codex clients. Models Provider reproduces that account-access boundary for this library; it is separate from the public, pay-as-you-go OpenAI API and may require compatibility updates when the Codex account protocol changes.
1 maintainer
Release files for codebind 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| codebind-0.4.0.tar.gz | 56.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codebind-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 76.5 kB
Release files / codebind-0.4.0.tar.gz
| Download URL | codebind-0.4.0.tar.gz |
|---|---|
| Size | 56.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
39483a26c1ab25178e930b0405844f63037cce037857ca11be9a1dfe8a4e0f7d
|
|
BLAKE2b-256 checksum How to use checksums |
61c0ee988f77bc63486a685563d05ddbfbd1cfb6a59d963052c109bc32b1b1d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
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 Sep 19, 2026.
Transparency logRelease files / codebind-0.4.0-py3-none-any.whl
| Download URL | codebind-0.4.0-py3-none-any.whl |
|---|---|
| Size | 20.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd70427249a1c14c4685e1a3fa017bae49c30126ddd2ef82d258f7c085bfb40a
|
|
BLAKE2b-256 checksum How to use checksums |
a5ce15c1564fad13b789f1e66cf93caa4a6b9a064c2c93ebf9a978e3a0b1cec6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
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 Sep 19, 2026.
Transparency log
