Claude Blog 采集 (2026-07-21)¶
共采集 5 篇文章
📋 文章索引¶
- Giving admins more visibility and control over Claude spend - Jul 02, 2026 (评分: 9.0)
- How Anthropic's marketing operations team uses Claude Cowork to automate reporting and campaign builds - Jul 08, 2026 (评分: 9.0)
- How people are using Claude Cowork - Jul 07, 2026 (评分: 9.0)
- Introducing routines in Claude Code - Apr 14, 2026 (评分: 9.0)
- Introducing the Claude apps gateway for Amazon Bedrock and Google Cloud - Jun 29, 2026 (评分: 9.0)
Giving admins more visibility and control over Claude spend¶
来源: Claude Blog 发布日期: Jul 02, 2026 采集时间: 2026-07-21 价值评分: 9.0/10 正文字数: ~1529 字符
摘要¶
Richer admin analytics, model-level entitlements, and spend alerts for Claude Enterprise so admins can track adoption, manage cost, and set guardrails that fit their org.
正文内容¶
New analytics and cost controls are available for Claude Enterprise.
We’re introducing richer admin analytics, model-level entitlements, and spend alerts for Claude Enterprise. As Claude takes on increasingly difficult and complex agentic work across the organization, usage and cost patterns look different from a standard chat tool. These controls give admins the visibility to understand how Claude is being used and the tools to manage costs. Today's additions build on controls Anthropic already provides: spend caps at every level, access and model routing, a usage analytics dashboard with exports and an Analytics API, and effort controls. Richer analytics and more granular cost controls are the newest additions to a control surface we've been building on for months.
Getting started For admins managing Claude across their organization: explore usage and cost breakdowns in the admin console, set model defaults and spend limits by group, and configure spend-threshold alerts to stay ahead of overages. Usage data is available in the admin dashboard, and the Analytics API lets finance and IT pull the same metrics into existing reporting systems, learn more here .
Explore more product news and best practices for teams building with Claude.
Transform how your organization operates with Claude
Product updates, how-tos, community spotlights, and more. Delivered monthly to your inbox.
Please provide your email address if you'd like to receive our monthly developer newsletter. You can unsubscribe at any time.
采集自 Claude Blog，由 collect_claude_blog.py 自动采集
How Anthropic's marketing operations team uses Claude Cowork to automate reporting and campaign builds¶
来源: Claude Blog 发布日期: Jul 08, 2026 采集时间: 2026-07-21 价值评分: 9.0/10 正文字数: ~1264 字符
摘要¶
How the marketing operations team at Anthropic uses Claude Cowork to automate marketing reporting and marketing campaign builds.
正文内容¶
Ian Chan and Annabel Custer, in marketing operations at Anthropic, share how they automate work their team used to do by hand across multiple platforms.
Marketing operations teams spend a meaningful portion of their time keeping the systems behind marketing programs in step with the business. While automation sits firmly in their purview, a lot of the work is anything but: martech tools don’t integrate cleanly with each other, reports are consolidated manually, landing pages get spun up one at a time. Ian Chan, on the marketing operations team at Anthropic, used to spend one to two days a week pulling together the weekly marketing metrics review. Annabel Custer, who focuses on campaign operations, used to set up each new event by clicking through Salesforce, HubSpot, Swoogo, and email tools in sequence. Both have now compressed days of manual work into hours by setting up workflows in Claude Cowork.
Explore more product news and best practices for teams building with Claude.
Transform how your organization operates with Claude
Product updates, how-tos, community spotlights, and more. Delivered monthly to your inbox.
Please provide your email address if you'd like to receive our monthly developer newsletter. You can unsubscribe at any time.
采集自 Claude Blog，由 collect_claude_blog.py 自动采集
How people are using Claude Cowork¶
来源: Claude Blog 发布日期: Jul 07, 2026 采集时间: 2026-07-21 价值评分: 9.0/10 正文字数: ~3345 字符
摘要¶
How are knowledge workers using AI? Anthropic's analysis of Claude Cowork sessions reveals the everyday tasks people delegate most—and what it means.
正文内容¶
In a sample of Claude Cowork sessions, we found that roughly half of all usage comprises “the work around the work”—tasks that are part of a broad swath of jobs, but are rarely a person’s core responsibility.
When we released Claude Code in 2025, we were surprised at how many non-technical users started playing around with it. People who had never opened the terminal before were using it to create agents that organized folders, deduplicated files, and wrote spreadsheet formulas. But for others, the terminal remained a slightly intimidating place—a literal “black box.” We built Claude Cowork to extend the agentic capabilities of Claude Code to the same chat interface people were already using to talk to Claude. Since we launched Claude Cowork in January, it’s become an especially potent tool for those whose work is focused on the creation and exchange of information, what many call “knowledge work.” People are using it for a variety of tasks that aren’t necessarily the hallmark of a specific role, but instead represent the connective work around a role that moves projects forward and keeps businesses running. That means tasks like drafting a status update, building a slide deck, or condensing reams of research into a single report. In this post, we share data from a sample of Claude Cowork sessions in May 2026, and explore what it tells us about how people are using AI in their day-to-day work, beyond the terminal. What the data shows We sampled 1.2 million anonymized and aggregated Claude Cowork sessions from May 11–31, 2026 and classified them according to a taxonomy of 20 different categories of work. Among our findings, the largest category of use is for “business process and operations”—things like pulling scattered updates into a single report, building onboarding checklists, and reconciling spreadsheets—at 33.4%. This makes sense, because business operations tasks span many different roles: people in finance, HR, and administrative jobs, for example, are all likely to make use of Claude Cowork for these types of tasks. Next was content creation and copywriting—synthesis-intensive business communications work like producing drafts, slide decks, posts, and proposals—at 16.4%. Staring down a blank page is often the first barrier to getting started, and Claude Cowork is a useful tool for threading thoughts and information into a rough draft. These types of tasks also cross roles: people in marketing, communications, business development, and project management, among others, are likely to collaborate with Claude Cowork on them. The next top categories are software development, at 8.7%; DevOps and infrastructure, at 7%; research and intelligence, at 6.4%, data analysis and business intelligence, at 5.8%, document processing and extraction, at 4.1%, and sales and revenue operations, at 4%. All other categories comprised less than 4% of the data set, including personal assistance at 3.8%, education at 2.4%, and meeting intelligence at 1.8%.
Explore more product news and best practices for teams building with Claude.
Transform how your organization operates with Claude
Product updates, how-tos, community spotlights, and more. Delivered monthly to your inbox.
Please provide your email address if you'd like to receive our monthly developer newsletter. You can unsubscribe at any time.
采集自 Claude Blog，由 collect_claude_blog.py 自动采集
Introducing routines in Claude Code¶
来源: Claude Blog 发布日期: Apr 14, 2026 采集时间: 2026-07-21 价值评分: 9.0/10 正文字数: ~1142 字符
摘要¶
Define repeatable routines that work your backlog, review your PRs, and respond to events in the cloud.
正文内容¶
Define repeatable routines that work your backlog, review your PRs, and respond to events in the cloud.
Today, we're introducing routines in Claude Code in research preview. A routine is a Claude Code automation you configure once — including a prompt, repo, and connectors — and then run on a schedule, from an API call, or in response to an event. Routines run on Claude Code’s web infrastructure , so nothing depends on your laptop being open. Developers already use Claude Code to automate the software development cycle, but until now, they've managed cron jobs, infrastructure, and additional tooling like MCP servers themselves. Routines ship with access to your repos and your connectors , so you can package up automations and set them to run on a schedule or trigger. How it works
Explore more product news and best practices for teams building with Claude.
Transform how your organization operates with Claude
Product updates, how-tos, community spotlights, and more. Delivered monthly to your inbox.
Please provide your email address if you'd like to receive our monthly developer newsletter. You can unsubscribe at any time.
采集自 Claude Blog，由 collect_claude_blog.py 自动采集
Introducing the Claude apps gateway for Amazon Bedrock and Google Cloud¶
来源: Claude Blog 发布日期: Jun 29, 2026 采集时间: 2026-07-21 价值评分: 9.0/10 正文字数: ~3266 字符
摘要¶
Connect Claude Code to Amazon Bedrock and Google Cloud with the new Claude apps gateway: corporate SSO login, centrally enforced policy, role-based access, per-user cost attribution, and spend caps—all from one stateless container on your infrastructure.
正文内容¶
Today, we're introducing the Claude apps gateway for Amazon Bedrock and Google Cloud. Previously, running Claude Code on these platforms has meant provisioning a cloud credential per developer, manually pushing settings to every laptop, and standing up separate tooling to see per-developer spend. The gateway is a self-hosted control plane that gives you corporate SSO login, centrally enforced policy, role-based access, and per-user cost attribution for Claude Code. Deploying the gateway The gateway is run as a single stateless container deployed on Linux and backed by a PostgreSQL database. It holds your upstream credential, authenticates developers against your identity provider, distributes and enforces managed settings, and reports per-user usage to a collector you operate. Onboarding a developer means adding them to your Identity Provider (IdP). Offboarding means removing them. The gateway is built and shipped by Anthropic inside the same claude binary your developers already install, so you can run it in one stateless container on your infrastructure. Because the gateway and the client are built together, the /login flow is gateway-aware, the client applies managed settings automatically at sign-in, and policy is enforced consistently on every request. How the gateway works The gateway handles: Identity. It acts as an OpenID Connect (OIDC) relying party against Google Workspace, Microsoft Entra ID, Okta, or any standards-compliant OIDC provider, and issues a short-lived session. No long-lived secrets sit on developer machines. Policy. You can define managed settings once on the server, and clients receive the policy at sign-in and the gateway enforces it on every request. You can adjust allowed models and default settings centrally. Telemetry. The client stamps a usage metric for every request, and the gateway relays it over OTLP to a collector you configure, in your network and on your retention schedule. Routing. The gateway holds your upstream credential and routes inference to the Claude API, Amazon Bedrock, or Google Cloud, with optional failover between providers. Spend caps. The gateway allows you to set daily, weekly, and monthly spend limits. Limits can be applied per organization, group, or user. The gateway does not send inference traffic or usage data to Anthropic unless you configure it to use the Claude API. We're also publishing the protocol the gateway uses, so other gateway developers can implement the same features. Getting started The gateway is available now. To get started: Deploy the gateway : Download the Claude Code CLI binary, point gateway.yaml at your OIDC issuer and upstream credential, and register one OIDC app in your IdP. Roll it out : Configure the forceLoginMethod and forceLoginGatewayUrl parameters in managed-settings.json on client machines. Clients connect to your gateway on first boot. See the documentation to learn more.
Explore more product news and best practices for teams building with Claude.
Transform how your organization operates with Claude
Product updates, how-tos, community spotlights, and more. Delivered monthly to your inbox.
Please provide your email address if you'd like to receive our monthly developer newsletter. You can unsubscribe at any time.
采集自 Claude Blog，由 collect_claude_blog.py 自动采集