Council Sentinel

Wishes in, PRs out.

Genie is a planning-and-execution layer for AI coding agents. You describe what you want in one sentence; Genie interviews you into a plan, dispatches agents to build it in parallel, reviews the result against acceptance criteria, and hands you something ready to merge.

The whole thing is a lightweight body: a set of skills, plain-markdown documents in git, and a single per-repo SQLite file. No daemons, no Postgres, nothing resident. A command opens the database, runs one transaction, and exits.

Stable is declared for Linux and macOS. Both legs run in the release gate, so a change that breaks either one does not ship. Windows is not supported; WSL2 works but is not on the tested matrix.

Install

curl -fsSL https://raw.githubusercontent.com/automagik-dev/genie/main/install.sh | bash

Every release is cosign-signed (keyless OIDC) with SLSA provenance, and genie update verifies it offline, with no GitHub credential: the release's own signed delivery evidence is checked against an embedded Sigstore trust root with the publishing workflow's certificate identity pinned, and the descriptor's artifactSha256 is bound to the downloaded tarball before anything is extracted. gh attestation verify is an advisory cross-check on top — a host with no gh still updates and says so in one line; a gh that ran and says the artifact does not verify still aborts.

The repository-hosted .well-known/latest.json and dev.json manifests are the authoritative channel pointers. GitHub's /releases/latest route and prerelease badge are deliberately not channel authority: a promotion advances only a monotonic manifest and never rewrites already-published assets or channel-significant draft/prerelease/latest metadata.

Genie ships exactly two surfaces, and nothing else:

1. The signed binary — installed and updated by install.sh and genie update.
2. The skills, and the saved-workflow catalog beside them — delivered by the skills.sh channel. genie install and genie update run the pinned skills CLI over the tree the signed release put on disk, deliver .claude/workflows/*.js into ~/.claude/workflows, then record what landed in ~/.genie/skills-install.json. Without the binary, the same skills install with npx skills add automagik-dev/genie (add -g for a machine-wide install; never --all, which asks the skills CLI to write a product home for every one of the 77 agents in its registry — 57 of them materialized on the measured dogfood host (2026-08-30, re-confirmed 2026-09-01; only 4 were recorded, leaving 53 unrecorded homes).

There is no Claude marketplace plugin, no Codex plugin, no Orca plugin, no Genie-installed hooks, and no role-agent profiles.

--integrations auto|codex|claude|all|none (or --skip-integrations) is the consent scope for the skills channel. Any value other than none installs to every detected agent skill home, because the skills CLI already installs per agent; none skips the channel entirely, writes no record, and reports skills: skipped (consent: none). A failed skills install never rolls back the promoted binary — it prints the exact remedy command and sets a non-zero exit code.

Upgrading from a plugin-era release? The one-shot, backup-first retirement genie update used to run for that era shipped from 5.260711.6 through the last 5.x release and was removed in v6, three stable releases after its compat window opened. A host that updated through any 5.x release is already clean and needs nothing. A host coming straight from the plugin era to v6 is not cleaned up by genie at all any more — see Removing plugin-era leftovers by hand. Genie still retires what the skills channel itself no longer delivers, backup-first, under ~/.genie/state-backups/skills-retirement- /.