AI Agents blogs
Featured blogs
Generated image: Villar David editorial
Blogs
AI Agents
Posts filed under AI Agents. View every category.
2026
Running Amp Orbs on my own workstation
I set up Amp's self-hosted Orbs on a Linux workstation with Docker. Here's what runs locally, how a thread starts and resumes, and what still goes through Amp.
What stays yours when the agent harness is managed
OpenAI's Agents API now hosts sessions, environments, context management, tool loading and subagents. You still have to define the work, the authority, the record and the recovery path around it.
Where agent supervision has to happen
Anthropic's numbers suggest experienced users let agents auto-approve more and also interrupt them more often. To me that says supervision should sit around a visible plan and the actions with real consequences, instead of a confirmation on every command.
The coding-agent interface is becoming a control plane
Once you're running several agents in their own worktrees with a review queue at the end, you're mostly supervising work that's already moving. The bits I care about are the boundaries you set, catching drift early and having enough evidence to understand each result before you merge it.
Production agents need institutional context
OpenAI's write-up on its in-house data agent is mostly about the context sitting around the model: schemas, code, permissions and saved corrections. What I want to know is who keeps that context right, and how a user fixes it when it's wrong.
2025
The agent’s activity log is part of the deliverable
When an agent changes code, data or config, I want its work record handed over with the answer, so whoever picks it up next can see what it tried, what passed and where it left things.
What I want from an always-on AI agent
I want an always-on agent to work like a worker with a job ticket: it takes a named job, leaves a record of what it did and puts any proposed change somewhere I can review it.
Operating local AI infrastructure after the migration
The migration's done, so now it's the boring stuff: services starting in the right order, data landing where I think it is, backups I can actually restore and failures I can see.
What has to survive when an AI assistant moves machines
Before I move an AI assistant to a new host, I'm listing the parts that have to survive and the test that shows each one did. Copying the prompt won't get me far, because most of the state lives in memory records, tools, scheduled jobs and the links back to source material.
Trying to remember everything made the agent worse
A total-recall experiment showed me that more retrieved history can crowd out the task the agent is actually meant to be doing. So I'm splitting memory into identity, durable decisions, project state and searchable archives, and choosing what loads by purpose.
What I am testing in long-term AI memory
I'm testing whether a graph can pull back a decision through what it's connected to: the person, the project and the source. What I want to find out is which records actually help the next session and which ones just make retrieval noisier.
Writing work orders for coding agents
Coding agents can now take an issue and hand back a pull request, so the issue is doing a lot more work than it used to. I want it to say what should change, where to look, what's in scope and how we'll know it works.
Scoping tool access for an AI agent
OpenAI's Responses API lets one agent use search, files and computer use. Each of those gives the agent a different kind of authority, so I'd sort out its identity and approval rules before connecting any of them.
2024
What computer use exposes in business software
Anthropic's computer-use beta can click, type and move around software without a purpose-built API. So every vague label, hidden bit of state and irreversible button on your screens becomes something the agent has to deal with.
Why I’m testing a graph for long-term AI memory
If an AI collaborator is going to work with me over months, it has to find its way back to who decided what, on which project, and based on what. I'm testing a graph-backed memory layer because those links get lost in a pile of transcripts, and I want to be able to check what it's stored.