AI 模型和平台
Microsoft 使 Copilot 通过创建系统可用
在 Google 上的首选来源中添加 Unite.AI
Microsoft于2026年10月28日制造出Microsoft Copilot的牵引力——已经将Copilot码，Copilot Studio,GitHub Copilotapp,Copilot CLI，和VS码等多型号的管弦乐层，通过Microsoft Foundary在官方Microsoft Blog上的公告中提供给开发者和企业。
Microsoft描述一个牵引器是模型周围的一切：使agent获得完成工作的正确指令，上下文，执行环境和控制的管弦层，支持模式上下文协议外加agent技巧和agent插件等开放标准。 GitHub工程团队建造了Copilot吊带，而Microsoft则在全公司范围内采用。 Microsoft Foundry Blog的同一天
Microsoft 称牵引装置是用来跨模范家庭表演的，支持20多个前沿模型，并带入自有钥匙，它根据任务将工作引向正确的模型或模型。 称公司运行了agent回路和沙盒，其治理和优化在其中构建，而客户则提供指令，技能，工具和模型选择。 Copilot SDK可供下载，并可以使用由Foundry管理的云中运行；Microsoft 称其平台仍然对其他的取用和框架开放。
Agent处管理执行
公众预览集成四个构件，可重复使用的技能包指令，脚本，以及支持资源入入程序agent可以跨任务应用。 连接工具跨度支持了Foundry和Model Context Protocol工具，并明确配置了认证和批准。 执行和授权让agents使用文件和代码工作，手定任务被内置子代理，而主agent协调结果。 源控agent定义可以与应用程序代码一并管理。 当任务在所配置的界限和政策界限内开发和协调模型和工具步骤时，被调用者管理工作环境，而客户可以选择一个被支持的Foundry模型而无需重写周围的管弦。
开发者可以通过预览版Azure开发者CLI (azd)表面，创用门户，Visual Studio代码的创用工具包，或Microsoft创用插件和GitHub Copilot应用中的技巧来作者agents. 包括两家公司的声明。 CTO Chris Evans 称他的团队在不到一周的时间里就有一个解决方案让它专注于设计和能力而不是下面的基础设施易控CEOO Orlando Ribas Fernandes 称利用这一优势为公司提供了一个基础，将复杂的采购流程转化为可测量的受管agent工作流程，同时将具有商业约束力的决定置于人类的控制之下。
预览限制和12月账单
在预览期间，客户在创建agent时会选择Microsoft和Copilot牵引。 已存在的agents没有改变，创建后切换了管带尚未支持，Foundry管理执行环境的CPU，内存和闲置设置。
Foundary Agent Service中Copilot牵引装置的计费从2026年12月1日开始按消费方式进行。 在该日期之前，哈尼斯运行时间使用是免费的，而模型推论和单独的计费工具和连接服务仍须支付其适用费用。 从12月1日开始，沙盒计算为每VCPU小时0.0994美元，内存为每GiB小时0.0118美元，价格因地区和协议而异。
该帖子还列出了Foundry Agent Service中的三种方法：当指令和支持的工具足以完成任务时，在没有被调用时，在没有被调用时，在没有调用的情况下，在调用agents的情况下，用Copilot的被调用，在技能，文件和子代理的情况下，在管理下执行；当团队需要自己的框架，agent循环，中间软件，依赖性，或运行时的行为同时保留了Findry管理的主机时，在调用agents时托管。
东道主Agents的长跑复原力
东道主agents的长跑韧性一般都有，工作需要数小时或数天。 铸币局检测到中断并用其原始输入重新开始工作，而客户的代码则会保存进度和中间结果，这样agent就可以恢复它所离开的地方。 当agent更新另一个系统时，工作流程还必须防止重启时的重复动作。 Microsoft指出，仅仅对话历史不足以恢复正在进行的工作。
建于 GitHub
Microsoft 称该管带由同一位GitHub工程师在其多型号管弦乐工作后所建造，并正在使该地Copilot经验标准化。 2026年9月4日，GitHub 推出工程"水分融合"(Project HydraFusion)，一个研究预览，利用三种模式从多个提供商建立跨模型的执行计划：单一，其中一个模型直接解决了任务；级联，其中高效的模型起草一个解决方案和质量门，决定是否升级为更强模型；在评论中，来自不同模型家族的独立唯读评论家在起草模型修订之前审查一个草案。 GitHub报告说，在离线评价中，HydraFusion提高了经核实的任务质量4.9个百分点，比Bench 2.1号终端的Claude Opus 5低了67%，在DeepSWE的1.5分内低了36%的费用，在其内部Bench检查站的0.1分内低了65%的费用。
GitHub还曾于2026年9月16日披露其将Copilot agent运行时间从TypeScript移植到Rust到位，到2026年8月21日达到832,378行生产Rust，跨越128个递增发运的牵引请求，Copilot SDK将运行时间暴露为6个语言前端。 Microsoft将行业领先的绩效和会议间接费用的减少以及时间到第一时间的减少归因于港口。 在基准测试中，Microsoft杰出工程师斯蒂芬·图布跑过C#SDK，创建客户端和会话并完成一个转弯的时间从端口前5.25秒下降到了292毫秒并加载了Rust的运行时间在流程中，10个客户端批次中最高峰所添加的内存从1,383 MB下降到了126 MB.
本文由 AI宝库自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
AI Models & Platforms
Microsoft Makes Copilot Harness Available Through Foundry
Add Unite.AI to your preferred sources on Google
Microsoft on October 28, 2026 made the Microsoft Copilot harness — the multi-model orchestration layer that already powers Copilot Code, Copilot Studio, the GitHub Copilot app, the Copilot CLI, and VS Code — available to developers and enterprise customers through Microsoft Foundry, in an announcement on the Official Microsoft Blog.
Microsoft describes a harness as everything around the model: the orchestration layer that gives an agent the right instructions, context, execution environment, and controls to accomplish work, with support for open standards such as the Model Context Protocol plus agent skills and agent plugins. The GitHub engineering team built the Copilot harness, and Microsoft has adopted it company-wide. A companion Microsoft Foundry Blog post the same day introduced the harness in Foundry Agent Service in public preview and announced general availability of long-running resilience for hosted agents.
Microsoft said the harness is built to perform across model families, with support for more than 20 frontier models plus bring-your-own-key, and that it routes work to the right model or models based on the task. The company said it runs the agent loop and sandbox with governance and optimization built in, while customers supply the instructions, skills, tools, and model choice. The Copilot SDK is available to download, and the harness can also run in the cloud managed by Foundry; Microsoft said its platforms remain open to other harnesses and frameworks.
Managed Execution in Foundry Agent Service
The public preview combines four building blocks, according to the Foundry Blog post. Reusable skills package instructions, scripts, and supporting resources into procedures an agent can apply across tasks. Connected tools span supported Foundry and Model Context Protocol tools with explicitly configured authentication and approvals. Execution and delegation let agents work with files and code and hand bounded tasks to built-in subagents while the main agent coordinates the result. Source-controlled agent definitions can be managed alongside application code. The harness manages working context as tasks develop and coordinates model and tool steps within configured limits and policy boundaries, and customers can choose a supported Foundry model without rewriting the orchestration around it.
Developers can author agents through the preview Azure Developer CLI (azd) surface, the Foundry portal, the Foundry Toolkit for Visual Studio Code, or the Microsoft Foundry plugin and skill in the GitHub Copilot app. The post includes statements from two companies. Confluence Technologies CTO Chris Evans said his team had a solution running in less than a week, letting it focus on design and capabilities rather than the infrastructure underneath. Fashable CEO Orlando Ribas Fernandes said the harness gives the company a foundation for turning complex sourcing processes into governed, measurable agent workflows while keeping commercially binding decisions under human control.
Preview Limits and December Billing
During the preview, customers select the Microsoft Copilot harness when creating an agent. Existing agents are unchanged, switching the harness after creation is not yet supported, and Foundry manages the execution environment’s CPU, memory, and idle settings.
Billing for the Copilot harness in Foundry Agent Service begins December 1, 2026 on a consumption basis. Harness runtime usage is free before that date, while model inference and separately billed tools and connected services remain subject to their applicable charges. Starting December 1, sandbox compute is billed at $0.0994 per vCPU-hour and memory at $0.0118 per GiB-hour, with prices varying by region and agreement.
The post also lays out three approaches in Foundry Agent Service: prompt agents without the harness when instructions and supported tools are enough for the task; prompt agents with the Copilot harness for managed execution with skills, files, and subagents; and hosted agents when teams need their own framework, agent loop, middleware, dependencies, or runtime behavior while retaining Foundry-managed hosting.
Long-Running Resilience for Hosted Agents
Long-running resilience for hosted agents is generally available, aimed at work that takes hours or days. Foundry detects interruptions and restarts the work with its original input, while the customer’s code saves progress and intermediate results so the agent can resume where it left off. When an agent updates another system, the workflow must also prevent duplicate actions on restart. Microsoft noted that conversation history alone is not enough to restore work in progress.
Built at GitHub
Microsoft said the harness was built by the same GitHub engineers behind its multi-model orchestration work, and that it is standardizing its Copilot experiences on that foundation. On September 4, 2026, GitHub introduced Project HydraFusion, a research preview that builds an execution plan across models from multiple providers using three patterns: single, in which one model solves the task directly; cascade, in which an efficient model drafts a solution and a quality gate decides whether to escalate to a stronger model; and critique, in which an independent read-only critic from a different model family reviews a draft before the drafting model revises it. GitHub reported that in offline evaluations HydraFusion improved verified task quality by 4.9 percentage points at 67% lower estimated cost than Claude Opus 5 on TerminalBench 2.1, came within 1.5 points on DeepSWE at 36% lower cost, and came within 0.1 points on its internal CheckpointBench at 65% lower cost.
GitHub had also disclosed on September 16, 2026 that it ported the Copilot agent runtime from TypeScript to Rust in place, reaching 832,378 lines of production Rust by August 21, 2026 across 128 incrementally shipped pull requests, with the Copilot SDK exposing the runtime to six language front-ends. Microsoft attributes industry-leading performance and reductions in session overhead and time-to-first-token to the port. In benchmarks that Microsoft Distinguished Engineer Stephen Toub ran through the C# SDK, the time to create a client and session and complete one turn fell from 5.25 seconds before the port to 292 milliseconds with the Rust runtime loaded in-process, and peak added memory in a ten-client batch fell from 1,383 MB to 126 MB.
Auto-fetched and translated by AI Gem Box. All rights belong to the original author.