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.

Intent Routing

# Intent Routing

Summary: Intents are the universal language of DaOS. When an agent or user issues a command like 'tdm.intent.search', the Contour Runtime identifies the best plugin to handle it, verifies permissions, and executes the logic within a secure sandbox.

Status: Feature overview

Topics:
- Intent-based architecture
- Capability discovery
- Request/Response cycle
- Authorization hooks

Packages:
- tdm-sdk

Commands:
- tdm mcp serve

Intent Routing

Intents decouple "What you want to do" from "How it's done". The Contour Runtime acts as a high-speed router for these requests.

Routing Lifecycle

1.Submission: A request is made (CLI, SDK, or cross-plugin).
2.Discovery: Contour looks for a plugin that exports the matching Intent name.
3.Policy Check: Trust Policies are evaluated for the specific caller/intent pair.
4.Execution: The target plugin is loaded into a WASM sandbox.
5.Bubbling: If a sub-intent is required, the plugin calls back into the Contour router.

Inspecting Runtime Routing

intent-cli.sh

# List available plugin capability cards
tdm plugin list

# Expose MCP tools for agent-side routing/readiness
tdm mcp serve

Cross-Plugin Communication

Plugins can call other plugins' intents by using the call_intent host function provided by the WASI environment.

plugin-recursion.ts

// Inside a WASM plugin
import { call_intent } from "tdm-wasi-helpers";

export function handle_my_intent(params: string) {
  // Call another intent to process data
  const result = call_intent("tdm.intent.transform", { data: params });
  return result;
}