[Feature Request] Agent capabilities manifest + rollout channel protocol

未关闭

#27 创建于 2026年7月22日 0 条评论 0 个 reaction 已指派 0 人在 GitHub 查看

还没有人认领这个 Issue。

评估

难度: 5/5
预计耗时: 一周以上
新手友好度: 35/100

Issue 类型: 功能
描述清晰度: 基本清楚
活跃度: 冷清
领域: api, backend-api-design

调研方向

该 payload 没有提及任何现有文件或测试。首先定义 GET /v1/agent/manifest 的契约和 capability 状态模型，然后审查 SSE/WebSocket CHANGELOG_DIFF 通道、SDK helper 以及 host UI 的要求。完成的标准是达成一致的协议 schema、提供一个完整示例和一个参考 SDK helper，但范围和在 repository 中的放置位置仍需 maintainer 确认。

由索引模型根据 Issue 内容生成。

描述

enhancement

Capability area

Agent harness / Agent Teams

What does M2.7 fail to do for you?

Workload: M3 (or M2.7) running inside host applications — web chat, Android app, IDE plugins, CLI — where the model is wrapped in an agent harness.

What M2.7 fails to do today:

It cannot tell — and cannot be told — which of its own capabilities are actually available to the current user/session. There is no protocol for the host application to advertise to the model:

which tools are enabled, behind a flag, gradually rolling out, or disabled
which surface (web / Android / iOS / IDE / CLI) and app version is hosting it
which account tier, region, or experiment bucket the user is in
when a capability's status changes mid-session

Concrete failure (real example):

User (Android app, free tier, EU region): "Generate a 10-second video of a cat playing piano."
Agent: "Sorry, that feature is not available in your account."
User: opens a bug report.
Reality: video gen is in gradual rollout at 12% and will reach them in ~3 weeks.

Every disabled feature surfaces as a bug. The user has no way to know whether it's:

a bug,
a region/tier lock,
an experiment-bucket exclusion,
a gradual rollout,
a deprecation,
or just "not enabled on this surface."

What I want M3 to support:

Pair the model with a small, model-agnostic Agent Capabilities Protocol:

GET /v1/agent/manifest at session start — static JSON listing
model, host_context, account, and capabilities[] with status
(available / behind_flag / gradual_rollout:<pct> / deprecated
/ disabled) and a human-readable reason + expected_full_rollout.
A live channel (SSE / WebSocket) emitting CHANGELOG_DIFF events
when a capability's status changes mid-session.
An SDK helper like
agent.capabilities().tool("gen_videos").status() so the model can
reason about availability before calling a tool.
A host-UI surface that mirrors rollout state to the end user
("Video gen is in gradual rollout for your account — ETA 2026-08-15").

Why this matters for M3 specifically:

M3 is positioned as a 1M-context agentic model running across many
surfaces. Without a standardized capability-discovery protocol, every
host reimplements the same rollout logic, every user gets a different
"not available" message, and every bug report is filed against a
feature the user was never supposed to see yet.

The protocol itself is model-agnostic and would also benefit M2.5 /
M2.7 / future releases. Happy to relocate this to a different repo
(e.g. Mini-Agent or a platform repo) if the team prefers.

What would "good" look like in M3?

I am happy to follow up with a PR for the schema doc (JSON schema +
worked example) and a reference SDK helper, once the team signals
this is in scope. If MiniMax-M3 is not the right home for a
model-agnostic protocol, please point me to the preferred repo and
I will relocate.

References

Related: this is conceptually similar to MCP toolAnnotations /
tool.listChanged notifications, extended to cover rollout state.
No prior issue found on MiniMax-AI/MiniMax-M3 (filed on 2026-07-22).

主要语言: 没有语言数据
星标: 489
派生: 59
PR 合并指标: 30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

先读完整个 Issue，再读项目的贡献指南。
在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
Fork 仓库，在一个分支上完成修改。
提交 Pull Request，并在描述里引用这个 Issue 编号。

MiniMax-AI/MiniMax-M3 的其他 Issue

[M3 Request] Claude Code 2.1.154+ sends MiniMax-M3 a reduced system prompt by default — please add CLAUDE_CODE_SIMPLE_SYSTEM_PROMPT=0 to your docs
未关闭
- 哪里不对？
难度 1/5 1 小时以内新手友好度 90/100

MiniMax-AI/MiniMax-M3#34 · 1 个 reaction · 2026年8月31日创建
[M2.7 Bug]
未关闭
- 哪里不对？
bug

难度 4/5 3-5 天新手友好度 45/100

MiniMax-AI/MiniMax-M3#35 · 2026年9月12日创建
[M3 Request] Release M3 under a FLOSS license
未关闭
- 哪里不对？
enhancement

难度 4/5 3-5 天新手友好度 45/100

MiniMax-AI/MiniMax-M3#33 · 2026年8月28日创建
Verify evals on Papers with Code
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 48/100

MiniMax-AI/MiniMax-M3#32 · 2026年8月28日创建
[minimax M3 Bug] Bug Report: Raw internal tool-call tokens (]<]minimax[>[) leaking into minimax-m3 response content with stop chat
未关闭
- 哪里不对？
bug

难度 4/5 3-5 天新手友好度 42/100

MiniMax-AI/MiniMax-M3#31 · 2026年8月19日创建

查看 MiniMax-AI/MiniMax-M3 的全部 Issue

相似的 Issue

[BUG][MCPConnection.transport][Default is streamable_http, so URL auto-detection never runs and /sse URLs use the wrong transport]
未关闭
- 哪里不对？
bug tools

难度 2/5 1-3 小时新手友好度 88/100

kyegomez/swarms#2412 · 2026年10月1日创建

维护者通常 1 天内回复
Move organization email-domain formatting out of the admin template
未关闭
- 哪里不对？
organizations

难度 2/5 1-3 小时新手友好度 72/100

pypi/warehouse#20645 · 2026年10月1日创建

维护者通常 1 天内回复
feat(providers): add xiaomi-mimo to NAMED_OPENAI_STYLE_PROVIDERS for live model discovery
未关闭
- 哪里不对？
难度 1/5 1 小时以内新手友好度 92/100

diegosouzapw/OmniRoute#15307 · 1 条评论 · 2026年10月1日创建

维护者通常 2 天内回复
[BUG]: Router combined-regex fast path fails to compile or mixes matches when routes have named groups
未关闭
- 哪里不对？
bug status: unverified

难度 2/5 1-3 小时新手友好度 78/100

phalcon/cphalcon#17636 · 2026年10月1日创建

维护者通常 1 天内回复
[BUG]: Non-finite router scoring weights pass KvRouterConfig validation (prefill_load_scale=inf fails every worker selection)
未关闭
- 哪里不对？
bug language::rust router

难度 2/5 1-3 小时新手友好度 84/100

ai-dynamo/dynamo#15528 · 2026年10月1日创建

维护者通常 1 天内回复

更多 Backend & API Design Issue

[Feature Request] Agent capabilities manifest + rollout channel protocol

哪里不对？

评估

调研方向

描述

Capability area

What does M2.7 fail to do for you?

What would "good" look like in M3?

References

环境准备

从这里开始

MiniMax-AI/MiniMax-M3 的其他 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

相似的 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

把新 issue 发到你的邮箱