Skip to content
Get started

Helm 0.1.0 · beta

A Command Deck for your TDT workspace

Helm runs on your machine and shows your workspace in one place. You get widgets you arrange, a graph of your brain, a knowledge editor, agent sessions and a terminal. It works alongside Claude Code and Codex.

npm install -g @usetdt/helm
Read the docs

Dashboard

Arrange the deck

Pick widgets from the library and drag them where you want them. Resize them on the six-column grid. Each widget reads live data from your workspace.

  • 15 built-in widgets
  • Settings for each widget
  • One layout per workspace

Brain graph

See what your workspace knows

Your notes, knowledge and projects appear as a graph, linked the way the brain links them. Search by title or note text, then open a node to read the record.

  • Live from tdt_brain_graph
  • Search that covers note text
  • Opens records in place

Knowledge editor

Read and edit records

Open a note, a knowledge record, a candidate or a project in a tab. Edits and reviews go to Claude Code or Codex, which use TDT’s preview and confirm steps. Nothing reaches your brain without your approval.

  • Read and Edit tabs
  • Candidate reviews
  • Changes go through TDT’s own checks

Sessions and terminal

Hand work to your agent

Type a request in the chat bar and choose Claude Code or Codex. The session opens beside the deck, and you can follow it, reply when it waits, or reopen it later. A terminal in the workspace folder is one tab away.

  • Claude Code and Codex
  • Sessions kept in ~/.helm/sessions
  • Terminal kept inside the workspace

Themes

Five themes

Holographic HUD, Aurora Glass, Neon Cyberpunk, Monolith and Satin Slate. Widgets and plugins draw with the same tokens, so everything changes together.

  • Theme tokens for plugins
  • WCAG AA contrast in every theme

Plugins

Software projects, on the deck

The software-production plugin adds a Kanban board, a Ready tasks list and a task pipeline. It reads your project tasks from their files, Linear or GitHub. Move a card into Doing and Helm offers to start the build with your agent.

Plugin requiredInstall it with helm plugin add helm-plugin-software-production

Build your own

Widgets and tools are npm packages. The SDK scaffolds one, checks it against the contracts and runs it in a sandboxed frame. You can also ask your agent to build one with the tdt-helm stack.

npx @usetdt/helm-sdk create widget my-widget
Plugin contracts

Local and private

Helm is a local server. Your workspace stays on your machine.

Only on your machine
The server listens on 127.0.0.1 only, and every request needs the token from your private URL.
No model inside
Helm never runs a model. It reads through tdt mcp serve and passes work to the agent you choose.
Confirmed writes
A plugin can only use the connections it declared. Writes ask you first, and TDT keeps its own approval steps.
Locked-down pages
Host and Origin checks and a strict Content Security Policy. Plugins run in sandboxed frames.

Get started

Helm is in beta. List your workspaces in ~/.helm/config.json, and the docs explain the rest.

  1. 1Install the requirements. Node 24 or later, TDT with the MCP extra, and Claude Code or Codex on your PATH.

    pipx install 'thisdamnthing[mcp]'

  2. 2Install Helm. From npm. On Linux, add --allow-scripts=node-pty so the workspace terminal can build.

    npm install -g @usetdt/helm

  3. 3Start it. Helm prints a private URL. Open it in your browser.

    helm