@axelgar/opentree 0.1.23 → 0.1.25

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +14 -4
  2. package/package.json +5 -5
package/README.md CHANGED
@@ -6,7 +6,7 @@ Think [Conductor](https://conductor.build), but for the terminal.
6
6
 
7
7
  opentree is a cross-platform CLI tool that manages multiple AI coding agent sessions. Each session runs in an isolated git worktree with its own branch, orchestrated via tmux. Perfect for working on multiple features/fixes simultaneously without context-switching overhead.
8
8
 
9
- <img src="docs/screenshot.png" style="width: 100%;max-width: 100%;">
9
+ <img src="docs/demo.gif" alt="opentree — orchestrate parallel AI coding sessions in isolated git worktrees" style="width: 100%;max-width: 100%;">
10
10
 
11
11
  ## Features
12
12
 
@@ -254,6 +254,13 @@ hour ago doesn't look the same as one that just landed:
254
254
 
255
255
  The status bar tallies the ones that want you: `N waiting` and, if any, `N stalled`.
256
256
 
257
+ Pane activity also rescues a stuck badge in both directions: a long-running
258
+ `in_progress` with a quiet status file but a still-active pane stays
259
+ `working…` instead of reading `stalled`, and a `needs_input` with pane output
260
+ *after* the status write (e.g. you approved a permission prompt, which isn't
261
+ a new top-level message) reads `working…` again instead of staying wedged on
262
+ `waiting`.
263
+
257
264
  **One-step setup.** Let opentree install the hooks for you:
258
265
 
259
266
  ```bash
@@ -268,9 +275,12 @@ launches, so the hooks write to the right worktree and stay inert (a no-op) in
268
275
  any session opentree didn't start. That means you install once, globally, and it
269
276
  just works across all your worktrees.
270
277
 
271
- `opentree agents setup <agent>` maps a new prompt `in_progress` and a
272
- permission prompt / notification / turn-end → `needs_input`. The bundled hooks
273
- report `status` only; the optional `message` is for hand-written or custom hooks.
278
+ `opentree agents setup <agent>` maps a new prompt and a completed tool call →
279
+ `in_progress`, and a permission prompt / notification / turn-end →
280
+ `needs_input`. The tool-completion hook is what flips the badge back to
281
+ `working…` after you approve a permission prompt mid-turn, since that isn't a
282
+ new prompt itself. The bundled hooks report `status` only; the optional
283
+ `message` is for hand-written or custom hooks.
274
284
 
275
285
  **GitHub Copilot** and **Pi** can't be fully automated (Copilot has no
276
286
  "waiting for input" event; Pi's notify config holds a single script) — running
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@axelgar/opentree",
3
- "version": "0.1.23",
3
+ "version": "0.1.25",
4
4
  "description": "Git worktree manager CLI for orchestrating parallel AI coding sessions",
5
5
  "repository": {
6
6
  "type": "git",
@@ -15,10 +15,10 @@
15
15
  "bin/opentree"
16
16
  ],
17
17
  "optionalDependencies": {
18
- "@axelgar/opentree-linux-x64": "0.1.23",
19
- "@axelgar/opentree-linux-arm64": "0.1.23",
20
- "@axelgar/opentree-darwin-x64": "0.1.23",
21
- "@axelgar/opentree-darwin-arm64": "0.1.23"
18
+ "@axelgar/opentree-linux-x64": "0.1.25",
19
+ "@axelgar/opentree-linux-arm64": "0.1.25",
20
+ "@axelgar/opentree-darwin-x64": "0.1.25",
21
+ "@axelgar/opentree-darwin-arm64": "0.1.25"
22
22
  },
23
23
  "engines": {
24
24
  "node": ">=18"