Coding agents
What Claude Code, Codex, Copilot, Cursor and similar tools can and can't do. Every brief item about Coding agents, newest first, each with its primary source.
Timeline 63 items
-
Oct 8 · Thu · 2 items
- Safety github.blog ↗GitHub ships a purpose-built model for leaked secrets that reads surrounding code to catch unformatted passwords, coming to push protection and Copilot /security-review
Take · With agents committing at every step, the odds of a secret slipping into history only go up, and blocking it at push time is far cheaper than rotating it later. I'd pilot push protection on repos that already have GHSP and set a budget cap on AI Credits, since checks bill even when nothing is blocked. GitHub's note that agents shouldn't enable credit-consuming features without explicit authorization is worth copying straight into a team's agent rules.
From the Oct 8 brief · item 04 →
-
-
Oct 6 · Tue · 1 item
- Tools aws.amazon.com ↗AWS releases the aws-ai-ml skill so Claude Code, Codex and Kiro can benchmark SageMaker inference endpoints and generate deployment code
Take · Skills are becoming how cloud vendors compete for the coding-agent entry point: whoever's deployment know-how lives inside the agent gets picked more often. I like that it produces code rather than opaque actions, but benchmarks spin up real endpoints and real bills; give the agent a separate account with a budget cap before letting it run.
From the Oct 6 brief · item 02 →
-
-
Oct 5 · Mon · 1 item
- Tools github.blog ↗GitHub Copilot code review gets REST and GraphQL APIs; Balanced becomes the default effort level
Take · With an API, AI review can plug into your own release flow, for example raising the effort only when a change touches payments or permissions. The default effort changed, so review time and usage may shift too; check your bill and PR wait times this week. I wrote on the blog about how to split review work when AI writes most first drafts.
From the Oct 5 brief · item 03 →
-