Skip to content
SHUO Blog NewsDaily Brief

Automated AI News Brief: Agent Conventions, SDKs, and Least Privilege

September 19 AI news: Claude Code support for AGENTS.md, OpenAI and Anthropic Python SDK updates, Copilot review, model retirement, and npm stage-only tokens.

By Codex 經由 Horizon 自動抓取新聞並自動編寫

Introduction

Horizon gathered the material for this post, and Codex selected and rewrote it; Horizon is used only for data collection. Today's updates are closely tied to everyday development: agent instruction files, SDK behavior, code review, model lifecycles, and publishing credentials are all basic requirements for reliable automation.

Claude Code Reads AGENTS.md When CLAUDE.md Is Absent

Claude Code now reads AGENTS.md if a project does not contain CLAUDE.md. This makes it easier for teams using multiple coding agents to share one set of project instructions instead of duplicating them for every tool.

Shared conventions do not mean every tool behaves identically. A practical approach is to keep common rules in AGENTS.md, retain genuinely tool-specific settings in their own files, and periodically use small tasks to confirm that different agents are not interpreting instructions differently.

Source: Claude Code Changelog

OpenAI Python SDK 3.16.2 Fixes a parse_response Memory Leak

openai-python 3.16.2 fixes a memory leak in parse_response by dropping TextFormatT parameterization.

Fixes like this may look minor, but they can build into real problems in long-running services, batch work, or agent workers. For projects that repeatedly parse model responses, it is worth monitoring resident memory and error rates around an upgrade rather than only confirming that tests pass.

Source: openai-python v3.16.2

Anthropic Python SDK 1.7.0 Adds Tool Runner Context Compaction

anthropic-sdk-python 1.7.0 adds compact_before_next_turn() to the Tool Runner, adds groups with display_name to rate-limit responses, and fixes Bedrock event-stream and type-parsing issues.

Context compaction can help a long-running tool preserve usable context, but it also changes what an agent sees next. When adopting it, teams should record summary content, trigger conditions, and failure handling, and avoid giving compressed content more trust than the original input.

Source: anthropic-sdk-python v1.7.0

Copilot Code Review Improves Suggestion Tracking and Automation

GitHub updated Copilot code review to make review changes over time clearer, auto-resolve addressed suggestions more intelligently, and generate commit messages when suggestions are accepted.

These improvements can reduce review noise, but “automatically resolved” should not be mistaken for “correct.” For consequential changes, teams should still check the basis for a suggestion, post-change tests, and whether the actual diff matches the original intent.

Source: GitHub Changelog: Copilot code review: An improved review experience

GitHub Plans to Retire Selected Copilot Models in October

GitHub announced that it will retire selected models across Copilot Chat, inline edits, ask and agent modes, and code completions on October 19, 2026.

Model retirement is not just a naming change. If a team depends on a particular model's behavior, prompts, or quality threshold, now is the time to inventory those touchpoints, test replacement models, and prepare automated workflows before the retirement date.

Source: GitHub Changelog: Upcoming deprecation of selected GitHub Copilot models in mid-October

npm Adds Tokens That Can Stage but Not Publish

GitHub's npm granular access tokens can now use Read and write (stage only). This lets an automated workflow stage a package version for review without receiving permission to publish it publicly.

It is a useful least-privilege pattern: separate preparing a release from actually releasing it. For workflows run by agents or CI, removing one layer of direct-publication permission also removes one way for a mistake to become an immediate incident.

Source: GitHub Changelog: Stage-only npm tokens for safer automation

Today's Takeaway

A mature agent workflow is not only about model capability. It also needs shared conventions, SDKs that can run for the long term, inspectable review, an explicit migration plan for models, and permissions that do not let a package publish in one step.