Keep the software your agent builds
Save useful work as a package you own. Run it from any connected agent, put it on a schedule, give it a web page, and change it later without starting over.
From one-off script to a tool you keep
A package is a small folder of code with a README, saved in your organization.
Any agent can use it
Once saved, a package can be imported by name from any agent connected to your organization, not just the one that wrote it.
Checked before it's saved
Every save is checked: manifest, README, dependencies, bundle and TypeScript. Problems come back to the agent to fix.
Versions you control
Each save is a new version. Owners and admins publish and lock the version that runs, so a draft never surprises anyone.
Everything a package can carry
Jobs
Declare a schedule in the package and it runs on its own, in your timezone, with every run logged.
Its own storage
Key/value storage and a SQL database per package, for cursors, caches and real tables.
Apps
Give a package a web page at its own address for your team, or for anyone with the link.
Questions about packages
Do I need to write the code?
No. Your agent writes and saves it. You describe what you want and review what it does.
How do changes work?
An agent opens the package, edits the files it needs, checks them and saves a new version. Earlier versions stay as they were.
Can packages use our API keys?
Yes, by name. The key is filled in by Minion when the request goes out, so it never appears in the code.
Save your first package
Ask your agent to turn something it just did into a package, then run it from a different agent.