v1.3.6

Pytxo v1.3.6

Desktop gets a Wall of every agent across workspaces, and agent workspaces now
start from the exact bytes Review compares them against.

These are prepared release notes, updated October 26, 2026, not a release
announcement.

[added]

• Wall. Desktop Work has a Wall view next to Run. It shows
  every agent of every workspace's active runs on one screen, one pane per
  repository. Each tile shows the CLI, task, state, elapsed time and the last
  two output lines; 48 agents fit as 8 × 6 at 1080p, and narrow windows
  scroll. A finished agent's tile stays hollow, as the agent's claim, until
  its run's Review is Ready to Apply or Applied, then fills. Each pane has a
  verdict line per run that opens that run's Review, and the header counts
  ready runs (ready N/M). The Wall never applies. Present shows the
  Wall alone, full screen, with the home folder shown as ~ in output.

[changed]

• Combined check failures are named. A run whose combined check ran and
  failed now records candidate_check_failed with the task and command
  (<task>: <command> failed on the combined change) instead of a general
  review preparation error. Verifiers that could not run and integrity
  failures keep their codes.

[fixed]

• Worktree workspaces. When Pytxo fell back to a git worktree because no
  copy-layer could be built, or was set to one (isolation = "worktree" with
  [blast] prefer_kernel_overlay = false), the agent got a fresh checkout of
  HEAD. Review and Apply compare a workspace byte for byte with the primary
  checkout's files, and a checkout does not reproduce them under
  core.autocrlf (Git for Windows' default) or with uncommitted, untracked or
  ignored files. An agent that edited nothing could be rejected as editing
  outside its claims. Worktree workspaces now take the primary checkout's
  bytes for every path Review reads; if that copy fails, the worktree is
  rolled back. The run log records why a fallback happened.
• Runs that failed before any check. On Windows, the copy-layer workspace
  copied the repository's .pytxo/data (run store and process registry) into
  every agent's workspace. Agents starting together could block each other's
  registry lock (os error 32) and fail the run before any check, or fall back
  to a worktree that Review then rejected. .pytxo is no longer copied; Review
  and verification already skipped it. In a stress test, 16 of 117 runs failed
  this way before and 0 of 60 after.
• Ignored check output. A task check that writes files Git ignores, such
  as __pycache__ from python -m unittest, failed review preparation as an
  agent edit outside its claims, then the combined check as a candidate
  mutation. An ignored file in the primary checkout, such as .env, failed
  the same way. Review now skips unclaimed paths that the primary checkout's
  own Git rules ignore, and the combined check tolerates changes to ignored
  paths that will not land. Claimed and tracked paths stay strict, and so do
  new files hidden only by ignore rules the agent edited.
• Apply receipts. Apply receipts recorded every combined check with
  "exit_code": null and "duration_ms": 0. They now carry each check's
  exit code and time, and the receipt's top-level duration_ms is the
  Apply's own wall time (the checks ran when the review was prepared).
  Reviews prepared by 1.3.5 or earlier keep their digest and still Apply;
  their receipts show an empty exit code and zero time.
• Log redaction. Logs and MCP payloads now redact Windows profile paths
  written with forward slashes (C:/Users/<name>, as Node, Git and many
  agents print them), with mixed or JSON-escaped separators, and macOS
  /Users/<name> homes. The running user's own home is redacted whole even
  when the name has a space (C:\Users\John Smith), including as Git Bash and
  WSL print it (/c/Users/…, /mnt/c/Users/…). Another user's profile name
  with a space still leaks the part after the space.
• pytxo land install hint. When a combined check failed in a repository
  with a package.json, pytxo land suggested installing dependencies in the
  check even when the same command had passed on an input alone under
  --per-input. A pass alone shows the check's set-up works, so the hint now
  appears only when no solo run of the command passed.

Scope

Desktop Work, agent workspace isolation, review preparation, Apply receipts,
log redaction and pytxo land output. Permission profiles and execution
domains are unchanged. The workspace fixes apply under DeepSpace, Orbit and
Galaxy; Supernova runs in the repository root and is unchanged. The GitHub
Action defaults to installing 1.3.6.

Install

npm i -g pytxo@1.3.6
pytxo --version

With npm 12 or pnpm 10, which skip install scripts by default, the first
pytxo command downloads the binary and checks it against the release's
SHA256SUMS.txt.

Release assets:

• https://github.com/Pytxo-dev/pytxo-releases/releases/tag/v1.3.6

Previous: v1.3.5.