Skip to content

Keel v1.8.0

Choose a tag to compare

View all tags
@joseconti joseconti released this 15 Jul 19:13
v1.8.0
0b37708

What's new in 1.8.0

Execution discipline in the CLAUDE.md lock

The portability lock every Keel project carries in its CLAUDE.md gains a fifth protocol item: mandatory execution discipline for ANY assistant or model working in a Keel repository, in any environment.

  • Batch independent tool calls in one parallel block; never run sequentially what does not depend on a previous result.
  • Delegate broad searches and scans to a subagent when the environment provides them; bring back conclusions, never file dumps.
  • No narration between tool calls; findings accumulate and are reported once, at the end of the work block.
  • Locate before reading: search first, then read only the relevant fragment — never whole files or directories "for context".
  • Edit surgically with exact-match edits; never rewrite a whole file to change one part.
  • Batch clarifying questions at the start of a work block; close every work block with an explicit verification step (diff, test, or re-read) before calling it done.

Existing projects pick the new block up through the normal lock-refresh mechanism (between the KEEL:BEGIN/END delimiters, with the user's OK).

Release update check at session start

Keel now keeps itself current. Once per session, before any phase work, it checks this repository for a newer release (preferred method: git ls-remote --tags, with the GitHub API and the releases page as fallbacks) and compares the latest tag against EVERY copy in play — the environment's install and the project's embedded .claude/skills/keel/ — each one separately, so an up-to-date app install never hides an outdated embedded copy in the opened project.

  • Copies the assistant can durably write (a user-level install, and always the project's embedded copy) are updated automatically: verified full-tree replacement, improvements summarized from the new CHANGELOG.
  • Copies it cannot write (app-managed skill storage, as in the Claude app / Cowork) get a single notice: the new version, what it improves, and how to update per INSTALL.md.
  • The check is best-effort and never blocks or delays the session's work.

Full details in keel/CHANGELOG.md.

How to update

Replace your installed keel/ directory with this release's (see INSTALL.md, section "Updating"). Keel is stateless, so overwriting is safe. From this version on, Keel performs this check for you at the start of every session.

Assets 2
Loading