AI 模型和平台
Microsoft 使 Copilot 通过创建程序可用
在 Google 上的首选来源中添加 Unite.AI
Microsoft于2026年10月28日制造了Microsoft Copilot的牵引力——已经授权Copilot码，Copilot Studio,GitHub Copilotapp,Copilot CLI，和VS码的多型号管弦乐层——通过Microsoft创始公司在官方Microsoft博客上的公告中提供给开发者和企业客户。
Microsoft描述一个牵引器是模型周围的一切：向agent提供正确的指令，上下文，执行环境，以及完成工作的控制，同时支持模式上下文协议外加agent技能和agent插件等开放标准。 GitHub工程团队建造了Copilot吊带，Microsoft在全公司范围内采用。 Microsoft Foundary Blog于同日发布推出
Microsoft 称牵引装置是用来跨模范家庭表演的，它支持20多个前沿模型，并带上你的钥匙，它根据任务将工作引向正确的模型或模型。 称公司运行着agent环路和沙盒，其治理和优化在其中构建，而客户则提供指令，技能，工具和模型选择。 Copilot SDK可供下载，机身也可以在Foundry管理的云中运行；Microsoft 称其平台仍然对其他机身和框架开放。
Agent服务处管理执行
公众预览集成四个构件，可重复使用的技能包指令，脚本，以及支持资源进入程序agent可以跨任务应用。 连接工具跨度被支持的Foundry和Model Context Protocol工具有明确配置的认证和批准。 执行和授权让agents用文件和代码工作，手定任务给内置的子代理，而主agent则协调结果。 源控agent定义可以和应用程序代码一起管理。 当任务在配置的界限和政策界限内开发和协调模型和工具步骤时，这个牵引器管理工作环境，客户可以选择一个支持的Foundry模型，而不重写周围的管弦。
开发者可以通过预览版的Azure开发者CLI(azd)表面，Foundry门户网站，Visual Studio代码的Foundry工具箱，或Microsoft Foundry插件和GitHub Copilot应用中的技巧来作者agents. 包括两家公司的声明。 CTO Chris Evans 称他的团队在不到一周的时间里运行了一个解决方案，让它专注于设计和能力而不是下面的基础设施。 易控CEOO Orlando Ribas Fernandes 称利用这一优势为公司提供了一个基础，将复杂的采购流程转变为可测量的受监管的agent工作流程，同时将具有商业约束力的决定置于人类的控制之下。
预览限制和12月计费
在预览期间，客户在创建agent时会选择Microsoft Copilot牵引。 现有的agents没有改变，创建后切换控制带尚未支持，Foundry管理执行环境的CPU，内存和闲置设置。
Foundry Agent Service中Copilot牵引的计费从2026年12月1日开始消费。 机理运行时间的使用在该日期之前是免费的，而模型推论和单独计费的工具和连接服务仍须支付其适用的费用。 从12月1日开始，沙盒计算为每伏CPU小时0.0994美元，内存为每吉B小时0.0118美元，价格因地区和协议而异。
该帖子在Foundry Agent Service中还列出了三种方法：当指令和支持的工具足以完成任务时，在不带牵引装置的情况下，在没有牵引装置的情况下，在Foundry agents的情况下，用Copilot的牵引装置，在技能，文件，和子代理的情况下进行有管理的执行；当团队需要自己的框架，agent循环，中间软件，依赖性，或运行时间行为同时保留Findry管理的主机时，在agents进行托管。
托管 Agents 的长期运行复原力
东道主agents的长效抗御力一般可用，工作需要数小时或数天。 铸币局检测到中断并用其原始输入重新开始工作，而客户的代码则会保存进度和中间结果，这样agent就可以恢复它留下的地方。 当agent更新另一个系统时，工作流程还必须防止重启时的重复动作。 Microsoft指出，对话历史本身不足以恢复正在进行的工作。
建于GitHub
Microsoft 称牵引装置是由同一批GitHub工程师在其多型号管弦乐工作背后建造的，它正在使其Copilot在该基础上的经验标准化。 2026年9月4日，GitHub 推出工程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 Atlas. All rights belong to the original author.