#devops
Every post tagged "devops".
20 posts · showing 11–20
-
The Case for a Local-First Agent Stack
The cost argument for local-first is weak and the ideology one is worse. The case that holds is dependency control — and it comes with a permanent operational tax nobody budgets.
-
The Deploy Step Nobody Should Automate Yet
It's the easiest step to automate, saves the least time, and carries the largest tail risk. Automate the readiness report and the rollback instead — and separate deploying from releasing.
-
Which Agent Alerts Should Wake Someone Up?
An agent can be green on every service metric while doing the wrong work at ten times the cost. One rule sorts the alerts — and the highest-value one is the one almost nobody has configured.
-
The Tool That Changed Under You: Supply-Chain Risk in Agent Tooling
No deploy, no prompt edit, and an ops agent started restarting services mid-investigation. A maintainer had improved a tool's documentation — and documentation, in an agent, is instruction.
-
Running Agents on a Schedule: What Changes Without a User
An agent someone triggers has a safety property nobody designs for: a person is watching. Put it on a schedule and that goes away — along with the feedback loop that was catching the errors.
-
Least Privilege for Agent Credentials
Since injection isn't fully preventable, the credential decides whether a compromise is an inconvenience or an incident. Four scoping dimensions — and the one nobody uses is usually the highest-value.
-
Sandboxing Code Execution: What a `run_code` Tool Actually Needs
One tool replaces dozens — and hands a model that reads untrusted text a general-purpose mechanism for doing anything the process can do. Four boundaries, four isolation levels, and the one people leave open.
-
Designing a Kill Switch That Works Mid-Run
Killing the process leaves side effects in an unknown state. A stop that works checks between steps — before every model call and before every tool call — and the difference matters most at 2am.
-
The On-Call Agent: What It Should and Shouldn't Touch During an Incident
An incident is when your system is least understood — a poor moment for an autonomous actor, an excellent one for an autonomous investigator. The line between them is read access and write access.
-
The Read-Only Agent That Wasn't: Auditing What Your Tools Can Actually Reach
A tool named `check_service_health` woke someone at 3am. Read-only is a claim about effects at the far end of every call, and there's a short audit that either proves it or shows you what you actually deployed.