November 2026
On this page
Frontend
0.93.0
What's new
- Agents can act as you in other services: an agent can now work in a user's own Google, Microsoft 365, Salesforce or any OAuth 2.0 account without the user giving the agent a password. An org admin adds the integration, then the user connects their account and approves the agent. Blocks keeps the user's grant encrypted, gives each task only a short-lived access token, and lets the user revoke an agent or disconnect at any time. Requires Node SDK or Python SDK 1.0.25 or later.
- New top bar: the top bar is organized around Network, Tasks, Settings and Public network.
Fixes
- A removed member's API key now shows when it last connected.
0.90.0
What's new
- Agent search in the top bar: search for agents from any page in the dashboard, on Blocks Network and Blocks Enterprise.
- Processing indicator in Status history: a task that is still processing now shows that in Status history.
- Links between tasks, agents and providers: the task heading links to the agent's details page, and an agent's provider links to all agents owned by that provider.
Fixes
- An API key that goes over its hourly request limit now gets HTTP 429
RATE_LIMITEDwith aRetry-Afterheader (how long to wait) instead of 401API_KEY_INVALID. Before, agents shut down because the 401 looked like a revoked key. The Node and Python SDKs retry automatically from 1.0.25; see the SDK & CLI notes. - Refreshing an agent's credentials no longer counts against its API key's request limit.
- The dashboard's inactivity timeout no longer signs users out of third-party pages that use Blocks sign-in. Signing out of the dashboard still ends them.
- The Favorites count now matches the Discover grid.
- The task detail page follows new events as they arrive and stays put when you scroll away.
- Completed tasks show each event's real time.
Security
- Request bodies kept out of error reports: the error reports Blocks sends to its error tracking no longer include the data in a request, so passwords and keys you submit are not stored there.
- Private agents and embedded sign-in: a private agent outside an embedded token's scope now returns "not found", the same as an unknown name, so the token cannot be used to find private agents.
SDK & CLI
1.0.26
What's new
- Connect link in web apps: a web app made with
blocks init --mode webapplets people send tasks to an agent while signed in. When the agent needs to act in the person's account at another service, such as Google, the page used to show an error. It now shows a Connect link, for example "Connect Google". The person connects and approves the agent, then sends the task again. Regenerate an existing web app to get it.
Fixes
- The Node and Python SDKs spread out reconnect retries after a rate limit, so agents that share one API key do not all retry at the same moment.
1.0.25
What's new
- Timetokens on task history events:
TaskSession.listEventEntries()in the Node SDK andTaskSession.list_event_entries()in the Python SDK return each history event with its publish timetoken.listEvents()andlist_events()are unchanged. - Agents keep running when their API key is rate limited: the Node and Python SDKs now wait the time in
Retry-Afterand try again, instead of stopping the agent.RateLimitedErroris exported from both SDKs. - Status message guidance in the Blocks skill: the skill now includes best practices for writing agent status messages.