Skip to content

0.7.0 - 2026-11-11

Latest

Choose a tag to compare

@github-actions github-actions released this 11 Nov 08:20
3eb5334

Release Notes

Added

  • --mcp name=url, at init and run, offers the agent an MCP server of
    your own over HTTP, such as Blender Lab's server for a running Blender
    (ADR 0032). It is pinned in run.json as launch.mcpServers; run --no-mcp drops the pinned ones. fx, OpenCode, Qwen Code and --harness acp get them; init and run refuse them with Pi or dsh.

Changed

  • After verify or a heavy job ends, Tenaz also stops the processes it
    left running in a session of their own (Node's detached: true,
    setsid), which killing its process group missed. Such a process was
    born while it ran, leads a process group of its own, has no terminal,
    runs as the same user, is not git, works inside the project, and was
    adopted by launchd, init or systemd --user or has a parent still
    in the command's group (ADR 0031; see its known gap in
    docs/COMPATIBILITY.md). In a raycaster run, a check's detached npx vite preview built up 175 servers, about 2.5 GB, until the engine ran
    out of memory.
  • --harness dsh turns off dsh's own automatic compaction, so a session
    ends at Tenaz's context budget instead of summarizing its history once
    dsh's count reaches about 49k tokens of a 131k window. That count
    includes reasoning the proxy does not send (ADR 0030). In a 7-hour
    raycaster run with 0.6.0, 18 summaries and the requests after them
    took about 51 minutes.
  • If dsh still asks to summarize its conversation (the setting above did
    not apply), the engine proxy refuses the request, as it does Qwen
    Code's, and the session ends there as one out of context instead of
    the summary counting as a turn. In the 0.6.0 raycaster run seven
    summaries counted toward one session's 40-turn limit, which stopped it
    at "60/40" with 53 real turns and its checks passing.
  • --harness dsh gives dsh the user's Playwright and npm caches
    (PLAYWRIGHT_BROWSERS_PATH, npm_config_cache), so browsers and
    packages it installs are where verify, which runs with the user's
    own HOME, finds them. The protocol now says that verify runs with
    that HOME. In the 0.6.0 raycaster run a browser installed into
    dsh's HOME failed the first task's first verify, and npm install
    ran from an empty cache (354 s).
  • The protocol no longer tells sessions to use timeout 120 <command>,
    which macOS does not have: most sessions of a macOS run lost a turn to
    "command not found". It now says to set the shell tool's own time limit,
    and to time out a program a check starts in the check's own language.
  • The orchestrator's message after it stops a long tool call no longer
    suggests timeout 60 <command>; it says to run the call again with
    the shell tool's own time limit.
  • A check tests its requirement in the state the spec describes: one
    about the first screen is checked before any user action. The
    protocol, which every role reads, now says so. A check that changes
    such a state first is MAJOR for the reviewer; when a card asks for
    one, the builder follows the spec. In two runs a check of a game's
    first frame opened a door first, and only the final review caught it.

Security

  • rmcp, the MCP library behind the media server, goes from 3.5.1 to 3.9.0
    for RUSTSEC-2026-0461: an unbounded tool cache in its HTTP server, which
    only this machine can reach (the server listens on 127.0.0.1). The
    upgrade also clears RUSTSEC-2026-0457 (the OAuth client) and
    RUSTSEC-2026-0462 (the HTTP client), which Tenaz does not ship; only its
    tests use the client.

Install tenaz 0.7.0

Install prebuilt binaries via shell script

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

Install prebuilt binaries via Homebrew

brew install aartiles/tap/tenaz

Download tenaz 0.7.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>