Agents worth keeping.
Each entry is a whole agent — the flow, the tools it calls, the files it reads — packed into one .heddle file that runs anywhere heddle is installed. No account, no registry, no install step for the agent itself.
Throw it any lump of text from a share sheet and it decides: a reminder, a note, or nothing. Runs on the phone itself.
Works on a codebase the way OpenAI's Codex CLI does: plan, shell, apply_patch, repeat.
First-line IT support that answers from the handbook packed inside it, and drafts a ticket when the handbook falls short.
Answers questions about a folder of documents that never leave the machine, quoting the file and line every claim came from.
Works an alert against the written runbook and takes the first remediation step only once a person has said yes — with every node and call recorded.
Writes the release notes for a range of commits by running the scripts your team already had, unchanged.
Records this machine's audio with a Core Audio tap and writes up the meeting. Any call app, no driver, no bot. macOS only.
One command.
Every entry is packed and published at its own address — a single archive carrying the flow, its tools and whatever data it reads. npx fetches heddle, the bare name fetches the agent, and nothing is installed.
What a bundle deliberately does not carry is credentials: a spec names its key as $OPENAI_API_KEY and it resolves on the machine that runs, never the one that packed. Sandbox policy is the same — a file that arrived in the mail does not get to decide what it may read, so --safe is yours to pass. How bundles work.
An entry is a directory.
A flow, a bundle.json saying what it is and how to pack it, a README, and the tools and files it needs. CI packs every entry on every change, so a listing here is a bundle that builds.