pytxo 1.3.6 → 2.0.1

package/README.md

@@ -1,12 +1,70 @@
-# pytxo (npm)
+# pytxo
 
-npm wrapper for the [Pytxo](https://pytxo.com) CLI. The first `pytxo` command downloads the same-version prebuilt binary from the public [pytxo-releases](https://github.com/Pytxo-dev/pytxo-releases) repository and checks it against the release's `SHA256SUMS.txt`. Package managers that run install scripts do this during `postinstall` instead; npm 12 and pnpm 10 skip it by default, and npm's warning about it is safe to ignore.
+**Land all your agents' branches in one command.**
 
-Community: [Discord](https://discord.gg/AUFRPFjSYv)
+Pytxo merges your Claude Code, Codex and Copilot branches in a throwaway
+worktree, runs your tests on the combined result, and lands what passes. What breaks stays out, and you see why. Free,
+open source, runs on your machine or in CI.
 
 ```bash
-npm i -g pytxo
-pytxo doctor
+npx pytxo demo      # watch it catch two branches that pass alone and fail together
+npx pytxo           # check the agent branches in your repository
+npx pytxo --apply   # and land them if they pass
 ```
 
-Set `PYTXO_SKIP_DOWNLOAD=1` and `PYTXO_BINARY=/path/to/pytxo` for local development.
+`npx pytxo` finds the agent branches (`claude/*`, `codex/*`, `copilot/*`,
+`cursor/*`, ... and every branch in a linked worktree), finds your test command
+(`npm test`, `pytest`, `cargo test`, `go test`, ...), and prints a verdict:
+
+```
+BLOCKED  claude/rename-price and codex/add-discount pass npm test alone but fail together.
+why      claude/rename-price renamed price to unitPrice; codex/add-discount still uses price (src/discount.js:1).
+next     rebase codex/add-discount onto claude/rename-price and use unitPrice, then run npx pytxo again.
+```
+
+Nothing in your repository changes unless you add `--apply`. Exit codes: `0` ready or landed (or
+nothing to check), `2` blocked or `--apply` landed only some branches, `3` stale (the target moved),
+`1` error, `130` stopped by Ctrl+C.
+
+In CI, one line in a workflow checks each agent pull request together with
+the other open ones into its base branch. Add
+`.github/workflows/pytxo.yml`:
+
+```yaml
+name: Pytxo
+on: pull_request
+permissions:
+  contents: read
+  pull-requests: write
+concurrency:
+  group: pytxo-${{ github.event.pull_request.number }}
+  cancel-in-progress: true
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: Pytxo-dev/pytxo/actions/land@v2
+```
+
+Your tests run in the job that holds this token, so give the workflow no other
+permissions or secrets. If Copilot's coding agent opens pull requests here, add
+`actions: read` so the check can include them once someone lets their run
+start; with it, code in the checked branches can also read every workflow
+run's logs and artifacts. See
+[the GitHub Action guide](https://pytxo.com/docs/getting-started/land-in-ci).
+
+Docs: [pytxo.com/docs](https://pytxo.com/docs) · Source:
+[github.com/Pytxo-dev/pytxo](https://github.com/Pytxo-dev/pytxo) · Community:
+[Discord](https://discord.gg/AUFRPFjSYv)
+
+## How the package works
+
+The first run downloads the same-version prebuilt binary from the public
+[pytxo-releases](https://github.com/Pytxo-dev/pytxo-releases) repository and
+checks it against the release's `SHA256SUMS.txt`. Package managers that run
+install scripts do this during `postinstall` instead; npm 12 and pnpm 10 skip
+it by default, and npm's warning about it is safe to ignore. Pytxo sends
+nothing anywhere.
+
+Set `PYTXO_SKIP_DOWNLOAD=1` and `PYTXO_BINARY=/path/to/pytxo` for local
+development.

package/bin/pytxo.js

@@ -3,16 +3,28 @@
 
 const { spawnSync } = require("node:child_process");
 const fs = require("node:fs");
+const os = require("node:os");
 
 const { dest, install } = require("../postinstall");
 
+// Lets the CLI say "run npx pytxo again" when it was started that way.
+const runAs = process.env.PYTXO_RUN_AS || (process.env.npm_command === "exec" ? "npx pytxo" : "pytxo");
+
 function run(bin) {
-  const result = spawnSync(bin, process.argv.slice(2), { stdio: "inherit" });
+  // The binary handles Ctrl+C itself: it removes its scratch checkout, a
+  // second Ctrl+C quits it at once, and it exits 130. Waiting for it keeps the
+  // terminal from coming back while it cleans up.
+  for (const signal of ["SIGINT", "SIGTERM", "SIGHUP"]) process.on(signal, () => {});
+  const result = spawnSync(bin, process.argv.slice(2), {
+    stdio: "inherit",
+    env: { ...process.env, PYTXO_RUN_AS: runAs },
+  });
   if (result.error) {
     console.error(result.error.message);
     process.exit(1);
   }
-  process.exit(result.status ?? 1);
+  // Killed by a signal: exit as a shell reports it, 128 plus its number.
+  process.exit(result.status ?? (result.signal ? 128 + os.constants.signals[result.signal] : 1));
 }
 
 async function main() {

package/lib/platform.js

@@ -3,6 +3,8 @@
 function getAssetName(platform = process.platform, arch = process.arch) {
   const assets = {
     "win32:x64": "pytxo-windows-x64.exe",
+    // Windows on Arm runs x64 binaries under emulation.
+    "win32:arm64": "pytxo-windows-x64.exe",
     "darwin:arm64": "pytxo-darwin-arm64",
     "darwin:x64": "pytxo-darwin-x64",
     "linux:arm64": "pytxo-linux-arm64",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pytxo",
-  "version": "1.3.6",
-  "description": "Pytxo agent hypervisor CLI — local-first PTY orchestration",
+  "version": "2.0.1",
+  "description": "Land all your agents' branches in one command. Pytxo merges your Claude Code, Codex and Copilot branches in a throwaway worktree, runs your tests on the combined result, and lands what passes.",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -11,12 +11,17 @@
   "bugs": "https://github.com/Pytxo-dev/pytxo-releases/issues",
   "keywords": [
     "pytxo",
-    "cli",
+    "claude-code",
+    "codex",
+    "copilot",
+    "cursor",
+    "coding-agents",
     "ai-agents",
-    "mcp",
-    "orchestration",
-    "terminal",
-    "rust"
+    "git",
+    "worktree",
+    "merge",
+    "ci",
+    "tests"
   ],
   "engines": {
     "node": ">=18"

package/postinstall.js

@@ -125,7 +125,10 @@ async function install() {
   const checksumUrl = `${releaseBase}/SHA256SUMS.txt`;
   const url = `${releaseBase}/${asset}`;
   console.error(`pytxo: downloading ${asset} ${TAG} and checking it against SHA256SUMS.txt…`);
-  const checksumText = (await downloadBuffer(checksumUrl)).toString("utf8");
+  const fetched = (promise) => promise.catch((error) => {
+    throw Object.assign(error, { downloadFailed: true });
+  });
+  const checksumText = (await fetched(downloadBuffer(checksumUrl))).toString("utf8");
   const checksum = expectedChecksum(checksumText, asset);
 
   if (fs.existsSync(dest)) {
@@ -136,7 +139,7 @@ async function install() {
     }
   }
 
-  const bytes = await downloadBuffer(url);
+  const bytes = await fetched(downloadBuffer(url));
   assertChecksum(bytes, checksum, asset);
   const suffix = process.platform === "win32" ? ".exe" : "";
   const temp = path.join(
@@ -167,7 +170,11 @@ async function main() {
 if (require.main === module) {
   main().catch((error) => {
     console.error(`pytxo: install failed: ${error.message}`);
-    process.exitCode = 1;
+    // A download that did not happen (offline, a proxy) must not fail
+    // `npm install` or `npx`: the launcher tries again on first run. A binary
+    // that fails verification fails the install.
+    if (error.downloadFailed) console.error("pytxo: the first run of pytxo will try again.");
+    else process.exitCode = 1;
   });
 }