Skip to main content

October 23, 2026

Highlights​

Another strong week of polish and admin tooling. Here is what matters most:

  • Org admins: member lists that are easier to scan, plus allocation emails that close the loop. Sort members by when they joined or last login, and when you raise someone's spend allocation they get an email confirmation instead of wondering whether anything changed.
  • Builders and platform teams: OAuth for custom deployments. Protect private APIs behind OAuth client credentials, with guided setup for Microsoft Entra ID, so deployed apps can authenticate without hard-coded secrets in plain text.
  • Everyone: chat and texting that feel more dependable. Smoother handling for spreadsheets and uploaded files, fewer surprises on mobile while tool-approval cards catch up, and SMS conversations that resume more naturally after you step away.

Read on for agent usage charts, Office add-in polish, and knowledge indexing improvements.

New features​

Know when a member's allocation goes up​

When an administrator increases a team member's personal spend allocation, that person now receives an email letting them know their limit was raised, with context about the organization and balance type.

Admins still manage limits in Usage & Billing; members get a clear signal that they can keep working without filing another request.

Sort your member directory​

The organization Members table now supports sorting by Joined and Last login, with paging that stays stable as you move through long rosters.

Use it to spot inactive accounts, onboard recent hires, or audit who has been active lately.

OAuth authentication for custom deployments​

Custom deployments can call APIs that require OAuth 2.0 client credentials. In organization settings you can configure the token endpoint, scopes, and credentials (including Entra ID-style setups), and Devs.ai attaches short-lived bearer tokens when your deployment runs.

This is for teams shipping apps on Devs.ai that need to reach protected backends without embedding long-lived API keys in code.

User message activity on agent usage​

On an agent's Usage tab, you can now see how many user messages the agent received, including a daily chart over the selected period.

It helps builders and admins understand engagement beyond token spend alone.

Improvements​

  • Knowledge sources that stall during indexing are reclaimed automatically so search and RAG stay fresher without manual cleanup
  • Office add-in task pane layout refinements for a cleaner editing experience
  • Global header renders once per page load for snappier navigation
  • Voice chats keep the same model access as the parent conversation when you switch modes
  • SMS and messaging channels infrastructure aligned with the main product release train for faster, safer updates

Bug fixes​

Reliability fixes across chat (spreadsheet delegation, sandbox file routing, inline text for more models), SMS and carrier messaging (STOP/YES handling, retries, and delivery budgets), custom deployment credential forms, tool approval on mobile, and agent usage display. Together they should reduce odd edge cases during everyday use.

⌘J