The Short Answer
The agent framework war is not about features — it is about who owns the runtime your agents execute inside. ibl.ai is the agentic AI platform where you own all the code and the data: you self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.
Two events nine days apart in spring 2026 framed the choice precisely, from opposite directions.
Intel made local inference cheap enough to put on a desk. Microsoft made cloud agent infrastructure coherent enough to standardize on. This post reads them together, because the decision they force is the same one.
What did Microsoft actually consolidate, and when?
Microsoft collapsed two competing agent frameworks into one runtime, and the consolidation finished earlier than most coverage suggests.
Microsoft Agent Framework reached 1.0 GA on April 2, 2026, completing the convergence of Semantic Kernel — the enterprise-oriented orchestration SDK with connectors and observability — and AutoGen, the multi-agent orchestration research project out of Microsoft Research. The framework was first announced on October 1, 2025, positioned then as building on both rather than replacing either.
The Microsoft 365 Agents SDK converges into the same abstractions, and the framework shares a runtime with Foundry Agent Service, so an agent prototyped locally moves to hosted execution without a rewrite.
At Build 2026 the framework added production features:
- Agent Harness — automatic context compaction, built-in instructions, file and shell access.
- Hosted Agents in Foundry — scale-to-zero pricing, persistent state, built-in observability.
- CodeAct — Hyperlight micro-VMs collapsing multi-step tool calls into single model turns, for a reported 52.4% latency reduction and 63.9% token savings on representative workloads.
This is real engineering, and the consolidation is a genuine improvement. Two SDKs with overlapping abstractions was a tax developers paid for no benefit. Removing it is good.
A correction worth stating plainly: this did not happen in August 2026. The GA landed on April 2, and the Build announcements followed. If you read a claim that Microsoft "just unified" its agent stack, the unification is roughly four months old and the direction was set the previous October.
What did Intel ship, and why does a $949 card matter?
Intel shipped enough VRAM at a low enough price to make serious local inference a workstation purchase rather than a data center project.
The Intel Arc Pro B70 launched on March 25, 2026 — nine days before Microsoft's GA — carrying 32GB of GDDR6 VRAM for $949, with 367 TOPS INT8, built on the larger "Big Battlemage" die. Intel also announced the Arc Pro B65 at the same capacity tier.
Memory capacity, not raw compute, is the binding constraint for running language models locally.
At 32GB you can comfortably run 7B and 13B models in FP16, and 27–34B models in 4-bit quantization — which covers a large share of practical enterprise inference: classification, extraction, summarization, retrieval-augmented answering, and routine drafting.
The honest caveat: Intel's software ecosystem remains the weakest of the three GPU vendors. CUDA dominates, ROCm is maturing, and Intel's oneAPI and OpenVINO stack trails both.
Intel archived the ipex-llm repository in January 2026, citing known security issues, which is not a reassuring signal for teams standardizing on that path.
So this is not "local inference has won." It is that the hardware floor dropped sharply while the software floor did not, and the economics of keeping routine inference in-house changed as a result.
Is an agent framework a library or a runtime?
This is the distinction that determines how much a framework choice costs you later, and it is the reason the two events above belong in the same post.
A library is something you call. If you dislike it, you replace the call sites. An agent framework is not that. It is the runtime your agents execute inside — it holds their memory, mediates their tool permissions, emits their telemetry, and writes their audit trail.
Your agents' state lives in its schema. Your compliance evidence comes out of its logs.
The asymmetry is straightforward. Swapping a language model should be a configuration change.
Swapping the runtime underneath a fleet of production agents is a migration project measured in quarters, because you are moving memory, permissions, evaluation history, and observability at once.
That asymmetry is why "which models does it support" is the wrong first question. Model support is the reversible decision. Runtime ownership is the one you live with.
Does cloud consolidation or local inference win?
Neither, and framing it as a binary is how organizations end up locked into whichever one they picked first.
Almost every real deployment is mixed. Routine, high-volume, privacy-sensitive work — document classification, PII extraction, internal retrieval — runs well on a 27–34B open-weight model you host, and the marginal cost of an additional request is electricity.
Hard reasoning, long-context analysis, and anything where quality dominates cost goes to a frontier model over an API.
The requirement that falls out of this is portability, not a side. You need an agent runtime that can route a request to a local model on your own hardware or to a hosted frontier model, per task, without rewriting the agent.
A runtime that assumes one of those cases makes the other expensive.
That is the practical test for any agent platform: if a better or cheaper model shipped tomorrow — or if a compliance review moved one workload on-premise next quarter — how long would adoption take? If the answer is longer than an afternoon, the platform is choosing for you.
What should you ask before standardizing on an agent framework?
Four questions, and they are all about exit cost rather than feature lists.
Where does agent memory live, and can you export it? If agent state is only readable through the vendor's API, your agents are not portable regardless of what the model layer supports.
Can the same agent definition run locally and hosted? Microsoft's shared runtime between Agent Framework and Foundry Agent Service is a genuine strength here — within Microsoft's ecosystem. The question is whether it extends past its boundary.
Who holds the audit trail? For regulated deployments the log is the compliance artifact. If it lives in someone else's tenant, your evidence is a subscription.
What happens if you stop paying? With a perpetual source-code license and self-hosting, the answer is that the system keeps running. With hosted agents, the answer is that it stops.
Framework consolidation is good for developers. It is also, structurally, a consolidation of dependency — and those two facts are not in conflict. You just have to price the second one before you commit to the first.
Where ibl.ai fits
ibl.ai is the agentic AI platform where you own all the code and the data. The agent runtime — memory, tool permissions, evaluation, audit trail — ships as source under a perpetual license and executes inside your own perimeter, so the runtime is not a dependency you rent.
It is model-agnostic across any LLM, which in practice means routing a classification job to an open-weight model on your own hardware and a hard reasoning task to a frontier API, per request, without changing the agent.
There is no per-seat pricing, so cost tracks consumption rather than headcount. Deploy anywhere: your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network.
ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.
Related: Why AI Agent Infrastructure Matters More Than the Model You Choose — the same asymmetry, argued from two funding events rather than two product launches.
Related: Microsoft 365 Copilot Alternative: Self-Hosted
Related: Copilot as Entertainment Only: Vendor Lock-In
Related: The Inference Era: Why AI Pricing Has to Move Past Per-Seat