Repository navigation
0.1.0 - 2026-10-27
Release Notes
Added
-
The README opens with a GIF of a scripted
tenaz demorun, recorded
with VHS fromdocs/demo/demo.tape. -
tenazbinary withinit,run,status,finishandparams. -
--helpdescribes the workflow with a non-interactive example;run --help
lists the exit codes andstatus --helpwhat each phase means. -
tenaz runexits with 0 when the goal is met, 3 when it completes with
gaps, 4 when it is blocked and 5 when it pauses; 1 is an error and 2 a
usage error. -
tenaz status --jsonprints the status as one JSON object (phase,
state,pid,blocked_reason,last_error, task counts, current task,
session in progress,origin); the text status gains aState:line. -
tenaz runholds a lock on the project while it works: a second run on
the same project is refused, andstatustells a working run (running)
from one that was killed or failed (interrupted). -
tenaz guideprints an Agent Skill for delegating goals to Tenaz from
another agent. -
The agent skill moved to
skills/tenaz/SKILL.md, sonpx skills add aartiles/tenazinstalls it. It now also covers installing and setting
up Tenaz:tenaz doctorand its fixes, what to ask the user to do
rather than doing it, andtenaz demo. -
tenaz demoshows a whole run in about a minute with no model and no
agent: the scripted harness builds a small goal in a newtenaz-demo
folder. It replaces the three commands the README gave for that, and
tenaz doctoroffers it while something is still missing. -
tenaz doctorchecks git, a coding agent, an engine and a model with
enough context, and says how to install or fix what is missing (the
install commands for Pi and fx, LM Studio or Ollama, the context setting
of each engine). It exits with 0 when a real run can start and 1
otherwise. The setup wizard gives the same advice when it finds no git,
no agent, no engine or too small a context. -
Setup wizard:
tenaz initwithout--model, in a terminal, finds the
coding agents onPATH, the engines on their usual ports with their
models, context windows and vision, and ComfyUI, then prints the
equivalent command line.--interactiveforces it with a piped stdin. -
run.jsonpins how to launch the run (launch: engine API and
start/stop commands, proxy, harness executable, ComfyUI and workflows,
media timeout), sotenaz runneeds no flags; a flag given torun
replaces the pinned value and is saved.runandstatusdefault to
the current directory. -
On a repository that already has commits,
initworks on a new branch
tenaz/<goal>in a worktree next to the repository instead of on the
current branch, refuses a tree with uncommitted changes, and records the
starting branch and commit inrun.json(origin).--in-placekeeps
the old behaviour;--worktreeand--namechoose the directory and
branch. The setup wizard asks which,runandstatussay where the
run works, and both point to the worktree from the original checkout.
A directory inside a repository that tracks nothing in it, such as an
ignored directory with seed files, is a new project rather than refused. -
tenaz finish: a branch in the original repository with the run's
result as one commit on the starting commit, without.tenaz/(nor,
for older layouts, the root files and.gitignorelines Tenaz added);
the run branch keeps the full history,--remove-worktreeremoves the
worktree. Nothing is pushed. -
The run's state lives in
.tenaz/(it was.agent/). A project still
in the old layout is not run:init,runandstatussay how to move
it (mv .agent .tenaz, the.gitignorelines,--refresh-templates). -
Tenaz keeps all its files under
.tenaz/: the brief is
.tenaz/brief.md(it wasBRIEF.md), the shared rules are
.tenaz/protocol.md(they were the project'sAGENTS.md) and the ignore
rules are in.tenaz/.gitignore(they were appended to the project's
.gitignore). The protocol now starts every session's prompt instead of
relying on the agent to loadAGENTS.md, soinitworks in a project
that has its ownAGENTS.md, and sessions may not edit the project's
AGENTS.mdorCLAUDE.md. A run started withBRIEF.mdat the root is
not run:runandstatussay how to move it (git mv,
--refresh-templates). -
existingProjectparameter.initsets it when the repository already
has commits:verifyis then.tenaz/verify, a wrapper around the
project's own tests, new checks go into the project's test suite, and
bootstrap plans only the change instead of a skeleton. -
Without
--engine,initasks the engine at--base-urlwhich API it
speaks (Sushi or generic) and names the provider after it. -
Orchestrator: bootstrap, build, verify, review,
split or block, replan and final review, with pause and resume. -
Lease manager keeping one engine resident at a time.
-
OpenAI-compatible engine proxy that holds requests while engines swap.
-
Harness adapters for fx over ACP and Pi over its RPC mode, plus a scripted
fake harness. -
Engine adapters for Sushi and generic OpenAI-compatible engines; ComfyUI
media adapter; MCP server exposinggenerate_image. -
The README and
docs/COMPATIBILITY.mdname MLX'smlx_lm.serverand
TensorFold as engines to use with--engine generic, untested. -
CI on macOS and Linux and a tagged release workflow.
-
Releases are built with dist and come with an install script
(curl ... | sh) that putstenazin~/.local/binand onPATH, and
a Homebrew formula inaartiles/homebrew-tap. -
requests.jsonlrows carry the engine's owntimingsper request
(server: prefill and decode milliseconds, cached tokens, and draft
counts when the engine reports them), andstatusprints the draft
acceptance. -
tenaz watchfollows a run from its files as it works, at four levels:
summary(the run log),actions(each tool call and reply on one line,
with context, output, thinking and decode speed),full(whole replies,
the start of tool results) anddebug(the harness's log too).--once
prints the current session and exits. -
A context budget lowered because the engine ran out of memory is raised
halfway back aftercapacityRecoverSessionssessions in a row (4 by
default; 0 keeps it lowered) that the engine held without critical memory
pressure. A raise the engine overflows again lowers it as before and
doubles the sessions the next raise waits for, up to four times as many;
a raise the engine held starts that count again. -
--images <base URL> --image-model <id>gives the agent its image tool
through an OpenAI Images API (POST /v1/images/generations), as MLX
servers, LocalAI and Atomic Chat serve it, with no workflow to export.
When that API is on the LLM's own server, the LLM stays loaded while the
image renders (ADR 0002). -
tenaz init's wizard offers an image tool when an engine on the usual
ports, Atomic Chat on 1337 or mlx-serve on 11234, lists an image model
(the LLM's own engine first), before it looks for ComfyUI.tenaz doctorlists the image engines it finds with the flags that use them.
TENAZ_NO_PROBEkeeps both from looking at the usual ports, for tests
and scripted setups. -
A builder session that answers its prompt while
./verify --taskruns no
passing check of its task gets one more prompt asking it to add them,
before the attempt is judged. In the Wild West run 32 of 197 attempts
passed--allbut failed only for lack of the task's own check. -
A raised context budget never goes above the headroom share of what the
engine said it could hold when an earlier raise overflowed it. Raising
past it only overflowed again: in the Wild West run the engine held
86016 tokens, yet the budget was raised above 68812 six times and lowered
back each time, and a low reading under passing memory pressure then
kept the budget at 38215 for seven hours while raises waited 64 sessions. -
A session is steered to wrap up when, at the pace its context grew over
the last requests, it would reach the context stop within
contextSteerTurnsturns (10 by default; 0 steers only at the budget), so
a slow-to-react model can still write its handoff before it is stopped. -
An attempt that uses up its context continuations and still fails
verifyis split at once instead of retried against the same budget
(contextSplit, on by default), when the split depth allows. -
A builder's briefing shows only the spec requirements its card requires,
with a pointer to the whole spec (citedSpec, on by default; a card that
names none the spec has gets the whole spec). A session that continues
stopped work no longer gets the repository map in its prompt. -
A session steered for going idle is asked to write what it already knows
(the files and facts the change depends on, and its plan) in its task's
notes before making the change, and the next attempt's briefing includes
those notes. -
Reading something not read before counts as progress for the idle rule,
like a file change; repeated reads of the same thing still count as idle. -
With fx, each session's reasoning text is kept in
.tenaz/private/<label>.thinking.md, with a line after each model
request. Before, only its length was kept. -
A bootstrap session after a failed one is told which files the earlier
sessions left (git diff --statsinceinit) and asked to continue from
them instead of starting over. Before, it got only the list of problems,
and explored and wrote the spec again. -
The bootstrap runs in three steps, one session each: the spec and map,
then a minimalverify, then the task cards (ADR 0003). Each
session gets only its step's part ofbootstrap.md, steps 2 and 3 get
the spec and map in their prompt, andmaxBootstrapAttemptsapplies to
each step. A step whose files are already right is passed without a
session.run.jsongainsbootstrap_step,BootstrapValidation
records gainstep, andtenaz statusshows the step. A local model
drafted the whole bootstrap in its reasoning and hit the output limit
before writing any file, even at low effort. -
The engine API Tenaz loads and unloads models with is called
load-api
(--engine load-api,"engine": "load-api"inrun.json) instead of
sushi, since mlx-serve has the same API;sushiis still read. mlx-serve
is detected on its port 11234 and named as itself, not as Sushi.
Fixed
- In an existing project, a change to
.tenaz/verify(the project's
verify) is shown in the reviewer's diff and in the builder's list of
changes kept from earlier attempts. Both left out all of.tenaz/, so a
reviewer could not see an edit to the checks' runner. - The media MCP server keeps a session open for a day without requests
instead of 5 minutes (rmcp's default). fx opens its session when an agent
session starts; a first image call more than 5 minutes later failed with
McpSessionExpiredand cost a call of the image budget, in both
image-landing runs. generate_imagewithout a width or height fills a ComfyUI workflow's
size placeholders with 1024 instead of leaving{{width}}as text,
which ComfyUI rejected.- Ctrl-C during the engine preflight pauses the run instead of ending it
with a failed preflight. - A harness that ends before its turn settles is retried like an engine
failure instead of being charged as a task attempt, and its exit code and
stderr tail are journaled (harness_exit). - A harness that ends while one of the session's tool calls runs counts as
a failed attempt instead of an engine failure, and the next briefing
names the call: a rerun made the same call and the harness died again
until the run blocked. When the output was not valid UTF-8 (fx dies on
it), the briefing also says not to cut output by bytes. - A session whose reply stopped at the output limit while the model was
still reasoning (fx exits on it withOutputTruncated) counts as a
failed attempt instead of an engine failure, the next briefing says why,
and the next session asks the engine for one step less reasoning effort
(through the proxy). Rerun unchanged at temperature 0, such sessions
reasoned the same way again until the run blocked. - A reply that reaches the output limit counts as cut even when the engine
ends it withtool_calls(TensorFold does, for a reply cut inside a
tool call's arguments). Tenaz retried such sessions as engine failures,
up to six times with waits, at the same effort. - A steer for context, turns or compaction asks each role for what it may
write before stopping: a reviewer its verdict file, the final reviewer
FINAL.md, a planner its cards. All were told to write handoff notes,
and reviewers did, in notes files that were then reverted. - A review asks for changes only with at least one MAJOR finding: the
reviewer prompt says so, and aCHANGESwhose findings are all MINOR is
accepted. One such review cost a whole builder and review cycle for a
missing line in a decisions file. - A reviewer's briefing lists the images the change adds or replaces, and
the reviewer prompt asks to look at them first, in one contact sheet when
there are more than two, and to check they match the project's other
images. The final reviewer looks at all the product's images first. In
the image-landing run on mlx-serve the reviewers opened page screenshots
only, and the final reviewer marked the visual requirements manual
without seeing the images, so a product that changed from image to image
went unnoticed. - Each line of
.tenaz/private/requests.jsonlrecords, undersent, the
sampling and limits the request asked the engine for, as the proxy
forwarded it:temperature,top_p,top_k,reasoning_effort(the
lowered one after a cut) andmax_tokens. A field the request did not
carry is left out: the engine used its own default. Only for requests
through the proxy. --set temperature=<t>pins the run's sampling temperature: the proxy
puts it in requests that carry none (fx sends none). Unset, as before,
each engine uses its own default, which made the TensorFold and mlx-serve
runs of the same goal sample at 0 and 0.8.- An attempt fails when
./verify --allpasses fewer checks of other tasks
than when the last task was done (passed_checksinrun.json): a check
was removed orverifyno longer runs it. Before, only the reviewer could
notice. A check weakened without being removed still passes this rule. - fx writes one ACP log per session instead of overwriting a shared one.
- An ACP session handles a proxy observation before the prompt's end, so
per-request usage is no longer occasionally lost or attributed to the
wrong turn. - The engine proxy adds the missing
actionto a tool call that sends a
commandwithout it, when every variant of the argument that takes a
commandfixes the sameaction(models drop it from fx'sshellcall,
which fx then rejects). - The engine proxy moves properties a model sends beside fx's
shell.request(such astimeout_msorcwd) into it, when the variant
itsactionselects takes them all and the request does not already hold
them; fx rejected those calls. - The engine proxy clamps an integer argument outside the range its schema
declares (such as fx'syield_time_msabove 30000) to that range; after
fx's rejection models retried with the limit anyway. - The protocol tells every session that commands run at the project root
and to use relative paths: models guessed the project's absolute path for
cwdorcd, and the guess was often wrong. - With a generic engine and no
--engine-stopand--engine-start, an
image now renders with the LLM still loaded, as the wizard says; before,
the image request failed. A stop command that fails no longer leaves the
agent's requests waiting until the next session.
Security
SECURITY.mdand the README say what Tenaz does not isolate (the agent's
commands,verify, the unauthenticated local proxy and MCP server) and
how to report a vulnerability privately.
Install tenaz 0.1.0
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/aartiles/tenaz/releases/download/v0.1.0/tenaz-installer.sh | shInstall prebuilt binaries via Homebrew
brew install aartiles/tap/tenazDownload tenaz 0.1.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 |