🧭 SynthID-Text Watermarks Go Live Today on Mythos 5, Opus 4.7, Opus 4.6, and Sonnet 4.6
Starting today, November 3, invisible text watermarks are embedded in output from four additional Claude models: Claude Mythos 5, Claude Opus 4.7, Claude Opus 4.6, and Claude Sonnet 4.6 — with the Amazon Bedrock rollout expected to follow within a few days. The watermark, a variant of Google DeepMind's SynthID-Text technique first published in Nature in 2024, works by subtly biasing the model's token-selection distribution so that the resulting text carries a statistically detectable pattern. The meaning, quality, and readability of the output are unchanged — and the signal survives copy-paste and moderate editing.
Who can detect it — and who cannot
- Eligible organisations under EU law (regulators, law enforcement, journalists, fact-checkers, researchers) can access a private watermark detector via Anthropic's API.
- General users and developers cannot currently detect watermarks in their own Claude-generated text — there is no public inspector endpoint.
- Workarounds exist for now: Models pre-dating the rollout (back to Claude 3 / Opus 2023 era) remain unwatermarked, and some API-level settings in older versions may suppress the pattern. Anthropic has not committed to closing these gaps on a fixed timeline.
Why this matters for operators and developers
The watermark is applied globally — including the US and Japan — because Anthropic cannot yet scope it to EU-only traffic. There is no opt-out. For operators using Claude output in published content, ghost-writing services, or automated content pipelines, this means all output now carries a verifiable AI provenance signal that authorised parties can check. Operators should review their terms-of-service and disclosure requirements accordingly: the watermark does not replace an obligation to disclose AI use, but it does create an independently verifiable trail that regulators can audit.
Practical note for high-volume API users
The watermark has no measurable latency or token cost impact — it operates at the sampling layer, not as a post-processing step. If your pipeline is already logging model outputs for compliance purposes, no changes are required. If your application explicitly strips or alters model text (paraphrasing APIs, translation layers), be aware that significant paraphrasing may degrade — but not fully remove — the watermark signal.
watermarking
SynthID-Text
EU AI Act
Mythos 5
Opus 4.7
Opus 4.6
Sonnet 4.6
AI provenance
compliance
🧭 CrowdStrike Launches Falcon Guardian AIDR for Claude Cowork — Plus an AI Kill Switch — at Fal.Con Europe
At Fal.Con Europe 2026 today, CrowdStrike announced native Falcon Guardian AI Detection and Response (AIDR) protection for Claude Cowork, Anthropic's enterprise multi-agent workspace. The integration places Claude Cowork agents under Falcon's enterprise security control plane — the same sensor stack that already covers Claude Code, GitHub Copilot, and Microsoft 365 Copilot — covering agent creation through execution on both Windows and macOS endpoints. Alongside this, CrowdStrike introduced the AI Kill Switch, a new capability in Falcon Guardian that allows security teams to terminate a misbehaving agent in real time, block it from restarting across the entire organisation, and cut its enterprise network access.
Falcon Guardian for Claude Cowork — what's new
- Unified AIDR surface: All Claude Cowork agent activity (tool calls, subagent spawns, MCP server interactions) is now visible in the Falcon console alongside traditional endpoint telemetry.
- Prompt injection detection: SafeMind-powered classifiers flag attempts to hijack agent instructions via poisoned tool results or malicious system-prompt fragments — a critical concern as agentic pipelines ingest untrusted web and document content.
- AI Supply Chain Protection: Falcon Guardian scans Claude Cowork plugins and MCP connectors for malicious AI skills, analogous to software supply-chain scanning for npm or PyPI packages.
- Endpoint Network Inspection (new, in preview): Monitors AI traffic entering and leaving endpoints, enabling policy enforcement on model-to-model and agent-to-external-service calls at the network layer.
AI Kill Switch
- Terminates unauthorised agents at the Falcon Gateway; endpoint-level termination is listed as "coming soon."
- Blocks the agent from launching again across the entire organisation — not just the affected device.
- Cuts the agent's enterprise network access, preventing exfiltration while the incident is investigated.
What Cowork operators should assess now
If your organisation already runs Falcon on managed endpoints, enabling Falcon Guardian visibility for Claude Cowork requires a configuration change in the Falcon console — no new sensor deployment. Operators not yet on Falcon will need to evaluate whether adding a second endpoint agent is justified by the agentic security coverage. CrowdStrike also announced a planned acquisition of Fiddler AI, which will add agent observability and pre-deployment explainability capabilities to the platform — particularly useful for teams that need to validate agent behaviour before giving it broad tool permissions.
CrowdStrike
Falcon Guardian
Claude Cowork
AI Kill Switch
AIDR
prompt injection
enterprise security
Fal.Con Europe
Fiddler AI
🧭 Claude Code v2.1.317 — Email Privacy Guard, Agent SDK onFailure: "block", and a Cost Reporting API
Claude Code v2.1.317 landed today with a handful of developer-facing additions worth knowing about, alongside a significant batch of bug fixes. Three features stand out for production deployments.
Three features worth your attention
-
Email privacy check before web/shell tool calls. If a tool call (web fetch, shell command) is about to transmit your authenticated account email address to an external service, Claude Code now prompts you before proceeding. This catches a class of accidental PII leakage where agent-generated URLs or curl payloads silently include the logged-in user's identity. The check fires on both
WebFetch and Bash calls.
-
Agent SDK
onFailure: "block" for callbacks. The Claude Agent SDK's callback system now accepts onFailure: "block" as a policy — if a registered callback fails, the agent's execution is halted rather than silently degraded. This is the safer default for production pipelines where a failed on_compact or on_tool_result hook means critical state was not persisted.
agent = Agent(
model="claude-sonnet-5-5",
callbacks=[
CompactionHook(on_compact=persist_state, onFailure="block"),
]
)
-
Cost Reporting API for Claude Apps gateways. A new
GET /v1/organizations/analytics/cost endpoint is available for operators running Claude Apps gateways. It returns per-model, per-app, per-seat cost breakdowns and accepts from / to date parameters. Combine this with the existing OTel metrics (which now include anthropic.plan, anthropic.seat_type, and anthropic.provider) for full spend attribution without leaving the Anthropic platform.
Notable bug fixes
- MCP servers (project-level and local) no longer disconnect after the first conversation turn — a regression introduced in v2.1.314.
- Auto mode no longer fails silently when an LLM gateway returns a 403 or 422; it now surfaces the error and retries with a fallback model.
claude auth status no longer prematurely invalidates valid sessions on certain network configurations.
- Windows: fixed tool call refusals on volumes with paths exceeding the MAX_PATH limit when long-path support is disabled.
- OpenTelemetry export hangs are resolved — exports now time out after 10 seconds rather than blocking indefinitely.
Claude Code
v2.1.317
email privacy
onFailure block
cost reporting API
OTel
MCP fix
Agent SDK