# Feature Roadmap This page provides an overview of tdx feature coverage and planned development. ## Feature Coverage Matrix The matrix below shows the current status of each command across five capability areas: | Legend | Meaning | | --- | --- | | ✅ | Available | | 🚧 | Planned | | ➖ | Not planned | ### Capability Definitions - **Read**: Query and retrieve resources (list, get, describe) - **Write**: Create and update resources (create, update, delete) - **Verify**: Validate configuration locally before deployment - **Sync**: Bidirectional sync between local files and remote resources (push, pull) - **Monitor**: Track execution status and metrics (logs, status, history) ## Data Commands | Command | Read | Write | Sync | Monitor | | --- | --- | --- | --- | --- | | [`tdx query`](/treasure-code/commands/query) | ✅ | ✅ | ➖ | ➖ | | `tdx query` (federated) | 🚧 | ➖ | ➖ | ➖ | | [`tdx job`](/treasure-code/commands/job) | ✅ | ✅ | ➖ | ✅ | | [`tdx database`](/treasure-code/commands/database) | ✅ | ✅ 1 | ➖ | ➖ | | [`tdx table`](/treasure-code/commands/table) | ✅ | ✅ 1 | ➖ | ➖ | | `tdx upload` | ➖ | 🚧 | ➖ | ➖ | | [`tdx workflow`](/treasure-code/commands/workflow) | ✅ | ✅ | ✅ | 🚧 2 | 1 Use `tdx query "CREATE SCHEMA ..."` or `tdx query "CREATE TABLE ..."` 2 Session/attempt monitoring via `tdx wf sessions`, `tdx wf attempts` ## CDP Commands | Command | Read | Write | Verify | Sync | Monitor | | --- | --- | --- | --- | --- | --- | | [`tdx segment`](/treasure-code/commands/segment) | ✅ | ✅ | ✅ | ✅ | 🚧 | | [`tdx parent-segment`](/treasure-code/commands/parent-segment) | ✅ | ✅ | ✅ | ✅ | 🚧 | | [`tdx connection`](/treasure-code/commands/connection) | ✅ | 🚧 | ✅ 3 | 🚧 | ➖ | | [`tdx engage`](/treasure-code/commands/engage) | ✅ | 🚧 | ➖ | 🚧 | 🚧 | | [`tdx journey`](/treasure-code/commands/journey) (batch) | ✅ | ✅ | ✅ | ✅ | 🚧 | | `tdx journey` (realtime) | 🚧 | 🚧 | 🚧 | 🚧 | 🚧 | 3 Connector config validation via `tdx connection schema` ## AI Commands | Command | Read | Write | Verify | Sync | Monitor | | --- | --- | --- | --- | --- | --- | | [`tdx agent`](/treasure-code/commands/agent) | ✅ | ✅ | 🚧 | ✅ | ➖ | | [`tdx llm`](/treasure-code/commands/llm) | ✅ | ✅ | 🚧 | ➖ | ✅ | | [`tdx chat`](/treasure-code/commands/chat) | ✅ | ✅ | ➖ | ➖ | ✅ | ## Utility Commands | Command | Read | Write | Sync | Monitor | | --- | --- | --- | --- | --- | | [`tdx user`](/treasure-code/commands/user) | ✅ | ➖ | ➖ | ➖ | | `tdx auth` | ✅ | ✅ | ➖ | ➖ | ## Claude Code Integration [`tdx claude`](/treasure-code/commands/claude) launches [Claude Code](https://claude.ai/code) with Treasure Data tools pre-configured. | Feature | Status | Description | | --- | --- | --- | | Conversation | ✅ | Interactive chat with Claude | | Tool calls | ✅ | Execute commands via Claude (tdx, Bash, etc.) | | [MCP](https://code.claude.com/docs/en/mcp) | ✅ | Model Context Protocol support | | [Skills](https://code.claude.com/docs/en/skills) | ✅ | Agent skills for specialized tasks | | [Plugins](https://code.claude.com/docs/en/plugins) | ✅ | Extensible plugin system | | [Hooks](https://code.claude.com/docs/en/hooks) | ✅ | Event-driven automation | | IDE: VS Code | ✅ | Run `tdx claude` in VS Code terminal | | Plan mode | ✅ | Structured planning for complex tasks | | [Extended thinking](https://code.claude.com/docs/en/common-workflows#use-extended-thinking) | ✅ | Reasoning with extended thinking | | [Subagents](https://code.claude.com/docs/en/sub-agents) | ✅ | Delegate tasks to specialized subagents | | [Agent SDK](https://platform.claude.com/docs/en/agent-sdk/overview) | ✅ | Build custom agents with Claude | | Opus model | ✅ | Support for Claude Opus model | ## Feature Highlights ### Marketing as Code (Sync) The sync capability enables [Marketing as Code](/treasure-code/guide/marketing-as-code), allowing you to: - Export resources to YAML files (`tdx segment pull`) - Edit configurations locally with version control - Deploy changes safely (`tdx segment push`) - Preview changes before applying (`--dry-run`) - Clone resources to new names (`tdx segment clone`) Currently available for **segments**, **parent-segments**, **batch journeys**, **workflows**, and **AI agents**. ### Local Verification (Verify) The verify capability validates configurations locally before deployment: - Check YAML configuration syntax and structure - Validate field references against the parent segment schema - Validate segment rules, operator types, and required fields - Validate journey step references and A/B test percentages - Validate connector configs against connection schemas - Detect issues early without affecting production resources Currently available for **segments** (`tdx sg validate`), **journeys** (`tdx journey validate`), **parent-segments**, and **connections** (`tdx connection schema`). Planned for LLM agents. ### Monitoring Monitoring capabilities allow tracking execution and status: - Job status and results (`tdx job list`, `tdx job show`, `tdx job result`) - Chat and LLM usage monitoring (`tdx chat logs`, `tdx llm logs`) - Workflow sessions and attempts (`tdx wf sessions`, `tdx wf attempts`) - Workflow logs (`tdx wf attempt logs`) - CDP execution tracking (planned for segments, parent-segments, engage, journeys) ## Roadmap Priorities ### Recently Completed (v0.10 - v0.12) - ✅ Workflow sync (`tdx wf pull`, `tdx wf push`, `tdx wf clone`) - ✅ Workflow secrets management (`tdx wf secrets`) - ✅ Default workflow project (`tdx wf use`) - ✅ Interactive workflow run (`tdx wf run`) - ✅ Segment validation (`tdx sg validate`) - ✅ Journey validation (`tdx journey validate`) - ✅ Connector config validation (`tdx connection schema`) - ✅ Journey wait step branching (different paths for matched vs timeout) ### Near-term - Local file upload to tables (`tdx upload`) - Federated query support (`tdx query`) - Query external data sources including Snowflake, BigQuery, Redshift, and Databricks - Connection write/sync support - Workflow monitoring enhancements (task progress, improved log streaming) - CDP monitoring (segment, parent-segment, engage, journey execution tracking) - Engage write/sync support - Journey realtime support (read, write, sync, monitoring) - Local verification for LLM agents ### Future - Enhanced monitoring dashboards - Cross-resource dependency tracking