Repository navigation
Releases
v3.1.0
3.1.0 — a target policy can carry a deadline ("deadline": RFC3339, or "deadline_after_seconds" from when the instance took the target on); past it, a target that has not exited raises one overdue incident, resolved by exit or by moving or clearing the deadline. overdue joins the default alert_on and never fires without a deadline. watch update --deadline 45m|RFC3339 and --clear-deadline set it live; status shows policy.deadline, deadline_passed and a DEADLINE column. A superseded run's incidents now close on every pass.
v3.0.1
3.0.1 — documentation and test examples use generic names; adds scripts/check-public.sh, a pre-push check that refuses to publish home paths, email addresses, token shapes or terms from a locally kept list (install with make hooks). No change to the CLI or the plugin.
v3.0.0
3.0.0 — hooks and doctor default to $CLAUDE_CONFIG_DIR/settings.json (falling back to ~/.claude); after /clear the feed shows session_followed with the new session_id instead of an exit; owner-tied instances and claude-inbox follow the owner across /clear; session registries are read from ~/.claude/sessions, $CLAUDE_CONFIG_DIR/sessions and BIRDDOG_CLAUDE_CONFIG_DIRS; status reports each watch's policy.
v2.0.0
2.0.0 — the tincan connector requires tincan 2.0.0 or newer, and reports a deduplicated delivery honestly.
Two breaking changes, both in the tincan notification route.
A route configured against tincan 1.10.1 now refuses to start until tincan is upgraded. The startup probe asks tincan send --help and reads the exit code, which tincan 2.0.0 documents as its capability check; every older build exits non-zero. It previously matched the string 'unrecognised argument' on stderr, because 1.9.2 and 1.10.1 both exited non-zero from a bare send and only the wording told them apart — that wording was tincan's usage prose rather than an interface, so a reword would have silently turned the probe into one that accepts a tincan that cannot deliver.
The meaning of a recorded delivery outcome has changed. duplicate_send is now reported as delivered rather than delivery_unknown. tincan 2.0.0 added a duplicate_peer_moved refusal for the retry whose target name has since moved to a different session, so duplicate_send now means the peer being addressed really does hold the message — the same claim accepted makes. Only the moved case stays delivery_unknown, which restores the ordinary retry path.
These are one change, not two: reporting a duplicate as delivered is only true where the other refusal exists to carry the moved case, so refusing every older tincan is what keeps it honest. 1.10.1 has send and delivers, and is refused for lacking the refusal rather than the subcommand.
Note that tincan's own 2.0.0 is not an API break — that major covers their clean-history republish and the npm provenance discontinuity that came with it.
Also in this release: docs/decisions.md D6 is revisited against an instrumented corpus now that activity_resolution exists, keeping the decision that no_progress ships with no default but narrowing the reason to a missing measurement rather than a missing principle; scripts/replay-activity.mjs keeps that replay so it need not be written from scratch again; and docs/troubleshooting.md gains an entry pointing a stuck session at no_progress.
v1.0.1
1.0.1 — first published stable release
birddog watches live Claude Code, Codex and opencode sessions on one machine
and tells an orchestrating agent what it observed: a session went idle, asked
for input, exited, or went quiet. It never sends a prompt, never approves
anything, and never starts, stops or restarts a session.
This is the first release of the reset repository, and the first stable one.
v1.0.0 was tagged and never published: its run failed before the publish job,
on a test fixture that a blanket *.jsonl ignore rule had kept untracked. The
tag is left in place rather than moved, and 1.0.1 is the version that ships.
Versions 0.1.0 through 0.6.1 remain on npm and are deprecated. Their
provenance attestations point at commits in a repository that no longer
exists, so npm reports that it cannot find the source commit for them. That is
expected and cannot be repaired.
From 1.0 birddog follows ordinary semver. Before it, the minor carried the
breaking-change signal because there was no major to spend, and release notes
from then read under that older rule.
Since 0.6.1: a session blocked on a natural-language question is reported as
waiting, by reading the session transcript, opt-in per target via
observations.transcript; an observed input request now says how it was learned
through a new evidence field; alerts can be delivered through the tincan CLI,
reaching a Codex or opencode orchestrator as well as Claude Code; and an
answered permission request stops being reported as pending, which previously
left a session reported as blocked for up to two hours after the human replied.