Everything your agents use, kept in one place.

Each feature lives in Minion, not inside one chat window. Connect any agent and it finds the same memory, keys, packages and jobs as the last one.

A pinned note card connected to three agent chips

Memory

Facts, preferences and working notes that every agent you connect can find, so a new chat or a new agent doesn't start from zero.

Explore memory
A shared document card with earlier versions behind it, a comment bubble and a handoff arrow

Notes

Markdown working docs your agents and your team share: plans, research, run logs and handoffs, with history, comments and self-expiring scratchpads.

Explore notes
A versioned code file packed into a box and run by three agents

Packages

Save the code your agent writes as a versioned package your whole organization can run, schedule and build on.

Explore packages
A package box feeding a key/value chip and a database with a table

Storage

A key/value store and a SQLite database for every saved package, so jobs keep their place and apps keep their tables.

Explore storage
Clock, webhook, event and email chips converging on a run card

Triggers

Run your packages on a schedule, when a webhook arrives, when an email lands, or when something else in Minion happens. No chat window required.

Explore triggers
A run list with one failed row leading to a bell and a person

Run history

Every execute call, job and webhook run kept with its logs and error, plus one list of what's waiting on a person, each with a link that clears it.

Explore run history
A masked secret passing through a shield to an API

Secrets

Give your agents the API access they need. They use keys by name; Minion fills the value in on the way out and never hands it back.

Explore secrets
A central key hub connected to four account sockets

Integrations

Connect accounts like GitHub and Google, and remote MCP servers, once. Your agents and packages use them without ever holding the tokens.

Explore integrations
An envelope feeding a message list, with one message held in quarantine

Team inbox

Every organization gets an email address its agents can read, search, reply from and automate, with rules for who gets in.

Explore team inbox
A three-column task board with a checklist card

Tasks

A shared task board for your team and its agents, with checklists, reminders and progress comments from people and agents alike.

Explore tasks
A SKILL.md folder connected to three agent chips

Skills

Your team's playbooks, written once and loaded by every agent when the task calls for them.

Explore skills
A small hosted intake form in a browser window

Apps

Ask your agent for a tool that fits the job. Minion hosts the app at its own address, keeps its data, and connects it to the packages you already use.

Explore apps

Each one works alone. Together they run the job.

An email lands in your team inbox and starts a package. The package calls an API with a key it never sees, then leaves a task saying what it did. Your agent sets it up once; Minion runs it every time after that.

  1. An email arrives
  2. A trigger fires
  3. Your package runs
  4. A key is used by name
  5. A task lands on the board
Connect your agent
Paste it into Claude, Cursor, Codex or ChatGPT once Minion is connected. Show the prompt

Connect to Minion at https://app.minion.codes/mcp. Then help me set up one workflow: when an email lands in our team inbox, run a package that does the follow-up work using the keys we've stored, and add a task to our board with what it did. Ask me what the follow-up should be before you start.