automagik-dev ships the agentic development toolchain — genie orchestrates wishes into shipped code via autonomous teams, omni lets agents speak across every channel humans live in, and rlmx gives them a research-grade reasoning loop. khal-os is the operating system that hosts what those agents build — a browser-based, macOS-inspired shell where every human and every agent lives alongside the apps (“packs”) they use together. Forward Deployed Engineers hired on khal-os don’t rebuild the primitives; they reach for the automagik toolchain to author khal packs faster, then ship those packs into customer organisations via khal-os’s deploy rails. One story: Automagik is how you build. Khal-os is where it runs.
This manual is written for Forward Deployed Engineers shipping packs onto khal-os. If you’re evaluating the product, start with What is Khal-OS.
Day 1 on khal-os
Four steps take you from an empty laptop to a pack running in the shell.Clone the workspace
Pull the khal workspace, wire your environment, and confirm the shell boots locally.
Your first pack
Scaffold a pack from the template and see it appear in the khal-os desktop.
Hooks reference
The
@khal-os/* React hooks you’ll reach for — auth, NATS, services, and more.Publish your pack
Tag a release, push to CI, and prepare the Helm chart customers will install.
Learn by example
Real patterns beat abstract advice. These pages walk through packs you can copy from.Frontend-only pack
A pack that lives entirely in the browser shell. No backend service required.
Full-stack pack
A pack with a Bun service behind it, talking to the shell over NATS.
Example packs
Reference packs you can read end-to-end to see the conventions applied.