Tori ships with a set of packs already in place, so a fresh install can open common projects and start the main agents without a trip to the catalog.
What ships inside Tori
| Kind | Pack | Id |
|---|---|---|
| Agent | Claude | claude |
| Agent | Codex | codex |
| Agent | Copilot | copilot |
| Agent | OpenCode | opencode |
| Agent | Pi | pi |
| Language | CSS | css |
| Language | HTML | html |
| Language | JSON | json |
| Language | TypeScript / JavaScript | typescript |
| Language | YAML | yaml |
| Linter | ESLint | eslint |
| Linter | oxlint | oxlint |
| Formatter | oxfmt | oxfmt |
| Formatter | Prettier | prettier |
| Formatter | Vite+ | vite-plus |
| Theme | Tori Dark | tori-dark |
| Theme | Tori Light | tori-light |
Bundled packs are ordinary catalog packs. Each release embeds gettori/packs at one commit, and each pack has a page in the catalog with its contributor, license and the version it was verified against.
How it updates
A pack is bundled when Tori needs it itself: the app ships the program it starts, a fresh install depends on it, or Tori’s own repository is built with it. Everything else is in the catalog, and Tori offers the one a file needs.
Bundled packs update with Tori. A release carries the bundled set as gettori/packs had it when the release was cut, and a newer file in the catalog waits for the next release.
Switching a bundled pack off
-
Open Settings (the gear in the title bar).
-
Go to the pack’s pane: LSP, Linters, Debuggers, Formatters or Agents.
-
Turn off the switch on the pack’s card. Tori stops starting it, and you can turn it back on there. Themes have no switch: pick another one in Appearance > Theme.