Kiln 1.0.2

Kiln 1.0.2

Fixes for live Claude Code sessions that finished their work but never closed. Kiln 1.0.1 was
prepared but not published; its changes are included here.

Fixed

• A phase no longer stays on Implementing after Claude has finished. Kiln waited for a
  report from its own hook that each tool call had finished before it closed a session. When
  that report never came, the session stayed open after Claude's final turn, the phase showed
  Implementing indefinitely, and the run went no further. Kiln now closes a session once Claude
  has given its final result and answered every message, as designed. Reports of finished tool
  calls are still required before you take over a session from the terminal.
• The report a tool call has finished no longer goes missing. When two of Kiln's hooks
  reached its lock at the same moment, one could fail and lose that report.
• A tool call the auto-mode classifier rejects no longer holds the session open. Kiln now
  treats any rejected tool call as finished, since it never ran.
• Taking over a long session is no longer refused. Kiln kept every process a session had
  ever started on its list, even after it ended, so a long session passed the list's limit and
  Pause & take over stayed blocked. Ended processes now leave the list.

Changed

• Over SSH, kiln run says how to reach the view instead of reporting an error. Kiln no
  longer tries to open a browser on a remote machine. It prints the view's address with an
  example ssh -N -L command for opening it from your own computer through a tunnel to the same
  port. On a machine with no way to open a browser, it says to open the address yourself. Only
  an attempt to open the browser that fails is still reported as an error.
• KILN_PORT_RANGE is a supported setting. Set KILN_PORT_RANGE=<first>-<last> to give a
  machine its own block of ports, for example when several machines are tunnelled to one
  computer. A value that isn't two ports from 1024 to 65535, first no greater than last, stops
  kiln run with a message instead of quietly using 4700-4799.
• kiln --version says when a build is not a release. A build packed or linked from a local
  checkout now prints (dev build, <when it was built>) after the version. Installed releases
  print the plain version, as before.

Upgrade

npm install -g @ensodynamics/kiln@1.0.2

A run stuck on Implementing this way can be stopped and started again with kiln run after
upgrading.

Kiln 1.0.0

Kiln 1.0.0

The first public release of Kiln.

Kiln builds a PRD you already planned with the Enso Method, one phase after another, with nobody sitting in the loop. Every phase gets a fresh Claude Code or Codex session. Git confirms the phase landed before the next one starts. When the last phase closes, delivery and test audits check the whole PRD, and the work waits for you as pull requests. A local browser view shows each session live, and you come back when it's done or when a phase genuinely needs you.

Install

npm install -g @ensodynamics/kiln
kiln --help

Then, from the root of a repository whose PRD has been planned and split into phases:

kiln run docs/prds/<name>

Requirements

• Node.js 22.15 or later and Git 2.29 or later.
• GitHub CLI signed in to github.com, with the repository's origin on GitHub.
• Claude Code 2.1.311 or later, or Codex 0.162.1 or later signed in through ChatGPT, with the Enso Method skills installed in it. Codex on Windows also needs PowerShell 7.5.2 or later.
• macOS is validated. Linux and Windows are best effort.

Kiln accepts every agent version at or above these minimums. When a newer Claude Code or Codex changes what live messaging, takeover or Codex command evidence relies on, that feature turns off with a compatibility notice and the rest of the run carries on.

Reporting problems

Open an issue at github.com/EnsoDynamics/kiln/issues. Report a suspected security vulnerability privately, as SECURITY.md describes, not in a public issue.

More at ensomethod.org/kiln.