Skip to main content

DVARA 1.9.0 — Govern coding agents, MCP and A2A

· 4 min read
DVARA Team
DVARA Team

Coding agents now make a large share of an engineering team's model calls. Most of those calls go straight from a laptop to a provider, outside your keys, policies, budgets and audit trail.

DVARA 1.9.0 brings them back onto the governed path. It also serves the newest MCP and A2A protocol versions, and it signs agent-to-agent delegation so each hop can prove whose authority it carries.

Govern coding agents​

Point a coding agent at DVARA, and every model call it makes goes through your keys, policies, guardrails, budgets, metering and audit. 1.9.0 supports:

  • Codex CLI, through the Responses API, on its default settings.
  • Gemini CLI, through a new Gemini API at /v1/gemini.
  • GitHub Copilot: the Copilot CLI and VS Code Copilot Chat's Custom Endpoint models.
  • OpenCode, through Chat Completions.
  • Cursor, as a preview, through a base URL at /v1/cursor, in chat and agent modes.
  • Claude Code, as before, through /v1/messages.

Copilot's inline completions, cloud agent and code review stay on GitHub. No gateway can govern them.

Tools that run at the provider, such as web search and code interpreter, are refused. DVARA cannot check what they do, so it does not let them through. Each setup page shows how to turn them off in the client. See Codex CLI, Gemini CLI, GitHub Copilot, OpenCode and Cursor.

Serve the newest MCP version​

DVARA now serves MCP 2026-07-28, the stateless version, beside 2025-11-25 and 2025-06-18. It passes the official MCP conformance suite.

Each governed server also has its own address, /mcp/{serverId}. A client that connects there sees just that server's tools, with their own names.

DVARA can now sign in to an upstream MCP server in more ways: static headers, OAuth client credentials, mutual TLS, AWS SigV4 and OAuth token exchange. See Authenticate to an upstream.

Speak A2A 1.0, and sign delegation chains​

DVARA serves A2A 1.0 by default, beside 0.3. Both official A2A SDKs and the official test kit pass against it.

When one agent hands work to another, DVARA now signs the delegation chain. It checks the chain at every hop, ties it to one workspace, and lets you revoke a single chain or everything one issuer signed. A hop that carries a signed chain cannot claim more authority than it was given. See the A2A delegation guard.

The Agent Card DVARA serves is written in your client's A2A version and signed. Flightdeck also adds an agent catalog, so you can register a known agent in one click.

Make passing on a caller's token a choice​

Some upstream servers and agents want the caller's own token. Sending it on unchanged lets anyone holding that token reach further than you meant. In 1.9.0 it is a choice you make on each server or agent, and each call that does it is recorded. Where the upstream supports it, DVARA can trade the token for a new one made only for that upstream.

See more of where spend goes​

Usage now shows spend by end user and by tag. It counts cached, cache-write and reasoning tokens, and the access log records them. A stream that fails is audited as failed, not as a served answer. Flightdeck warns you when a workspace's IP rules are saved but not enforced.

Read this before upgrading​

Check four things before you move production traffic:

  1. A refused A2A JSON-RPC call now answers HTTP 200, with the error in the JSON-RPC body, so the official SDKs can read it. A bad key still gets 401. Set a2a.protocol.json-rpc-error-status=refusal to keep the old status codes.
  2. Passing a caller's own token to an upstream is now an explicit, audited choice. The upgrade switches existing delegated servers and agents to it, so they keep working.
  3. Tools that run at the provider are refused on /v1/responses and the Gemini API.
  4. Workspace IP rules apply only when IP access is on at the Gateway, with DVARA_LLM_GATEWAY_IP_ACCESS_ENABLED=true.

Flightdeck applies the database changes when it starts. The upgrade guide has the details.

Try DVARA 1.9​

The images ghcr.io/dvarahq/dvara-gateway:1.9.0 and ghcr.io/dvarahq/dvara-flightdeck:1.9.0 and the Helm chart 1.9.0 are out now. DVARA Open Source 1.9.0 is out too: get the release, follow the Open Source quickstart, or book a walkthrough of the Enterprise platform.