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.

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 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.