Official SDK Strategy for Python, TypeScript and Go #39
Labels
No labels
bug
documentation
duplicate
enhancement
future idea
good first issue
help wanted
invalid
question
roadmap:phase-agents
roadmap:phase-backend
roadmap:phase-cli
roadmap:phase-docs
roadmap:phase-foundation
roadmap:phase-hardening
roadmap:phase-installer
roadmap:phase-plugins
roadmap:phase-runtime
roadmap:phase-store
roadmap:status-active
roadmap:status-blocked
roadmap:status-done
roadmap:status-planned
roadmap:v2-agent-orchestration
roadmap:v2-auth
roadmap:v2-chat-runtime
roadmap:v2-cli
roadmap:v2-dashboard
roadmap:v2-hardening
roadmap:v2-model-providers
roadmap:v2-plugins-store
roadmap:v2-realtime
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
FTMahringer/Synapse#39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem / Motivation
The ongoing roadmap mentions official SDKs for Python, TypeScript and Go. As Synapse grows into a plugin and automation platform, external developers and future clients will need stable SDKs instead of directly calling raw REST/WebSocket APIs.
SDKs would also help keep plugins, CLI tooling, frontend integrations and external automations consistent.
Proposed Solution
Create an official SDK strategy covering:
Possible SDK scopes:
Core SDK features:
Future Ideas
Priority
Medium / High
This becomes more important once external users, plugins, and separate clients interact with Synapse.