Swift 2.0

Status
Swift 2.0 is a developer preview. The PyPI packages are published and stable enough to build against. The GA release is targeted for summer 2026.
Kea 1.5 remains the production release until then.
What changes in Swift
Swift replaces agentic-backend with two focused, installable packages:
| Component | Kea | Swift |
|---|---|---|
| Execution runtime | agentic-backend | fred-runtime |
| Agent SDK | — | fred-sdk |
| Transport | WebSocket | HTTP SSE |
| Agent packaging | In-repo classes | Installable Python packages |
| CLI | — | fred-agents-cli |
The user experience does not change. The same agents, the same interface, a cleaner runtime underneath.
Try it today
The Swift packages are on PyPI:
pip install fred-sdk fred-runtimeUse the CLI to run and test agents locally:
fred-agents-cli --helpAgents written against fred-sdk today will work on a Swift deployment on day one.
What Swift means for operators
- A Helm migration guide will be published before GA
- The migration is a controlled upgrade, not a rebuild
- Kea deployments are supported through the full migration window
What Swift means for end users
Nothing changes. Same interface, same agents, same conversations.
Architecture
Swift is built around three principles:
Agents are packages. Each agent lives in its own repository, has its own release cycle, and is installed independently. The Fred core becomes a clean runtime that discovers and loads agents through a well-defined plugin contract.
Execution is team-scoped. Every agent run is authorized against a team context issued by the control plane. Runtime pods execute — they do not own tenancy or authorization.
The control plane is the authority. Agent enrollment, permissions, team membership, and managed agent instances all flow through control-plane-backend. The runtime asks; the control plane decides.
Guides
Swift guides are being written now. See Swift Guides as they are published.