Skip to content
Only Tutorials#Coding
  1. Google Developers Blog60

    Google study finds stale TODO bug references distract coding agents in 13% of sessions

    ) references. Agents acted on the bug ID in 6% of encounters, and 83% of those actions were unprompted by the developer; 41% of unprompted detours chased already closed tickets while 57% hit still-open bugs and expanded scope. Controlling for developer, codebase complexity, task type, model tier and other factors, unprompted bug detours added 70% more steps, 77% more tokens and 105% more wait time per session.

    Why it matters: Google's large-scale trace analysis shows stale TODO bug references pull coding agents into unprompted detours, and its cleanup agents removed thousands of obsolete references with over 95% reviewer acceptance.

  1. Anthropic · Claude.dev62

    How the Claude Code team does code review

    The Claude Code team describes its layered code review flow, in which most reading is done by machines and human attention is reserved for risk-based approval. From June to September, merged pull requests to the Claude Code codebase more than doubled while the share that had to be reverted fell by more than 40 percent. The process stacks verification before the PR, required CI, Claude review, security review, risk-tiered human approval and a merge queue with flags and fast rollback, and the team turned past incidents into a daily eval set for the reviewer.

    Why it matters: Anthropic's Claude Code team details how it moved most code reading to automated layers while merged PRs doubled and reverts fell over 40 percent, offering a transferable review model for agent-heavy teams.

  1. OpenAI Developers Blog62

    OpenAI publishes Codex prompting guide for gpt-5.3-codex

    OpenAI released a Codex prompting guide for developers calling the Codex-tuned gpt-5.3-codex model directly through the API, recommending medium reasoning effort for interactive coding and high or xhigh for the hardest tasks. The guide covers migrating an existing harness to the open-source codex-cli, including the standard Codex-Max prompt, the apply_patch, shell_command and update_plan tools, and first-class compaction via /compact in the Responses API for multi-hour sessions. It also describes the new phase field, supported only on gpt-5.3-codex, which marks assistant items as commentary or final_answer and must be preserved in history to avoid performance degradation.

    Why it matters: OpenAI's official guide details how to tune prompts, tools and compaction for gpt-5.3-codex, giving teams a concrete migration path for their own coding agents.

You are all caught up