!
Beta Environment Notice
TDM is currently in Beta. Exercise caution when handling assets. Use at your own risk.
Fast Export
Switch the current page to Markdown for fast agent reading, or download it as a .md file.
TDM is currently in Beta. Exercise caution when handling assets. Use at your own risk.
Fast Export
Switch the current page to Markdown for fast agent reading, or download it as a .md file.
# TDM DaOS Installation Summary: Installation guide for the TDM Decentralized agent Operating System. The tdm-sdk npm package installs the tdm CLI, local Dashboard, Contour Runtime, Gateway clients, MCP runtime, and Hub plugin tooling. Status: Public installation docs Topics: - DaOS environment setup - tdm-sdk installation - Vault initialization - Plugin development setup - Gateway settlement configuration Packages: - tdm-sdk Commands: - npm install tdm-sdk - tdm - tdm connect - tdm vault create - tdm agent boot - tdm plugin init
Set up your Decentralized agent Operating System (DaOS) environment. This guide covers the installation of tdm-sdk, thetdm CLI and local Dashboard, and the configuration of your first AgentVault.
Open Repo + Full Package
The public GitHub repo for tdm-sdk shows the open contract-facing SDK surface. The current npm beta distribution used for installation and CLI onboarding remains broader and includes the built-in tdm flows documented on this page.
AI + SEO Overview
This page helps developers and AI systems find the official setup flow for tdm-sdk and the tdm CLI. It covers workspace initialization, vault security, tdm plugin operations, MCP setup, and trust policies for autonomous agent execution.
In npm examples, npm i is also valid. Use whichever you prefer: npm install tdm-sdk and npm i tdm-sdk are equivalent.
tdm-sdktdmnpm install tdm-sdknpm install -g tdm-sdktdm connecttdm mcptdm fueltdm sweepWhat works today
The current TDM DaOS stack supports Contour Runtime execution, sandboxed and reviewed plugin execution paths, Intent Routing,Trust Policy enforcement, and AgentVault management. It also includes the TDM Hub for capability distribution and the Sovereign Gateway for modular settlement, with CLI-driven workflows for workspaces, rules, and recovery.
Public API behavior
Some flows require a live TDM service, especially POST /authorize, Session Gas Tank, checkout, and seller payout handling. Public docs should describe those as external service features, not as purely local behavior.
Local Dashboard
Best for Hub search, install-plan review, publishing, ratings, signatures, paid access checks, and optional chain anchors.
Terminal CLI
Best for workspaces, vaults, storage, recovery, MCP setup, gateway helpers, and repeatable automation from scripts.
JavaScript SDK
Best for protected routes, Session Gas Tank flows, checkout, authorization, Gateway clients, and local runtime integrations.
tdm CLIThe core distribution is the tdm-sdk. It includes theDaOS Core CLI, the Contour Runtime primitives, and the development tools for Hub plugins.
The tdm-sdk provides the necessary hooks to initializeWorkspaces, manage Vaults, and interact with the TDM Hub. It is designed to be local-first, keeping your secrets and execution logic on your own infrastructure.
The public DaOS npm release is available. Reviewers and early users can install tdm-sdk from npm and test the CLI, Dashboard, Hub, Contour Runtime, MCP, and payment/gateway surfaces from the same package.
The same package also ships a small examples/ folder so your first integration can start from a copy-paste snippet instead of reverse-engineering the whole stack.
Install the public package once with npm. It gives you the local Dashboard, the tdm CLI, MCP setup, Hub tooling, Contour Runtime primitives, and JavaScript helpers from the same distribution.
The primary entrypoint is now the local Dashboard. Run tdm after installation to open the localhost UI for Hub installs, publishing, signatures, ratings, and policy review. For terminal-only work, use tdm cli; tdm / is still available for quick area browsing. We intentionally document tdm / with a space; tdm/ is not a public command form.
Terminal launcher navigation follows normal terminal expectations: Esc goes back, Tab completes, F2/F3/F4 toggle favorites, areas, and the state strip, Left/Right switch home sections, and Ctrl+D closes from the empty home screen. Favorited commands appear in a personal Pinned home section, capped at 9 items so quick-pick keys stay predictable.
The launcher also understands @path and $skill. @path inserts a local file or folder path. $skill inserts the path to an existing local skill file discovered in the current workspace. It does not create a new skill automatically. In normal shells, quote $skill if your shell expands $ on its own.
On a fresh machine, run tdm doctor before onboarding if you want to confirm terminal, keyring, and local runtime prerequisites up front.
For guarded runtime and agent destinations, the public CLI now also exposes one coherent trust path: verify ownership with tdm trust verify, promote approved targets with tdm allowlist add, use --scope vault when one vault needs its own narrower route policy, review policy with tdm allowlist list, and preflight a route with tdm allowlist check.
A workspace is your local "Contour". It groups together your agents, vaults, and plugins.
After installation, confirm that the public CLI is available as tdm.
The public workflow starts with tdm connect. Interactive live seller commands can now auto-start that setup when it is still missing, while advanced manual credential editing through tdm login still exists for headless or runtime-only setups.
Manage your local runtime, plugins, and trust policies from the CLI.