Current Trend State — as of 2026-08-30T00:00Z (English snapshot)

Maintenance note: this file reflects the candidate/confirmed trends still worth tracking. Each run may add, upgrade, downgrade, or retire entries. A trend requires multiple independent signals (cross-date, cross-organization); a single news item or one-day heat is not a trend.

Candidates under observation

Strengthening: Open-weight agentic coding models from Chinese labs competing at frontier level

  • Status: strengthening (upgraded from emerging on 2026-08-28 — confirmation criterion substantially met: GLM-5.3 weights landed + Artificial Analysis independent eval)
  • Confidence: Medium
  • First observed: 2026-08-15 (covering the 2026-08-14 window)
  • Last updated: 2026-08-30
  • Evidence:
    1. Qwen3.8-27B weights released (Apache 2.0, 91k downloads day-one, 2026-08-14)
    2. GLM-5.3 launch (2026-08-14; weights landed 2026-08-25, see item 5)
    3. Adjacent context: Meta Muse Glimmer / Muse Spark 1.2 open weights (2026-08-10, US lab — same direction, different scope)
    4. Background: Kimi K3 2.8T open weights (2026-07-16)
    5. GLM-5.3 weights landed: HF zai-org/GLM-5.3 (FP8, 153 files) + GLM-5.3-BF16 created 2026-08-25, 753B total params, ungated; the custom glm-5.3 license is MIT-style with a single security-review clause for >$10B-revenue MaaS businesses; day-0 vLLM/SGLang/TokenSpeed/KTransformers/Unsloth/vLLM-Ascend support (primary source, ev-20260814-02 update)
    6. Independent eval: Artificial Analysis Intelligence Index — GLM-5.3 (max) at 60 (on par with Kimi K3, +7 over GLM-5.2); GLM-5.3-Flash at 57 (added 8/26); GLM-5.3-Flash open-sourced under plain MIT the same day (320B-A18B, new base, hybrid sparse-linear attention — same-org reinforcing signal, ev-20260825-01)
    7. Qwen3.8-Flash-Next open-weight architecture preview (Qwen, dated 2026-08-26; HF repo created 8/24; coverage-gap recovery, ev-20260826-04): 125B/6B-activated + 51B n-gram embedding + 4B MTP (~180B), Gated DeltaNet linear attention + Qwen Sparse Attention every 4th layer, 262k native context (1M via YaRN), multimodal; custom qwen-community-1.0 license; 52k downloads and 4.2k likes in 4 days — a same-direction open-weight reinforcement from a different org, landing hybrid linear attention in the same week as GLM-5.3-Flash (cross-org technical convergence)
    8. GLM-5.3-Flash download velocity (verified 2026-08-29): 189,793 downloads (~4 days after listing; 30d window = all-time) + 1,557 likes; GLM-5.3 FP8 at 8,804 (753B artifact); vLLM recipe page live, NVFP4 quantized-serving discussions appearing (ev-20260825-01 update)
    9. Tencent Hy4 preview open weights (Tencent, announced 2026-08-28, HF repos created 8/27; coverage-gap recovery, ev-20260828-02): 770B total / 49B active MoE, context beyond 1M, Apache 2.0 (per HF tags), standard + FP8 weights with a day-0 vLLM recipe — the third Chinese lab to open-source major weights in one week, and the closest candidate yet for the same-tier-different-org criterion (b); however the only eval is a vendor-run blind test (163 experts / 203 tasks, 2.99 vs GLM-5.3 2.92, Kimi K3 2.94), there are no public benchmark scores, and it is a preview; ~1.4k downloads in 2 days
  • Why strengthening: The confirmation criterion "GLM-5.3 weights land + independent benchmark reproduction" is substantially met — weights landed 8/25 under a permissive license, and Artificial Analysis independently places GLM-5.3 in the same tier as Kimi K3. GLM-5.3-Flash (plain MIT, new base, linear-attention cost reduction) is a same-org reinforcing signal. Why not High: the criterion's other items (another same-tier release next cycle, sustained HF download velocity) are still pending, and the independent eval covers the API rather than community reproduction on the weights; also track the safety spillover of emergent cyber capability in the weights (directly echoing the warning in ev-20260818-04).
  • 2026-08-16 run: No new independent signals in window (GLM-5.3 reaching Product Hunt #3 is community heat only). Status/Confidence unchanged.
  • 2026-08-17 run: Coverage-gap note: Qwen3.8-2.4T-A95B (the open-weight sibling of the Qwen3.8-Max flagship, Apache-2.0 + official FP8) was published to HF on 2026-08-13, before this KB's first scan window. Logged as background evidence only, not counted as a new in-window signal (same organization as the 27B). Adoption: 7.9k/10.7k downloads (BF16/FP8) in the first days, day-0 support from vLLM, SGLang and TokenSpeed, plus an NVIDIA GB300 NVL72 serving blog. Status/Confidence unchanged.
  • 2026-08-18 run: No new signals in window (GLM-5.3 weights still pending ~8/28). Status/Confidence unchanged.
  • 2026-08-19 run: No new in-window signals (GLM-5.3 weights still pending; the zai-org/GLM-5.3 HF repository does not exist yet). Background cross-reference (not counted as evidence): OpenAI's "The Defender's Window" (8/10, out of window) expects an open-weight model with near-frontier cyber capabilities by end of August, significantly intensifying the threat landscape — timing aligns with GLM-5.3 (~8/28). Status/Confidence unchanged.
  • 2026-08-20 run: No new in-window signals (GLM-5.3 weights still pending; HF API confirms zai-org/GLM-5.3 is still absent and zai-org's latest public model remains GLM-5). Qwen3.8's continued HF trending dominance (1M+ main-repo downloads, unsloth GGUF 4.3M) is a continuation of existing background, not counted as new evidence. Status/Confidence unchanged.
  • 2026-08-21 run: No new in-window signals (GLM-5.3 weights still pending ~8/28; HF API still returns 401 for zai-org/GLM-5.3 — the repository does not exist). Qwen3.8-27B (1.37M downloads), Kimi-K3, MiniMax-H3 and the DeepSeek-V4-Flash family continue to dominate HF trending, a continuation of the existing Chinese open-weight dominance background, not counted as new evidence. Status/Confidence unchanged.
  • 2026-08-22 run: No new in-window signals (GLM-5.3 weights still pending ~8/28; HF API still returns 401; zai-org's latest public model remains GLM-5). Chinese labs were quiet in-window. The Qwen3.8-27B ecosystem on HF trending (1.73M main-repo downloads, unsloth GGUF 5.8M, FP8 1.9M, derivative Uncensored variants 100k-1.1M) is a continuation of existing background. A background cross-reference grew materially stronger (still not counted as evidence): OpenAI's official security post "Pacing model development..." (announced 8/18, long-form post 8/20) confirms the model-driven breach of HF production infrastructure and assesses Astra as near the Critical cyber-capability threshold — aligning with "The Defender's Window" (see ev-20260818-04). Status/Confidence unchanged.
  • 2026-08-24 run: No new in-window signals (GLM-5.3 weights still pending ~8/28; HF API still returns 401; Chinese labs quiet over the weekend). The "GLM-5.3 found 1,097 vulnerabilities" piece and the TokenCost pricing article circulating in-window both repeat 8/14 launch-week facts. New mirror-image background (not counted as evidence): on 8/22 WSJ reported that Nvidia plans to build a US open-weight model through its $6B Poolside deal, explicitly targeting DeepSeek and Kimi — the first heavyweight US supply-side response to the trend (see ev-20260822-01). Status/Confidence unchanged.
  • 2026-08-28 run: Upgraded to strengthening / Medium: the confirmation criterion is substantially met — GLM-5.3 weights landed 8/25 (permissive glm-5.3 license, ungated, 753B) plus the Artificial Analysis independent eval at 60 (on par with Kimi K3); GLM-5.3-Flash open-sourced under plain MIT the same day (same-org reinforcement, ev-20260825-01). Safety note: the model card discloses emergent post-training cyber capability (CyberGym 84.5 open-weights SOTA; ExploitGym more than double GLM-5.2), timing-wise consistent with OpenAI's "Defender's Window" expectation of end-of-August open-weight cyber capability (background cross-reference, not counted as evidence).
  • 2026-08-29 run: Criterion-by-criterion audit: (a) community independent reproduction of the weights NOT met — the "community evaluation results" PRs merged 8/28-29 (HF discussions #2/#3) only sync model-card numbers into .eval_results metadata (source field "Model Card"), not third-party runs; (b) same-tier release from another org partially met — Qwen3.8-Flash-Next is an open-weight architecture preview but experimental, not a same-tier flagship; (c) download velocity met on the Flash side (189,793/4d). New evidence items 7 and 8. Two hybrid-linear-attention releases in one week form a technical convergence. 1/3 criteria fully met — stays strengthening / Medium. Also: the GLM-5.3 model card was rewritten 8/27 with the full benchmark table public (TB 2.1 88.2 / DeepSWE 66.9 / CyberGym 84.5; same base, post-training-only gains).
  • 2026-08-30 run: No new releases in-window (Saturday). Criterion audit: (a) community reproduction of the weights still NOT met — new HF discussions are all minor (citation error, FP8/BF16 question, refusal feedback, typo PR); no reproducible third-party Terminal Bench / SWE runs. (b) Same-tier release from another org — Tencent Hy4 preview (770B/49B, Apache 2.0, 1M+ context) is the strongest candidate yet, but preview positioning plus a vendor-only blind test leaves this close-but-not-fully-met. (c) Download velocity — the 30-day pools for GLM-5.3-Flash (189,793) and Flash-Next (52,341) did not roll over (likes +60 / +74); re-sample next cycle. Evidence item 9 added (Hy4, ev-20260828-02). Mirror background (not counted): Nvidia's reported $12.9B Hugging Face acquisition (8/27, ev-20260827-03) — the second heavyweight US supply-side move after Poolside/Nemotron, again confirming from the other side that the open-weight frontier is the battleground. Stays strengthening / Medium.
  • What would confirm (remaining criteria for High): (a) community independent reproduction on the weights (third-party Terminal Bench / SWE runs — note: model-card metadata sync does not count); (b) another same-tier open-weight release from a different organization next cycle (Flash-Next is an experimental preview, only partially satisfying this); (c) sustained HF download velocity (4 days of hard data on the Flash side; needs to continue)

Emerging: MCP entering enterprise security & enforcement phase

  • Status: emerging (upgraded from candidate on 2026-08-16)
  • Confidence: Medium
  • First observed: 2026-08-15 (covering the 2026-08-14 window)
  • Last updated: 2026-08-30
  • Evidence:
    1. Cloudflare One Gateway MCP detection/enforcement GA — experimental.is_mcp, Portal-only enforcement, OAuth pre-registration (2026-08-14, primary source, ev-20260814-03)
    2. Workday Adaptive Planning first-party MCP Server in 2026R2 release notes (2026-08-14, official docs) — enterprise SaaS supply side
    3. Practical DevSecOps MCP Security Statistics 2026: 82% of implementations are vulnerable to path traversal; 40+ MCP CVEs disclosed by early August — security demand side
    4. Ecosystem scale: 10,000+ MCP servers after the 2026-07-28 stateless spec revision
    5. Background (verified): Netskope's MCP Security Dashboard in Advanced Analytics became available to all customers with Advanced Analytics enabled on 2026-06-12 (official release notes); however, the 22 MCP data attributes remain behind a feature flag (Sales/Support activation) — not a clean GA (verified 2026-08-20 as pre-coverage background)
    6. Background (verified): Netskope Release 140.0.0 (monthly update posted 2026-08-11, pre-coverage) ships Agentic Broker, which applies real-time protection policies to MCP traffic from a dedicated RTP page, scoped per server, per catalog category, or across any MCP traffic, and extends MCP activity visibility in SkopeIT. This is a second vendor's enforcement capability, but it is pre-coverage background, the 22 MCP data attributes remain behind a feature flag, and there is no public telemetry (verified 2026-08-22)
    7. Background (verified): Zscaler announced Zscaler AI Broker on 2026-06-09 (Zenith Live), a security broker for agent communication over MCP and A2A, paired with an Agent Registry that shows, per agent, which resources it is authorized to access — part of its Zero Trust platform for Agentic AI. This is the third SSE/security vendor with an MCP enforcement capability after Cloudflare and Netskope, but the press release does not state GA vs. preview status and there is no public telemetry (verified 2026-08-24 as pre-coverage background; the 8/17 check missed it)
    8. Background (verified): Netskope's 2026-03-11 press release announced the Netskope One AI Security suite (incl. Agentic Broker — visibility and control over all MCP transactions, sanctioned or not) as "generally available today", meaning the Broker product itself has been GA since March; however the 22 MCP data attributes remain behind a feature flag with no public telemetry (verified 2026-08-29 as pre-coverage background)
  • Why upgraded: Multiple independent signals from different organizations and dates (network vendor, enterprise SaaS, security research) point the same way — MCP is moving from a novelty protocol to governed enterprise infrastructure.
  • 2026-08-17 run: Checked whether Zscaler/Netskope/Palo Alto ship MCP identification — none found (only SASE comparison articles and Zscaler's own MCP server integrations). The confirmation criterion remains unmet. Status/Confidence unchanged.
  • 2026-08-18 run: Background note: Netskope's MCP security capabilities were announced as Preview on 2025-12-01, with GA planned for H1 2026; no dated GA announcement found. On capability this partially meets the second-vendor criterion, but it predates KB coverage and is logged as background only. Additional context: the 2026-07-28 MCP auth spec (OAuth 2.1/OIDC) met enterprise pushback (anonymous DCR criticism); CSA catalogued ~7,000 exposed MCP servers in early 2026, roughly half unauthenticated; NSA/DoD issued security design guidance in June 2026. Criterion refined to: a second security vendor shipping GA MCP identification plus published telemetry. Status/Confidence unchanged.
  • 2026-08-19 run: No new in-window signals; the Netskope GA criterion remains unmet. Adjacent signal (not counted as evidence): Codex 0.148.0's MCP recovery after OAuth re-auth and sandbox fail-closed are client-side reliability hardening, not enterprise identification or enforcement. Status/Confidence unchanged.
  • 2026-08-20 run: Substantive criterion progress: Netskope's official release notes (2026-06-12) confirm the MCP Security Dashboard is available to all customers with Advanced Analytics enabled, but the 22 MCP data attributes still require a feature flag plus Sales/Support activation. Conclusion: partial GA, not a clean GA; the confirmation criterion (second-vendor GA plus public telemetry) remains unmet. The fact predates KB coverage and is recorded in the evidence list as verified background. No other in-window signals. Status/Confidence stays emerging / Medium.
  • 2026-08-21 run: No new in-window signals; the Netskope clean-GA criterion remains unmet. Adjacent signals (not counted as evidence): Claude Code 2.1.238's stdio MCP handshake-order fix and elicitation-dialog fixes are client-side reliability work; Tencent/AI-Infra-Guard trending on GitHub is a community-tool signal. Status/Confidence stays emerging / Medium.
  • 2026-08-22 run: Verified-background progress: Netskope 140.0.0's Agentic Broker (8/11, pre-coverage) enforces real-time policies on MCP traffic — a second vendor's enforcement capability after Cloudflare, recorded as evidence item 6. The clean-GA criterion remains unmet: the August monthly update does not mention the 22 MCP data attributes leaving the feature flag, and there is no public telemetry. No other in-window signals. Status/Confidence stays emerging / Medium.
  • 2026-08-24 run: One new verified-background evidence item (item 7): Zscaler AI Broker (6/9, pre-coverage) is a third vendor's MCP/A2A enforcement capability, plus an Agent Registry. The press release does not state GA status and there is no public telemetry, so the clean-GA criterion (second-vendor GA plus public telemetry) remains unmet; on the Netskope side, the August monthly update says nothing about the 22 MCP data attributes leaving the feature flag. No other in-window signals. Status/Confidence stays emerging / Medium.
  • 2026-08-28 run: No in-window signals. Re-checks: Netskope's official release notes still stop at 140.0.0 (checked 8/28) — the 22 MCP data attributes remain behind the feature flag with no public telemetry; the MCP-gateway wording in Zscaler's 2026-01-27 press release verified as earlier pre-coverage background (same organization as evidence item 7 and older, not counted again). The clean-GA criterion (second-vendor GA plus public telemetry) remains unmet. Status/Confidence stays emerging / Medium.
  • 2026-08-29 run: No new in-window signals. Re-checks: Netskope's official release notes still stop at 140.0.0 (no 141.x found); the 22 MCP data attributes remain behind the feature flag. One newly verified pre-coverage background fact registered — the 2026-03-11 press release confirms the Agentic Broker product has been GA since March (evidence item 8) — but the clean-GA criterion (attributes out of flag + public telemetry) remains unmet. Status/Confidence stays emerging / Medium.
  • 2026-08-30 run: No new signals in-window. Re-check: Netskope official release notes still stop at 140.0.0 (verified via search 2026-08-30, no 141.x found); the 22 MCP data attributes remain behind the feature flag with no public telemetry; no Zscaler GA announcement. The clean-GA criterion (second-vendor GA + public telemetry) remains unmet. Status/Confidence stay emerging / Medium.
  • What would confirm: Second security vendor (Zscaler/Netskope/Palo Alto) shipping GA MCP identification with public telemetry; MCP auth spec adoption in major agent frameworks

Established: Coding agents converging into multi-agent runtimes

  • Status: established (candidate→emerging 2026-08-18; →strengthening 8/20; →established 2026-08-28 — confirmation criterion (a) met: Codex 0.150.0 stable ships agent-initiated cross-task messaging; in the same window Gemini CLI 0.57.0 shipped a2a-server in stable and on npm, making Google the seventh organization with protocol-level interop in a stable runtime)
  • Confidence: High
  • First observed: 2026-08-15 (covering the 2026-08-13/14 window)
  • Last updated: 2026-08-30
  • Evidence:
    1. Anthropic Claude Code: default-on subagent forking + cross-session SendMessage (2026-08-13/14)
    2. GitHub/Microsoft Copilot Agent Plugins 1.0 GA (2026-08-13)
    3. DeepSeek Harness (dsh) MIT open-source agent runtime (2026-08-14)
    4. OpenAI Codex subagents GA — manager agents spawn specialized subagents in parallel (2026-03-16; official @OpenAIDevs announcement, snowflake timestamp 2026-03-16T20:09Z, corroborated by media; verified 2026-08-18 as pre-coverage background)
    5. OpenCode experimental background subagents, primary/subagent structure (v1.14.51, pre-v1.18.x line; verified 2026-08-18 as pre-coverage background)
    6. OpenAI Codex CLI 0.148.0 stable ships codex exec fork session forking + async hooks that invoke MCP tools (2026-08-18T22:26Z, primary source, ev-20260818-02)
    7. Gemini CLI's main branch hosts packages/a2a-server (an A2A protocol server); nightlies from 8/14–18 reference a2a-server and SSR Agent (observed 2026-08-19 as early indication — upgraded to a stable artifact on 8/25, see item 11)
    8. Cursor's "Cloud Agents and Cursor Harness Improvements" lands always-on system primitives in the stable product: event-driven Subscriptions (subscribe to PRs/Slack/schedules and wake up; automatically drive self-created PRs to completion), VM-per-subagent isolation + swarm, /goal long-lived objectives, non-interrupt steering (2026-08-19, official changelog, ev-20260819-01)
    9. OpenAI Codex CLI 0.149.0 stable ships an interactive agents dashboard (search/start/open/rename/stop tasks — the first fleet-management UI in a stable CLI agent runtime) and codex queue (send messages into existing local/remote sessions; queued messages reliably wake idle sessions; duplicate-session-name resolution) (2026-08-20T21:04Z, primary source, ev-20260818-02 update)
    10. OpenAI Codex CLI 0.150.0 stable ships task-level @ references and inter-agent messaging — "ask agents to read, create, or message tasks": agent-initiated cross-task/inter-agent messaging lands in a non-Anthropic stable runtime; plus Interrupt hooks (commands/MCP handlers on turn interruption) (2026-08-26T19:37Z, primary source, ev-20260818-02 update)
    11. Gemini CLI 0.57.0 stable's release tag contains packages/a2a-server (an A2A protocol server), published to npm as @google/gemini-cli-a2a-server@0.57.0, with a wave of [SSR Agent] fixes merged — Google becomes the seventh organization with protocol-level inter-agent interop in a stable runtime (2026-08-25T18:37Z, primary source, ev-20260825-02)
  • Why established / High: Confirmation criterion (a) (agent-to-agent messaging semantics in a non-Anthropic stable runtime) is met by Codex 0.150.0 — agents can read, create, or message other tasks from the terminal, so inbox semantics are no longer Anthropic-only; in the same window Google shipped the A2A protocol server into the Gemini CLI stable line and published it on npm. Equivalent primitives are now verified across seven organizations (Anthropic, GitHub/Microsoft, DeepSeek, OpenAI, SST/OpenCode, Anysphere/Cursor, Google) in stable or installable artifacts, spanning March to August 2026. The engineering impact has landed: the orchestration plane is shifting from human-initiated sessions to resident, event-driven, interoperable task systems — multi-agent orchestration is becoming a built-in capability of CLI runtimes rather than a framework choice. Residual gaps (not blocking established, kept under watch): Google's a2a-server has zero documentation or announcement; public production case studies and adoption telemetry are still missing; on the Anthropic side, Claude Code 2.1.248 extended cross-session messaging to Bedrock/Vertex/Foundry and telemetry-off deployments (same-org hardening, not counted separately).
  • 2026-08-16 run: No new signals in window (no new Claude Code release; Cursor Builds default-on is 8/17, not yet in effect).
  • 2026-08-17 run: Cursor Builds became default-on for all environments as scheduled. But Builds is a warm-snapshot infrastructure improvement, not a multi-agent primitive, so it is not counted as evidence.
  • 2026-08-19 run: Two in-window evidence items added: (a) Codex CLI 0.148.0 stable ships codex exec fork plus async hooks that can invoke MCP tools (primary source); (b) Gemini CLI's main branch now hosts packages/a2a-server — early indication. Criterion (a) remained unmet at that point. Status/Confidence unchanged.
  • 2026-08-20 run: Upgraded to strengthening — Cursor's 8/19 stable release lands always-on system primitives (sixth organization, two new primitive types; official changelog as primary source). Criterion (a) remained unmet: Cursor Subscriptions are event-source wake-ups, not agent-to-agent messaging; Gemini CLI 0.56.0 stable shipped without a2a-server. Not upgraded to established (no public production case studies or adoption telemetry); confidence stays Medium.
  • 2026-08-21 run: One new in-window evidence item: Codex 0.149.0 stable ships the agents dashboard and codex queue. Criterion (a) partially met: cross-session messaging had landed in a non-Anthropic stable runtime, but user/orchestrator-initiated; agent-to-agent inbox semantics remained Anthropic-only. Not upgraded to established; confidence stays Medium.
  • 2026-08-22 run: No new in-window evidence. Claude Code 2.1.239's ListAgents/SendMessage improvements harden Anthropic's existing messaging primitive (same organization, not counted separately); Codex 0.150 remained alpha-only; Gemini CLI had no new stable (a2a-server still main-branch only). Criterion (a) unchanged. Status/Confidence stays strengthening / Medium.
  • 2026-08-24 run: No new in-window evidence. Claude Code 2.1.240/241 (8/22) are patch releases with no documented changes (same organization, not counted separately); Codex 0.150 remained alpha-only (no new stable); Gemini CLI had no new stable (a2a-server still main-branch only); Cursor's official changelog had no new entry. Criterion (a) unchanged: cross-session messaging had landed in a non-Anthropic stable runtime (recorded 8/21), while agent-to-agent inbox semantics remained Anthropic-only. Status/Confidence stays strengthening / Medium.
  • 2026-08-28 run: Upgraded to established / High: criterion (a) met — Codex 0.150.0 stable (8/26) ships task-level @ references plus agents reading/creating/messaging tasks (agent-initiated, cross-task inbox semantics), along with the Interrupt-hooks event primitive; in the same window Gemini CLI 0.57.0 stable (8/25) shipped a2a-server in its release line and published @google/gemini-cli-a2a-server@0.57.0 to npm (ev-20260825-02; Google as the seventh organization). On the Anthropic side, Claude Code 2.1.248 extended cross-session messaging to Bedrock/Vertex/Foundry and telemetry-off deployments, with 2.1.243/247/248 continuing to refine it (same-org hardening, not counted separately). Residual watches: Google's a2a-server is undocumented; no public production case studies or adoption telemetry yet.
  • 2026-08-29 run: No new cross-org evidence in-window. Codex 0.151.0 stable (8/29) landed the extensions middleware primitive (inspect/replace MCP tool results) and a configurable grace period for optional MCP server tool discovery; Claude Code 2.1.251 (8/28) landed PreModelSwitch/PostModelSwitch hooks and live streaming of a foreground subagent's tool calls to Remote Control clients — same-org hardening on both sides, not counted as new evidence. Residual watches unchanged: @google/gemini-cli-a2a-server still undocumented with no new stable (nightlies only since 0.57.0); public production case studies and adoption telemetry still missing. Status/Confidence stay established / High.
  • 2026-08-30 run: No new cross-org evidence in-window. Codex shipped only 0.151.0-alpha.7.2 (8/29 21:46Z, an alpha-channel patch with no documented changes); Claude Code has no new release (latest 2.1.251); Gemini CLI remains 0.57.0 stable + nightlies. Residual watches unchanged: @google/gemini-cli-a2a-server still undocumented with no new stable; public production case studies and adoption telemetry still missing. Status/Confidence stay established / High.
  • What would confirm: Met (2026-08-28): (a) Codex 0.150.0 stable inter-agent messaging + Gemini CLI a2a-server in stable. Remaining watch items: (b) whether community orchestration consolidates on a de-facto standard tool or named pattern; (c) public production case studies and adoption telemetry from ≥2 independent organizations

Invalidated / retired

(none)