Diminuendo-specific SDK work should follow the Fabric SDK family rather than inventing a parallel gateway SDK model.
Recommended Direction
| Use case | Preferred API |
|---|---|
| First-party web/desktop/TUI clients | Fabric conversation, stream, presentation, and resource profiles through Diminuendo |
| External ACP clients | ACP sidecar compatibility surface |
| Tool/resource integrations | MCP sidecar where the host expects MCP |
| Agent-to-agent exchange | A2A sidecar where the peer expects A2A |
| UI event integrations | AG-UI sidecar where the consumer expects AG-UI |
Fabric SDK Family
Use the shared Fabric SDK guidance for language-specific work:
- TypeScript for Diminuendo, web clients, and local tooling.
- Rust for codex-tui and runtime-adjacent clients.
- Go for Ensemble integration.
- Python for agents and test clients.
- Swift for Apple-native client surfaces.
See Fabric SDKs for the shared contract.