these 2 derivations will be built: /nix/store/z90qvm3xacgd8lvkck1mf0jgll85nv00-agent-deck-1.16.36.drv /nix/store/cjmv26f062fyb8hcbw7nr16jm2hv1hh9-check-agent-deck.drv warning: ignoring the client-specified setting 'store', because it is a restricted setting and you are not a trusted user building '/nix/store/z90qvm3xacgd8lvkck1mf0jgll85nv00-agent-deck-1.16.36.drv' on farm.numtide.com:50051 agent-deck-1.16.36> bld1: building z90qvm3xacgd8lvkck1mf0jgll85nv00-agent-deck-1.16.36.drv agent-deck-1.16.36> Using versionCheckHook agent-deck-1.16.36> Running phase: unpackPhase agent-deck-1.16.36> unpacking source archive /nix/store/3yq2390qf9xp0g09qg6g6m0r6kx4rbmw-source agent-deck-1.16.36> source root is source agent-deck-1.16.36> Running phase: patchPhase agent-deck-1.16.36> Running phase: updateAutotoolsGnuConfigScriptsPhase agent-deck-1.16.36> Running phase: configurePhase agent-deck-1.16.36> Running phase: buildPhase agent-deck-1.16.36> Building subPackage ./cmd/agent-deck agent-deck-1.16.36> Running phase: checkPhase agent-deck-1.16.36> 2026/11/03 23:16:03 WARN codex_hook_status_unreadable instance=partial path=/tmp/nix-ymtTYN/TestWriteCodexHookStatus_PartialPriorFailsClosed1567289970/001/.local/share/agent-deck/hooks/partial.json bytes=10 agent-deck-1.16.36> Codex notify hook installed successfully. agent-deck-1.16.36> Config: /tmp/nix-ymtTYN/TestCodexHooksInstallUninstall1491618159/001/.codex/config.toml agent-deck-1.16.36> Codex notify hook removed successfully. agent-deck-1.16.36> Codex notify hook upgraded successfully. agent-deck-1.16.36> Config: /tmp/nix-ymtTYN/TestCodexHooksInstall_UpgradesLegacyTableWithoutMarkers1748919673/001/.codex/config.toml agent-deck-1.16.36> Codex notify hook upgraded successfully. agent-deck-1.16.36> Config: /tmp/nix-ymtTYN/TestCodexHooksInstall_UpgradesLegacyMarkerBlock2034789475/001/.codex/config.toml agent-deck-1.16.36> Codex notify hook upgraded successfully. agent-deck-1.16.36> Config: /tmp/nix-ymtTYN/TestCodexHooksInstall_ReplacesBlockInPlaceAndKeepsMode2841341667/001/.codex/config.toml agent-deck-1.16.36> Codex notify hook removed successfully. agent-deck-1.16.36> Error reading codex config: open /tmp/nix-ymtTYN/TestCodexHooksInstall_UnreadableConfigIsNotOverwritten2444514082/001/.codex/config.toml: permission denied agent-deck-1.16.36> Error writing codex config: open /tmp/nix-ymtTYN/TestCodexHooksInstall_ReadOnlyConfigIsNotReplaced3544520967/001/.codex/config.toml: permission denied agent-deck-1.16.36> Codex notify hook upgraded successfully. agent-deck-1.16.36> Config: /tmp/nix-ymtTYN/TestCodexHooksUninstall_KeepsLineEndingscrlf1116286640/001/.codex/config.toml agent-deck-1.16.36> Codex notify hook removed successfully. agent-deck-1.16.36> Codex notify hook upgraded successfully. agent-deck-1.16.36> Config: /tmp/nix-ymtTYN/TestCodexHooksUninstall_KeepsLineEndingsno_final_newline2119279818/001/.codex/config.toml agent-deck-1.16.36> Codex notify hook removed successfully. agent-deck-1.16.36> Error: the agent-deck notify block in /tmp/nix-ymtTYN/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.work1217507890/001/.codex/config.toml sits below a [table], where notify belongs to that table. agent-deck-1.16.36> Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'. agent-deck-1.16.36> Error: the agent-deck notify block in /tmp/nix-ymtTYN/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.qa,wes510254427/001/.codex/config.toml sits below a [table], where notify belongs to that table. agent-deck-1.16.36> Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'. agent-deck-1.16.36> Error: the agent-deck notify block in /tmp/nix-ymtTYN/TestCodexHooksInstall_BlockBelowTableIsRefused_hooks_._a=b2203094347/001/.codex/config.toml sits below a [table], where notify belongs to that table. agent-deck-1.16.36> Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'. agent-deck-1.16.36> agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-ymtTYN/TestEventProfileUsesStorageFallbackForMissingInference8763279/001/.claude-ghost" would select profile "ghost", which does not exist; falling back to profile "work" instead of creating it. Known profiles: none yet. Pass -p/--profile or set AGENTDECK_PROFILE explicitly to pick a different profile, run `agent-deck profile create ghost` if you intend to create it, or unset CLAUDE_CONFIG_DIR to use the default profile. agent-deck-1.16.36> Gemini hooks installed successfully. agent-deck-1.16.36> Config: /tmp/nix-ymtTYN/TestGeminiHooksInstallUninstall3003512764/001/.gemini/settings.json agent-deck-1.16.36> Gemini hooks removed successfully. agent-deck-1.16.36> ✓ Reordered group 'Beta': position 1 → 0 agent-deck-1.16.36> ✓ Reordered group 'Beta': position 1 → 2 agent-deck-1.16.36> ✓ Reordered group 'Gamma': position 2 → 0 agent-deck-1.16.36> ✓ Reordered group 'Alpha': position 0 → 0 agent-deck-1.16.36> ✓ Reordered group 'Gamma': position 2 → 2 agent-deck-1.16.36> ✓ Reordered group 'Alpha': position 0 → 2 agent-deck-1.16.36> agentpaths: resolved agent-deck path under the real home (/tmp/nix-ydC3Fx/.config/agent-deck); this touches REAL user data. If this is a test, it is NOT sandboxed; call testutil.IsolateHome() in TestMain and run with a temp HOME+XDG (2026-06-04 data-loss incident, S4). agent-deck-1.16.36> WARNING: no notify-daemon running; completions are not being recorded, so an empty drain or 0 done does not mean nothing finished. Start one with `agent-deck notify-daemon` (`agent-deck conductor setup` installs it as a service). agent-deck-1.16.36> WARNING: no notify-daemon running; completions are not being recorded, so an empty drain or 0 done does not mean nothing finished. Start one with `agent-deck notify-daemon` (`agent-deck conductor setup` installs it as a service). agent-deck-1.16.36> agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-ymtTYN/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG4124774196/001/.claude-ghost" would select profile "ghost", which does not exist; falling back to profile "work" instead of creating it. Known profiles: none yet. Pass -p/--profile or set AGENTDECK_PROFILE explicitly to pick a different profile, run `agent-deck profile create ghost` if you intend to create it, or unset CLAUDE_CONFIG_DIR to use the default profile. agent-deck-1.16.36> agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-ymtTYN/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG4124774196/001/.claude-ghost" would select profile "ghost", which does not exist; falling back to profile "work" instead of creating it. Known profiles: work. Pass -p/--profile or set AGENTDECK_PROFILE explicitly to pick a different profile, run `agent-deck profile create ghost` if you intend to create it, or unset CLAUDE_CONFIG_DIR to use the default profile. agent-deck-1.16.36> agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-ymtTYN/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG4124774196/001/.claude-ghost" would select profile "ghost", which does not exist; falling back to profile "work" instead of creating it. Known profiles: work. Pass -p/--profile or set AGENTDECK_PROFILE explicitly to pick a different profile, run `agent-deck profile create ghost` if you intend to create it, or unset CLAUDE_CONFIG_DIR to use the default profile. agent-deck-1.16.36> --- FAIL: TestIssue2921ClaudeLikeFakeIsGoneWhenItsCleanupReturns (0.00s) agent-deck-1.16.36> issue2921_guarded_fake_cleanup_test.go:36: fixture did not start agent-deck-1.16.36> notify-daemon: binary upgraded (running 1.16.36, on-disk 1.16.36-next); recycling agent-deck-1.16.36> notify-daemon: binary upgraded (running 1.16.36, on-disk 1.16.36-next); recycling agent-deck-1.16.36> Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)... agent-deck-1.16.36> Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)... agent-deck-1.16.36> Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)... agent-deck-1.16.36> remote-agent: probe: storage gone agent-deck-1.16.36> remote-agent: binary upgraded (running v1.16.36); exiting so the controller reconnects agent-deck-1.16.36> remote-agent: probe produced no listing (Error: database is locked) agent-deck-1.16.36> remote-agent: probe produced no listing ([]) agent-deck-1.16.36> remote-agent: no input for 300ms, exiting agent-deck-1.16.36> remote-agent: the host now selects another profile; exiting so the controller reconnects agent-deck-1.16.36> agent-deck-1.16.36> ═══ Remote: offline (a@offline) ═══ agent-deck-1.16.36> – Skipped: agent-deck not found on remote or host unreachable agent-deck-1.16.36> agent-deck-1.16.36> ═══ Remote: offline (a@offline) ═══ agent-deck-1.16.36> ✗ Failed: stub: no platform agent-deck-1.16.36> A remote sweep is already running on this controller (pid 33747, started 11:17PM); waiting for it... agent-deck-1.16.36> agent-deck-1.16.36> ═══ Remote: lab (a@lab) ═══ agent-deck-1.16.36> – Skipped: sweep already in progress, remote lab is being updated by 33747 agent-deck-1.16.36> agent-deck-1.16.36> ═══ Remote: other (a@other) ═══ agent-deck-1.16.36> ✓ Up to date (v1.16.0) agent-deck-1.16.36> agent-deck-1.16.36> ═══ Remote: lab (a@lab) ═══ agent-deck-1.16.36> ✓ Up to date (v1.16.0) agent-deck-1.16.36> agent-deck-1.16.36> ═══ Remote: other (a@other) ═══ agent-deck-1.16.36> ✓ Up to date (v1.16.0) agent-deck-1.16.36> Warning: the session restarted, but its new tmux name could not be recorded: record restart outcome for tmux session "agentdeck_cli-restart-target_ede561b9": record restart outcome for "8dc02759-1793747841": instance row not found agent-deck-1.16.36> The session is running; agent-deck may show it as errored until the name is saved. agent-deck-1.16.36> Handed switch-account of self to a detached agent-deck (pid 999): it targets the session this command runs in, whose restart ends this pane. Output: /tmp/x.log. Check the result with `agent-deck session show f1d0ce9b-1793747866` once the session is back. agent-deck-1.16.36> Warning: output freshness timeout (300ms) — response may be stale agent-deck-1.16.36> Warning: output freshness timeout (300ms) — response may be stale agent-deck-1.16.36> Warning: output freshness timeout (300ms) — response may be stale agent-deck-1.16.36> Launch agent re-registration deferred: a remote sweep (pid 12345, started 23:18:23) is still running agent-deck-1.16.36> Imported 2 channel(s) agent-deck-1.16.36> C0AABSF5GKD -> si-bugs/watcher.toml agent-deck-1.16.36> C1BBCDF6HLE -> feat-req/watcher.toml agent-deck-1.16.36> agent-deck-1.16.36> Note: Set the ntfy topic in each watcher.toml (all Slack channels agent-deck-1.16.36> share one ntfy topic from the Cloudflare Worker). agent-deck-1.16.36> Clients written to: /tmp/nix-ymtTYN/TestImportChannels_EndToEnd2070164056/002/clients.json agent-deck-1.16.36> Imported 1 channel(s) agent-deck-1.16.36> C0AABSF5GKD -> si-bugs/watcher.toml agent-deck-1.16.36> agent-deck-1.16.36> Note: Set the ntfy topic in each watcher.toml (all Slack channels agent-deck-1.16.36> share one ntfy topic from the Cloudflare Worker). agent-deck-1.16.36> Clients written to: /tmp/nix-ymtTYN/TestImportChannels_Idempotent2155514922/002/clients.json agent-deck-1.16.36> Imported 1 channel(s) agent-deck-1.16.36> C0AABSF5GKD -> si-bugs/watcher.toml agent-deck-1.16.36> agent-deck-1.16.36> Note: Set the ntfy topic in each watcher.toml (all Slack channels agent-deck-1.16.36> share one ntfy topic from the Cloudflare Worker). agent-deck-1.16.36> Clients written to: /tmp/nix-ymtTYN/TestImportChannels_Idempotent2155514922/002/clients.json agent-deck-1.16.36> Imported 0 channel(s) agent-deck-1.16.36> Clients written to: /tmp/nix-ymtTYN/TestImportChannels_EmptyChannels624141712/002/clients.json agent-deck-1.16.36> Installed skill: watcher-creator -> /tmp/nix-ymtTYN/TestWatcherInstallSkill3570675375/001/xdg-config/agent-deck/skills/pool/watcher-creator agent-deck-1.16.36> Installed skill: watcher-creator -> /tmp/nix-ymtTYN/TestWatcherInstallSkill_DirMode2865256201/001/xdg-config/agent-deck/skills/pool/watcher-creator agent-deck-1.16.36> Created watcher: create-topic-ntfy (type: ntfy) agent-deck-1.16.36> Warning: ntfy watcher: this topic is easy to guess and the public server https://ntfy.sh has no access token set, so anyone who guesses the topic can read its events and inject fake ones. Fix one of: use a random topic (agent-deck watcher create ntfy --name --random-topic); set an access token ($NTFY_TOKEN or --token-file with chmod 600, or token = "..." under [source] in watcher.toml); or use your own ntfy server (--server https://ntfy.example.com, or server = "..." under [source]). agent-deck-1.16.36> Created watcher: create-topic-slack (type: slack) agent-deck-1.16.36> Warning: slack watcher: this topic is easy to guess and the public server https://ntfy.sh has no access token set, so anyone who guesses the topic can read its events and inject fake ones. Fix one of: use a random topic (agent-deck watcher create slack --name --random-topic); set an access token ($NTFY_TOKEN or --token-file with chmod 600, or token = "..." under [source] in watcher.toml); or use your own ntfy server (--server https://ntfy.example.com, or server = "..." under [source]). agent-deck-1.16.36> Usage: agent-deck watcher [args] agent-deck-1.16.36> agent-deck-1.16.36> Watchers listen for inbound events (webhooks, push notifications, agent-deck-1.16.36> GitHub events, Slack messages) and route them to conductor sessions agent-deck-1.16.36> so your running agents can act on them automatically. agent-deck-1.16.36> agent-deck-1.16.36> Commands: agent-deck-1.16.36> create --name Create a new watcher (types: webhook, ntfy, github, slack) agent-deck-1.16.36> start Mark a watcher as running (run by the profile's watcher engine) agent-deck-1.16.36> stop Mark a watcher as stopped agent-deck-1.16.36> reload [--json] Apply watcher and clients.json changes to the running engine now agent-deck-1.16.36> list [--json] List all watchers with status and event rate agent-deck-1.16.36> status [--json] Show watcher info, recent events and events not delivered yet agent-deck-1.16.36> test Route a synthetic event to verify routing config agent-deck-1.16.36> routes [--json] Show all routing rules from clients.json agent-deck-1.16.36> import Migrate bash issue-watcher channels.json to Go watcher config agent-deck-1.16.36> install-skill Install a skill to ~/config/agent-deck/skills/pool (e.g. watcher-creator) agent-deck-1.16.36> agent-deck-1.16.36> Examples (one per adapter type): agent-deck-1.16.36> agent-deck-1.16.36> # Generic HTTP webhook on 127.0.0.1:9000. Requests must be signed with a agent-deck-1.16.36> # secret: generated and stored in its watcher.toml unless given by agent-deck-1.16.36> # $WEBHOOK_SECRET or --secret-file (chmod 600): agent-deck-1.16.36> agent-deck watcher create webhook --name my-webhook --port 9000 agent-deck-1.16.36> agent-deck-1.16.36> # GitHub repository webhook with HMAC-SHA256 verification agent-deck-1.16.36> # Secret comes from the environment or a chmod-600 file, never a CLI arg: agent-deck-1.16.36> GITHUB_WEBHOOK_SECRET=... agent-deck watcher create github --name gh-alerts agent-deck-1.16.36> agent-deck watcher create github --name gh-alerts --secret-file ~/.gh-webhook-secret agent-deck-1.16.36> agent-deck-1.16.36> # ntfy push-notification topic. On the public https://ntfy.sh anyone who agent-deck-1.16.36> # knows the topic can read and post to it, so use a random topic: agent-deck-1.16.36> agent-deck watcher create ntfy --name phone-alerts --random-topic agent-deck-1.16.36> # or an access-protected topic on your own ntfy server (token from the agent-deck-1.16.36> # environment or a chmod-600 file, never a CLI arg): agent-deck-1.16.36> NTFY_TOKEN=... agent-deck watcher create ntfy --name phone-alerts \ agent-deck-1.16.36> --server https://ntfy.example.com --topic phone-alerts agent-deck-1.16.36> agent-deck-1.16.36> # Slack-bridged via ntfy topic (see skill for Cloudflare Worker setup) agent-deck-1.16.36> agent-deck watcher create slack --name team-slack --random-topic agent-deck-1.16.36> agent-deck-1.16.36> After creating, activate and inspect: agent-deck-1.16.36> agent-deck watcher start agent-deck-1.16.36> agent-deck watcher list # see health + events/hour agent-deck-1.16.36> agent-deck watcher test # fire a synthetic event agent-deck-1.16.36> agent-deck-1.16.36> Routing: edit ~/data/agent-deck/watcher/clients.json to pick which agent-deck-1.16.36> conductor / group receives events. See `agent-deck watcher routes` for agent-deck-1.16.36> the currently-loaded rules across all watchers. agent-deck-1.16.36> agent-deck-1.16.36> Conversational setup (recommended for first-time use): agent-deck-1.16.36> agent-deck watcher install-skill watcher-creator agent-deck-1.16.36> # Then inside Claude Code in an agent-deck session, ask: agent-deck-1.16.36> # "Use the watcher-creator skill to set up a GitHub watcher" agent-deck-1.16.36> agent-deck-1.16.36> Full reference: https://github.com/asheshgoplani/agent-deck#watchers agent-deck-1.16.36> No routing rules configured. agent-deck-1.16.36> No watchers configured. agent-deck-1.16.36> Run 'agent-deck watcher create --name ' to create one. agent-deck-1.16.36> Installed skill: watcher-creator -> /tmp/nix-ymtTYN/TestXDGTask6_WatcherInstallSkillUsesConfiguredPoolPath4192692363/001/xdg-config/agent-deck/skills/pool/watcher-creator agent-deck-1.16.36> FAIL agent-deck-1.16.36> FAIL github.com/asheshgoplani/agent-deck/cmd/agent-deck 169.483s agent-deck-1.16.36> FAIL error: dependency 'z90qvm3xacgd8lvkck1mf0jgll85nv00-agent-deck-1.16.36.drv' failed