FabrCore 1.7.1: Build Agents That Keep Working—Safely
FabrCore v1.7.1 is available today. This release turns long-running agent work into a native, durable part of the runtime—then surrounds it with bounded context, explicit team composition, secure reusable skills, and a real-time protocol designed for production clients.
The Agent Harness Finishes Multi-Step Work
The new Agent Harness composes onto a FabrCoreAgentProxy or Microsoft Agent Framework agent. It gives the model a structured todo list, an iteration loop, plan-and-execute modes, durable snapshots, background delegation, and private internal specialists.
For AI agent developers, that means the jump from "answer this prompt" to "complete this objective" no longer requires a parallel orchestration service. The work runs inside the same Orleans-backed agent identity that already owns messages, state, health, telemetry, and recovery.
Squads Make the Team Deployable
Surface and Blueprints now support top-level squads in two explicit forms. Orchestrator squads model stable conversational teams with a coordinator and durable members. Task squads model objective-driven work with todos, iteration, an executor, SMEs, and bounded delegation.
The experimental Swarm layer and its nested configuration are removed. The replacement has a cleaner boundary: Blueprints declare the team, Surface presents and operates it, and native agents carry the durable work.
Context Has a Safety Ladder
v1.7.1 introduces five ordered controls: evict old tool results at 50%, truncate remaining tool-result groups at 80%, compact persisted history at 87%, engage a projection fuse at 90%, and stop at the hard prompt budget. Per-turn input budgets bound agents that make many individually valid calls.
The runtime describes the resolved ladder and records stop diagnostics. Developers can see which control fired, why a run ended, and whether model or agent overrides placed the thresholds out of order.
WebSocket v2 Is Authenticated and Durable
The new protocol replaces query-string identity with 30-second single-use tickets and the fabrcore.v2 handshake. Typed operations replace raw wire objects. Stable client ids, ordered sequence numbers, acknowledgements, replay, and explicit gap recovery give applications an honest at-least-once delivery contract.
The new FabrCore.Client.WebSocket package handles tickets, reconnect backoff, typed request methods, delivery enumeration, checkpoints, and resynchronization events for .NET clients.
Skills Are Exact, Immutable, and Principal-Owned
Harness Skills package reusable instructions and reference content as immutable name@version artifacts. Agents select exact versions through _HarnessSkills; there is no floating latest version during execution. Packages are text and ZIP resources only—no scripts or executables—and administration is principal-scoped behind FabrCoreAdmin.
This gives teams a reproducible way to teach agents organization-specific procedures without rebuilding the agent or turning prompt content into trusted executable code.
A Cleaner Runtime
- Automatic discovery:
AddFabrCoreServerandAddFabrCoreServicesscan the application and referenced FabrCore dependency graph.AdditionalAssembliesremains for truly dynamic code. - Secure model management: in-process resolution reads the active store directly; remote configuration routes require the admin policy and API key.
- Cloud reliability: connect long polling has dedicated timeout and retry behavior.
- Microsoft 365 polish: typing timers stop before final success and error responses.
- Dependency alignment: Microsoft Agent Framework packages move together to 1.16.0.
Upgrade Deliberately
This release contains intentional breaking changes in WebSocket ingress and Swarm configuration. Review the upgrade guide before deploying, especially if an application opens raw sockets, provisions nested squads, or supplies identity through old headers and query parameters.
Build the Agent That Owns the Outcome
Update your FabrCore packages to v1.7.1, compose a Harness around an existing agent, and give it one bounded objective. The runtime now has the planning, persistence, context control, delegation, transport, and operational surface to carry that work responsibly.