Skip to main content
Pre-release

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"
token = 3
stop_on_entry = false

def attention():
    layernorm
    qkv_projection
    attention_mixing
    output_projection
    residual_add

def mlp():
    layernorm
    expansion
    gelu
    projection
    residual_add

submodule = "token_embedding"

layer = 0
attention()
mlp()

layer = 1
attention()
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. After layer = N, attention() and mlp() resolve to that transformer block and become authored execution stops. Set breakpoints on these calls or use Step Over to advance through them. Runtime vectors appear in debugger scopes; the source file is never rewritten.

Press Step Into (F11) on attention() or mlp() to enter its authored definition in the same file. Attention exposes LayerNorm, the combined QKV projection, the concatenated per-head attention result, output projection, and residual add. MLP exposes LayerNorm, expansion, GELU, projection, and residual add. F10 advances inside a definition; Shift+F11 returns to the next model operation. The call site remains visible as the parent stack frame.

token = 3 makes token position 3 the default for every ordinary source breakpoint. To override it for one breakpoint, use the shorter conditional expression token=4. Positions are zero-based. The debugger prefills tokens before the selected position into the KV cache, then captures that token with a one-token forward pass. Stepping beyond the last selected layer advances to the next token using the updated cache.

Watch one zero-based dimension with residual_stream[42], input[42], output[42], or delta[42]. The Residual stream (output) debugger scope exposes the current hidden representation explicitly. Run llmdbg: Plot Current Vector from the Command Palette or debug toolbar to inspect the full vector as a dimension plot, histogram, or top-activation chart. An open plot updates automatically after each debugger stop.

Attention stops expose the 768D LayerNorm output, combined 2304D QKV projection, 768D concatenated attention-head result, and 768D output projection. MLP stops expose the 768D LayerNorm output, the 3072D linear expansion before activation, the 3072D expansion after GELU, and the 768D projection. Use indexed Watches such as layernorm[42], mlp_expansion_pre_activation[42], mlp_expansion[42], and mlp_projection[42]; all available vectors also appear in the plot selector.

Expanding Top activated neurons at an MLP stop lazily ranks the five largest post-GELU activations. Each neuron shows its output-direction norm, the top five tokens from W_down[neuron] @ W_unembed, and the top five direct token contributions after scaling by the current activation. Token IDs and decoded text are both displayed. Results are cached for the current token and layer. Add top_neurons to Watch to keep this tree visible while stepping; VS Code reevaluates it at every stop and preserves the expandable neuron/token structure. At non-MLP stops it reads available at MLP stops.

The yellow execution arrow identifies the next submodule to execute. Step Over executes that submodule, moves to the next statement, and exposes the completed operation under Previous output and its detail scopes. Watch dimensions are writable through VS Code's Set Value action. For example, set output[42], mlp_expansion[1843], or top_neurons[0].activation; llmdbg records the intervention, replays the selected token from its KV-cache prefix, and refreshes all downstream values. Rank-based top_neurons[0] may identify a different neuron after mutation; use mlp_expansion[neuron_id] when targeting a fixed neuron.

License

MIT

Metadata

Release files for llmdbg 0.0.3a19

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for llmdbg 0.0.3a19
File Size Uploaded Provenance
llmdbg-0.0.3a19.tar.gz 52.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for llmdbg 0.0.3a19
File Interpreter ABI Platform
llmdbg-0.0.3a19-py3-none-any.whl Python 3 none any Details

Total release size: 76.9 kB

Release files / llmdbg-0.0.3a19.tar.gz

Download URL llmdbg-0.0.3a19.tar.gz
Size 52.0 kB
Tags Source
SHA-256 checksum
How to use checksums
f8f92cee4313d0f75d7a05d76df4e2ce8917481bdb7bd7b4451563c9757ff525
BLAKE2b-256 checksum
How to use checksums
e1ae61b5ef4ec6e9834cffdba676457dbb0dca4639beafc910098546cc5b3566
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.3a19-py3-none-any.whl

Download URL llmdbg-0.0.3a19-py3-none-any.whl
Size 25.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a8b950027651c7e5fb94377b1b42da84d8e2fdcadd4e1981d8346a8ddb14d629
BLAKE2b-256 checksum
How to use checksums
0064ebdb54f01f4b057e8d3e02780d4c33cd43d60f243a828a784fe1dd53b004
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.3a19

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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page