7 min
When the 3am job fails
Scheduled jobs and agent automations fail quietly, and you find out days later when the output stops. Here's how Minion keeps every run, writes a diagnosis note for each failure, and lists what's waiting on you.
Notes From the Minion Himself
Why your assistant deserves a home, written while building it — 17 articles so far.
6 min
Notes vs memories: where an agent's work should live
Chat history isn't memory. I split what my agents keep into short facts every agent can search and longer notes for plans, research and handoffs.
7 min
Your clients' API keys shouldn't live in your .env
If client API keys live in your .env and their automations live on your laptop, every handover is a mess. Give each client its own Minion organization instead: keys they own, roles for your team, and a handover that's mostly removing people.
7 min
Jobs that remember where they left off
A nightly agent job that summarizes the same 200 issues every night has no memory of last night. Here's why scheduled work needs state, and how Minion packages keep cursors and SQLite tables between runs.
5 min
Your MCP connections shouldn't live on your laptop
Keep remote MCP connections in one place, then switch agents or machines without rebuilding your toolbox. How Minion makes your connected services portable, and what still needs authorization.
5 min
Tasks and reminders that tell you when they fail
Minion now has a shared task list your team and every connected agent can update, plus one-shot reminders. The part I cared most about: when a reminder can't reach you, it stops retrying and says so.
8 min
Hermes Agent needs a home
Hermes Agent remembers, writes its own skills, and runs cron on a $5 VPS. Minion gives it shared memory, tasks and saved code that the next agent you open can use too.
6 min
How to turn agent work into software you own
I keep having a conversation I should have stopped having.
6 min
OpenClaw 2 needs a home
OpenClaw 2.0 is a personal AI that lives on your machine. Minion is the runtime that keeps its memory, keys, packages, and jobs running when that machine sleeps. Here's how they stack.
7 min
Minion vs Executor?
Minion is your assistant's runtime and home. Executor is the integration gateway that catalogs the tools it can reach. Add Executor as an MCP server with code mode off, and each layer does the job it was built for.
6 min
Your assistant's home
Your AI assistant accumulates things worth keeping. Memory, keys, code, scheduled jobs, an inbox. Those things should live somewhere durable that you own, no matter which agent you talk to this year.
6 min
Gateways connect. Homes accumulate.
MCP gateways and Minion get compared a lot, but they solve different problems. A gateway is a catalog of tools with pluggable ways to call them. Minion is a runtime where your assistant's stuff lives and keeps running. The difference shows up the moment you try to toggle code mode off.
6 min
The personal assistant that can't leak your keychain
My assistant's account holds 51 secrets. Here's the security architecture that makes the scary failure modes structurally impossible instead of policy-discouraged.
6 min
Why your assistant's home should make zero inference calls
Minion makes zero inference calls. That's not a limitation, it's the business model, and it changes who your assistant platform is actually working for.
5 min
Every install is a fork you own
In most ecosystems, installing someone's automation means renting a black box. In Minion's community, one-click install creates a fork you own. Here's why that changes how you treat other people's code.
5 min
The automations you never got around to building
Your real competitor for automation isn't a better tool, it's not automating at all. Why the activation energy of hosting and credentials killed your automations, and what changes when your agent has a durable home.
5 min
Self-service means ownership
Why Minion makes you create your own OAuth apps and bring your own keys, framed honestly. A few minutes of setup buy you your own app, your scopes, your rate limits, and no middleman between you and your data.