Feature update：Auth, Streaming, and Builder Reliability Improvements in feros

Feature update：Auth, Streaming, and Builder Reliability Improvements in feros

This product update covers five recent feros improvements: a Clerk v7 auth flow fix, safer SSE parsing, OpenRouter service tier compatibility, builder TTS fallback refactoring, and workspace/address settings stability fixes.

authstreamingbuilderopenrouterreliability

We shipped a focused set of reliability improvements in feros across authentication, streaming behavior, model-provider compatibility, and builder/runtime configuration handling.

1) Clerk v7 auth flow + SSE parsing fixes

A key fix landed for the Clerk v7 custom auth flow, along with corrections for server-sent event (SSE) parsing behavior.

This improves login/session stability and reduces streaming edge-case failures in app flows that depend on long-lived event streams.

2) OpenRouter service_tier validation is now more permissive

We relaxed strict validation for OpenRouter service_tier in the pydantic-ai path.

This reduces avoidable config failures and makes integration behavior more tolerant of valid provider-side variations.

3) Builder TTS fallback resolution refactor

The TTS fallback resolution path in the builder was refactored to make fallback selection cleaner and easier to reason about.

This is a reliability/maintainability step that supports more predictable voice output behavior when primary TTS options are unavailable.

4) Workspace JSX guard fix

A JSX guard fix in workspace/page.tsx addresses a frontend robustness issue.

This helps prevent avoidable runtime/UI breakage in workspace rendering paths.

5) Address settings consolidation fix

We also fixed issues around address settings consolidation.

This improves consistency in how settings are handled and reduces potential misconfiguration drift.

Why this set matters

Taken together, these updates tighten critical product surfaces:

  • Access reliability: auth/session flow hardening
  • Streaming correctness: safer SSE handling
  • Provider compatibility: less brittle OpenRouter validation
  • Voice-path robustness: clearer TTS fallback behavior
  • Studio stability: safer workspace/settings behavior

If you’re running feros in production or pre-production environments, these fixes should reduce friction in both setup and day-2 operations.

Follow the project at github.com/ferosai/feros for ongoing product updates.