jupyter-ai-acp-hub
Jupyter AI ACP personas that treat ACP sessions as ephemeral runtime state.
The visible Jupyter chat history remains in .chat files, but live ACP session
IDs are not persisted into chat metadata and are not loaded after restart. This
avoids stale session/load failures in JupyterHub pods where chat files survive
but agent subprocesses do not.
Personas
@HubClaude: wrapsclaude-agent-acp@HubOpenCode: wrapsopencode acp
These personas are intentionally separate from upstream @Claude and
@OpenCode so they can be tested side by side.
Install
For a running JupyterHub notebook pod, avoid pulling Jupyter server
dependencies into ~/.local:
python -m pip install --user --no-deps jupyter-ai-acp-hub
For a local development checkout:
python -m pip install -e ".[test]"
Restart the Jupyter server process after installation so Jupyter AI reloads the entry points.
jupyter-ai-acp-hub intentionally has no required runtime dependencies. It is
meant to use the Jupyter AI ACP packages already present in the notebook image.
If you are installing into a clean environment, use:
python -m pip install "jupyter-ai-acp-hub[runtime]"
The underlying agents still need to be available in the notebook image:
claude-agent-acpfor@HubClaudeopencodefor@HubOpenCode
Behavior
- always creates a fresh ACP session for each live persona instance
- never writes
metadata.acp_session_idsinto.chat - never loads
metadata.acp_session_idsfrom.chat - returns the live session ID from the current session future
- injects recent chat history once after creating a fresh session, using the
bounded recovery context from
jupyter-ai-acp-client
Verify
python - <<'PY'
import importlib.metadata as metadata
for ep in metadata.entry_points(group="jupyter_ai.personas"):
if ep.name.startswith("hub-"):
print(ep.name, ep.value)
PY
Metadata
Release files for jupyter-ai-acp-hub 0.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 | Actions |
|---|---|---|---|---|
| jupyter_ai_acp_hub-0.1.2.tar.gz | 3.7 kB | With provenance | Details for jupyter_ai_acp_hub-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyter_ai_acp_hub-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for jupyter_ai_acp_hub-0.1.2-py3-none-any.whl |
Total release size: 8.0 kB
Release files / jupyter_ai_acp_hub-0.1.2.tar.gz
| Download URL | jupyter_ai_acp_hub-0.1.2.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
448afddf59d2732fe12460cb249b1c4267593fade290a99700e8f37bab84fba7
|
|
BLAKE2b-256 checksum How to use checksums |
bbe9eb76cf690894727aaa6c536feb9d071a707ec28b50d6bd17925bb25f5c78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 20, 2026.
Transparency logRelease files / jupyter_ai_acp_hub-0.1.2-py3-none-any.whl
| Download URL | jupyter_ai_acp_hub-0.1.2-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3ef0ceff1d07ec92491cf0acb3f903790463b7997c9e9482439d67542b5a431a
|
|
BLAKE2b-256 checksum How to use checksums |
3f7bc2f22057675cd39f3e1a09ae9c154d9563c9f8eaabddcac95fa0de649fbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 20, 2026.
Transparency logSecurity for jupyter-ai-acp-hub 0.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for jupyter_ai_acp_hub-0.1.2.tar.gz
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 May 20, 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.