AI Weekly Malaysia

Hillel Wayne's Buttondown post What TLA+ can and can't check responds to Boris Cherny's claim that Opus used TLA+ to find race conditions in code, pushing back on the idea that formal methods will solve agentic software development. It walks through what TLA+ can express, including behaviors as state sequences, the temporal operators [] always, P' next, and <> eventually, plus invariants and action properties, while promising to focus on properties TLA+ cannot even express. The excerpt ends mid-explanation of action properties and stutter-invariance, and the Hacker News thread had 222 points and 47 comments.

Why: If you use coding agents like Claude Code or Opus for bug-fixing, do not treat a TLA+ run as a turnkey correctness guarantee: the author notes you still need a property to verify, and correct designs do not automatically translate into correct code. Teams should decide who writes and reviews the invariants or properties before trusting agent-generated fixes.

Anthropic introduced mods for Claude Code: small TypeScript functions that hook into events Claude Code emits (tool calls, permission prompts, UI draws) to run before, after, instead of, or wrapping them. A mod can rewrite prompts before they reach the model, block/retry tool calls, approve or deny permissions, redact secrets from tool output, and add or replace UI elements in the CLI, desktop app, or both. Mods ship inside plugins and are explicitly not sandboxed — they run with the same machine access as Claude Code itself, so the post says to install only from trusted sources.

Why: If your team runs Claude Code, this is a new install surface: mods arrive as plugins and execute unsandboxed with the same access as Claude Code, so the practical decision is whether to allow third-party mods at all and who reviews them. The useful capability to note is prompt/tool-call interception — you can now redact secrets from tool output before Claude reads it, or block and retry specific tool calls, without waiting on Anthropic to ship a feature. Hooks previously could not rewrite events, draw UI, or replace features; mods can, which changes what you'd build in-house versus install.

A 1h32m Latent Space episode with Anthropic's Thariq Shihipar framed as a catch-up on Claude Code's recent releases: Opus 5.5, a Plugins portal, and Cloud Sessions/Claude Projects arrived 'last week,' Sonnet 5.5 shipped the day of recording, and Claude Mods — user-extensible behaviour for Claude Code, with a linked cheatsheet and GitHub issue — is the item the show flags for special attention. The intro also lists Anthropic's claimed numbers (largest-ever raise in May at $47B ARR, $65B ARR in July, IPO target of $2T with ~$100B ARR estimated for end-2026) and earlier Claude Tag, Fable 5 and Mythos 5.1 launches, plus a Boris Cherny post about a community-built Tetris-in-Claude mod (603K views, 312 replies). The excerpt itself contains no benchmarks, pricing, or migration detail — it is a launch list plus a podcast pointer.

Why: If you run Claude Code in a team, the two things that change your setup are Claude Mods and the Plugins portal: they are a distribution channel for shared agent behaviour, so the decision is whether to package your existing prompts/config as a mod/plugin or keep it as a private repo. Separately, Opus 5.5 and Sonnet 5.5 landing roughly a week apart means any model version pinned in your CI or agent config will likely need bumping soon, so pin deliberately and note what you'd have to re-test. Treat the ARR, IPO and model-launch figures as vendor framing — the text gives no independent verification.

Anthropic published a customer announcement that Barclays is expanding its use of Claude across the bank, targeting Claude Code adoption by 50% of its developer population by end of 2026 and a majority of software engineers in 2027. The post also cites Barclays' Colleague Knowledge Assistant, live since 2025 and built on a retrieval-augmented generation architecture over Claude, used by more than 16,000 colleagues supporting over 20 million UK retail customers. No measured productivity, cost, or quality results are given, and the numbers are Barclays' stated targets plus a vendor-published adoption claim.

Why: This is a vendor-published case study, not a measurement, so do not use it as evidence that AI coding tools cut delivery time. What is usable is the target shape: a large regulated bank publicly committing to 50% Claude Code adoption among developers within a year, which is a concrete benchmark to cite if you are arguing for or against an internal rollout, and a signal for founders selling AI tooling into banks or regulated enterprises that procurement conversations now assume governance and RAG-style knowledge assistants, not just model access. Nothing here changes what a Malaysian builder ships this week; there is no pricing, availability, or regional detail.