zavu functions (alias fn) drives Zavu Functions — your TypeScript running on
every messaging event. The most-used subcommands are also available at the top
level: zavu deploy is zavu fn deploy.
Scaffold
index.ts, a package.json declaring @zavudev/functions, a
tsconfig.json, and .zavu/config.json holding the function’s id. Run
zavu fn init --help for the current template list.
Commit
.zavu/. It holds the functionId, and there is no command to look
one up — a teammate who clones without it cannot deploy.zavu agents pull.
Deploy
zavu fn push updates the draft without deploying. Useful to save work in
progress; nothing changes in production until deploy.
Run it locally
fn invoke runs your code with Bun. Every other command runs
under plain Node.Logs
Secrets
list shows the last four characters, never the secret.
Reach them in your handler with process.env.STRIPE_KEY.
Triggers
Versions and rollback
rollback republishes a previous
one’s source and dependencies; it always asks for confirmation. Secrets are not
rolled back.
Delete
Where to go next
How agents work
What a deploy actually does, with diagrams.
zavu agents
Test, connect and inspect the agents your code declares.
