Skip to content

Releases

v0.111.2

Choose a tag to compare

@github-actions github-actions released this 15 Nov 00:48
cbdf0b4

Fixed

  • locks stats no longer counts a worker's tool call timed longer than the whole attempt it ran in (a
    machine that slept read as an 8-hour sed); it says how many it left out (Store.tool_time_impossible).
  • locks footprint compares releases only on briefs of tasks outside a workflow, whose briefs carry what
    earlier steps said, and names a release's growth only when both sides hold MIN_TASKS (10) briefs.

v0.111.1

Choose a tag to compare

@github-actions github-actions released this 14 Nov 04:16
71e2921

Changed

  • The orchestrating session no longer asks the person to type a locks command. A resume that grants
    (--allow, --allow-approval, --keep) waits for the person's yes in the conversation, then the session
    runs it and Claude Code's permission prompt is their approval; where Claude Code refuses it outright, the
    session points to the stop's button on the board instead of a line to type (commands/orchestration.md,
    locks guide endings).

v0.111.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 03:09
75a0144

Changed

  • The compaction advice is judged against the window the session really runs in and kept ahead of the
    harness's own compaction: the model a session's SessionStart names ([1m], which the transcript's model id
    never says) and any compaction the transcript keeps (preTokens) set the window,
    CLAUDE_CODE_AUTO_COMPACT_WINDOW narrows it, and CLAUDE_AUTOCOMPACT_PCT_OVERRIDE or the session's own
    automatic compactions say where the harness compacts by itself; the worth, pressing and urgent shares stay
    below that (Context.shares), and with the harness's compaction off nothing is pressing. While work the
    session sent still runs, from RUNNING_SHARE of the window, the session is told it is the moment to decide
    whether to compact before that work's ending or after it, before the harness decides for it.

v0.110.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 01:21
3f9d4d6

Added

  • Each tool call keeps how long it took, as Claude Code's PostToolUse reports it (duration_ms), and locks stats shows where the workers' tool calls spent their time: by signature, the calls, their total and the longest. The store's schema moves to version 2 (one added column).
  • /locks:insight runs in a fork of the session (context: fork, in the foreground): the traces, the analysis and doctor it reads stay out of the context every later turn re-reads, and only its report comes back.

v0.109.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 01:00
bc0a7bc

Added

  • TRACER as a way of working, not only documents: locks method tracer on puts a project on the method, and locks method says the phase it is in (read from what docs/tracer/ holds), its slices and the bundled workflow of that phase. Five new workflows do the phases before the slices: tracer-contract, tracer-spec, tracer-empathy, tracer-design and tracer-slices; their writing steps are held to docs/tracer/ and openspec/ by their surfaces, and the person's decisions (the contract's sign-off, the expectations that enter, the design base) are question steps.
  • A build request in a project on the method hears the phase it would skip, or the next slice: advice, never a block.
  • A slice's Definition of Ready is checked in code before any worker (ready: tracer on tracer-slice's build step): one whose requirements, empathy round, capability, critical flows or floors are missing stops as unready, naming what is missing.
  • locks method counts the expectations the slices' verifiers found that no CORRECT line, floor or catalogue entry covered.

v0.108.1

Choose a tag to compare

@github-actions github-actions released this 13 Nov 23:48
aa208e7

Fixed

  • A worker that locks' own guard refused to start locks work (a run, a workflow, the queue) stops the task as a decision at once, its work kept, instead of climbing: more effort met the same refusal twice before a third cell said so.

v0.108.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 22:25
3fc68d0

Added

  • scripts/demo.py DIR [--shots]: demo data for the README's screenshots, written by locks' own
    commands with the scenarios' fake claude in two generic repositories (no money spent), times and
    costs spread to a real worker's size; --shots retakes docs/images/ with Playwright. The
    screenshots are retaken with it.

Fixed

  • The board's Spend screen said $-0.00 for sessions when every dollar was a worker's (a float's
    rounding); it says $0.00.

v0.107.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 18:25
a8b0fd5

Added

  • What each workflow cost here, on the board. The Workflows screen gives every definition its record
    in the project (api.workflow_record): runs started, runs done and the median cost of a done run, read
    from the steps of up to RECORD_RUNS runs. Observed, never a budget.

Fixed

  • A continued session's attempt no longer counts the session it continued twice. The CLI's
    total_cost_usd for a --resume or a --fork-session is the whole session's (measured: a fork and a
    resume of a $0.0048 session each said $0.0059), and locks kept it as the attempt's own: every attempt
    given more turns or more effort, a trunk's fork and a resume after a death counted what came before
    again. In a real feature-parallel run a part that forked the plan was kept at $1.00, $0.64 of it the
    plan's. Now each worker session's whole cost is kept (orchestrate.session_cost, the store's meta),
    and an attempt that continues one keeps what it added (launch.own_cost, LaunchSpec.resume_cost_usd);
    the CLI's figure stays as WorkerResult.session_cost_usd. A session whose cost was never seen (one
    from before this release) keeps the CLI's figure, as before.

v0.106.1

Choose a tag to compare

@github-actions github-actions released this 13 Nov 15:55
dd1b574

Fixed

  • The bundled feature-parallel's plan is read blind. Its plan step names start: opus/high, and
    the critique counted that as a person's pin: it never drew an arm, so the one bundled workflow with
    parts never ran it (found by a real run of bench/speed/matrix.py). A start a workflow step's
    definition names is no pin.
  • A tracked tool artifact is never committed as the work. A kept branch dropped its tools'
    artifacts with git rm --cached, which staged the deletion of the ones a repository tracks: a feature
    run committed eight .pyc its check removed, its review read them as the change's, and two fix rounds
    could not undo them (stopped as review). They are now reset to HEAD.

v0.106.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 15:36
b906b3f

Added

  • A review's fix goes on in the session of the worker that built the change. In feature, bugfix
    and tracer-slice the fix step forks its builder's session (trunk), told it is its own change and
    given the rows the review confirmed, instead of a fresh worker orienting again in code it never saw.
    Only on the builder's model; whether it pays is the trunk's existing fork/fresh trial.
  • scripts/mutate.py: mutation testing of one module against the tests named for it, stdlib, the
    module always put back. Its first run: findings.py against tests/test_checking.py, 21 of 26
    mutants caught, the five left all text-clipping lengths, no rule.
  • docs/workflows.md: which bundled workflow fits which work, with one measured run of each.

Fixed

  • The PreCompact hook has 30 seconds, not 5. It writes the compaction's digest from the whole
    transcript; on a long session it was cancelled ("Hook cancelled") and the digest was not written.