A portable, versioned archive
A .honey file is proposed as a ZIP-compatible archive. Its honey.json manifest describes the package identity, version, type, dependencies, required connections, and permissions. The format is designed to be independent of any one agent runtime.
Three kinds of Honey
A Skill packages a focused capability. A Bee packages an agent configuration and its capabilities. A Swarm packages a coordinated team. Depending on its purpose, an archive can include skills, agents, routines, team definitions, optional memories, assets, and tests.
Connections travel as requirements
A package declares which connections it needs; it does not carry passwords, API keys, or session tokens. The planned import wizard collects missing credentials through masked forms and stores them in the destination’s encrypted vault, with no plaintext fallback.
Inspect before you activate
The planned engine validates archive contents, paths, checksums, dependencies, and compatibility. Provenance and signatures help establish where a package came from, but do not replace permission review. Unsupported features must be reported. Executable code requires explicit review and isolation; imported routines start paused.
A recipe is the job; a package carries it
A Honey recipe combines instructions and capabilities for a useful outcome. A .honey archive makes that recipe portable. The current website’s text template downloads are task briefs, not .honey archives or installed automations.
Try an editable workflow brief ↗What we’re building next
First comes the specification, packer, validator, and representative Skill, Bee, and Swarm samples. Next are tested migration adapters and the importer. The Beehive catalog and Honey Maker build on that foundation.
Explore the migration plan ↗