# Roadmap

Say what the latest Straza release added, what is confirmed for the next two months and what is planned after that.


Only confirmed work carries a month, and only for the next two months. A month is an estimate, and each release dates the next two months again. Everything else is planned and has no month yet.

## New in 2.2.0

| Feature | What you get |
|---|---|
| Microsoft Entra Agent ID | An AI agent acts as its own Entra agent identity at an MCP server. Straza gets the agent that identity's token through its agent blueprint, so the server sees the agent and not a shared account. |
| The agent's Entra identity on its record | An agent's record names the Entra agent identity it acts as. SCIM, the admin API and `strazactl` write it, and the console shows it. |
| Sign in through Microsoft Entra | A person enrolls a machine with their Entra account. |
| Signing keys in the console | An administrator promotes the key Straza signs client assertions with, and each key carries a certificate for Entra. |

## December 2026

| Feature | What you get | Status |
|---|---|---|
| Confirm a new device | A new machine, phone or browser starts working only after you confirm it on a device you already enrolled. This closes a [known limit](https://docs.straza.ai/security/security-model/index.md#known-limits). | designing |
| Approver certificate rotation | A rotated server certificate announces its successor, so enrolled phones keep working without a new enrollment. | designed |
| Readable requests on the phone | The approver app lays out what a held call does in plain fields, as the console's record sheet does, with the raw arguments one tap away. | planned |
| Call outcomes and token usage | Each MCP call's record gains its duration and outcome, and each recorded turn gains the model and its token usage, so analytics has history from the first day. | designed |
| MCP server from an OpenAPI file | You import an OpenAPI file and Straza serves its operations as MCP tools, listed by role, decided by policy and recorded like any other tool. | planned |

## January 2027

| Feature | What you get | Status |
|---|---|---|
| Strazalytics | Statistics per agent, machine and MCP server: calls, denials, approval times and failures. It runs as a separate, optional service that reads Straza's event stream. | designed |
| Linux package repositories | apt and dnf repositories with a signing key, so a machine updates the Straza client like any other package. | planned |
| Signed Windows installer | The MSI and the Windows binaries carry an Authenticode signature. | planned |
| Pinned connections | A client pins the server's TLS key at enrollment and refuses any other, and a device-bound certificate adds to attestation. | designed |
| MCP revision 2026-07-28 | The gateway speaks the current MCP revision to clients and servers. | planned |
| MCP prompts and resources | The gateway governs prompts and data resources as it governs tools: listed by role, decided by policy and recorded. | designed |

## Planned

These items are accepted and have no month yet. Each gets one when it is confirmed for the next two months.

| Feature | What you get | Status |
|---|---|---|
| Passkeys | A deployment that uses Straza as its own identity provider signs people in without passwords. | planned |
| Approver app on F-Droid | The Android approver app is also published on F-Droid. | planned |
| Approver app redesign | The approver app on iPhone and Android gets a new design, so a request is quicker to read and to decide. | planned |
| Signed app manifests | A server manifest installs only when its publisher's signature verifies. | planned |
| Egress allowlist per MCP server | Each governed MCP server reaches only the hosts you list. | planned |
| Git for Codex CLI and Gemini CLI | Git through a Straza grant works in Codex CLI and Gemini CLI as it does in Claude Code, inside their sandboxes on Windows too. | planned |
| Cells | Independent deployments, each with its own database and event spine, under one identity manager, for residency, a regulated business unit or size. | designed |
| Kubernetes operator | Custom resources make a cell declarative, so access and policy come from configuration, as MCP servers already do. | planned |
| Full lifecycle of autonomous agents | An AI agent's identity is bound to its workload, with attestation of the image each session ran in. Creating and retiring an agent from the identity manager already works. | planned |
| Microsoft Teams approvals | A person decides a held call in Teams, as they can in Slack today. | planned |
| Agents inside WSL2 | An agent a person starts inside WSL2 is governed by the Straza service on Windows, as an agent on Windows itself is. | planned |
| Cursor | Cursor joins Claude Code, Codex CLI and Gemini CLI under the harness hooks. | planned |
| A2A | Straza decides and records calls between agents over the A2A protocol, as it does tool calls. | planned |
| AI agents as approvers | A rule can name an AI agent as a decider of a held call. It is off unless a policy turns it on, and the record names the agent that decided. | planned |
| AI classifier | A rule can send a call to a model you run, which answers allow or deny with a reason. It is off unless a policy turns it on, and the built-in check with no model stays the default. | planned |

## How to read this page

Designed means a written design exists, and planned means the work is accepted and waits for its design. Every item gets a written design before code, and each lands whole with its tests and the pages that describe it. When an item ships, it moves to the [changelog](https://docs.straza.ai/project/changelog/index.md) and leaves this page.



