Roadmap
Build locally. Extend everywhere.
Truss is evolving in public. This is the direction we are actively working toward, not a promise of fixed delivery dates.
- Bring your own API key for OpenAI, Anthropic, OpenRouter, Groq, Together AI, Gemini, xAI, Mistral AI, DeepSeek, Perplexity, Fireworks AI, NVIDIA NIM, Xiaomi MiMo, or Ollama Cloud.
- Keep provider selection, model routing, tools, and safety policies behind the same provider-neutral runtime interfaces.
- Store keys locally in the client or environment you control; Truss will not require a hosted control plane or proxy your requests.
Next upMore places to work.
- Native provider adapters and account flows where an API-key compatibility endpoint is not the right integration.
- A Neovim and LazyVim plugin that brings the same runtime into a keyboard-native editor workflow.
- Richer context selection through editor symbols, diagnostics, recent changes, and relationships between workspace files.
- A more capable MCP experience with clearer connection controls, discovery, and portable workspace configuration.
- Plugin registries and an SDK for providers, tools, memory, context sources, and client surfaces.
- Optional remote execution, sandboxes, model benchmarking, and explicit multi-agent workflow graphs without coupling the core runtime to one service.
- Session replay and durable workspace knowledge that make long-running work easier to inspect and resume.
