Skip to content

v1.2.0: external agents, MCP over HTTP, secrets, and AI Act Art. 50 - #96

Merged
antiv merged 1 commit into
mainfrom
claude/v1.2.0-changelog
Sep 3, 2026
Merged

antiv merged 1 commit into
mainfrom
claude/v1.2.0-changelog

Conversation

@antiv

@antiv antiv commented Sep 3, 2026

Copy link
Copy Markdown
Owner

Summary

Release v1.2.0 adds support for external agents (pointing at any OpenAI-compatible endpoint), MCP over HTTP, environment variable secrets in config, and EU AI Act Article 50 compliance features (AI disclosure and generated image marking).

Changes

  • External agents — agents can now point to an OpenAI-compatible endpoint via model_base_url and model_api_key, applying RBAC, guardrails, evals, versioning, audit, and cost tracking without requiring agents to be built in MATE
  • MCP over HTTP — external MCP servers with a url are reached directly over HTTP/SSE instead of spawning npx mcp-remote as a subprocess; stdio servers unchanged
  • ${VAR} secrets — MCP server entries and agent endpoint keys can reference server environment variables, keeping credentials out of the database and config exports; unset variables skip the server or refuse to build the agent
  • AI disclosure (Art. 50) — the widget tells users they are talking to an AI by default; no on/off switch, only a waiver field that records why the notice was hidden, preventing decision and justification from separating
  • Generated image marking (Art. 50(2)) — PNGs carry an XMP packet with IPTC trainedAlgorithmicMedia marker ahead of the 2 December 2026 deadline
  • MCPToolset renamed to McpToolset — ADK 2.3 keeps the old name as a deprecated subclass for backward compatibility
  • Security hardening — provider keys no longer follow external agents to third-party hosts; unresolvable ${VAR} references refuse to build; stored endpoint keys never reach the browser
  • Documentation — added documents/AI_ACT.md explaining what applies when and what MATE does and does not do about compliance
  • Integration test — new test against a live OpenAI-compatible endpoint proves configured host, credential, and usage object cross the wire correctly

Notes

The AI Act features are defaults that point the right way; they do not make anyone compliant. Compliance obligations sit with the provider or deployer of a system, not the framework. The audit trail and waiver mechanism ensure decisions and their justifications are recorded and cannot come apart.

The external agent path is the primary focus for feedback — testing against whatever endpoint you're running is most valuable.

https://claude.ai/code/session_01ToCUNy2SqwvfTq4a6xfSk1

Covers everything merged since 1.1.0: external agents behind an
OpenAI-compatible endpoint, MCP over HTTP, ${VAR} secrets, Art. 50
disclosure and image marking, plus the corrected compliance wording and
the README demo links.

The security section is separate rather than folded into Added, because
two of those entries describe credentials that used to be able to leave
the host and now cannot.

The announcement leads with the external-agent change rather than the
feature list. It is the one that answers "why would I rebuild my agents
to try your dashboard", which is the question the project has been
failing to answer for six months. The Art. 50 wording says explicitly
that MATE does not make anyone compliant.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ToCUNy2SqwvfTq4a6xfSk1
@antiv
antiv merged commit 81788cf into main Sep 3, 2026
1 check passed
@antiv
antiv deleted the claude/v1.2.0-changelog branch September 3, 2026 04:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants