Skip to content
Jacob NolletteCloud & software engineer
Topic · 8 case studies

Agents & AI

Specialist AI agents, the browsers and knowledge stores that let them act, and the fences that keep them inside their domain.

Six Agents, One Channel Each

I run six AI agents. Each is resident in one chat channel, each has its own memory on its own volume, and each has a job: administration, facilities, maintenance, health, finance, security. The one-agent-per-channel rule came from a real failure. When two agents...

A Browser Farm for Agents

An AI coding agent can read a public page with curl. It cannot read a client portal, check whether a deploy actually renders, or pull a number off a dashboard that has no API. Those all need the same thing: a browser that is already signed in. So I built a pool of...

The Question That Vanished, and the Fix That Was Almost Right

I run a self-hosted AI agent called Atlas. It lives in Slack, runs on my own Kubernetes cluster, and thinks on a pair of 24 GB datacenter GPUs in my basement — no cloud model in the path. Yesterday I asked it to do something routine: download a YouTube video into the...

Working Inside a Small Context Window

An agent stopped compacting its own conversation and posted a warning: it was over the compression threshold, and compression was now blocked. Not an error. Not a crash. It just stopped being able to continue the thread. The symptom looked like a model problem. It was...