Changelog

Connector setup without secrets, a default helper library, and tighter controls for admins all land in this release.

• Credential-free connector setup: the agent can now create API-key and OAuth connectors, up to 20 in a batch, with no secret anywhere in the conversation. Each one comes back with a dashboard link where an admin enters the credential.
• 132 ready-made helpers across 19 connectors, including Google Workspace, Slack, GitHub, Notion, Jira and HubSpot, each kept within that connector's default scopes. Helpers are opt-in per organization.
• Three-layer URL containment on helpers: checked when a helper is saved, enforced in the sandbox at run time, and enforced again by the proxy.
• Redaction settings via MCP: org admins can read and update PII redaction rules from the AI client, with merge semantics so existing rules are never overwritten.
• Per-web-app audit: every call an org web app makes is logged as its own row and attributed to that app in API usage.

Read more in the docs: https://docs.keyboard.dev/docs

This week: connectors your agent can set up without ever seeing a secret, redaction rules you can manage from chat, and an audit trail for every web app.

• Credential-free connector setup: your AI agent can now set up API-key and OAuth connectors, up to 20 at a time, without a secret ever appearing in the conversation. Each one comes back with a dashboard link where an admin enters the credential.
• Redaction settings from your AI client: org admins can review and update redaction rules without leaving the chat. Changes merge with existing rules instead of replacing them.
• Per-web-app audit: every call an org web app makes is logged as its own entry, and each app's admin page shows who built it, who published it last, what it connects to and who can open it.
• Usage by app: API usage now records which web app made each call, so usage can be broken down by app.
• Newer models selectable: the latest model releases can be added to your organization's allow-list from the model picker.

Read more in the docs: https://docs.keyboard.dev/docs

The admin home page now opens with what needs your attention, with faster ways to scan the rest.

• Needs attention, first: the admin home page now leads with cards for teams over or near their limits, flagged and failed AI actions, overdue or due-soon access reviews, connectors failing on 5% or more of API calls, API usage outliers and available updates. It says "All clear" only when the checks actually ran.
• At a glance: 30-day tiles for AI events, AI spend, active users and policy coverage, each compared with the previous 30 days, next to a 7-day AI activity chart, team usage against limits and top connectors.
• Accurate team limits: team usage is now measured in the same unit as the limit, fixing teams that wrongly appeared far over their limit.
• Sortable tables: click a column header to sort almost any table in the dashboard. Status and risk columns sort by severity.
• Release discovery for self-hosted installs: standard update tools can now see which Keyboard releases are available, so new versions can be detected and proposed.

Read more in the docs: https://docs.keyboard.dev/docs

This release brings apps your agent can build and share, a leaner starting context, and a guided path to self-hosting.

• Org web apps: your AI agent can build an app, publish it to your organization's own Keyboard web app site and hand back a link. Share it org-wide or with specific teams and people, and choose who else can manage it. Web apps stay off until an org admin turns them on.
• Compact starting context: admins can switch on a compact mode where the agent starts with app names and flags, then fetches full details only when a task needs them.
• Tagged org notes: admins can tag notes by topic. The agent sees a topic index up front and is told to read the relevant notes before it starts work.
• Guided self-hosting setup: choose your cloud, how to deploy and the shape of the deployment, then follow only the steps that apply, as a checklist that ticks off from live status.
• Self-service sign-in URLs for self-hosted orgs: admins register their own callback URLs, each bound to the organization that owns it.

Read more in the docs: https://docs.keyboard.dev/docs