Open in tt-awesome →

tt-vscode-toolkit

official
TypeScript · Apache-2.0 · 10⭐ · Dec 18, 2025
tt-vscode-toolkit preview

48 interactive lessons covering the full Tenstorrent developer path — from hardware detection to custom training — with click-to-run commands and hardware auto-detection. Available in VSCode and code-server.

LATEST v0.1.31 2026-09-09T22:09:46Z Release notes ↗
4 previous releases
v0.1.27 2026-08-19T17:24:38Z
v0.1.19 2026-07-16T21:17:06Z
v0.1.17 2026-07-13T15:57:03Z
v0.0.518 2026-06-30T17:57:43Z
See all releases on GitHub ↗
# Changelog

All notable changes to the TT-VSCode-Toolkit will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

---

## [0.1.29] - 2026-09-07

Correctness pass on what a TT-QuietBox 2 actually ships. The three-path venv
activation blocks added in 0.1.25 offered `~/.tenstorrent-venv` as the "QB2
pre-installed" environment for TT-NN and vLLM, and described a QB2 as "4
independent single-chip devices". Neither claim is true, and this release
corrects both everywhere they were found — including in this repo's own
`CLAUDE.md`, `llms.txt`, and two lessons outside the original diff
(`content/pages/FAQ.md`, `monkeypatch-ttnn.md`) that had never been touched
by the earlier topology/venv corrections this built on.

Verified against `tt-installer`'s `install.m4`, the published `tt-metalium`/
`tt-metalium-models` GHCR image configs, `tt-inference-server`'s `run.py`,
and tt-metal `main` — plus live end-to-end testing on a QB2-equivalent
board — rather than other Tenstorrent docs, which largely descend from the
same stale source note this release supersedes.

### Fixed

**`~/.tenstorrent-venv` is not a TT-NN or vLLM environment.** `tt-installer`
only ever installs `tt-smi`, `tt-flash` and (opt-in) `tt-topology` into it, so
`import ttnn` and `import vllm` both fail there. TT-NN lives **only** inside
the TT-Metalium container (`tt-metalium`, where `python3` is
`/opt/venv/bin/python3`); vLLM runs in a container `tt-inference-server`
launches. Corrected everywhere this was asserted or assumed:
- The "QB2 pre-installed image" activation line in all 11 TT-NN blocks across
  `explore-metalium`, `video-generation-ttmetal`, `animatediff-video-generation`,
  `cookbook-game-of-life`, `cookbook-mandelbrot`, `cookbook-particle-life`,
  `cookbook-image-filters`, `cookbook-audio-processor`, and the four lessons
  that used it as a premise (`lfs-00-intro`, `lfs-05-train-and-run`,
  `ct1-understanding-training`, `ct4-finetuning-basics` — their `ttml`-needs-a-
  source-tree conclusions were already correct; only the premise changed).
- `tt-installer`'s own "may not include the container wrapper" framing —
  backwards: a QB2 *has* the wrapper (it's the only way to reach TT-NN) and
  has no host-side TT-NN. Its "Test TT-Metalium" button and pytest demo
  example were also broken independent of this: missing `-c` (so `bash` tried
  to run the whole command string as a filename), a bare `ttnn.__version__`
  that doesn't exist on the built package (now `getattr(ttnn, "__version__",
  "import OK")`), and — for the demo — the wrong container and a Blackhole
  demo path that moved in tt-metal's January 2026 reorg (now
  `tt-metalium-models` + `models/demos/vision/segmentation/ufld_v2/blackhole`,
  with `--install-metalium-models-container` named as off-by-default).
- `vllm-production`'s new "On a QB2 — read this first" section (pointing a
vscode lessons interactive getting-started code-server
wormhole blackhole quietbox ttsim