Claude for Government Goes Public Beta: Claude Code and Cowork Hit FedRAMP High

Anthropic just closed one of the last gaps in Claude's enterprise story: the public sector. This week, the company announced that Claude Code and Claude Cowork are now available in public beta inside Claude for Government Desktop, running in a FedRAMP High authorized environment — the same tier of compliance required for the most sensitive unclassified federal workloads. It's built on the identical application commercial customers already use, just delivered through a hardened, agency-grade deployment path.

If you've been tracking Claude's momentum through Claude Sonnet 5's rollout, the Cowork expansion to web and mobile, or Anthropic's enterprise push into KPMG, PwC, and EPAM, this is the next logical step: government agencies were the one major buyer segment still largely locked out of Claude's most capable agentic tools. That changes now, and it opens a real opportunity for anyone building AI skills with an eye toward public-sector work.

What Actually Shipped

The announcement bundles two of Claude's most-used products into a single FedRAMP High-authorized desktop experience:

Claude Code in government. Public sector engineering teams can now use Claude Code — Anthropic's terminal-based coding agent — to build and modernize the software systems that run public services. That covers everything from legacy case-management systems to citizen-facing web portals, without engineers having to route sensitive government code through a consumer-tier environment. Claude Cowork in government. Cowork works directly with files on the desktop, letting agency staff delegate memo drafting, RFP reviews, casework summaries, and slide decks to Claude instead of assembling them by hand. This is the same Cowork model that just expanded to web and mobile for commercial users, now running inside a compliance boundary built for government data. Governance controls agencies actually need. This isn't just Claude with a government sticker on it. The release adds administrator controls for setting configuration defaults and allocating spend across departments, plus tamper-evident audit logs that support the formal Authorization to Operate (ATO) process security teams have to complete before any tool touches government systems. Local-first data handling. Conversation history is stored locally on the agency-managed device, inference runs inside the FedRAMP High boundary, and the application deploys through standard agency MDM platforms — the same device management tools IT departments already use to push and monitor software. Fixed-increment spend controls. Program offices can tie AI spend directly to appropriated funds using standard seats, or define their own seat tiers with spend and model limits. Usage is purchased in fixed increments with a hard not-to-exceed cap — a detail that matters enormously in government procurement, where open-ended usage-based billing is often a non-starter.

Why FedRAMP High Matters Here

FedRAMP (the Federal Risk and Authorization Management Program) is the framework federal agencies use to vet cloud services before they're allowed to touch government data. There are three impact levels — Low, Moderate, and High — and High is reserved for the most sensitive unclassified information: data where a breach could cause severe or catastrophic harm to operations, assets, or individuals.

Getting a product authorized at FedRAMP High isn't a checkbox exercise. It requires an accredited third-party assessment, continuous monitoring, and sign-off from a federal agency sponsor. Anthropic has been building toward this for a while — Claude in Amazon Bedrock was separately approved for FedRAMP High and DoD Impact Level 4/5 workloads earlier this year — and this release extends that same compliance posture to Claude's own desktop application, not just the underlying model API.

Practically, that means an agency IT team evaluating Claude for Government doesn't need to build a custom compliance wrapper around it. The audit trail, the spend controls, and the authorization boundary are already part of the product.

How This Compares to Claude's Other Government Access Points

This desktop beta isn't Anthropic's first move into regulated government infrastructure, and it's worth understanding how it fits alongside the other paths agencies already had:

Claude in Amazon Bedrock (FedRAMP High, DoD IL4/5). Agencies already running AWS GovCloud could access Claude models through Bedrock, approved for FedRAMP High and even Department of Defense Impact Level 4 and 5 workloads — the tier used for controlled unclassified information and some national security systems. This route is API-first and suits agencies with existing engineering teams building custom applications on top of Claude. Claude in Microsoft Foundry (GA, U.S. data region). For agencies standardized on Azure, Claude models became generally available in Microsoft Foundry this month, with inference running in a U.S. data region and native integration with Microsoft Entra ID for authentication — useful for agencies that already manage identity through Microsoft's stack. Claude for Government Desktop (this release). This is the first packaged, ready-to-deploy application — not an API an engineering team has to build around. An agency's IT department can push it through existing MDM tooling and have staff using Claude Code and Cowork inside a compliant boundary without writing a line of integration code. It's aimed squarely at agencies that want agentic AI capability now, without standing up a custom platform team first.

Put together, these three paths mean an agency can pick the access model that matches its existing infrastructure and in-house technical capacity — from full API control to a turnkey desktop app — while staying inside the same FedRAMP High compliance boundary either way.

