genie update only on the releases from v5.260830.20 through v5.260919.14. A host that never ran one of those updates still has it, and later releases, v6 included, do not remove it: remove it by hand if you want it gone.git push inside your agent session and refuse a push that targeted main or master. That guard no longer exists: an agent can now attempt a push to any branch and Genie will not stop it locally.main, enforced server-side by GitHub rulesets: pull requests are required, direct pushes are blocked, and a review from someone who is not the author is required before merge. This is strictly stronger than the old client-side check, because it cannot be bypassed by an agent that never loaded a Genie hook, and it applies to every actor including humans.gh api repos/<owner>/<repo>/rulesets). If it does not, configure it, because the client-side guard is no longer standing behind it.gh credentials is you, as far as the ruleset is concerned, so a required reviewer who is not "the author" is satisfied by any second credential, and an agent acting with a maintainer's token has a maintainer's powers. This gap existed before the guard was removed and is not closed by anything Genie ships. If it matters to you, give agents their own scoped credentials.dev; main is humans-only" convention are operator policy, carried in every agent brief and in the repository's AGENTS.md, enforced by server-side branch protection on main and by nothing client-side.AGENTS.md so it lands in every brief.genie omni serve was unchanged in every other respect: it was still the resident NATS bridge, it still drained the approval queue, and the queue and inbox still persisted in the global ~/.genie/genie.db. genie omni status and genie omni inbox read them without touching the network. CLI-originated approvals still flowed through the queue exactly as before.genie omni is gone too. Genie no longer has the Omni runner, its approval queue or its inbox, and nothing in v6 writes to ~/.genie/genie.db in normal use. genie doctor --fix-global-db changes it only when you run it. The advice below still applies: approve in the session, or configure the agent so the prompt never appears.GENIE_AGENT_NAME / GENIE_AGENT_ID written into the session's opening context;GENIE_AGENT_NAME and GENIE_AGENT_ID are still real environment variables and still configure the CLI; only the injection into session context is gone. Wish state itself is unchanged: it lives in git under .genie/wishes/ and in .genie/genie.db, and every Genie skill reads it explicitly at the point of use rather than trusting an injected preamble.genie board and genie task status <id> are the authoritative views, and a skill that resumes a wish opens WISH.md itself. If you resume long-running work, make re-reading the wish the first step of the session rather than assuming a warning would have fired.123456789# First install — the bootstrap script fetches the signed binary, # which then installs the skills channel itself curl -fsSL https://raw.githubusercontent.com/automagik-si/genie/main/install.sh | bash # Every update afterwards — swaps the binary and reinstalls its skills genie update # Skills for your user without the Genie CLI (drop -g for a project-scoped copy) npx skills add automagik-si/genie -g
genie update installs the exact skills that shipped inside the release you are running. The public npx skills add command installs the repository's default branch, regardless of any @<ref> suffix. See Installation for why, and use genie update when you need the version that matches your binary.genie doctor after either one: its skills: lines report, per agent home, how many of the recorded skills are present and which release they came from.