Claude Code v2.1.277 adds AGENTS.md support and gateway egress-boundary mode
cliClaude Code 2.1.277 introduces AGENTS.md as a fallback for CLAUDE.md (configurable under Project instructions in /config), a CLAUDE_GATEWAY_PROXY_IS_EGRESS_BOUNDARY=1 mode that hands hostnames to a forward proxy instead of resolving locally, and optional static `headers:` on gateway upstreams. Also: many fixes for -p/SDK sessions, resume/cache correctness, plugin install, sandbox globs, subagent MCP re-render breaking prompt cache, and headless cost totals.
An agent can now share project instructions with other tools via AGENTS.md (used when CLAUDE.md is absent), and operate behind egress-only forward proxies without local DNS resolution.
Notable: AGENTS.md adoption aligns Claude Code with the emerging cross-tool convention. Egress-boundary flag is useful for enterprise deployments. Many bug fixes affect SDK/headless agent workflows (prompt cache correctness on resume, subagent MCP re-render).
npm i -g @anthropic-ai/claude-code@2.1.277# Use AGENTS.md as shared project instructions
cat > AGENTS.md <<'EOF'
# Project instructions
- Use pnpm, not npm
- Run `pnpm test` before committing
EOF
# Launch Claude Code; with no CLAUDE.md present it now reads AGENTS.md
claude
# Or run behind a forward-proxy egress boundary
export CLAUDE_GATEWAY_PROXY_IS_EGRESS_BOUNDARY=1
export HTTPS_PROXY=http://proxy.internal:8080
claude -p "summarize this repo"