Claude Updates & Release Notes
192 updates curated from 106 sources by the Releasebot Team. Last updated: Nov 13, 2026
- Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Operate Claude Managed Agents inside your security perimeter
Claude releases self-hosted Managed Agents in private beta, letting teams run the full agent service in their own cloud or on-premises environment. Organizations control credentials, session history, and where model requests go, with security and activity tracking built in.
Introducing self-hosted Claude Managed Agents. Now you can run agents in your own environment, whether that’s in your own cloud or on-premise. You host the agents, credentials, and session history, and choose where requests to Claude are sent.
Self-hosted Claude Managed Agents is now available in private beta. Developers can build agents that work directly in their company's code and internal systems, and run those agents in their own environment.
Self-hosting is a new way to run Managed Agents, a suite of composable APIs for building and deploying autonomous agents. Managed Agents provides the agent harness, sandboxes, credential handling, and session history to get long-running agents into production.
Run your agent control plane in your own environment
We first launched Managed Agents as a hosted service on the Claude Platform, where Anthropic runs the infrastructure for you. For teams who needed their code to stay in their own environment, we added self-hosted sandboxes.
Since then, agents have become more capable and are taking on more critical work, like fixing broken builds, testing releases, triaging alerts, and working through your bug backlog. They run unattended on your code and need access to your internal systems. For agents with that level of access, some teams want the whole service in their own environment, not just the sandbox. Until now, that meant building the platform themselves.
With self-hosted Managed Agents, every part of the service runs in your own cloud or on-premise, including the harness, sandboxes, credentials, and session history. You operate the Managed Agents server, its database, and the workers where agents run their shell and file tools. Model requests go where you choose, whether that's Anthropic directly, your cloud provider (Amazon Bedrock, Google's Agent Platform, or Microsoft Foundry), or your own gateway. Your developers still build agents with the same core APIs as the hosted Managed Agents service.
Session history is stored in your own database. If your organization has zero data retention (ZDR) in place with Anthropic, it applies to the requests sent to Claude in the same way as any other Messages API call.
Designed for agent security
When an agent runs unattended inside your code and systems, you can't rely on a person checking every step, so the limits have to be built into the system itself. That's why agent security starts with architecture, and why we designed Managed Agents around four principles. These principles apply whether Anthropic hosts everything, you host just the sandbox, or you host the whole service.
The brain and the hands are split
The harness (the brain) calls Claude, and the sandbox (the hands) is where the agent's code runs. They are kept separate by design. The agent's code runs in the sandbox, while the agent loop, session history, and vault secrets stay outside it. Separating them also means an agent doesn't depend on one sandbox surviving its whole run, sandboxes start only when a tool needs them, and session history lives outside the sandbox as an event log.
Credentials stay out of the sandbox
Vaults are designed to keep credentials out of the sandbox. For MCP tools and supported API calls, a proxy outside the sandbox adds the credential to the request. With self-hosted Managed Agents, you can also store credentials in your own secrets manager.
Network access can be limited
You can limit each environment to a list of allowed hosts, and requests to any other host are blocked. For an agent that fixes broken builds, that list might be just your git host and your package registry. When you host the sandbox yourself, you set the same limits in your own firewall.
Every session leaves a full record
Managed Agents keeps a record of every step an agent took, including the tool calls it made and what came back. The record exports over OpenTelemetry, so you can send it to the monitoring tools you already use and review agent activity alongside the rest of your systems.
Get started
Self-hosted Claude Managed Agents is now available in private beta. Contact your Anthropic account team to request access, or read the docs to learn more.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Introducing Claude for Manufacturing
Claude launches Claude for Manufacturing, a plugin with 17 skills and connectors to Autodesk Fusion, Infor, Microsoft 365, and Oracle NetSuite. It helps teams draft quotes, investigate quality issues, diagnose breakdowns, and prepare reports, with people reviewing work before it is sent or applied.
A new plugin with 17 skills and four connectors helps manufacturers draft quotes, quality reports, and supplier requests from the systems they already run.
Today we’re launching Claude for Manufacturing, a plugin that includes skills for work from pricing a new job to diagnosing a stopped machine. An estimator can now have Claude read a customer’s request, compare costs on similar jobs, and draft the quote. The plugin works from a manufacturer’s own records through connectors to Autodesk Fusion, Infor, Microsoft 365, and Oracle NetSuite. Claude for Manufacturing is built so the person responsible can review and approve the work before it reaches a customer or supplier.
Manufacturing teams can spend much of the day gathering information. In a 2025 Manufacturing Leadership Council survey, 79% of manufacturers said they enter data manually. With Claude carrying each process to the point of review, an estimator can focus on the price, a quality engineer on the fix, and a technician on what to check first.
Skills built for manufacturers
The plugin’s 17 skills cover sales, quality, operations, supply chain, design, and setup. Some handle a single task, while others run several in order, so Claude can carry a job through several steps until a person needs to review it. The skills can run processes that include:
- Quoting a new job: An estimator can ask Claude to read a customer’s request, list what’s missing, compare costs on similar jobs, and draft the quote for release.
- Investigating a failed inspection: A quality engineer can have Claude document the failure, check past reports for the same problem, rank the likely causes, and draft the corrective action report.
- Diagnosing a breakdown: A technician can have Claude read the sensor exports, repair notes, photos, and manual, then rank the likely causes for the technician to check and decide on next steps.
- Sourcing from another supplier: A buyer can have Claude prepare the request for quotes, then compare the bids that come back.
- Comparing designs with Autodesk Fusion: An engineer can have Claude generate variations from an existing model, score them against the engineer’s targets, and draft a decision memo.
- Reporting on production: A plant manager can have Claude compile production data into one report showing output against target, equipment downtime, and what the downtime and missed output cost.
These skills are a starting point. Organizations can build on them to fit their specific operations, and we plan to add new manufacturing skills over time.
Connectors to manufacturing systems
Claude for Manufacturing works with the software at the core of manufacturing operations, and that software stays central to how teams run the business:
- Autodesk Fusion: Engineers can compare more design options before choosing one, because Claude generates variations from their existing model.
- Infor: Buyers and planners can check purchase orders and stock before they act, because Claude looks them up in Infor.
- Microsoft 365: Quality engineers can bring procedures, supplier emails, and exported reports into one job, because Claude finds them in shared folders and inboxes.
- Oracle NetSuite: Estimators can price new work against actual orders, inventory, production steps, and job costs, because Claude pulls those records when it drafts a quote.
Manufacturers can also use the plugin with systems that have no connector. They save regular exports from those systems to Microsoft 365, and Claude works from the files to draft a quote or compile a production report.
Making changes in Infor with Claude
Infor, which makes core software for manufacturers, is also releasing its own plugin. With the Infor connector in Claude for Manufacturing, teams can look up records. With Infor’s plugin, they can also make changes in Infor from Claude.
For example, if a steel shipment slips by two weeks, a buyer can ask Claude which customer orders are affected and how much steel other sites have. Once the buyer approves, Claude can release a purchase order to another supplier and reschedule the affected production in Infor. Claude’s access follows the buyer’s Infor permissions.
Manufacturing teams stay in control
Skills are built to end with a user’s review, so an estimator checks and releases a quote, and a quality engineer verifies a fix for the corrective action report. To support that review, Claude can link figures and claims back to the underlying data and documents.
Claude for Manufacturing doesn’t operate equipment. For that, Anthropic is developing the Model Hardware Standard, a research preview that gives programmable equipment a standard way to describe its measurements, settings, and safety limits.
How to get started
On Team or Enterprise plans, install the plugin and tell Claude, “Set us up.” Claude asks which systems the team uses, tests the connectors, and reports which skills can’t fully run yet.
To see the plugin at work, register for our technical webinar on November 17 at 11:00 a.m. ET. To talk through a company’s manufacturing systems, contact our sales team.
Original source All of your release notes in one feed
Join Releasebot and get updates from Anthropic and hundreds of other software products.
- Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Introducing Claude Meetings
Claude launches Meetings in beta for Team and Enterprise, joining Google Meet calls as a visible participant to answer questions, collaborate on documents and whiteboards, and create notes and action items. Teams can revisit meeting transcripts and artifacts in Claude.
Claude can now join your video calls as a visible participant, follow the conversation and start on work during the meeting. Claude Meetings is now in beta.
Your team can ask Claude questions during the meeting, out loud or in chat. By default, Claude answers in writing, and it can use your connected tools with your permission.
Claude also works with you live to build docs, whiteboards (opens in new tab), or other artifacts, while teammates on the invite refine them. Claude writes the notes and action items, so no one on the call has to.
Claude Meetings is starting to roll out in beta on Team and Enterprise plans. Support for other video conferencing platforms is coming soon.
What it looks like
Say your team is planning a customer event, and Claude is on the call. You say, “Claude, start a doc for this plan.” Claude writes up what the team has said so far, and teammates on the invite can edit the plan while you keep talking.
When you start discussing the budget, someone asks Claude what last year’s event cost. Claude asks for their approval to look it up, posts it in the meeting chat, and compares it to the current plan. When you start discussing timelines, someone asks Claude to put it on a whiteboard, and the team works on the schedule alongside the doc.
Before the meeting ends, someone asks Claude to share a recap with the team. After the call, any notes, action items, plan, and whiteboard are on the meeting’s page in claude.ai (opens in new tab).
Later, you can go back to meetings you were part of and ask Claude about them, or add Claude to the next one from your calendar in claude.ai.
We’re working with partners like Gong, Attention, Granola, Fireflies.ai, Otter, and Plaud, so you’ll soon be able to send a meeting’s transcript to the tools your team already uses.
Security and privacy
Claude adds a separate page for each meeting in claude.ai (opens in new tab) with the notes, transcript, and anything it built. People from your organization on the invite can see it and edit what Claude made, and it can be shared with others in your organization from the page.
By default, Claude is set to stay out of calls when someone from outside your organization is invited, and to leave if someone from outside joins partway through. An admin can allow Claude on calls with outside guests. On those calls, Claude posts its notice in the call’s chat but doesn’t reply there, and what guests say is included in the notes and transcript.
Claude uses each person’s connected tools with that person’s permission. It asks the first time, and a yes applies going forward. For now, when someone asks out loud, Claude asks each time to confirm who’s speaking. An answer posted in the call’s chat is visible to everyone on the call.
When Claude joins, it appears as a participant and posts a notice in the call’s chat. It saves a transcript, summary, and screen descriptions, not audio.
Before you add Claude or turn on auto-join, make sure everyone on your calls is OK with being transcribed.
Getting started
Claude joins when someone adds it or has auto-join on. Support is currently available for Google Meet, with other platforms coming soon. On Team plans, inviting Claude to your meetings is available by default, and an admin can turn it off. On Enterprise plans, an admin turns it on for all or part of the organization. While it’s in beta, it isn’t available to some organizations, including those with zero data retention (ZDR), HIPAA-ready configuration, or customer-managed encryption keys (CMEK).
During the beta, Claude’s notes and transcripts are free on Team and Enterprise plans. So are its answers in your calls, unless an answer uses one of your connected tools, which counts toward your plan’s usage. The docs, whiteboards, (opens in new tab) and other artifacts Claude makes in a call are free through February 10, 2027.
Setup steps are in the Help Center.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
November 12, 2026
Claude introduces Meetings in beta for Team and Enterprise, joining Google Meet calls to take notes, answer questions, and create artifacts live.
Claude Meetings is rolling out in beta on Team and Enterprise plans in Claude and Claude Desktop. You can add Claude to a Google Meet call as a visible participant that takes notes, answers questions, and builds artifacts, such as docs, whiteboards, and slides, during the call. For more information, see Use Claude Meetings.
Original source - Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
Your apps can now open in Claude, and Claude can work in them
Claude now lets users open connected apps beside conversations or full screen, work with Claude on live pages and files, and pin favorite tools. The experience is rolling out on web and desktop across all plans, with MCP Apps capabilities in public preview for developers.
Our partners can now embed their apps directly in Claude, so you and Claude can work in the same tool, on the same screen, without switching tabs.
Earlier this year, we launched interactive connectors to bring a small live view of tools into Claude. Starting today, where a connector supports it, you can open a tool beside your conversation or expand it to full screen, and ask Claude to work alongside you and make changes directly.
This is rolling out on the web and in the Claude desktop app on all plans, as part of the new Claude experience that brings chat and Cowork together. You’ll see these features once your account is updated with the new Claude or your organization turns it on.
What’s new:
- Claude can work in your open tools. You can ask Claude to make changes to a page, row, or file that you have open and approve its actions the same way you approve a connector’s actions. Changes appear in the tool as Claude makes them, so you can keep working right alongside it.
- The whole tool opens next to your conversation. You can work in the tool and hide the chat or go full screen when you need room. For tools like Confluence or Notion, that means you get the full editor, signed into your own account, rather than a limited preview.
- Open a connected tool directly, without having to write a Claude prompt. When you want Claude’s help, you can ask from the same screen.
- Pin the tools you use most. You can arrange them alongside your artifacts and access them with one click in your sidebar and the + menu.
Work with Claude in the tools you use
We’re starting with a small group of tools from our directory, including Asana, Canva, Carta, Dropbox, monday.com, Smartsheet, Vercel, and Webflow.
Here’s what you can do with some of the tools available in Claude today:
- Adobe. Ask Claude to retouch, edit and add effects to photos; highlight, edit and redact PDFs.
- Atlassian. Open a Confluence page beside your chat, ask Claude to write and edit, and review its changes live on the page.
- Box. Open a Box file beside your chat, ask Claude to revise it, and compare the versions side by side before you keep the changes.
- HubSpot. Prioritize pipeline tasks and follow-ups, then act on them in Claude.
- Notion. Ask Claude to create a Notion doc or database. Build as you chat, or edit it yourself, without leaving Claude.
Figma, Harvey, and Shopify are also building integrations, and we encourage other developers to do the same.
For developers: built on MCP Apps
Interactive connectors run on MCP Apps, the open extension to the Model Context Protocol that lets an MCP server bring its own interface into AI applications. An MCP App you build isn’t limited to Claude and can run in any AI application that supports the extension.
Until now, MCP Apps in Claude have mainly appeared as interactive views in the conversation. Claude now supports more of the extension, such as app tools, along with embedded sites, so a developer’s full app can run inside Claude.
Support for these capabilities is in public preview for developers. Developers can start building with them today. Read our docs to start building.
Getting started
You can connect the tools we mention above from the directory, then open any tool from your chat or pin it to your sidebar.
For admins: If your organization already allows all of a connector’s tools, its new features appear as they roll out. Admins can restrict a connector’s tools the same way they do today.
Original source Similar to Claude with recent updates:
- Claude Code updates490 release notes · Latest Nov 14, 2026
- Anthropic updates79 release notes · Latest Oct 14, 2026
- ChatGPT updates251 release notes · Latest Nov 13, 2026
- OpenAI updates302 release notes · Latest Nov 13, 2026
- Claude Developer Platform updates187 release notes · Latest Nov 12, 2026
- Gemini updates468 release notes · Latest Nov 13, 2026
- Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
More ways to work with Claude: Sheets, Whiteboards, and Interactive Connectors
Claude introduces collaborative Sheets, Whiteboards, and Data artifacts, plus interactive app connectors that bring tools like Adobe and Atlassian into Claude. New enterprise controls and auto-connect beta help teams work across apps with managed access and permissions.
Work at the speed of thought
We've seen Claude Code change how developers work. Engineers went from manually coding line by line, to describing ideas and reviewing what Claude built. It reconnected them with the joy of building. Our goal is to bring that magic to every team, and today we're expanding what Claude makes possible. We're introducing new artifact types with Claude Sheets, Claude Whiteboards, and Claude Data. We're also making it easier to work in your most-used apps with an upgrade to interactive connectors. Claude Meetings is coming soon.
All your connectors and context
In Claude Code, the context Claude needs is already in the codebase. For other teams, context sprawls across emails, apps, and drives. Claude reaches it through connectors built on the Model Context Protocol (MCP), the open standard we introduced for connecting AI to the tools you use. Claude Marketplace lists more than 9,000 connectors and plugins, including community-built ones.
Interactive connectors take this further. Starting today, partners can embed their apps directly in Claude, so you can work in Adobe, Atlassian, and others without switching tabs. Plugins from Salesforce (beta), NetSuite, and Workday (beta) come with built-in skills, so sellers can prep for a call, accountants can analyze financial data, and HR teams can handle time off and expenses.
Bring ideas to life faster, together
Starting today, Claude can build spreadsheets, whiteboards, and dashboards with your team. These work with its existing abilities to create documents, slide decks, and designs, and with Claude Motion (beta), which helps you turn content into short animations. In each one, Claude quickly picks up what you need, so your thinking sets the pace of work:
New artifact types:
- In Claude Sheets, your team and Claude build spreadsheets together, collaboratively organize data, create and edit formulas, and work across multiple tabs.
- Claude Whiteboards is a digital whiteboard that your team can use to lay out and organize ideas together in a meeting, then ask Claude to summarize the findings.
- Claude Data (formerly Dashboards) connects to tools like Snowflake and Salesforce and can use definitions your data team certifies (beta) to create dashboards, visual data stories, or narrated short videos.
You can also ask Claude to build custom artifacts for the way your team works, like an account tracker, a daily briefing, a project status board, or a contract review table. Since Claude carries the same context through every step, an idea can carry over from a whiteboard to a spreadsheet to a dashboard, without the need to reiterate the details.
Coming soon, Claude Meetings will let you add Claude to a call to take notes and update the documents your team is working on during the conversation.
Teams already working this way
Inside Anthropic, non-technical teams are starting to get as much out of Claude as our engineers. Our legal team worked with Claude to build a Slack-based legal review tool that automatically draws redlines from the team’s own playbook. This brought marketing reviews from three days down to 24 hours, and easy fixes are made before a lawyer reviews the draft. Our finance team turned a long business update document for executives into an interactive page, and now the whole team updates it together with Claude.
Neither of these teams writes code, but they're experts in their fields. They used Claude to turn that knowledge into tools that saved them time, and that others can use. Our customers are working this way too:
“At Accenture, Claude is helping us transform the way our legal teams work. We're excited about the opportunity to reimagine legal workflows and unlock new ways for our legal professionals to support our business.”
Mindy Lok, Legal Chief Technology Officer, Chief Intellectual Property Officer, Accenture
“Our FP&A team used to spend about 10 hours every forecast cycle on slides, commentary, and validation. We automated that assembly work in Claude and brought it down to under 30 minutes. Claude took all of that off our plate. Now we're doing what finance is supposed to do: finding the insight and driving the decision. That's a meaningful shift for a team supporting a business of this size.”
Ash Gupta, Director of Financial Planning and Analysis, Advantage Solutions
“At Datadog, Claude has extended from coding to knowledge work. Our product managers are using Claude to move from an idea to a feature brief, PRD, and testable prototype much faster, giving them more time to focus on customer needs, product judgment, and the right problems to solve. When someone builds something good with Claude at Datadog, it spreads fast.”
Yanbing Li, Chief Product Officer, Datadog
At Gusto, one member of the commercial legal team built a tool in a few hours that turns negotiated terms into signature-ready contracts. Turnaround went from over a week to hours, with that person still reviewing anything negotiated.
Gusto
“Claude and HubSpot work seamlessly together, so our CSMs have all the context they need to walk in prepared for every call. Live dashboards in Claude pull from HubSpot to show what matters for each call and which customers to reach out to next, and follow-up emails are drafted within 30 minutes of a call ending. Work that used to take hours every week now runs in the background, so our team can focus on helping customers build better solutions, prove value, and grow better.”
Jon Dick, Chief Customer Officer, Hubspot
Built for and with enterprises
As Claude starts to connect to more tools, businesses need better ways to oversee its access and actions. We build in security and compliance controls to help enterprises meet their own requirements, and we use the same Claude for our own most sensitive work. On Enterprise plans, admins decide who can use which products and connectors, and set spend limits for the organization at a granular level.
That control applies to the tools Claude connects to. With Claude auto-connect, now in beta on eligible Team and Enterprise plans, connecting an app like Notion, Atlassian, or Dropbox is a one-time setup. Employees are then connected to the tool the first time they use it in Claude, instead of connecting each one individually.
Whichever way a tool is connected, Claude works within your existing permissions. Admins can also limit what each connector does, meaning that Claude might be able to read Slack but not send messages on your behalf.
Protecting sensitive business data is core to how we build, and we're continuing to harden those protections as Claude takes on longer, more complex work:
- Data from Enterprise organizations is encrypted in transit and at rest.
- On Enterprise plans, security teams can see how Claude is being used, through audit logs and a Compliance API that works with more than 100 security and compliance tools, including Splunk and CrowdStrike.
- In the new Claude experience on Enterprise, each cloud session runs in its own isolated virtual machine, with connector credentials kept outside it.
Work that keeps up with your ideas
Modern work is set up around software, but Claude works around you. It knows your team's work through the tools you connect, helps you bring ideas to life in the formats you need, and runs within the controls your admins set. That leaves you more time to focus and make progress on big goals.
Original source - Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
Introducing Claude Whiteboards, Claude Sheets, and Claude Data
Claude launches Whiteboards and Sheets in beta and brings Claude Data to general availability, helping teams brainstorm, build spreadsheets, and share live data together. The new collaborative tools are available across web, desktop, and mobile on paid plans.
Now you can brainstorm on whiteboards, build sheets, and share data directly in Claude.
Today we’re launching Claude Whiteboards and Claude Sheets in beta, and Claude Dashboards becomes generally available as Claude Data. Whiteboards is a shared board where your team brainstorms with Claude, Sheets is a spreadsheet Claude builds and edits with you, and Claude Data adds data stories, certified queries, and live sharing. These are available on all paid plans.
Working with Claude on a project often meant moving the output over to another tool or program, where Claude didn’t have live access to follow progress and changes. Now, your documents, boards, sheets, and dashboards can stay in Claude, with access for your team to continue editing together. When ready, you can bring the outputs directly into tools from our partners and continue working there.
Claude Whiteboards
Many people use Claude as a thought partner, but brainstorming with it has typically meant copy-pasting the results elsewhere so you can then start brainstorming or collaborating with your coworkers. Now, you can talk through a messy plan out loud with Claude, and Claude can turn it into a board with a timeline with owners and dates, so you and your team can collaborate in real time. In a retro meeting, for example, everyone can add their notes, and Claude can group them by theme and draft the action items for each person. You can focus on any part of the board by dragging a box around it and asking Claude questions. When you’re done brainstorming, Claude can turn the board into a doc or deck, or bring it into tools like Lucid, Miro, or Vani by Zoho, where you can continue working on it with your team.
Claude Sheets
Claude can now generate spreadsheets with tabs, formulas, formatting, and drop-downs, often from just a prompt like asking for a campaign tracker or a hiring budget. It can edit in the cells, outlining each new edit so you can track changes. You can share sheets with your team, so you and Claude can work on them together.
For now, sheets have simple spreadsheet functionality, but we are working on adding more. When you need the full functionality of Excel, you can export your file to .xlsx or CSV, or use Claude for Excel (opens in new tab). You can also continue working in partner tools including Airtable, Asana, monday.com, and Smartsheet.
Claude Data
Claude Dashboards (opens in new tab) launched in beta in October, enabling teams to ask quick questions of their company’s data in tools like Amazon Redshift, BigQuery, and ClickHouse. Starting today, it’s generally available as Claude Data. We changed the name because the way companies use their data is broader than dashboards, and the product now covers how they work more broadly. Certified queries and live sharing are in beta. Here are some ways teams can use Claude Data:
- Create certified definitions of metrics. Your data team can certify the queries everyone should use, so you don’t end up building or working on dashboards with conflicting data. Charts built on these metrics carry a "certified" badge showing they’re certified.
- Craft stories from data. You can work with Claude in Claude Data to draft data stories or narrated videos from your metrics, for you to review before sharing.
- Share current numbers with everyone. With live sharing, your colleagues can see up-to-date numbers when they open a shared dashboard, even if they don’t have access to the connectors that keep that data current. Viewers see the results of the queries you’ve approved, and can’t run others with your access.
- Match your look-and-feel. Design systems are now supported in Claude Data.
- Get faster loading with caching. Previously, every dashboard would reload on every load. Now, dashboards support caching, and refresh cadences can be set on a per-dashboard basis.
- Track changes over time. Claude Data now has tracked changes, so you can see who has made edits and roll back to a specific version if needed.
Our partners for Claude Data include Amplitude, Mixpanel, Omni, PostHog, and Sigma.
Work in your other tools, too
Starting today, interactive connectors (opens in new tab) can open as full apps beside your conversation or in full screen, so you can work in tools like Adobe, Atlassian, Box, and Notion yourself, or ask Claude to make changes with you.
Getting started
Claude Whiteboards, Sheets, and Data work on web, desktop, and mobile. Claude Data needs a data connector, such as a warehouse or CRM.
For admins: On Team plans, all three are on by default. On Enterprise plans, Claude Whiteboards and Sheets are off by default, and Claude Data turns on by default on November 19, 2026. You can change these anytime in Organization settings > Artifacts.
Original source - Nov 9, 2026
- Date parsed from source:Nov 9, 2026
- First seen by Releasebot:Nov 11, 2026
Claude Fable 5.2 and Mythos 5.2
Claude releases Fable 5.2 and Mythos 5.2, faster models with improved coding, reasoning, vision, cybersecurity and scientific capabilities. Fable is available broadly with improved safeguards, while Mythos access is limited to vetted organizations. Both offer an optional fast mode.
We’ve upgraded Claude Fable and Claude Mythos—models that are designed to tackle the most daunting technical challenges.
Claude Fable 5.2 and Claude Mythos 5.2 show improvements in areas like coding, reasoning, and vision. During prerelease testing they’ve helped our engineers complete otherwise-infeasible software migrations, designed three working electronic devices from scratch, solved two open problems in the physics of black holes, made substantial progress on robotics evaluations, and formalized the proof of Fermat’s Last Theorem in 30 hours—among many other applications we’ll discuss below.
Claude Fable and Claude Mythos are the same underlying model. Fable has strong cybersecurity and biology safeguards to guard against misuse, which allows us to make it available to all users. Organizations pursuing beneficial applications in cybersecurity or biomedical research can apply for access to Mythos through our recently expanded Life Sciences and Cyber Verification Programs.
Testers have found that Fable 5.2 and Mythos 5.2 communicate more clearly than past Fable and Mythos models. They generate outputs up to 30% faster than Claude Fable 5.1 and Claude Mythos 5.1, and they’re available at a lower price: $8 per million input tokens and $40 per million output tokens.
Fable 5.2 and Mythos 5.2 also come with an optional fast mode, which speeds up token generation by up to 2.5 times. Fast mode is available for $16 per million input tokens and $80 per million output tokens.
Safety and alignment. To help ensure safety and alignment keep step with growing model capabilities, we ran extensive prerelease safety testing on the model that underlies Fable 5.2 and Mythos 5.2. This included developing novel evaluations that give deeper insight into specific concerning behaviors like sandbox escapes. We believe high-stakes risks from misalignment remain low, and the model performed as well as, or better than, our recent models on most alignment measures. Fable 5.2’s cyber and biology safeguards are as robust as those of Fable 5.1 but produce fewer unnecessary blocks, and we have implemented our strongest-ever protections against distillation attacks.
When to use Claude Fable 5.2 and Mythos 5.2. Fable and Mythos are best for the most ambitious, open-ended technical work. For most coding and knowledge tasks, we recommend that users start with Claude Opus 5.5, our strongest daily driver, and then switch to a different model as required, depending on the scope and complexity of their work—upward to Fable or Mythos, or downward to Claude Sonnet 5.5 or Claude Haiku 5.5. Fable 5.2 can also play the role of Advisor (where Haiku, Sonnet, or Opus models consult it to help solve harder problems) or Orchestrator (where it delegates simpler tasks to smaller models).
Evaluating Claude Fable 5.2 and Mythos 5.2
Benchmark performance. The benchmarks table below shows that Claude Fable 5.2 and Mythos 5.2 are a step above Opus 5.5 in almost all the capabilities we evaluated:
Effort and efficiency. On Medium effort (the default in Claude apps and Claude Code), Fable 5.2 can accomplish challenging tasks with fewer tokens than Fable 5.1. In early testing on the FrontierCode 2.0 evaluation, Fable 5.2 at High effort scored about level with Opus 5.5 at Max effort, for roughly half the cost per task. At Xhigh effort, it also scored the highest of any released model tested.
Coding
Over 90% of the changes merged into Anthropic’s core codebase are now written by Claude (with human guidance). We’ve used Fable 5.2 to fix stubborn bugs in minutes, optimize performance across all of our services, and complete high-value software projects that would otherwise have been too slow or too costly to attempt. A team of agents running an earlier version of Fable 5.2 migrated a critical production service from Python to Rust—the service is now more efficient, more reliable, and starts about 26 times faster. We’ve found that Fable 5.2 exercises strong engineering judgment and can produce high-quality results from even ambiguous requests.
As an experiment, one Anthropic engineer gave Fable 5.2 the task of designing a prototype operating system. Starting from an empty folder, the model coordinated over 1,000 subagents, working around the clock for eight days writing, testing, and reviewing code. It produced a working operating system that boots on a laptop, with its own core that runs the machine, drivers for the disk, keyboard, and network, permanent file storage, windows, a login screen, an installer, and built-in Claude functionality (see the video below).
Early testers have been impressed at how successfully Fable 5.2’s coding skills can be applied to a wide range of tasks:
“The model is in my head. It understands the intent behind every prompt I’ve given it. I haven’t had to say ‘No, I meant…’ a single time. Projects we’ve been pushing along with other models for weeks got finished and approved by our teammates in a few days with Claude Fable 5.2, and the humans reviewing its code had less to say.”
COMPANY
Vercel
AUTHOR
Joe Haddad, Member of Technical StaffCybersecurity
Claude Mythos 5.2 is our most capable model for cybersecurity engineering. It catches more vulnerabilities than our previous models, and is better at reproducing and fixing them (note that Claude Fable 5.2’s safeguards will block most cybersecurity-related tasks). A security company found that one in six confirmed bugs found by Claude Mythos 5.2 were missed by all of the other frontier models they tested. On our internal evaluation, CVE Rediscovery,¹ Claude Mythos 5.2 found 10.2% more vulnerabilities than Claude Opus 5.5 and 14.4% more than Claude Mythos 5.1. Claude Mythos 5.2 also shows better judgment and calibration—one tester found that previous models had overstated the seriousness of about 1 in 20 findings, whereas Claude Mythos 5.2 hadn’t overstated any.²
CVE Rediscovery is an internal cybersecurity evaluation that assesses how many published CVEs (Common Vulnerabilities and Exposures) a model can independently find when given a snapshot of the project before a CVE was fixed. Our October 2026 run against 1,829 CVEs showed Claude Mythos 5.2 outperformed Claude Mythos 5.1 and Claude Opus 5.5 at every effort level.
Claude Mythos 5.2’s cyber capabilities are accessible through our Cyber Verification Program, which we’re continuing to expand and improve. Claude Enterprise customers (even if they aren’t members of the Cyber Verification Program) can access Claude Security, which scans codebases for vulnerabilities using our most capable models—which now includes Claude Mythos 5.2. A recent update to Claude Security helps it watch repositories as code is updated, track any findings to ensure they’re fixed, learn from additional context, and connect to a user’s tools through an API and MCP.
“We have worked closely with Anthropic’s new model, Claude Mythos 5.2, to do a next round of high-fidelity threat discovery and elimination within our own systems for potential issues we did not uncover with earlier Mythos models. The output is more readable and empowered our team to spot-check faster and more easily. We built our Code Guardian harness with Mythos 5.1, and we’d switch to Mythos 5.2 to give our customers more powerful cyber capabilities.”
COMPANY
Rubrik
AUTHOR
Arvind Nithrakashyap, Co-Founder and Chief Technology OfficerScience and engineering
Important tasks in science, engineering, and mathematics increasingly depend on coding: analyzing data, modeling molecules, designing parts, and controlling instruments are all done through software. Below, we discuss how Claude Fable 5.2 and Claude Mythos 5.2 have helped researchers make progress on difficult problems in these areas.
Theoretical physics
Claude Fable 5.2 solved two open problems in theoretical physics. Both concern black holes, and the effort to unite the two linchpin theories of modern physics, relativity, and quantum mechanics.
Both of Claude’s results rely on holographic duality, the idea that certain universes containing gravity can be precisely described by a quantum theory containing no gravity at all. In the first problem, physicists in 1983 had shown that as these universes heat up, black holes form abruptly, like water boiling; but their method worked only in large universes that were big enough for relativity to apply. A calculation to determine whether the same was true in very small universes, where only the quantum description can be used, was laid out in 2003 but was too laborious to complete. Fable 5.2, working largely autonomously, completed it and found the transition is abrupt there, too. In the second problem, Fable 5.2 found the exact limit of a technique physicists have used for more than 15 years to rule out candidate theories of quantum gravity in a simplified universe. Read more about these results in their respective preprints, here and here.
Protein folding
Adeno-associated viruses are small, harmless viruses whose protein shell, the capsid, can be used to deliver gene therapies. The protein structure of the capsid is important—for example, it affects whether the therapy will be blocked by a patient’s immune system—but it’s also highly complex. Existing protein-folding models like AlphaFold can predict individual proteins, but a capsid is built from dozens of them. Building on two open-source protein-folding models, Claude Mythos 5.2 found a novel way to accurately predict a whole capsid’s structure. It wrote code that ran these models on overlapping groups of protein chains, and used the information on the known symmetries of the capsid to merge them together.
Claude’s method worked across several capsids, both natural and engineered (in our tests, it accurately modeled 28 of the 34 it attempted).³ Three computational biologists shared the following reflections on how Claude’s skills could be used to speed up their research into gene therapies:
“This acceleration could save meaningful time and cost from our capsid folding pipeline, enabling us to deploy compute more efficiently across many capsid properties that are needed for a genetic medicine. We are excited to help Anthropic push the reasoning capabilities further to reduce the cost of designing capsids overall.”
COMPANY
Dyno Therapeutics
AUTHOR
Sam Sinai, Cofounder and Head of AIMathematics
Mathematical formalization. Formalization is the process of translating a mathematical proof into a language that a computer can check step by step. It can help human mathematicians gain confidence in results without having to check them by hand (this matters even more when AI models generate results that are hard for humans to verify). Because formalization is such a laborious process, if AI could assist with it, mathematicians could spend more time exploring novel ideas.
Our first formalization of Fermat’s Last Theorem, performed by an unreleased research version of Claude, took 11 days. It relied on a purpose-built harness along with guidance from a human researcher. By contrast, a team of 1,000 Fable 5.2 agents fully formalized the theorem in just 30 hours, with minimal human intervention. Fable 5.2 started from minimal prompts, built its own ways to coordinate, and used no mathematical references, only a list of intermediate theorem statements to score progress. It needed one-third as many action tokens as our first formalization and produced a proof seven times shorter. As can be seen in the figure below, Opus 5.5 (with the same 1,000-agent setup) completed only 26% of the formalization in 18 hours, and barely made any more progress after 30.
Read more about the formalization here.
Hardware and robotics
Many of AI’s potential benefits—for example, in speeding up laboratory research—depend on it being able to act in the physical world. Claude Fable 5.2 continues our models’ trend of increasing usefulness in the real world, showing promising results on tasks such as designing hardware devices and substantial advances in controlling physical robots.
Hardware engineering. We tested Fable 5.2’s skills in hardware engineering, asking it in a one-paragraph prompt to design and produce three working electronic devices with their own circuit boards, 3D-printed enclosures, and software. The devices, shown below, were a home voice-assistant hub, a USB speakerphone, and a handheld virtual pet. We collaborated on this project with Diode, a company that designs and manufactures circuit boards.
Claude wrote its own specifications, selected available electronic components from US distributors, routed each device’s four-layer circuit board, modeled the enclosures with computer-aided design, and programmed the devices’ software. Each board was ready for manufacturing in under a day, with minimal human input. Once Diode had built the boards, Claude guided the company’s engineers through the testing and assembly of the devices. All three devices worked without needing any electrical modifications. Read more about Claude’s hardware engineering skills here.
Robotics. Compared with earlier Claude models, Fable 5.2 shows substantially improved skills in controlling physical robots—even for robotics tasks on which it has never explicitly been trained. The video below shows robots controlled by Fable 5.2 completing a variety of tasks, including solving a puzzle cube, unscrewing a bottle cap, and drawing a picture of a robot. On the public RoboDojo benchmark, which tests how AIs can control a simulated two-arm robot from camera images, Fable 5.2 outperformed other frontier models that were run on the same harness, as well as most AI systems built specifically to control robots.
RoboDojo Sim tests control of a simulated two-arm robot. Scores are based on our internal runs for each model using the highest available effort level. At Max effort, Fable 5.2 scores 64.9%, more than double GPT-6 Astra (29.8%) and Fable 5.1 (27.6%).
Research and analysis
Early testers using Claude Fable 5.2 for research and analysis tasks found that it can handle more ambiguous, data-heavy tasks than previous models and has better judgment on ambiguous tasks—particularly those that require abstract reasoning and design. Proprietary trading firm Jump Trading tested Fable 5.2 on proxy evaluations that resemble some of its quantitative research tasks, embedding it in a harness similar to the one the firm uses for its own research. In one run, Fable 5.2 effectively played all the necessary roles: code-writer, coordinator, planner, and job-submitter. Previous models had required substantial investments of time to manually rebalance roles to accommodate different models’ strengths and weaknesses.
Other testers from research and analysis organizations sent us the following statements on their experiences with Fable 5.2:
“Claude Fable 5.2 is incredible at playing every major role within a research system: defining questions, interpreting, coordinating, and of course finding and implementing the key ideas. Definitely one of the strongest on taste and judgment that we’ve seen. In an internal research automation benchmark, it achieved a full 10% lower error than the next best model.”
COMPANY
Jump Trading
AUTHOR
Lucas Baker, Head of LLM R&DSafety and alignment
No single test can tell us how a highly capable model will behave once it’s deployed, so we rely on many different tests and many different types of evidence before release. For the model underlying Claude Fable 5.2 and Claude Mythos 5.2, our predeployment safety work included alignment training and testing, newly designed evaluations on the model’s propensity to take unhelpful actions, building stronger safeguards against misuse, and scaling up our behavioral monitoring. The model was also tested before release by external evaluators, including the UK AI Security Institute, Frontier Design, and METR. See the Claude Fable 5.2 and Mythos 5.2 System Card for a summary of their reports⁴ and for a full description of our own safety and capabilities testing.
Alignment testing
We ran a suite of evaluations for how well-aligned Claude Fable 5.2 and Claude Mythos 5.2 are in behavioral terms, testing how often they behave in unintended and potentially unsafe ways. Weighing everything we’ve seen across a range of evaluations, we’ve assessed the risk of these models behaving in unsafe ways in high-stakes situations to be low (as with our other recent models).
We tested Claude Mythos 5.2 (the same underlying model as Fable 5.2 without certain cybersecurity or biology safeguards), on our automated behavioral audit, which tests how a model behaves across approximately 1,900 scenarios. Claude Mythos 5.2 performed as well as, or better than, Opus 5.5, Sonnet 5.5, and Claude Mythos 5.1 on most measures. For example, it scored better than all three on most measures that involve misleading users. Hallucinating inputs, falsely claiming to have completed a task, omitting important information, and failing to disclose bad or lazy work were all lower in Claude Mythos 5.2.⁵
Overall score from our automated behavioral audit, a composite of many undesirable behaviors including cooperation with human misuse and autonomous actions across a range of scenarios. Lower scores are better. See Section 6.4.1 of the Claude Fable 5.2 and Claude Mythos 5.2 System Card for full details.
We paid particular attention during our testing to behaviors that contributed to recent notable cybersecurity and alignment incidents. For example, we found that Claude Mythos 5.2 has a lower propensity than Opus 5.5, Sonnet 5.5, and Mythos 5.1 to engage in biased or motivated reasoning (such reasoning might mean it “explains away” evidence that it isn’t in a simulation and thus takes actions without a realistic understanding of the consequences).
We ran multiple different evaluations to test the model’s tendency to attempt escaping its sandbox. In two evaluations we’d used previously, Claude Mythos 5.2 made substantially fewer attempts at sandbox escape than any other model we’ve tested. In a dedicated evaluation—an adversarial experiment including over 1,800 scenarios, most of which could not be solved without escaping a sandbox, and where the sandbox has a deliberate weakness—Claude Mythos 5.2 made use of credentials or files that we had placed outside its sandbox in 3.1% of scenarios, about as often as Opus 5.5 (3.3%), less often than Sonnet 5.5 (5.1%), and well below previous iterations of Claude Mythos (5 and 5.1, which scored 39% and 21%, respectively). We found that other techniques, such as describing the sandbox and adding tools to report weaknesses, reduced Claude Mythos 5.2’s escape attempts even further. On other measures—one, for example, involving taking harmful actions after erroneously concluding it was in a simulation—Claude Mythos 5.2 scored slightly worse than Opus 5.5, and about level with Claude Mythos 5.1.
The problem of building evaluations that reliably catch every failure before a model is deployed remains unsolved. The complexities of evaluating highly capable models often muddy the picture—for example, Claude Mythos 5.2 and Fable 5.2 each voice suspicion that they are being evaluated more often than any of our recent models, which challenges our ability to assess how they will act in real-world settings. As these settings expand and capabilities increase with future models, we expect this challenge to grow. That is why we do not rely on these evaluations alone to provide a holistic picture of safety: we draw on monitoring during training, reviews of transcripts from internal use, testing by external evaluators, and interpretability techniques for examining what is happening inside the model. We are also working to make our evaluations more realistic and to better understand what they miss.
Safeguards
Cybersecurity and biology safeguards. Consistent with previous Claude Fable models, Fable 5.2 comes with safety classifiers that block high-risk cyber activities, including penetration testing, exploit generation, and binary-based vulnerability, as well as most tasks in research biology. When a query is blocked, users will instead receive a response from Opus 4.8 for cybersecurity and Opus 5 for biology. Since the release of Claude Fable 5.1, we have continued to reduce false positives for our safety classifiers. Based on early testing across claude.ai, Claude Code, and Cowork, we observed about 55% fewer blocks with Fable 5.2 compared with Fable 5.1—about 60% fewer in cybersecurity and 40% fewer in biology. Claude Mythos 5.2 is available to vetted organizations that work in these dual-use areas.
AI research and development. The model that underlies Claude Fable 5.2 and Claude Mythos 5.2 is a step forward in general capabilities. However, during the model’s training, we took steps to limit advances in the specific research capabilities that could most directly accelerate AI development. Thus, in relevant areas, including accelerator kernel optimization and improving large language model architectures, Fable 5.2 and Claude Mythos 5.2 perform at about the level of Opus 5.5. Importantly, we ensured that the training changes did not affect related capabilities like agentic coding, hardware development, and traditional AI or machine learning research (including interpretability research). We do not alter these capabilities as the model is being served to users (that is, at inference time). As described in Section 1.5 of the System Card and similarly to previous models, Fable 5.2 and Claude Mythos 5.2 also include transparent fallbacks to Opus 5 for a small set of topics in this domain, including kernel development on certain nonstandard accelerators.
Anti-distillation. Distillation, where a model is trained on the outputs of a more advanced one to extract the advanced model’s capabilities, occurs illicitly on an industrial scale, often involving thousands of fake Claude accounts. Since distillation allows for advanced capabilities to be released without the safeguards we’ve built into Claude, it creates safety and national security risks (see our September 2026 threat intelligence report for details on illicit distillation activity we’ve detected and disrupted so far). Fable 5.2 has the strongest protections against distillation of any model we’ve released; it uses the techniques we described in a recent report, which have reduced the data harvested by distillers by 90% to 99%.
We are also expanding the rollout of an API feature that helps guard against illicit distillation: preserved thinking now applies to all accounts. Preserved thinking prevents distillers from editing Claude’s prior context in an attempt to extract its reasoning (developers can refer to our preserved thinking docs to learn how to update integrations with new API features).
Data privacy and Enterprise Frontier Safeguards
Some more complex forms of AI model misuse can be detected only when observing patterns across multiple requests. For this reason, powerful models like Claude Fable 5.2 and Claude Mythos 5.2 rely on safeguards that monitor a window of usage data (as opposed to individual responses). With Enterprise Frontier Safeguards, automated safety monitoring is run on prompts and responses that are stored in a customer’s infrastructure, making it compatible with zero data retention (ZDR). Enterprise Frontier Safeguards is now in private beta with customers like Bridgewater, Salesforce, and Stripe.
Enterprise customers can request access to Enterprise Frontier Safeguards by contacting their account team or by completing this form. Eligible customers can continue using Claude Fable 5.2 and Claude Mythos 5.2 with zero data retention before implementing safety monitoring with EFS. For other customers, we have 30-day retention for safety monitoring.
Availability
Claude Fable 5.2 is available today on all platforms, including Amazon Web Services, Google Cloud, and Microsoft Azure. Developers can get started with claude-fable-5-2 on the Claude Platform.
This week, we’re giving subscribers on eligible paid plans extra Fable usage. Plans and seats that include Fable models get one to three Fable resets based on how long they’ve subscribed, and Fable is included for up to 50% of weekly usage limits for Pro plans and standard seats on the Team plan. Learn more about the Fable 5.2 launch promotion here.
Cybersecurity professionals can apply for access to Claude Mythos 5.2 through the Cyber Verification Program. Claude Enterprise customers can also use Claude Security, powered by our full family of models, including Claude Mythos 5.2. Life sciences researchers can also apply for access through the Life Sciences Verification Program.
Fast mode for Claude Fable 5.2 and Claude Mythos 5.2 is available on Claude Code, the Claude Platform, Claude Models on Google Cloud (Anthropic managed and Google managed), and Microsoft Foundry (Anthropic hosted). Note that access to Claude Mythos fast mode is available only to organizations who are part of our Verification Programs.
Footnotes
1 CVE refers to Common Vulnerabilities and Exposures, a system that enumerates software vulnerabilities.
2 The counts are raw findings from one tester’s audit, although testers consistently found that Claude Mythos 5.2 identified more vulnerabilities than earlier models. On our own evaluations, vulnerability identification is roughly on par with Opus 5.5 (see the system card).
3 Earlier work on modeling AAV capsids and other large symmetric protein systems includes FoldaVirus, EvoDOCK and its symmetric extension, SymProFold, CapBuild, MoLPC, CombFold, Uni-Fold Symmetry, Apodex Discovery, and the “big bang” initialization (the last of which was referenced in the prompt we gave to Claude Mythos 5.2). These methods typically assemble the full structure from separately predicted chains or small groups of chains. Claude was permitted to use known symmetries but was instructed not to rely on assembly. Note that accuracy is measured by comparing Cα RMSD with the experimental structure: 1.2 Å for OpenFold3-preview2 and 1.4 Å for ESMFold2 on AAV2 (PDB:1LP3). A capsid counts as accurately modeled if either model came within 3 Å. For AAV2, Claude’s method required about 58 minutes of inference on one NVIDIA H200 GPU for OpenFold3-preview2 and about seven minutes for ESMFold2.
4 None of the external organizations reviewed the contents of this blog post or the contents of the System Card. Those organizations do not necessarily agree with any of the claims made in either publication.
5 We ran these tests on Claude Mythos 5.2 because testing the model with reduced safeguards provides the most comprehensive look at model behavior. We expect Fable 5.2 to behave similarly; in some cases, more potential pathways for misuse should be blocked given its stronger safeguards.
Original source - Nov 6, 2026
- Date parsed from source:Nov 6, 2026
- First seen by Releasebot:Nov 7, 2026
November 6, 2026
Claude adds beta project tags for Enterprise organizations to track spend by cost code, charge code, or client-matter number.
Track spend by cost code with project tags (beta)
Eligible Enterprise organizations can now tag projects with the codes they already use, like a charge code or client-matter number, and see most spend in those projects by tag. This feature is available in beta. For more information, see Track spend by cost code with project tags.
Original source - Nov 5, 2026
- Date parsed from source:Nov 5, 2026
- First seen by Releasebot:Nov 5, 2026
- Modified by Releasebot:Nov 13, 2026
November 5, 2026
Claude adds new Enterprise security and admin controls, including a security center and centralized management, with several features in beta. It also begins rolling out beta Personal Finance, letting US subscribers link accounts to view balances and spending and ask questions about their money.
New security and admin controls for Enterprise plans
Claude Enterprise has new security and admin features, including a security center, inference hooks, centralized management, and additional access controls, several in beta. For more information, see our blog post: More visibility and control over Claude Enterprise for security teams.
Personal Finance in Claude
We’re rolling out Personal Finance, a beta that lets you link your bank, credit card, loan, and investment accounts to Claude, so you can see your balances and spending on one page and ask Claude questions about your own money. It's available on Pro, Max, and Ultra plans, and is available in the US only. For more information, see our blog post: Introducing Personal Finance in Claude.
Original source - Nov 5, 2026
- Date parsed from source:Nov 5, 2026
- First seen by Releasebot:Nov 5, 2026
Introducing Personal Finance in Claude
Claude launches Personal Finance in beta for US Pro, Max, and Ultra users, letting people securely connect bank and card accounts for read-only answers about spending, balances, upcoming bills, and more—all in everyday language.
Ask Claude about your money and get straight answers from the accounts you connect.
Getting answers about your money no longer means opening every banking app and doing the math yourself. With Personal Finance in Claude, you can securely connect your bank and card accounts and ask in your own words. Access is read-only, and Personal Finance can’t move, manage, or invest your money.
Claude gives you answers in everyday language, from your balances and transactions, and explains any term that's new to you. Like the rest of Claude, Personal Finance has no ads or sponsored recommendations, and it doesn’t offer credit cards, loans, or savings accounts of its own, so your money questions get a straight answer.
Personal Finance starts rolling out in beta this week, on the Pro, Max, and Ultra plans in the US.
What it looks like
Say it's late in the month and payday is still 10 days away. When you ask Claude, "Where did my money go this month?" it adds up your spending across the accounts you connected and sorts it by category. In this example, that comes to $4,309.37, with more than half going to rent and utilities and $1,024.51 to food and drink.
From there, you can dig deeper: "Is that more than usual?" "Anything else I'm missing?" "So what's left before payday?" Claude checks the previous months and points to a membership renewal. Then Claude tells you about four payments that will come out of your checking account before payday, and what you’ll have left: $1,393.22.
If you ask whether anything looks off, Claude reads across every account you've connected and can point to what's easy to miss, like charges that hit twice, unexpected fees, or a bill that’s crept up all year. You can also ask bigger questions, like "Am I spending more than I make?" or "What's an APR, and what has mine cost me this year?" Claude explains the term, then adds up the interest you've been charged.
Ask for a weekly spending chart, a calendar of what's due, or a dashboard of the numbers you choose, and Claude builds one you can keep adjusting.
Security and privacy
Claude's access is read-only. Personal Finance helps you understand your money, and it isn't designed to give investment advice. Claude can make mistakes in its answers, so ask which transactions are behind a number, and check important figures with your bank.
Your accounts are only connected once you sign in to your bank yourself through Plaid, a service that connects apps to banks. That's where you agree to its terms and approve Claude's read-only access, so Claude doesn't ask for or see your bank password.
For the accounts you choose to connect (and only those), Claude sees the bank's name, each account's name, type, and last four digits, balances and credit limits, and up to two years of transactions. When you chat with Claude in the Personal Finance hub, those conversations aren't used to train our models. For anything you share with Claude outside the hub, your privacy settings apply. You can unlink an account anytime, and then Claude can no longer see its data. More details can be found in our Privacy Center.
Getting started
When you see Personal Finance in Claude's sidebar, open it, connect one account, and ask a single question, like "Can I afford a trip this spring?" or "How much could I save each month?" You'll find the setup steps, and how your data is used and kept, in the Help Center. (opens in new tab)
What’s next
Personal Finance is a first step. For life’s bigger money decisions, we think people are best served by Claude working alongside the licensed professionals and regulated firms they trust. We’re exploring how to make that possible in Claude, and we’d like to hear from banks, wealth managers, and financial services companies who want to help shape it.
Original source - Nov 5, 2026
- Date parsed from source:Nov 5, 2026
- First seen by Releasebot:Nov 5, 2026
More visibility and control over Claude Enterprise for security teams
Claude Enterprise adds stronger security visibility and control with a security center, generally available inference hooks, centralized administration, and new access controls. EDR sensor support for Cowork and unified Claude also expands endpoint monitoring, with several features available in beta.
Claude Enterprise has new security and admin features, including a security center, generally available inference hooks, centralized management, and additional access controls.
To see how Claude is set up, the security center shows how your organization’s Claude settings compare with Anthropic’s recommended configuration. To apply your policies, inference hooks send prompts and tool calls to your data security tools for a check. To manage access, centralized management gives your company one admin console for company-wide settings, and new access controls let you sign members out through the Admin API, manage your IP allowlist yourself, and help prevent shadow IT by blocking personal and other outside Claude accounts in Claude Desktop on managed computers.
We also recently announced an Endpoint Detection and Response (EDR) integration, which runs your organization's sensor inside the unified Claude and Cowork virtual machine on the user's computer.
Security teams need to see how Claude is configured, what it does on company devices, and how data is handled as people work. These features give them that visibility and control.
Security center: review your Claude security settings in one place
Security teams can review Claude's security settings for chat, Cowork, and Claude Code on one page, instead of setting by setting. The security center is a new page in Organization settings that compares settings with Anthropic's recommended configuration, so your team can see what to change and where to change it.
For each control, the security center shows the current value, the recommended value where there is one, and a link to the setting where you can change it. It also shows which settings are new or recently changed. The security center checks your configuration each time the page loads, so automatically checked controls reflect your current settings. Organizations with the Compliance API can read the same results through it.
Attestations give your admins a shared workspace for security reviews. They can work through the process together once, recording the current state of each control, accepting risks, and flagging issues in one place.
You can download the security center page as a report to share with auditors and relevant stakeholders. The report marks which controls the page checked automatically and which an Owner confirmed. The security center is guidance based on Anthropic's recommendations, not a certification or a guarantee of compliance with any law or standard.
Inference hooks
Inference hooks connect Claude to the data security tools your organization already uses, so your data loss prevention (DLP) and security policies can apply to prompts and tool calls as people work.
There are two kinds of hooks, both now generally available:
- Prompt hooks send prompts from supported Claude products to your security tool for a check.
- Pre-tool-call hooks check tool calls in supported Claude products before they run.
Hooks work with security vendors. Your team keeps the policies it has already written and applies them to Claude.
Centralized management: one console for identity and access across your organization
Centralized management gives your parent organization, which represents your company across its Claude Enterprise and Claude Platform organizations, its own admin console at admin.claude.com. Admins manage company-wide settings there once for the organizations under your parent, instead of from individual organization settings. These settings include single sign-on, directory sync (SCIM), domain verification, groups, and Compliance API keys.
The console shows every organization under the parent in one place and adds two roles. Parent organization owners can manage everything at the parent level, including who holds the owner and admin roles. Parent organization admins can manage everything except those role assignments.
Companies can also connect more than one identity provider, each with its own single sign-on and SCIM configuration. An acquired company can keep its existing provider, or your team can move to a new provider one domain at a time.
Each organization keeps its own members, roles, settings, and organization-level security controls, such as IP allowlisting, tenant restrictions, and session duration. A parent role doesn't grant access inside an organization by default, but Compliance API keys created at the parent can read data across organizations.
Access controls: member sign-out and shadow IT prevention
Security teams can now sign a member out of Claude with a single Admin API call, without removing them from the organization. The call ends that member's sign-in sessions on every browser and device, and apps like Claude Code have to sign in again. It doesn't end API keys, cloud sessions already running, or scheduled routines, and the member can sign in again afterwards.
Enterprise admins can now set up and manage their IP allowlist themselves, without going through Anthropic. An IP allowlist limits access to most Claude products to the IP addresses your organization approves.
Admins can now set the most-used Claude Desktop settings, with no device management push. To help prevent shadow IT, admins can also block personal and other outside Claude accounts in Claude Desktop on managed computers. Owners can also limit which workspace folders people can use with Claude.
Endpoint Detection and Response (EDR) in Cowork and unified Claude
When Cowork and unified Claude work locally, they run shell commands and code in an isolated virtual machine on the user's computer for additional protection. That isolation helps protect the device, and security teams have asked for the same visibility into the virtual machine that they have everywhere else on the endpoint.
Admins can now run their organization's EDR sensor inside the Cowork virtual machine. The sensor reports activity there to the same console your security team already monitors. This covers the virtual machine on the user's computer, not Cowork sessions in the cloud.
Admins set up the integration through device management on macOS and Windows. Each time the virtual machine starts, Claude verifies the sensor package's signature from your EDR vendor before installing it. Sensors run in detection mode: they report activity to your security team and don't block it. The integration works with supported EDR vendors, which are listed in the Help Center.
Getting started
These features are available for Claude Enterprise, with some exceptions during beta listed in the Help Center.
The security center is in beta. Inference hooks, including prompt hooks and pre-tool-call hooks, are generally available. Admins can manage both inference hooks and the security center in Organization settings.
Centralized management is also in beta. To start setup, an admin of any organization under your parent goes to admin.claude.com and proposes the parent organization admins. Admins of the other organizations review and approve, and the last approval completes setup. Setup can't be undone, so identify your parent organization admins before you start.
Signing members out through the Admin API and the self-serve IP allowlist are in beta. Owners can manage Claude Desktop settings in Organization settings, also in beta.
Endpoint detection and response in Cowork is in beta on macOS and Windows for Claude Team and Enterprise, and for the Claude desktop app on Amazon Bedrock, Google Cloud Vertex AI, and Microsoft Foundry, deployed through MDM for supported vendors.
Original source - Nov 4, 2026
- Date parsed from source:Nov 4, 2026
- First seen by Releasebot:Nov 5, 2026
New agents and products for security, productivity, and creative work on Claude Marketplace
Claude expands its Marketplace with more than 25 partner agents and products across security, development, creative work, and productivity. Eligible enterprise customers can apply committed Anthropic spend to these solutions, making it easier to use Claude alongside tools from partner platforms.
We’ve added new agents and products to Claude Marketplace, where teams find partner tools and services to help them get more from Claude. The additions cover security, developer infrastructure, creative, and productivity.
Eligible enterprise customers can apply a portion of their committed Anthropic spend toward these solutions. This lets them use one commitment across Claude and partner products, whether they’re buying something new or expanding with a platform they already use.
There are now over 25 partner agents and products on the marketplace. Here are the latest additions and what teams can do with them.
Products and agents for securing code and systems
- Chainguard: Chainguard Harness builds applications from source in an isolated microVM and probes the live app for exploitable vulnerabilities. It helps teams fix what Claude finds, with custom remediation recommendations for reproducible vulnerabilities.
- Checkmarx: Checkmarx One pairs rules-based analysis with AI reasoning to find vulnerabilities in code. It helps teams prioritize findings and fix them before code ships.
- Cyera: Cyera Agent Guardian inventories Claude deployments, governs permissions before Claude runs, and enforces policy on prompts, files, and tool calls. It helps teams test those controls through red teaming.
- Rubrik: Rubrik Code Guardian uses frontier AI models from Anthropic to review a secure copy of GitHub or Azure DevOps repositories for multi-step attack paths. It helps security and engineering teams rank issues by severity and turn confirmed critical ones into tracked tickets.
- Tanium: Tanium Cloud gives teams real-time visibility and control across their endpoints. It helps IT and security teams find and fix vulnerabilities, misconfigurations, and missing patches.
Development infrastructure for engineering teams
- Datadog: Datadog Agent Observability traces agent execution through tools and services. It helps teams improve agent quality, performance, and cost efficiency by surfacing production patterns and recommending fixes.
- Netlify: Netlify Enterprise deploys apps, sites, and agents to a global edge network, with preview URLs on every change. It helps teams take what they build with Claude from prototype to production with no infrastructure to configure, and includes SSO, role-based access, and audit logs.
Tools for marketing and creative work
- AirOps: AirOps provides an agentic platform for AI search strategy, content, and multichannel execution. It helps marketing teams analyze brand performance in AI search and tie results to pipeline and revenue.
- Runway: Runway generates and edits video, images, and audio. It helps creative and marketing teams turn a brief into finished assets and edit footage with natural language.
- Webflow: Webflow provides built-in tools to build, manage, and optimize websites. It helps marketers, designers, developers, and agents make changes, with controls and governance built in.
Productivity apps for every team
- Asana: Asana AI Teammates are prebuilt agents that use context from the Asana Work Graph, each with its own identity, scoped permissions, and audit trail. They help teams handle multi-step work, routing decisions that need judgment to the owner.
- Glean: Glean connects company knowledge and workflows across systems. It helps employees find answers and complete multi-step tasks across connected apps.
- monday: monday agents work inside projects, boards, docs, and meetings, using their owners and deadlines as context. They help PMO, IT, marketing, finance, and operations teams control what AI can access, approve, and spend.
- Zoom: Zoom Agentic Search answers questions inside Claude using the latest meeting summaries, work conversations, documents, and connected third-party sources. Teams get permission-aware results without analyzing raw transcripts or chaining tools together.
Get started
You can browse all agents and products on Claude Marketplace and request to buy from any listing. If you’re building on Claude and want to join the marketplace, see the ways to join.
Original source - Nov 2, 2026
- Date parsed from source:Nov 2, 2026
- First seen by Releasebot:Nov 2, 2026
Make long-running agents faster with message threads
Claude adds message threads to the Messages API in public beta, letting agents send only new messages between turns to reduce latency in long-running sessions. The feature is available across Claude Platform and supported cloud offerings, with token usage unchanged.
New in the Messages API, send your conversation once, and the API receives only what’s new with every turn.
Message threads is now available in public beta on the Claude Platform. With message threads, agents no longer need to resend the full conversation history on every turn, reducing latency for long-running sessions.
How message threads works
A coding agent might make hundreds of requests in one session, and each request resends every earlier message and tool result. Once a conversation reaches hundreds of thousands of tokens, resending all of it adds time before Claude starts responding. With message threads, agents send only what’s new since the last turn, which reduces time to first token (TTFT).
With message threads on by default for most Claude Code users, requests with 500k to 1M tokens see median TTFT drop by about 35%.
To use message threads, add the thread parameter to Messages API requests. The first request includes the full conversation and starts a thread. Each request after that includes only the new messages and the ID of the previous response. Between turns, we hold each thread in memory, where it’s encrypted and not written to disk. A thread expires 5 minutes after its last request and your client then resends the full conversation to start a new one. While each request is smaller with message threads, Claude still reads the full conversation on every turn, so token usage stays the same.
Message threads is best for active sessions where latency matters, including:
- Long-running coding agents, where each tool result or file edit adds to the conversation.
- Computer use agents, where screenshots stay with the thread instead of being re-uploaded on every turn.
- Document and image-heavy workflows, where requests are made smaller.
The more context an agent carries, the more message threads can reduce time to first token.
Getting started
Message threads is available now in public beta on the native Claude Platform, and on Claude Platform on AWS, Claude in Microsoft Foundry, and on Claude Models on Google Cloud (Anthropic managed). Standard Claude token rates and existing rate limits apply. See the documentation to get started.
Original source - Oct 28, 2026
- Date parsed from source:Oct 28, 2026
- First seen by Releasebot:Oct 29, 2026
Smart reports, surveys, and pooled group budgets for Claude Enterprise
Claude Enterprise now offers generally available smart reports, in-app surveys, and pooled group budgets, helping organizations understand team workflows and spending, gather feedback, and share budgets across groups.
In many organizations, members have identified the unique work that Claude can unlock. The next step is expanding that work to every team.
Smart reports show what that work is, and where that work is happening, in-app surveys capture their feedback about how Claude is enabling them to do new work, and pooled group budgets let admins set one shared budget per team. All three are now generally available for Claude Enterprise.
Smart reports show how your teams work in Claude, and how to spread what’s working
Smart reports surface what a team gets done with Claude, and what that work costs. The reports show ambitious work your teams are doing with Claude, and how Claude made it possible. They then show how to turn that work into repeatable workflows, so the rest of your organization can do it too.
Pick a team, a date range, and the products to include. Claude analyzes a sample of the team’s transcripts and groups the work into workstreams. See the spend for each one, the deliverables produced, and the most common points of friction, such as a missing connector or a failed tool call.
Each report has one consolidated list of recommendations, including recurring workflows to turn into skills and rules to add to your code repository. Share any finding as an artifact with the people who can act on it. Reports also answer custom questions about model usage and cost, and admins can save their questions and custom insights as templates to reuse in future reports. If a spend limit is holding someone back, admins with billing permission can raise it from the report.
Owners can let team leads who aren’t admins run reports for their own groups, so the people closest to the work act on the findings. Smart reports help admins understand adoption and inform investment planning, but they aren’t for evaluating individual performance or making employment decisions.
In-app surveys capture feedback
In-app surveys add the team's own perspective on that work. The default questions focus on value: the most valuable thing someone has done with Claude recently, how Claude changed the time that work took, which use of Claude a teammate should copy, and, if the team lost access tomorrow, what would break or slow down first. Admins can customize or remove questions and choose who receives a survey, when it runs, and where it appears. Members see it as a short card after a reply in the tool they’re already working in.
Responses appear on the survey page as they arrive, and admins can export them to a spreadsheet. In-app surveys can now be enabled for organizations that use customer-managed encryption keys, and for organizations that set one retention period for all data, surveys and their responses are deleted on that schedule.
In-app surveys are treated as your data, so Anthropic accesses them only as necessary to operate the service.
Pooled group budgets put spend where the work happens
Pooled group budgets give a group one shared monthly budget, so people who use Claude heavily are less likely to hit an individual limit early in the month while others leave budget unspent. Member limits still work as a guardrail against unusually high individual use. Every request counts against both, and a member stops at whichever runs out first. When someone hits a limit, they can request more from inside Claude, and the request goes to admins for review. The setup suggests an amount based on the group's recent usage, and admins with billing permissions receive email alerts at 50%, 75%, 95%, and 100% of a budget.
Getting started
Smart reports, in-app surveys, and pooled group budgets are generally available today for Claude Enterprise. Availability varies by configuration, including for organizations with a HIPAA configuration or customer-managed encryption keys. Visit the Help Center for eligibility and detailed setup steps.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.