Denpex: GPU, CUDA & PyTorch Crash Diagnostics for VS CodeSelect a GPU error log. See the supporting evidence, likely cause, and what to check next, without leaving VS Code. Investigate CUDA out-of-memory errors, NCCL timeouts, PyTorch crashes, NVIDIA Xid faults, Slurm jobs, Kubernetes GPU failures, and vLLM inference errors. Local diagnosis is free, unlimited, and offline. No account, API key, or separate Node.js installation required.
A short, single-play demonstration of the actual Console renderer and shipped local engine on a bundled synthetic log. No LLM or live customer cluster is used. View the still image. Where the answers come fromLocal diagnosis runs the bundled deterministic engine: known failure rules, evidence checks and cross-rank correlation. It does not call an LLM. When logs cannot establish a cause, it should request more evidence rather than invent one. Optional cloud review can use deeper model reasoning on the log you explicitly approve for upload; it still cannot establish facts absent from that evidence. One account-free cloud review may be available in the editor, subject to server limits. Preview and edit the excerpts before choosing Send. Further cloud review and shared incident history can continue through an eligible connected account or company evaluation. Local diagnosis stays unlimited. Start with one useful result
For a one-off error, keep using free local diagnosis. For recurring team incidents, evaluate whether connected evidence, notifications and saved cloud investigations reduce your work. A Datacenter evaluation should use your own incident, not just a sample. What is free, and what is optional?
After the trial, local diagnosis stays free. Subscribe only if the team workflow earns its place. Quick Install
Or search Denpex in the VS Code Extensions tab ( Try a diagnosis
No log handy? Open the Denpex sidebar and run a bundled sample: an OOM followed by NCCL timeouts, GPU device loss, a network-interface mismatch, a Kubernetes device-plugin fault, or vLLM KV-cache exhaustion. The report separates an initiating failure from downstream symptoms when the log supports that distinction. If it cannot establish the cause, it asks for more evidence instead of treating a timeout as an explanation. What a diagnosis showsThe report leads with the likely cause, checkpoint safety when relevant, and recommended actions. Expand the evidence and causal chain to see how Denpex reached its conclusion. If the logs do not establish a cause, the report identifies what evidence is missing.
Captured from the current extension's Console renderer after running its bundled synthetic vLLM log through the shipped offline engine. The report shows evidence and suggested checks, not proof of workload recovery. Inspect incidents in Fleet
Search incidents, select a result and review the recorded guidance beside the queue. This capture uses the actual compiled extension workspace with synthetic example telemetry. Find the affected host on the map
The map groups reported hosts by cluster and fits the available fleet. Select a host to inspect its GPUs. Red and orange signals identify devices to investigate; they do not establish the root cause. Inspect exact device identity and evidence
The inspector connects device identity, reported measurements and the next evidence step. These Fleet and Topology captures use synthetic example records, not a live customer cluster. Connected users see their account's reported inventory and measurements. Accounts without telemetry see setup instructions. VS Code theme and panel size can change the appearance. Use it where you work
Console, Fleet and TopologyOpen Denpex: Open Console to paste a log, run a local diagnosis and ask about its recorded cause, evidence, fix or checkpoint safety. These local follow-ups do not invoke an LLM. Arbitrary questions require a separate cloud review. Choose Fleet or Topology in the console, or run Denpex: Open Fleet and Denpex: Open Topology. These editor panels use the website's shared components and read your connected account's reports and telemetry. A plan with the corresponding access is required. With no telemetry, the map shows setup instructions, not demo nodes. Stale telemetry is not presented as healthy. Account reports are read-only in the editor. Billing, API-key management, integrations and operational changes remain website actions. Opening a fleet view does not upload your local log or start LLM reasoning. Credentials stay in the extension host, not in the webview. Local diagnosis runs on the extension host, including Remote-SSH hosts and containers. The bundled engine also works without internet access. Interactive Terminal LinksRecognized GPU and ML error lines become clickable in the integrated terminal. Open a diagnosis from the error, then check its supporting evidence before making changes. Errors you can investigate
The engine recognizes patterns across PyTorch, NCCL, DeepSpeed, Slurm, Kubernetes, vLLM, TensorRT-LLM and related GPU tooling. Recognition does not certify every software/hardware combination or prove the cause from a single error line. Investigate training, inference and GPU infrastructure failuresFor GPU cloud operators, platform and infrastructure teams, SREs, ML engineers and researchers working with GPU workloads. Use the evidence available to your role: application logs, scheduler events, device identity and host diagnostics. For a distributed PyTorch failure, keep the original logs from every rank plus launcher and host events when available. An OOM or worker exit on one rank can be followed by NCCL watchdog timeouts on surviving ranks. Denpex checks covered signatures and supporting context; missing logs or uncertain device identity can leave the initiating cause unresolved.
These tools answer complementary questions. Read the first-failed-rank investigation guide, PyTorch Flight Recorder tutorial, PyTorch memory snapshot documentation and NVIDIA GPU node triage guidance. Evaluate the extension on a known incident
For inference incidents, preserve vLLM worker logs, startup settings and memory information. A generic engine-dead message does not by itself identify KV-cache exhaustion or a hardware fault. See the vLLM error reference. Optional cloud reviewStart locally. If you need another pass, choose Preview cloud review in the report. Inspect and edit the proposed excerpts, then explicitly choose Send for cloud review. One account-free review may be available, subject to server limits. Its assessment appears in the same incident, with the preceding local report still available. More evidence may be needed, and a second assessment does not prove a root cause. If you deliberately request further cloud review or shared history, Denpex can offer a company evaluation or connection to your existing account. The evaluation requires work-email verification. Your pending incident can remain in encrypted editor storage for 24 hours; resuming it never uploads automatically. Cloud review sends the selected log to Denpex. It is optional; local diagnosis stays unlimited. For regular cloud use:
Company-domain verification applies. If automatic verification fails, contact support@denpex.com for review. You can keep using the local engine while waiting. Connecting an account does not upload a log or start a diagnosis. Credentials are stored in VS Code SecretStorage. See the extension guide for setup details. PrivacyReturn to an investigationChoose Save locally in a report to keep its findings, evidence excerpts and recovery assessment history on the extension host. Saving requires explicit confirmation. These files are not encrypted, are limited to 2 MiB each and remain until deleted; keep sensitive evidence out if your policy prohibits local storage. Up to 100 reports can be saved. Use Reopen or Denpex: Reopen Saved Investigation after restarting the editor. Export report writes a Markdown handoff to a location you choose. Delete saved report removes a selected saved report after confirmation. The original input log is not separately retained, so provide it again for a fresh diagnosis or cloud review. Recovery assessments are your observations, not independent certification by Denpex. Saving or exporting preserves unsuccessful assessments as well as the latest result. Default behaviorLocal diagnosis, predictive terminal monitoring, sample failures, and RMA payload generation run entirely on the extension host. Clipboard text is read only after you choose it from the source picker. Recent-diagnosis persistence stores only a timestamp, failure type, and engine source - not logs, evidence excerpts, or the report body. Anonymous product-step counts are off by default. Denpex does not display an automatic consent prompt. Use Denpex: Manage Anonymous Step Counts if you want to enable them. They also require the editor's telemetry setting to be enabled. If enabled, Denpex sends only the extension version and a fixed step label (sample or own-log result, cloud preview, approval, cloud result, request for further cloud review, company evaluation request, or account connection). It sends no log, result, email address, file path, machine detail, or install identifier. Choose Denpex: Manage Anonymous Step Counts at any time to turn it off or on. An on-prem or custom API setup does not send these counts to Denpex. Each step is counted at most once per installation. These opt-in aggregate counts are not a count of unique people and cannot establish an individual conversion rate. In Read the full Denpex privacy policy. Settings
Support
GPU artifact inspectionUse Denpex: Inspect GPU Artifact Locally for Flight Recorder JSON rank dumps, CUDA memory snapshot JSON, Nsight SQLite, checkpoint candidates and aligned rank timings. Python 3 is required. No pickle is executed, no checkpoint is changed, and no artifact is uploaded automatically. Memory measurements stay separate by GPU. Metadata alone does not verify checkpoint recovery. Denpex: Shared Cloud History reads diagnoses saved by the website, extension, API and MCP. Local-only results stay on this machine until you explicitly choose cloud review. Your connected account and effective plan are verified by the server. |




