hypernote 0.1.1

Thin control plane for Jupyter notebook execution with jobs, attribution, and runtime lifecycle

Hypernote

• Notebook-first - Hypernote is a thin execution control plane on top of Jupyter shared documents.
• One notebook truth - notebook edits, execution, and late-open JupyterLab views all operate on the same logical document.
• Agent-first surface - the Python SDK is primary, and the CLI is a thin shell over it.
• Ephemeral control plane - Jupyter owns durable .ipynb contents and outputs; Hypernote owns in-memory runtimes, jobs, and attribution.

What it ships

• notebook-first SDK in hypernote/sdk.py
• agent-first CLI in hypernote/cli/main.py
• Jupyter server extension for execution and runtime control
• notebook-scoped runtime lifecycle with attach, detach, recovery, and stop
• job polling and input() round-trips for headless execution
• live-server and browser regression coverage for shared-document behavior

Quick start

uv sync --all-extras
uv run hypernote --help
uv run hypernote create tmp/demo.ipynb
uv run hypernote ix tmp/demo.ipynb -s 'value = 20 + 22\nprint(value)'
uv run hypernote status tmp/demo.ipynb --full

Mental model

Jupyter owns:

• notebook persistence
• shared YDoc document state
• kernel and session primitives
• notebook rendering in JupyterLab

Hypernote owns:

• runtime lifecycle around a notebook
• job coordination and stdin round-trips
• actor attribution
• SDK, CLI, and thin REST handlers

Documentation

• Getting Started
• CLI Reference
• SDK Reference
• Runtime Model

Verification

uv run ruff check hypernote tests
uv run python -m pytest -q