Skip to content

v0.2.2 — verify speaks, screenshots live with the project

Choose a tag to compare

@bfortunato bfortunato released this 05 Sep 09:52
· 25 commits to main since this release

Fixed

  • --verify reported nothing. Inverting the output contract in 0.2.1 dropped both things the
    flag exists for. It says them again:

    click at (200, 200) — changed 6% — 41 ms
      20260905T093017.762Z-click.png
    

    unchanged is printed as a word, not a false: it is the one an agent has to notice, because it
    means the coordinate was stale.

  • Every run now ends with what the envelope carried, for thirteen tokens against its 177:

    ok — profile laptop, backend local, screen 1920x1080, scale 1
    failed at action 3 — profile laptop, backend local, screen 1920x1080, scale 1
    

    Cheap must not mean lossy. scale unknown prints as words, because refusing to guess is only
    useful if the caller can see it happened. stdout says what happened, stderr says why.

  • A repeated screenshot directory cost more than the whole summary line. A path is 23 tokens
    and a batch of five verified actions repeated the directory in all of them. It is named once now,
    and the lines carry filenames.

New

  • Screenshots live with the project, in .use-computer/screens/, with the XDG data directory
    as the fallback when there is no project. The tool writes .use-computer/.gitignore when it
    creates the directory — a capture is the whole desktop, and a working tree is one git add -A
    away from committing it. That also closes a gap older than this release: .env has been
    described as gitignored since the beginning and nothing ever made it so.

  • use-computer prune removes them, with --dry-run and --keep N. It deletes only files
    matching the names it writes, never the directory, and counts what it left alone.

The bundled skill

Rewritten around the two ways of knowing — structure and pixels — what each reaches, what each is
blind to, and which error means go and look. --via, the flag that chooses which rung of the
ladder an action takes, is finally in there. A test now asserts that everything the skill mentions
actually exists.