Skip to content

v0.10.0

Choose a tag to compare

View all tags
@quailops quailops released this 28 Oct 05:17
v0.10.0
8bfbf53
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.10.0 (2026-10-28)

⚠ BREAKING CHANGES

  • after upgrading, an enrolled repo's implement and human-initiated flows (and any flow of its own that calls Implement.claim or Hybrid.claim) take a claim ref that only Claims.releasing lets go when the run ends. Update them with chernabog recipes diff / recipes add, or wrap the run in Claims.releasing(Claims.issue(issue)), then chernabog trust the repo. Until then, chernabog cancel <run> on the run a skip names deletes the claim ref it left.
  • engines.chernabog in .chernabog/package.json is refused, as is a manifest without an @chernabog/sdk pin; run chernabog recipes upgrade. An older chernabog refuses machine config and state.db once this one has stamped them; restore the copy in ~/.config/chernabog/backups/ to roll back.

Upgrading a repo whose recipes chernabog baked

Recipes are now the @chernabog/recipes package (0.1.0, released alongside this). A repo whose recipes an earlier chernabog baked has no recipe package in .chernabog/, so chernabog recipes diff can't yet compare its flows with anything, including the claim-ref change above. In each such repo's checkout:

  1. Run chernabog init once. It installs @chernabog/recipes in .chernabog/ and overwrites nothing; when it asks which recipes to copy, pick none.
  2. Run chernabog recipes diff implement human-initiated to see what changed, such as the Claims.releasing wrapping, and bring it over by hand. (recipes update keeps a file with no recorded version as it is, so it won't bring the change over.)
  3. Commit .chernabog/, bun.lock included, merge it, and chernabog trust the repo.

See a repo baked before recipes were packages. This release also ships @chernabog/sdk 0.7.0.

Features

  • a person's Yes, not the agent, opens the pull request on the hybrid path (#128) (5f6e7c9)
  • a plan recipe: an agent turns a spec issue into an epic of ordered sub-issues (#140) (28e264f)
  • a resolve-conflicts recipe, and review/re-review leave a conflicting approval to it (#118) (4a1cd50)
  • a run's changes here and a persona's GitHub notifications tick flows right away, not on the next cron tick (#141) (ad9ef65)
  • cancel a run in flight with chernabog cancel (#119) (926ead3)
  • chernabog decides which repos' flows it runs, and state and runs survive an upgrade (#124) (ad7132d)
  • claims are refs of their own, apart from the work branch (#139) (3fe9282)
  • recipes: recipes as packages: @chernabog/recipes on its own cadence, company recipe packages, and flows that import a recipe (#130) (1d076c5)
  • rehearse a flow end to end on a scratch repo, with stand-ins for the agent (#121) (c909932)
  • tui: tabs by project and persona, runs you can scan by issue and PR, a run's step history and work threads (#127) (2a5c035)

Bug Fixes

  • the release PR's SDK bump moves the SDK range this binary runs, and its tests pass before npm has it (#131) (7daa1b8)
Assets 7
Loading