@brutalsystems/birddog 0.1.4 → 0.2.0

package/README.md

@@ -42,7 +42,7 @@ Then watch something. Take a `session_id` (and, for Claude Code, the `pid` and
 ```sh
 birddog start --config birddog.json
 birddog status --instance <id>
-birddog events --instance <id> --after <cursor> --wait 30
+birddog events --instance <id> --after <cursor> --wait 25
 birddog stop --instance <id>
 ```
 
@@ -87,10 +87,12 @@ threads as `notLoaded` to anyone who does not own them, which describes the
 asking process rather than the session — so birddog says it cannot see the
 state instead of guessing one.
 
-Nor will it tell you a worker is unblocked. No provider exposes permission
-requests to an outside observer today, so every target reports input-request
-visibility as `unavailable`. An absence of observation is never reported as
-evidence of absence — and a turn ending is not work finishing.
+Nor will it tell you a worker is unblocked. Where a permission request can be
+seen it is reported, and where it cannot birddog says `unavailable` rather than
+implying there is none — Claude Code's registry reports a waiting session and
+an instrumented opencode session reports the request itself, while Codex
+exposes neither. An absence of observation is never reported as evidence of
+absence, and a turn ending is not work finishing.
 
 ## Start here
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brutalsystems/birddog",
-  "version": "0.1.4",
+  "version": "0.2.0",
   "description": "Watch live coding-agent sessions on this machine and report what they are doing. Observation only: it never prompts, approves, or starts and stops a session.",
   "keywords": [
     "claude-code",