Agent files New in 0.9.0
Weeks of documents, lessons and corrections shouldn't live in one place only.
Any process agent you own fits in one .captain file: to back it up, move it to another deck, or hand a trained one to a client and update it later.
In the kiosk: the agent's ⋯ → Back up / export, in the Its place row, and New agent → From a file.
Pick what goes in, then fine-tune it with the Includes list.
Who it is and what it was taught. A fresh copy for someone else to start from.
That, and what it learned since, without its conversations and files.
Everything, conversations and files too. The one to restore from.
What it learned — look it over. Before a Template or Trained file leaves, you see what it learned. Insights that are usually about you or your clients (preferences, feedback, projects, deadlines, people) start unticked, and People it knows is a separate tick.
An agent file carries what the agent knows, not the keys to your accounts.
.env, keys and tokens, its logs and your own profile.The dialog shows what the file holds, who made it and when, and whether it is Signed by this deck, by a deck you trust, or unsigned.
On Its own model or on One of your models.
Into an existing agent: what it knows stays, and the file only adds what it hasn't got.
Its memory, files, conversations and tasks are replaced. Its model and keys stay.
A backup is taken first and kept a week, with Undo. Scheduled tasks always arrive switched off.
Packages For consultants and firms
Name a Template or Trained export under Updates later, say "Bookkeeper for Acme", and each export becomes its next version. When the client brings in a newer one, Flight Deck offers Update to version N.
The old version's items are replaced by the new ones.
What the agent learned at the client, and what they changed there, stays.
A package's onboarding becomes the agent's base, which the person adds to but can't change.
Backups Settings → Agent backups
In the kiosk, Settings → Agent backups → Back up my agents automatically.
Every day or every week, from an hour you pick.
Keep 1 to 60 per agent, 7 by default, for all agents or the ones you choose.
On the deck, with an optional copy into a folder of your files.
Backups kept downloads, deletes or restores any of them.
Scheduled backups are full and never carry keys. Copies in your files aren't pruned.
Every deck signs its bundles with its own key, and a file changed after signing is refused.
Limits: export and import are in the kiosk only, and Docker agents can't be exported yet. Files go up to 2 GB.
Back up agent-bundles/ in the deck's data folder and bundle_signing_key in its home: losing the key gives the deck a new fingerprint.
Agent files docs · The Flight Deck guide · Onboarding trains the agent you'll pack
Keep reading
Everything your agents were asked, on one board, and a check that "done" really happened.
One log of everything the deck and your agents did on their own, and a bell for what needs you.
Agents hand each other work, answer email meant for them, learn from corrections you approve, and know your goals.
Join the waitlist for Cohort 001, our first early-access group, and you'll get an email when you're in. Or run Captain on your own machine today.