Operations | Monitoring | ITSM | DevOps | Cloud

AGENTS.md vs. skills: How to steer a coding agent

Every team adopting coding agents hits the same question early: where do you put the instructions that tell the agent how your codebase actually works? Two answers dominate the conversation right now. One is AGENTS.md, a plain markdown file at the root of your repo. The other is skills, packaged instruction sets an agent loads on demand. Most of the debate treats this as a formatting decision. It isn’t.

Starting your engineering career in the AI era: 6 takeaways for junior developers

“We don’t need junior engineers anymore” has become one of those lines people repeat because it sounds obvious. The AI writes the code, so why pay someone to learn how to write it? On the latest Confident Commit podcast, Rob Zuber makes the case that this take is exactly backwards.

What is an AI sandbox? A developer's guide

An AI sandbox is an isolated environment where code from an AI coding agent runs without direct access to your machine or your production systems. If the agent runs a destructive command or a mistaken script, the damage stays contained inside the sandbox. Developers use AI sandboxing to let agents execute code freely while keeping the host and its credentials out of reach.

What is a remote MCP server?

As development shifts toward agentic workflows, an AI agent is only as capable as the systems it can reach. Local MCP servers allow desktop CLI and IDE agents to execute multi-step tasks on your machine. But remote MCP servers (also called hosted MCP servers) extend that reach to cloud-based and background agents, allowing an agent running in a web browser, a CI runner, or a backend service to access external tools over HTTP without needing a developer’s machine running local child processes.

Upgrade Your AWS Deploy Orb to Get Deploy Markers

Upgrade to the latest version of your AWS deploy orb to get automatic registration of deploy markers. This will give you instant access to deployment timeline, auto-rollback, and version comparison when something breaks — for about five minutes of effort. It will also switch you to OIDC, so there are no long-lived keys to manage. It’s a single version bump. Here’s how.

5 takeaways from the State of Software Delivery Q2 Pulse report

AI is pushing code volume up almost everywhere. Shipping it is still the hard part, and the gap between leaders and everyone else is getting wider. Today we’re releasing the 2026 State of Software Delivery Q2 Pulse report, a shorter check-in between our annual reports. We analyzed more than 20 million CircleCI workflows from March 2026 to see what’s changed since the comprehensive 2026 State of Software Delivery report we published in Q1.

Rebuilding the CircleCI CLI from scratch

Every developer knows the moment: CI goes red, and you face a choice. Open the browser and click through the web UI to the run, the workflow, the job, the step, the log line. Or stay in the terminal, where the fix is going to happen anyway. The new CircleCI CLI exists so you can stay. It’s 1.0, it’s in beta, and it’s a ground-up rewrite in Go, not an iteration on the CLI we’ve shipped for years.

ACP vs MCP: What's the difference for agentic coding?

An AI coding agent holds many conversations at once. Not only is the user prompting it, the agent also talks to the IDE, showing diffs and asking before it touches a file. At the same time it talks to tools, pulling a failing build or querying a database. Two open protocols standardize those conversations. This guide compares ACP vs MCP in practical terms: what each protocol does and when each applies. ACP (Agent Client Protocol) connects a code editor to an AI coding agent.

Why you should use Language Server Protocol (LSP) with Claude Code

Agentic coding tools like Claude Code can write, refactor, and debug across an entire codebase, but by default they read code as plain text, the way grep does. The Language Server Protocol (LSP) changes that: it’s the same code-intelligence layer an IDE uses, and wiring it into an agent lets it read code by meaning instead of by string match. The bigger the codebase, the more a wrong guess about a symbol costs, and the more that structural view pays off.