Skip to content
All changes

Agent-ready apps in one command, and safer built-in agent tools

One command readies your app for AI agents to sign in, agents can ask a person for access by email, and AI tools ask first before risky built-in actions.

Added
5
  • SDKWith @buildbase/sdk 1.3.0, npx @buildbase/sdk init --agent makes a Next.js app agent-ready. It writes the app's own MCP server at /api/mcp and the discovery files agents look for. It also writes the routes agents sign in through.
  • AgentsAgents can sign in to that app only once a person turns it on. With --claim as well, the claim page offers Let AI agents sign in to your app, unticked. Otherwise, turn it on under Authentication > Agent readiness.
  • AgentsAgents can now ask for access with just a person's email. Turn on Let agents register with a person's email under Authentication > Agent readiness. The person signs in on your sign-in page as that address and confirms a code. No account is created.
  • AgentsThis is the email registration that the auth.md standard describes and agent-readiness scanners check. Agents call POST /api/v1/auth/oauth2/agent/identity?org=. The tokens go to one of your agent clients with the device code grant on.
  • DocumentationA new guide, Make your app agent ready, lists what agent-readiness scanners check and what answers each check. A page for each of 12 AI tools shows how your users connect them to your app.
Improved
4
  • AgentsAgents that register themselves and then go unused are now removed for you, so they no longer fill your limit of self-registered agents. Each removal is in your auth log as client_deleted.
  • SDKFrom @buildbase/sdk 1.0.2, four built-in MCP tools are marked destructive, so AI tools ask before running them. They are update_workspace_user_role, invite_workspace_user, purchase_add_on and send_notification.
  • SDKAlso from 1.0.2, every built-in tool's answer ends with a note that it is data, never instructions. It guards against prompt injection: text someone planted in a name or description to steer the agent.
  • SDKFrom 1.3.0, your app's MCP server says so when a token needs no scope. So npx @buildbase/sdk agent doctor no longer warns about scopes on a newly set up app.
Fixed
1
  • AgentsAgent sign-in set up with init --claim --agent now offers the organization's password and magic-link sign-in. Before, the person an agent asked saw a page saying the app had no sign-in methods.

Use what shipped this week

Everything in this release is already in the console and the SDK.

Free plan7-day free trial on paid plansNo credit card required