What This Actually Looks Like Day to Day

It's easy to read "Claude Code for government" and picture only defense contractors and intelligence analysts. In practice, the use cases Anthropic is describing are far more mundane — and far more widely applicable across agency types:

• A state transportation department's engineering team uses Claude Code to modernize a decades-old permitting system originally written in a language nobody on staff still knows well, working feature by feature with Claude reading and explaining the existing codebase before touching it.
• A federal grants office uses Cowork to draft first-pass responses to routine public records requests, with a human reviewing and finalizing every output before it goes out — the audit log capturing exactly what Claude produced and what the reviewer changed.
• A county social services department uses Cowork to summarize lengthy casework files into consistent intake briefs, cutting the time caseworkers spend on paperwork so they can spend more of it on actual casework.
• An IT security team uses the tamper-evident audit logs not just for compliance sign-off, but as an ongoing record they can point to during budget reviews to show exactly how AI spend maps to work completed.

None of this requires exotic AI expertise. It requires people who know how to set up a Claude Code project, write a clear task for Cowork to execute, and review agentic output critically — skills that transfer directly from commercial Claude use.

What This Means If You're Building AI Skills for a Government Career

This launch matters beyond the enterprise press release. Government agencies — federal, state, and local — are enormous employers, and they've historically lagged the private sector in AI tooling because compliance requirements made adoption slow. That gap is now closing fast:

• California already piloted an Anthropic-built assistant, Poppy, with more than 2,800 state employees across 67 departments, with a full statewide rollout targeted for this month.
• Anthropic separately announced expanded Claude access across all three branches of the federal government earlier this year.
• Claude for Government Desktop now gives agencies a self-contained way to deploy Claude Code and Cowork without a lengthy custom integration.

If you're preparing for a Claude Certified Architect (CCA) credential or otherwise building toward an AI-adjacent role, government and public-sector organizations are becoming a real hiring channel — not just a slower-moving side market. Agencies rolling out FedRAMP High-authorized AI tooling need people who understand both the technical side (prompting, agent workflows, Claude Code) and the compliance context (audit logging, ATO processes, spend governance) that public-sector deployments require. That combination — technical AI fluency plus an understanding of governed, auditable deployment — is exactly the kind of practical knowledge that separates a resume that gets a second look from one that doesn't.

How to Get Ahead of This Shift

1. Learn Claude Code fundamentals now, in a commercial environment. The Claude for Government version is functionally the same application — skills you build with Claude Code today for personal projects or your current job transfer directly. If you haven't set it up yet, our guide on getting started with Claude Code walks through installation and your first agentic session. 2. Understand agentic file work, not just chat. Claude Cowork's value in a government context is delegating document-heavy tasks — memos, RFP reviews, case summaries. If your current Claude experience is limited to chat-style Q&A, spend time with Cowork or an equivalent agentic file workflow so the concept of "delegate a task, review the output" feels native. 3. Get comfortable with governance vocabulary. Terms like FedRAMP, ATO, audit logging, and spend allocation aren't just compliance jargon — they're the vocabulary hiring managers in regulated industries (government, healthcare, finance) use to evaluate whether a candidate understands deployment, not just prompting. Our breakdown of Claude's enterprise admin analytics and spend alerts is a good primer on how these controls work in practice. 4. Track certification as a credential signal. A recognized certification is a fast way to prove baseline competence to a hiring manager who doesn't have time to evaluate your skills hands-on — especially in government hiring processes that lean heavily on formal qualifications.

Key Takeaways

• Claude Code and Claude Cowork are now in public beta inside Claude for Government Desktop, running in a FedRAMP High authorized environment.
• The release adds agency-grade governance: admin spend controls, tamper-evident audit logs for the ATO process, local conversation storage, and MDM-based deployment.
• FedRAMP High is the compliance tier for the most sensitive unclassified federal data — this is a meaningful trust signal, not a marketing label.
• Government and public-sector AI adoption is accelerating (California's Poppy rollout, expanded federal access), creating a growing hiring channel for people who combine AI fluency with governance literacy.
• The skills gap to close is small: the underlying tools are the same ones available commercially today.

Next Steps

Ready to build the skills this shift is rewarding? Start with our Claude Certified Architect (CCA) exam prep to build verifiable, resume-ready proof of your Claude expertise, and pair it with hands-on practice using Claude Code and Cowork on real projects. The agencies adopting this tooling need people who already know how to use it — get there first.