AI Weekly Malaysia

Anthropic published a guide on reducing token costs and improving efficiency when using Claude Code. Key recommendations include running /clear between tasks to avoid sending irrelevant context, setting model and effort levels before starting to prevent prompt cache busts, and using @-mention for files instead of naming them to save Read calls. It also advises using /compact before taking a break since the prompt cache expires after an hour.

Why: If you use Claude Code, changing your model or effort level mid-conversation busts your prompt cache and increases token cost, so you should configure these upfront. You should also run /compact before stepping away, as summarizing while the cache is still active is significantly cheaper.

Anthropic is making auto mode the default in Claude Code from August 14, 2026, for Pro, Max, and Team plans, with Enterprise and API platforms remaining opt-in for now. Auto mode routes every tool call through a classifier that blocks irreversible or destructive actions, falling back to manual approvals after 3 consecutive or 20 total blocks per session. Anthropic's controlled study of 1,053 paid testers found humans caught deliberately inserted dangerous commands only 13.6% of the time while auto mode blocked 89%, and that users approve 97% of permission prompts—suggesting manual review is largely muscle memory.

Why: If you use Claude Code on Pro, Max, or Team plans, your sessions will auto-accept tool calls unless you explicitly change the default after August 14. Decide now whether to keep auto mode or revert to manual approvals, and understand the fallback threshold (3 consecutive blocks or 20 per session) so you know when you're back to manual. The 97% human approval rate is a useful data point if you're building trust models for AI agent guardrails in your own products.

Developers report that Anthropic's Claude API returns empty or truncated thinking blocks for Opus 4.8 and Sonnet 5 even when summarized thinking is explicitly requested, yet the underlying reasoning tokens are still billed in full as output tokens. Anthropic's own documentation confirms users are charged for all thinking tokens generated regardless of whether the thinking text is returned, and the issue may stem from display-summary testing rather than a broad outage.

Why: If you enable thinking on Claude Opus 4.8 or Sonnet 5, you may be paying for reasoning tokens you never see — so audit your token usage and consider lowering the thinking budget or disabling thinking entirely until the blank-block behavior is confirmed fixed. This directly affects your API cost per call.

Anthropic will embed imperceptible text watermarks and digitally signed file metadata in output from Claude models, citing EU AI Act compliance. Marking will apply worldwide across Claude Platform API, Claude, Claude Code, Claude Cowork, Claude Tag, and third-party providers (AWS, Google Cloud, Microsoft Foundry)—not just EU deployments. No technical documentation or examples have been released yet, and researchers have already demonstrated that image watermarking can be undone, raising questions about how resistant text watermarks will be to OCR-based stripping.

Why: If you ship products on the Claude API or use Claude in agent pipelines that generate customer-facing text, your outputs will carry watermarks globally once this rolls out. Decide now whether provenance marking creates issues for your use case—e.g., content platforms, SEO pipelines, or white-label SaaS where AI-generated text provenance could become a liability or competitive disadvantage. Also evaluate whether watermark persistence through copy-paste and editing affects downstream processing in your stack.

Grace Clarke, a self-taught AI educator and former marketing consultant, rebuilt her entire service business on Claude Code, automating 20 hours of weekly admin into a pipeline that handles proposals, client tracking, and email. She teaches a practical workflow including 'voice guide' skill files for consistent AI output, 'intent engineering' over prompt engineering, and a custom Gmail replacement built in under 30 minutes via Cowork.

Why: For non-technical builders and vibe coders, this is a concrete blueprint for running a real service business on Claude Code rather than just experimenting. The specific techniques—skill files for voice consistency, password-protected interactive HTML proposals instead of traditional docs, and handing off work between Claude Code and Cowork via Markdown session files—are immediately actionable patterns you can copy for your own workflows.

Anthropic will watermark all text and files generated by models released after August 2, 2026, to comply with the EU AI Act's Transparency Code. The watermark travels with copy-pasted text and may persist through some editing, though Anthropic hasn't clarified how much editing removes it. Watermarking applies across Claude API, Claude, Claude Code, Claude Cowork, and Claude Tag, with file watermarking using the C2PA open standard.

Why: If you ship Claude-generated text to end users—especially EU customers—your output will now carry an embedded watermark that survives copy-paste and some editing. Builders using Claude Code or the API should test whether watermarks affect downstream processing, content pipelines, or user-facing output, and factor this into compliance posture for EU markets.

Anthropic will begin digitally watermarking AI-generated text and images produced by Claude, as part of its compliance plan for the EU's Artificial Intelligence Act. The article is primarily a headline-level announcement; the full body text was not provided beyond site navigation boilerplate.

Why: If you ship Claude-generated content into products or content pipelines serving EU users, expect watermarking to be embedded in outputs—this could affect content provenance, SEO, plagiarism detection, and downstream processing. Builders should check whether watermarked outputs break existing text/image pipelines before the feature rolls out.

Anthropic extended its Compliance API to cover Claude Cowork (desktop, web, mobile) and Claude Code (CLI, desktop app) in beta for Claude Enterprise customers. The new session endpoints return consolidated transcripts including prompts, responses, tool calls, MCP content, and metadata like verified user ID and timestamps, with no separate integration required beyond an existing Compliance Access Key.

Why: If your team uses Claude Code or Cowork under a Claude Enterprise plan, compliance and security teams can now pull session transcripts for audit and eDiscovery without building separate logging infrastructure. Note the gaps: Claude Code on the web, Claude Platform sessions, and Bedrock/Vertex AI/Foundry deployments are NOT covered, so if you run Claude Code through a cloud provider you still lack this visibility.

Anthropic updated Claude Tag, its Slack-integrated assistant, to read context across an entire channel rather than processing messages one at a time. The previous lightweight yes/no classifier is replaced with a four-option decision system (reply inline, start a thread, route to existing work, or stay silent), and Anthropic reports roughly 30% better accuracy in deciding when to proactively respond. The additional context does not count toward usage or spend limits on any plan.

Why: If your team uses Claude Tag in Slack, expect more unsolicited but context-aware interventions—test it in a low-stakes channel first to see whether the new proactive behavior helps or creates noise. If you were holding off due to spend concerns, the no-additional-cost framing removes that barrier, though it's worth watching actual token consumption over time.

Anthropic CFO Krishna Rao is leading preliminary investor meetings ahead of a potential IPO, but discussions have been high-level with no specific financials or valuation on the table yet. Anthropic confidentially filed its prospectus with the SEC in June but has not disclosed an IPO timeline. Meetings have covered Claude models, Claude Code development, enterprise positioning, and management.

Why: For founders and AI/ML builders, the key signal is that Anthropic is positioning Claude Code and enterprise adoption as its IPO narrative — expect continued investment in coding tools and enterprise features as it courts public market investors. No action required yet, but if you're building on the Claude API or Claude Code, expect product roadmap acceleration and possible pricing changes as IPO pressure mounts.

The headline indicates Anthropic is adding an invisible watermark to Claude's AI-generated text, but the extracted article text contains only Ars Technica's cookie consent and privacy policy boilerplate—no substantive reporting is present.

Why: No actionable details are available from the provided text. Builders cannot assess detection methods, API impact, or compliance implications without the actual article content.

Anthropic published a help center page explaining how Claude marks AI-generated content, but the article text extracted contains only the help center navigation and table of contents, not the actual policy or technical details.

Why: The source text does not contain the substantive content needed to determine what watermarking or labeling mechanism Claude uses, so no concrete action or decision can be derived from it.