Install boards, automations, and integrations in one click — or build, version, and publish your own. Codex is the recipe library that powers brains, with packaging, dependencies, and upgrades that work like the package managers you already know.
Boards (CRMs, trackers, pipelines), automations (digests, triagers, summarizers), integrations (Gmail, GitHub, Stripe, Monday) — installed in one click, scoped to your brain, ready to run.
browse the catalog →Author a recipe in TypeScript with a manifest, declare its dependencies, publish a version. Your team installs it; the next team installs it too. Recipes compound.
jump to publish →Each recipe is a packaged unit of capability — a board schema, an automation program, an integration adapter, or a bundle that combines all three. Install in the web UI or from the CLI; brains resolves dependencies and configures the right scopes before anything runs.
// docs · catalog→Recipes come in four kinds: board (a typed dataset + UI), automation (a sandboxed program), integration (a connector to an external tool), and bundle (a recipe of recipes). Installing a bundle installs every child atomically.
Recipes declare what they need — other recipes, integrations, scopes. Codex resolves the tree, installs in order, and treats a bundle as the canonical upgrade unit so children never drift out of sync with their parent.
// docs · dependencies→When you install hiring-pipeline v2.1.0, codex sees its declared deps (a board schema, a scoring automation, the gmail integration), resolves their versions, and installs them in topological order. Upgrades work the same way — bump the parent, codex cascades to every child. Bundle children can't be upgraded out-of-band; the parent owns them.
Author a recipe in TypeScript with a manifest declaring kind, deps, scopes, and inputs. Run a local review against the sandbox. Publish — to your team's private registry, to your org, or to the public catalog. Every publish is a version; rollback is one command.
// docs · publish→A recipe's manifest.json declares everything codex needs to install it safely: which integrations it talks to, which scopes it needs, what inputs the user must provide, what triggers it subscribes to. Anything not declared can't run. Reviewers see the whole shape in one place.
Recipes version like code, because they are code. Every publish is recorded with a semver tag, a changelog, and a diff against the prior version. Installs are pinned by default; upgrades are explicit; rollbacks are one command.
// docs · versions→Authors publish with semver. Installers pin to a version or a range. Codex tracks who installed what, when, with which inputs. If a v1.3.0 ships a regression, every install can roll back to v1.2.4 with one command — the manifest is the same shape, so the rollback is safe.
Every recipe runs in a contained worker with no ambient FS, network, or env. Scopes are declared in the manifest and enforced at the runtime boundary.
An automation can depend on a board, an integration, and another automation. Codex resolves the graph; you write the program.
Publish to your team's private registry, your org, or the public catalog. Same packaging, same upgrade path, different audience.
Codex compounds with every team using it — yours included.