Skip to content

0.2.0 - 2026-10-28

Choose a tag to compare

@github-actions github-actions released this 28 Oct 13:20

Release Notes

Added

  • capacityRetryWaitSec (10 by default): the pause before a session is
    rerun after the engine ran out of memory and Tenaz lowered the context
    budget. It was a fixed 10 seconds. A stop (Ctrl-C) during the pause now
    pauses the run at once; before, the pause ran out and the next session
    started first. tenaz demo sets it to 0, so the demo ends about 10
    seconds sooner.

  • A time limit per tool call, toolMinutes (10 by default, 0 turns it
    off). A call that runs over it, such as a script in an endless loop, is
    stopped and the same session is told which call and what to do; a second
    one ends the session. Pi's bash has no default timeout, and a hung call
    held a session for 21 minutes. See ADR 0004.

  • Release archives come with a GitHub build provenance attestation, which
    shows that an archive was built from this repository by the release
    workflow. Check one with
    gh attestation verify <archive> --repo aartiles/tenaz.

Changed

  • The sessions that write task cards (the bootstrap's task-cards step,
    split and replan) are told the builders' context budget in tokens, with
    a rule: what a builder reads and writes for a card fits in about two
    thirds of it, at roughly 4 characters per token, and a card over that is
    split before it is written. The prompts only said "context-limited
    sessions": in the Digger 3D run of 2026-10-27 a card that needed eight
    modules read was split twice, and builders ended past the budget.

Fixed

  • A run paused during the review of an attempt that passed verify (or
    stopped there because the engine gave out) runs verify on that
    attempt again when it resumes and, if it still passes, reviews it
    again. It counted the attempt and built the task again, and a pause in
    the review of the last allowed attempt split the task. The Digger 3D run
    of 2026-10-27 was paused this way during the review of T012ba's attempt
    2.

  • A session stopped at its second context compaction is continued by a
    fresh session, like one stopped at its context budget, and no longer
    counts as a failed attempt. Both mean the context ran out; in the Digger
    3D run of 2026-10-27 the compaction stop charged T012ba an attempt.
    An attempt that uses up its continuations this way is split, as one
    stopped at its budget is (contextSplit).

  • A session stopped at its context budget keeps the work of the reply that
    crossed it. The stop came at the reply's end, before its tool calls ran,
    so a model that wrote a whole file in that reply lost it: three files in
    the Digger 3D run of 2026-10-27, and each continuation wrote it again
    into the same stop. The reply's tool calls now run first, and the session
    stops before its next reply.

  • The engine proxy no longer garbles a character that the network splits
    across two chunks of a streamed reply. It decoded each chunk on its own,
    so an accented letter or emoji cut in half reached the harness as �
    in every repaired stream. It now decodes only whole events.

  • A request the harness cancels because Tenaz stopped the turn no longer
    counts as an engine error. Pi reports it as one ("This operation was
    aborted"), so a session aborted at its second compaction was rerun as an
    engine failure: the attempt did not count and an engine retry was spent.

  • verify runs in a process group of its own, and Tenaz kills the group
    when it ends or times out. A check that started npm run dev and failed
    left Vite running on its fixed port, so the next check failed on the port
    (with --strictPort), and a leftover process that kept verify's output
    open made Tenaz wait for it.

  • verify runs with NO_COLOR=1 as well as CI=1. CI turns colours
    on in some tools (Vite), so a check that read their output failed under
    Tenaz and passed in the builder's shell. Escape codes are also left out of
    failure messages and output tails. The protocol tells builders the
    environment verify runs in.

  • tenaz watch shows Pi sessions. Pi's stream keeps Pi's own records,
    which watch dropped (or showed raw, marked ?, at debug); it now
    translates them as the Pi adapter does.

  • The setup wizard names the provider as tenaz init with flags does. For
    an engine address that does not answer yet, it pinned local; the flags
    pinned the provider usual on that port (llamacpp on 8080, ollama on
    11434, ...). Both now take that one, and local only for another port.
    The provider is part of model in run.json (provider/id), and the
    wizard's advice on the context window now names that engine (Ollama's
    context setting for an address on 11434).

Install tenaz 0.2.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/aartiles/tenaz/releases/download/v0.2.0/tenaz-installer.sh | sh

Install prebuilt binaries via Homebrew

brew install aartiles/tap/tenaz

Download tenaz 0.2.0

File Platform Checksum
tenaz-aarch64-apple-darwin.tar.gz Apple Silicon macOS checksum
tenaz-x86_64-unknown-linux-gnu.tar.gz x64 Linux checksum

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo aartiles/tenaz

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>