runt jupyter commands manage standalone Jupyter kernels (launched outside of the notebook app).
These commands are for standalone kernels started with
runt jupyter start. Kernels managed by the daemon (from notebook app) are listed with runt notebooks instead.Subcommands
| Command | Description |
|---|---|
ps | List running kernels |
start | Start a new kernel |
stop | Stop a kernel by ID |
interrupt | Send interrupt signal to a kernel |
exec | Execute code in a running kernel |
console | Launch interactive console (see Console) |
clean | Remove stale connection files |
sidecar | Launch sidecar viewer for a kernel |
runt jupyter ps
List all running kernels (both standalone and daemon-managed).Options
Output in JSON format
Show port numbers and connection file paths
Example Output
- SOURCE:
runtimed= daemon-managed,jupyter= standalone kernel - NOTEBOOK: Only shown for daemon-managed kernels
Verbose Output
runt jupyter start
Start a standalone kernel.Arguments
Kernel name to launch (e.g.,
python3, julia, deno).Must be a valid kernelspec installed on the system. List available kernelspecs with jupyter kernelspec list.Example
runt jupyter exec— Execute code- External Jupyter clients (connect via the connection file)
runt jupyter sidecar— View outputs
runt jupyter stop
Stop a running kernel.Arguments
Kernel ID to stop (from
runt jupyter ps).Required unless --all is used.Options
Stop all running standalone kernels.
Examples
runt jupyter interrupt
Send an interrupt signal to a running kernel (equivalent to Ctrl+C).Arguments
Kernel ID to interrupt.
Example
runt jupyter exec
Execute code in a running kernel.Arguments
Kernel ID to execute code in.
Code to execute. If omitted, reads from stdin.
Examples
Execute inline code
Execute from stdin
Execute from file
Output Handling
- stdout: Printed to terminal
- stderr: Printed to terminal (in red if supported)
- Return values: Displayed as plain text
- Errors: Full traceback shown
Exit Codes
0: Code executed successfully1: Execution error (exception raised)
runt jupyter clean
Remove stale kernel connection files.Options
Timeout in seconds for heartbeat check when determining if a kernel is alive.
Show what would be removed without actually deleting files.
Example
Dry Run
runt jupyter sidecar
Launch the sidecar output viewer for a running kernel.Arguments
Path to a kernel connection file (e.g.,
~/.local/share/jupyter/runtime/kernel-12345.json)Options
Suppress output messages
Dump all Jupyter messages to a JSON file for debugging
Example
The sidecar is primarily for debugging. For interactive notebook work, use the nteract Desktop app instead.
Connection Files
Standalone kernels create connection files at:- ZeroMQ port numbers (shell, iopub, stdin, control, heartbeat)
- IP address and transport protocol
- HMAC signature key
Advanced: Custom Kernel Commands
For kernels without a kernelspec, userunt console --cmd instead:
Troubleshooting
Kernelspec not found
Kernelspec not found
Error:
Kernelspec 'python3' not foundSolution:- List installed kernelspecs:
jupyter kernelspec list - Install the missing kernel:
Can't connect to kernel
Can't connect to kernel
Error: Connection timeout or “kernel not found”Solution:
- Verify kernel is running:
runt jupyter ps - Check the kernel ID matches exactly
- Look for errors in kernel output (kernels log to terminal by default)
Stale connection files
Stale connection files
Symptoms:
runt jupyter ps shows dead kernels, or connection files left after crashesSolution:Related Commands
runt console— Interactive REPL (easier than start + exec)runt notebooks— List daemon-managed kernelsrunt shutdown— Shutdown a notebook’s kernel