Changelog

Coworker agents in Teams and your own KMS keys

Talk to your coworker agents in Microsoft Teams

Organizations that work in Microsoft Teams couldn't hand work to a coworker agent without switching to Slack. Your coworker agents now work in Microsoft Teams too: message an agent in a Teams chat and it replies in the thread with a live status card and a Stop button, running as the teammate who sent it.

Each agent's bot is created inside your own Microsoft tenant, so the install stays in your environment. It is in early access while we finish self-serve setup, so email founders@mintive.com and we will connect it for your tenant.

Docs: Coworker agents overview

Hold the encryption key to your own data

Security teams want to be able to cut off a vendor's access to their data without waiting on the vendor. You can now encrypt the connector credentials your users and agents store in Mintive with your own AWS KMS key, managed entirely in your AWS account.

Point us at your key and role from Enterprise settings, run the verification test, and enable it: credentials saved from then on are wrapped under a key only you control, and you can change or revoke it yourself. It is an Enterprise feature we turn on per organization.

Docs: Customer-managed encryption

Give auditors a read-only view of every MCP in your org

The people who audit what is connected usually shouldn't be able to change it. You can now grant a read-only, role-based view that sees every MCP across your organization: its configuration, saved tools, access lists, and full change history, with call and edit rights left off.

It is built for security and compliance reviewers. Assign it from your custom roles.

Docs: Roles and permissions

Also in this release

  • Triage what Mint Guard catches

    Mint Guard scans your agents' tool traffic for prompt injection and blocks it in enforcing mode. The new Review tab collects each high-confidence detection, so your security team can mark it benign or resolved with a note and keep an auditable record in the audit log and SIEM.

  • Custom instructions for any connector

    Write server instructions for a connector or a bundle from the tool customization tab, and Mintive serves them to the agent's client, coworker agents included.

  • Agent access maps

    Each coworker agent opens to a Visualization tab: a map of who can reach it, which triggers and Slack channels fire it, and every connector it can call with live tool counts, alongside its model, workspaces, and secrets.

  • Agent Monitor shows more

    See the actual prompt behind Claude Code and Codex runs, and who triggered each coworker agent run.

  • More in your SIEM

    LLM Gateway calls export as OpenTelemetry GenAI traces, audit logs now stream to Azure Monitor and Microsoft Sentinel, and the caller's IP lands on every activity event.

  • More coding agents governed

    OpenCode and Claude Desktop join Cursor, Claude Code, and Codex as agents Mintive governs.

  • Bedrock, GCP, and Azure, standard

    Amazon Bedrock is now a standard provider in the LLM Gateway, and you can pull connector and agent credentials from GCP Secret Manager or Azure Key Vault without asking us to switch them on.

  • Admin API with scoped keys

    Manage Mintive programmatically with bearer API keys scoped to specific permissions, against a published OpenAPI spec.

  • Require user approval, as a rule

    "Require user approval" is now a first-class rule action, so you can gate specific tool calls on a human sign-off.

  • The CLI is now mintive, and the portal can be yours

    The installed mintmcp CLI is renamed mintive (with a mintmcp alias so existing setups keep working), and organization white-label settings put your own logos across the app and the login portal.

Run your agents on Mintive

Connect your agents, tools and models through one gateway, and see every call in the log.

No sales call needed!