AI product updates, June 20: Hermes reaches messaging apps, GLM-5.2 targets long coding runs
A quieter release day still brought useful developer updates: Hermes Agent v0.17.0 expands into messaging and async work, Z.ai ships GLM-5.2 for 1M-token coding, Pay.sh adds human approval gates for agent payments, and Apple’s Core AI push gets clearer.
A quieter release day still delivered the kind of infrastructure updates that change how AI products get used: agents reached more messaging surfaces, coding models pushed harder into long-context engineering work, payment flows added explicit approval gates, and Apple’s local-inference stack became easier to classify.
Today’s verified product changes
| Update | Releasing entity | Release date | What changed | Availability |
|---|---|---|---|---|
| Hermes Agent v0.17.0, 「The Reach Release」 | Nous Research | June 19, 2026 | A large agent-platform release adds iMessage support through Photon Spectrum, a Raft gateway, desktop-app upgrades, background subagents, image-to-image editing, Automation Blueprints, WhatsApp Business Cloud API support, richer Telegram formatting, Skills Hub security scans, and memory atomic batch operations. | Public GitHub release and update path for Hermes users. 1 |
| GLM-5.2 | Z.ai | June 17, 2026 | Z.ai positions GLM-5.2 as a flagship open-source model for long-horizon work, especially coding and sustained engineering tasks, with a 1M-token context window and claimed efficiency gains from IndexShare and MTP improvements. | Available through GLM Coding Plan, chat.z.ai, ZCode, Hugging Face and ModelScope weights; MIT licensed, according to Z.ai. 2 |
| Pay.sh v0.19.0 and v0.20.0 | Solana Foundation | June 16 and June 18, 2026 | The agent-payment stack added Qoder IDE/CLI setup, fail-closed behavior when a metered endpoint has no payment backend, elicitation tooling, and a later preference for Sign-In-with-X spend credits over paying. | Public GitHub releases; Solana Compass published a detailed explanation of the human-approval flow. 34 |
| Core AI positioning after WWDC | Apple | Reported June 20, 2026 | Apple’s Core AI is being described as the successor path for neural networks and transformers, while classic non-neural machine-learning workloads remain on Core ML. The official Apple documentation fetched this round only confirms the base description: running AI models in apps on Apple silicon. 5 | Apple silicon only, according to InfoQ’s developer-focused report. 6 |
| GitHub Issues duplicate detection and MCP issue fields | GitHub | June 18, 2026 | GitHub put duplicate issue detection into public preview and added issue-field support to the GitHub MCP server, so connected AI tools can read, write, and filter issue fields such as priority, area, and dates. | Public preview for duplicate detection; MCP field support available through GitHub’s MCP server. 7 |
Lead update: Hermes turns into a cross-channel agent surface
Hermes Agent v0.17.0 is today’s most practical release because it is less about one model and more about where an agent can operate. Nous Research says the release covers roughly 1,475 commits, 800 merged pull requests, 1,693 changed files, more than 235,000 insertions, more than 50,000 deletions, 300-plus closed issues, and 245 contributors. 1
Loading content card…
The important product direction is reach. Hermes adds iMessage through Photon Spectrum, an official WhatsApp Business Cloud API adapter, and richer Telegram Bot API 10.1 formatting. 1 That moves the agent closer to everyday work channels instead of requiring the user to stay inside a dedicated chat or IDE interface.
The second direction is background work. The release expands background and asynchronous subagents, while also adding desktop improvements, image-to-image editing, Automation Blueprints, Skills Hub redesign and security scanning, memory atomic batch operations, secure dashboard authentication, and cost optimization for curator workflows. 1 The official announcement on X describes the release as 「The Reach Release」 and points users to the same GitHub release trail. 8
Loading content card…
For teams already testing agentic workflows, the read is simple: Hermes is becoming a coordination layer across messaging, automation, memory, security, and desktop execution. The next question is less 「can it call tools?」 and more 「can an organization govern what it can do across all the places employees already work?」
Model update: GLM-5.2 aims at long coding runs
Z.ai’s GLM-5.2 is the most relevant model-side update in this sweep. Z.ai describes it as a flagship model for long-horizon tasks, particularly coding and sustained engineering, with a 1M-token context window. 2 The company says IndexShare reduces per-token FLOPs by 2.9 times at 1M context and that its MTP work raises acceptance length by up to 20 percent. 2
The benchmark claims are notable but should be treated as vendor claims until broader independent testing catches up. Z.ai says GLM-5.2 reaches 74.4 on FrontierSWE, which it calls the highest-ranked open-source result, plus 81.0 on Terminal-Bench 2.1 and 62.1 on SWE-bench Pro. 2
Availability is broad enough to matter for developers: Z.ai lists GLM Coding Plan, chat.z.ai, ZCode, Hugging Face and ModelScope weights, and compatibility with Transformers, vLLM, SGLang, xLLM, ktransformers, ZCode, Claude Code, and OpenCode. 2 The MIT license is also important because it lowers the friction for product teams that want to evaluate a long-context coding model outside a fully closed API.
Agent payments: Pay.sh adds approval and fallback discipline
Pay.sh’s v0.19.0 release is a small release with a high-signal safety pattern. The release adds
pay qodercli, Qoder IDE/CLI setup integration, and CI tooling around elicitation and pay skills. It also makes the server fail closed when a metered endpoint has no payment backend. 3Loading content card…
The mechanism matters because agentic products are starting to call paid APIs on a user’s behalf. Solana Compass explains that when an AI agent initiates a paid API call through MCP, Pay.sh pauses before USDC moves. It prioritizes biometric approval and falls back to MCP
elicitation/create when biometrics are not available. 9 After the user accepts, the implementation still checks approved=false, and timeouts or transport failure prevent signing rather than defaulting to payment. 9The v0.20.0 follow-up changes payment preference by favoring Sign-In-with-X spend credits over paying. 4 That is not a public pricing change, but it is a product-behavior change: the stack now tries to spend an existing credit path before invoking a payment path.
Apple Core AI: clearer local-inference boundary
Apple’s own Core AI documentation fetched for this issue is sparse; it only gives the high-level description that Core AI lets developers run AI models in apps on Apple silicon. 5 For the fuller developer interpretation, InfoQ reports that Core AI is the successor direction for neural networks and transformers, while Apple still recommends Core ML for classic non-neural machine-learning tasks. 6
InfoQ also reports that Core AI targets iPhone, iPad, Mac, and Vision Pro on Apple silicon, supports model sizes from 3B vision models to 70B reasoning LLMs, and offers a unified API across CPU, GPU, and Neural Engine with Swift APIs, zero-copy paths, ahead-of-time compilation, PyTorch conversion, compression, and model-cache specialization. 6
For product teams, the practical implication is not that every app suddenly ships a frontier model locally. It is that Apple is trying to make the local path clearer for privacy-sensitive, offline-capable, or per-token-cost-sensitive features.
GitHub Issues: useful, but a follow-up rather than today’s lead
GitHub’s June 18 changelog adds two practical project-triage features. Duplicate issue detection is in public preview and can suggest up to three possible matches while a user is creating a new issue. 7 GitHub also says AI tools connected through the GitHub MCP server can read and write issue fields, letting agents update structured fields such as priority, area, and dates, or filter issues by those values. 7
This overlaps with yesterday’s GitHub coverage, so it belongs here as a short operational update rather than the lead. The durable point is still important: issue trackers are becoming writable structured surfaces for agents, not just places agents summarize.
What to watch next
- Hermes governance: messaging support and background subagents raise the value of audit logs, permissioning, and enterprise policy controls.
- GLM-5.2 independent testing: the 1M-token and coding claims are strong enough to watch, but they need outside evaluation across real repositories.
- Pay.sh MCP client support: human approval is only useful if enough agent clients implement it cleanly.
- Apple Core AI adoption: the key signal will be whether developers ship local model features that were previously too expensive, private, or latency-sensitive to run through cloud APIs.
Not included today: Google Workspace search snippets were visible during research, but the official update page and Atom feed were not readable enough to verify a fresh entry. I am not treating snippets alone as product-update evidence.
References
- 1
- 2Z.ai GLM-5.2 blog on Hugging Face
huggingface.co
- 3Solana Foundation pay v0.19.0 release
github.com
- 4Solana Foundation pay v0.20.0 release
github.com
- 5Apple Core AI documentation
developer.apple.com
- 6
- 7
- 8
- 9
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.