This release is a pre-release and may not be stable for production use.
llmdbg
llmdbg is an early-stage debugger for stepping through language-model layers
and presenting human-readable interpretations of internal vectors. It speaks
the Debug Adapter Protocol
so editor integrations can use a standard debugger UI.
The current prototype includes real GPT-2 Small loading, layer-state capture, logit-lens interpretations, and a VS Code debug extension. A deterministic built-in trace remains available when no model is configured.
pip install --pre llmdbg
llmdbg --version
VS Code prototype
Build and install the extension:
cd vscode-extension
npm install
npm run package
code --install-extension llmdbg-0.0.1.vsix
Create a gpt2.llmdbg file in the workspace:
model = "openai-community/gpt2"
revision = "main"
device = "cuda"
dtype = "bfloat16"
prompt = "The capital of France is"
stop_on_entry = false
submodule = "token_embedding"
layer = 0
submodule = "transformer.h.0.attention"
submodule = "transformer.h.0.mlp"
layer = 1
submodule = "transformer.h.1.attention"
submodule = "transformer.h.1.mlp"
Open that file and press F5. If VS Code asks for a debugger, choose
llmdbg. No launch.json is required. If a workspace launch configuration
is preferred, the complete minimal version is:
{
"version": "0.2.0",
"configurations": [
{
"type": "llmdbg",
"request": "launch",
"name": "llmdbg: Active file",
"config": "${file}"
}
]
}
On first use, the extension creates a private Python environment in VS Code's
extension storage. It does not install anything into the workspace. The first
GPT-2 run downloads and loads the model, then keeps its tensors resident in a
persistent model-host process. Stopping and restarting the debugger reuses the
resident model and runs only a new forward pass. Closing/reloading VS Code
stops the host and releases the model. Each submodule statement is an
authored model execution stop. Set breakpoints on these statements or use
Step Over to advance through them. Runtime vectors appear in debugger
scopes; the source file is never rewritten.
To stop at a specific prompt token and layer, add a conditional breakpoint to
the desired submodule statement and use a zero-based condition such as
token.position == 3. The debugger prefills tokens before that position into
the KV cache, then captures the selected token with a one-token forward pass.
Stepping beyond the last selected layer advances to the next token using the
updated cache.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for llmdbg 0.0.3a7
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 | |
|---|---|---|---|---|
| llmdbg-0.0.3a7.tar.gz | 38.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llmdbg-0.0.3a7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.8 kB
Release files / llmdbg-0.0.3a7.tar.gz
| Download URL | llmdbg-0.0.3a7.tar.gz |
|---|---|
| Size | 38.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b073e8ada228933ac2f4b3acc3eb48de5e25fbff0cbfa373be79b23a70e469c7
|
|
BLAKE2b-256 checksum How to use checksums |
d5642ab7f4f01791dd7d84b679bd7d370c90835ef957a7947e4f98190c778012
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / llmdbg-0.0.3a7-py3-none-any.whl
| Download URL | llmdbg-0.0.3a7-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eb075eaa3c5f541c3826346c99b7b39992d52d8b4fc9a62454c4cf388e574b46
|
|
BLAKE2b-256 checksum How to use checksums |
54b9aebe907aa165c29c4602fec05d777d67738911088b0f3aae5e15026797b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for llmdbg 0.0.3a7
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
