Fred release Swift 2.0.x Developer preview · GA summer 2026 Speed is nothing without direction.

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:

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-runtime

Use the CLI to run and test agents locally:

fred-agents-cli --help

Agents 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.

Platform capabilities

For a complete inventory of what Swift supports — ingestion formats, SSE event contracts, APIs, agent templates, governance model, security posture — see the Feature Reference.

Guides

Swift guides are being written now. See Swift Guides as they are published.