Native Anthropic Support and Unified Provider Management in Aiden

Major Update: Aiden Firmware has merged native Anthropic support and unified Provider management, giving you a dedicated Anthropic integration path while making Provider behavior more consistent across language, text-to-speech, and speech-to-text services. These are merged firmware changes, not a universal rollout, and their availability depends on your configured Provider, endpoint, firmware environment, and supported capabilities.

The runtime path we added

The new native Anthropic support gives Aiden a defined path for the Anthropic Messages API rather than treating Anthropic-format requests solely as a generic compatibility case. You can use Provider-level custom endpoints when your deployment requires one. Endpoints remain explicitly configured, and the update does not verify every third-party service.

The work in PR #504, PR #508, PR #518, and PR #532 adds shared runtime bindings for the native path, along with streaming responses, multimodal content handling, tool calls and tool results, and structured stream diagnostics.

For your Agent workflows, Claude tool use is covered in both directions: the firmware can represent tool-call messages and the results returned to the model. Streaming and structured diagnostics create a clearer foundation for following response events as they arrive, while multimodal content is within the scope of this implementation.

That scope is intentionally specific. These merged changes do not cover every Anthropic or Claude capability, persist thinking signatures across turns, add a non-stream fallback, change retry behavior, or make the update available in every firmware environment. Instead, they give Aiden a more direct way to model the request, response, and streaming lifecycle elements that this integration supports.

What changes in Provider configuration

In parallel, PR #495, PR #496, PR #525, and PR #529 unify Provider metadata and configuration behavior across LLM, TTS, and STT services.

For your AI Provider configuration, Config Web now remembers the last model selected for each LLM Provider. When you return to that Provider, your prior model selection can remain associated with it, reducing repeated selection work across Provider changes.

The same shared foundation also connects TTS HTTP Server and AudioDialog to the same Provider generation during hot switching. In practical terms, those components use coordinated Provider state when the active Provider changes. This update is about consistent configuration and shared generation behavior, not a claim of better model quality, voice quality, retry behavior, or universal device support.

What this means for your Aiden setup

Together, these firmware updates reduce fragmentation across two important areas: a dedicated Anthropic path for supported interaction patterns, and a shared Provider foundation for model and audio configuration. You can maintain Provider-specific model selections with greater continuity while audio-facing components coordinate during Provider changes.

The update gives you a clearer configuration path and more useful stream diagnostics without turning a defined implementation into a claim of complete Claude coverage. Follow Aiden’s project progress for future firmware milestones and community technical updates.