don't know how to build these paths: /nix/store/3y9z9sblmf40bjlpjydkhvnxmzbk7fa4-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/1w5hbhiygv99n15j75vcc4c6ylqf9csw-agent-deck-1.16.35.drv' on farm.numtide.com:50051 agent-deck-1.16.35> bld1: building 1w5hbhiygv99n15j75vcc4c6ylqf9csw-agent-deck-1.16.35.drv agent-deck-1.16.35> Using versionCheckHook agent-deck-1.16.35> Running phase: unpackPhase agent-deck-1.16.35> unpacking source archive /nix/store/k1s5z7sm1gl0gavln4pl53w4fi2k0yvk-source agent-deck-1.16.35> source root is source agent-deck-1.16.35> Running phase: patchPhase agent-deck-1.16.35> Running phase: updateAutotoolsGnuConfigScriptsPhase agent-deck-1.16.35> Running phase: configurePhase agent-deck-1.16.35> Running phase: buildPhase agent-deck-1.16.35> Building subPackage ./cmd/agent-deck agent-deck-1.16.35> buildPhase completed in 58 seconds agent-deck-1.16.35> Running phase: checkPhase agent-deck-1.16.35> 2026/11/01 04:54:24 WARN codex_hook_status_unreadable instance=partial path=/tmp/nix-7mCBE3/TestWriteCodexHookStatus_PartialPriorFailsClosed2014229125/001/.local/share/agent-deck/hooks/partial.json bytes=10 agent-deck-1.16.35> Codex notify hook installed successfully. agent-deck-1.16.35> Config: /tmp/nix-7mCBE3/TestCodexHooksInstallUninstall3008936965/001/.codex/config.toml agent-deck-1.16.35> Codex notify hook removed successfully. agent-deck-1.16.35> Codex notify hook upgraded successfully. agent-deck-1.16.35> Config: /tmp/nix-7mCBE3/TestCodexHooksInstall_UpgradesLegacyTableWithoutMarkers2142828215/001/.codex/config.toml agent-deck-1.16.35> Codex notify hook upgraded successfully. agent-deck-1.16.35> Config: /tmp/nix-7mCBE3/TestCodexHooksInstall_UpgradesLegacyMarkerBlock2796137051/001/.codex/config.toml agent-deck-1.16.35> Codex notify hook upgraded successfully. agent-deck-1.16.35> Config: /tmp/nix-7mCBE3/TestCodexHooksInstall_ReplacesBlockInPlaceAndKeepsMode953924304/001/.codex/config.toml agent-deck-1.16.35> Codex notify hook removed successfully. agent-deck-1.16.35> Error reading codex config: open /tmp/nix-7mCBE3/TestCodexHooksInstall_UnreadableConfigIsNotOverwritten3891963120/001/.codex/config.toml: permission denied agent-deck-1.16.35> Error writing codex config: open /tmp/nix-7mCBE3/TestCodexHooksInstall_ReadOnlyConfigIsNotReplaced3944249858/001/.codex/config.toml: permission denied agent-deck-1.16.35> Codex notify hook upgraded successfully. agent-deck-1.16.35> Config: /tmp/nix-7mCBE3/TestCodexHooksUninstall_KeepsLineEndingscrlf1107328537/001/.codex/config.toml agent-deck-1.16.35> Codex notify hook removed successfully. agent-deck-1.16.35> Codex notify hook upgraded successfully. agent-deck-1.16.35> Config: /tmp/nix-7mCBE3/TestCodexHooksUninstall_KeepsLineEndingsno_final_newline198030538/001/.codex/config.toml agent-deck-1.16.35> Codex notify hook removed successfully. agent-deck-1.16.35> Error: the agent-deck notify block in /tmp/nix-7mCBE3/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.work1516091442/001/.codex/config.toml sits below a [table], where notify belongs to that table. agent-deck-1.16.35> Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'. agent-deck-1.16.35> Error: the agent-deck notify block in /tmp/nix-7mCBE3/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.qa,wes1797576958/001/.codex/config.toml sits below a [table], where notify belongs to that table. agent-deck-1.16.35> Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'. agent-deck-1.16.35> Error: the agent-deck notify block in /tmp/nix-7mCBE3/TestCodexHooksInstall_BlockBelowTableIsRefused_hooks_._a=b4117199449/001/.codex/config.toml sits below a [table], where notify belongs to that table. agent-deck-1.16.35> Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'. agent-deck-1.16.35> agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-7mCBE3/TestEventProfileUsesStorageFallbackForMissingInference4171839056/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.35> Gemini hooks installed successfully. agent-deck-1.16.35> Config: /tmp/nix-7mCBE3/TestGeminiHooksInstallUninstall2455944541/001/.gemini/settings.json agent-deck-1.16.35> Gemini hooks removed successfully. agent-deck-1.16.35> ✓ Reordered group 'Beta': position 1 → 0 agent-deck-1.16.35> ✓ Reordered group 'Beta': position 1 → 2 agent-deck-1.16.35> ✓ Reordered group 'Gamma': position 2 → 0 agent-deck-1.16.35> ✓ Reordered group 'Alpha': position 0 → 0 agent-deck-1.16.35> ✓ Reordered group 'Gamma': position 2 → 2 agent-deck-1.16.35> ✓ Reordered group 'Alpha': position 0 → 2 agent-deck-1.16.35> agentpaths: resolved agent-deck path under the real home (/tmp/nix-QNirt0/.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.35> 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.35> 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.35> agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-7mCBE3/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG1850021618/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.35> agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-7mCBE3/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG1850021618/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.35> agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-7mCBE3/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG1850021618/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.35> --- FAIL: TestIssue2921ClaudeLikeFakeIsGoneWhenItsCleanupReturns (0.00s) agent-deck-1.16.35> issue2921_guarded_fake_cleanup_test.go:33: fixture did not start agent-deck-1.16.35> notify-daemon: binary upgraded (running 1.16.35, on-disk 1.16.35-next); recycling agent-deck-1.16.35> notify-daemon: binary upgraded (running 1.16.35, on-disk 1.16.35-next); recycling agent-deck-1.16.35> Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)... agent-deck-1.16.35> Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)... agent-deck-1.16.35> Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)... agent-deck-1.16.35> remote-agent: probe: storage gone agent-deck-1.16.35> remote-agent: binary upgraded (running v1.16.35); exiting so the controller reconnects agent-deck-1.16.35> remote-agent: probe produced no listing (Error: database is locked) agent-deck-1.16.35> remote-agent: probe produced no listing ([]) agent-deck-1.16.35> remote-agent: no input for 300ms, exiting agent-deck-1.16.35> remote-agent: the host now selects another profile; exiting so the controller reconnects agent-deck-1.16.35> agent-deck-1.16.35> ═══ Remote: offline (a@offline) ═══ agent-deck-1.16.35> – Skipped: agent-deck not found on remote or host unreachable agent-deck-1.16.35> agent-deck-1.16.35> ═══ Remote: offline (a@offline) ═══ agent-deck-1.16.35> ✗ Failed: stub: no platform agent-deck-1.16.35> A remote sweep is already running on this controller (pid 24177, started 4:56AM); waiting for it... agent-deck-1.16.35> agent-deck-1.16.35> ═══ Remote: lab (a@lab) ═══ agent-deck-1.16.35> – Skipped: sweep already in progress, remote lab is being updated by 24177 agent-deck-1.16.35> agent-deck-1.16.35> ═══ Remote: other (a@other) ═══ agent-deck-1.16.35> ✓ Up to date (v1.16.0) agent-deck-1.16.35> agent-deck-1.16.35> ═══ Remote: lab (a@lab) ═══ agent-deck-1.16.35> ✓ Up to date (v1.16.0) agent-deck-1.16.35> agent-deck-1.16.35> ═══ Remote: other (a@other) ═══ agent-deck-1.16.35> ✓ Up to date (v1.16.0) agent-deck-1.16.35> Warning: the session restarted, but its new tmux name could not be recorded: record restart outcome for tmux session "agentdeck_cli-restart-target_4c479bd0": record restart outcome for "95206b02-1793509005": instance row not found agent-deck-1.16.35> The session is running; agent-deck may show it as errored until the name is saved. agent-deck-1.16.35> 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 bb505d29-1793509036` once the session is back. agent-deck-1.16.35> Warning: output freshness timeout (300ms) — response may be stale agent-deck-1.16.35> Warning: output freshness timeout (300ms) — response may be stale agent-deck-1.16.35> Warning: output freshness timeout (300ms) — response may be stale agent-deck-1.16.35> Launch agent re-registration deferred: a remote sweep (pid 12345, started 04:58:31) is still running agent-deck-1.16.35> Imported 2 channel(s) agent-deck-1.16.35> C0AABSF5GKD -> si-bugs/watcher.toml agent-deck-1.16.35> C1BBCDF6HLE -> feat-req/watcher.toml agent-deck-1.16.35> agent-deck-1.16.35> Note: Set the ntfy topic in each watcher.toml (all Slack channels agent-deck-1.16.35> share one ntfy topic from the Cloudflare Worker). agent-deck-1.16.35> Clients written to: /tmp/nix-7mCBE3/TestImportChannels_EndToEnd3494541902/002/clients.json agent-deck-1.16.35> Imported 1 channel(s) agent-deck-1.16.35> C0AABSF5GKD -> si-bugs/watcher.toml agent-deck-1.16.35> agent-deck-1.16.35> Note: Set the ntfy topic in each watcher.toml (all Slack channels agent-deck-1.16.35> share one ntfy topic from the Cloudflare Worker). agent-deck-1.16.35> Clients written to: /tmp/nix-7mCBE3/TestImportChannels_Idempotent3813172127/002/clients.json agent-deck-1.16.35> Imported 1 channel(s) agent-deck-1.16.35> C0AABSF5GKD -> si-bugs/watcher.toml agent-deck-1.16.35> agent-deck-1.16.35> Note: Set the ntfy topic in each watcher.toml (all Slack channels agent-deck-1.16.35> share one ntfy topic from the Cloudflare Worker). agent-deck-1.16.35> Clients written to: /tmp/nix-7mCBE3/TestImportChannels_Idempotent3813172127/002/clients.json agent-deck-1.16.35> Imported 0 channel(s) agent-deck-1.16.35> Clients written to: /tmp/nix-7mCBE3/TestImportChannels_EmptyChannels2983806124/002/clients.json agent-deck-1.16.35> Installed skill: watcher-creator -> /tmp/nix-7mCBE3/TestWatcherInstallSkill756851191/001/xdg-config/agent-deck/skills/pool/watcher-creator agent-deck-1.16.35> Installed skill: watcher-creator -> /tmp/nix-7mCBE3/TestWatcherInstallSkill_DirMode2906059966/001/xdg-config/agent-deck/skills/pool/watcher-creator agent-deck-1.16.35> Created watcher: create-topic-ntfy (type: ntfy) agent-deck-1.16.35> 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.35> Created watcher: create-topic-slack (type: slack) agent-deck-1.16.35> 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.35> Usage: agent-deck watcher [args] agent-deck-1.16.35> agent-deck-1.16.35> Watchers listen for inbound events (webhooks, push notifications, agent-deck-1.16.35> GitHub events, Slack messages) and route them to conductor sessions agent-deck-1.16.35> so your running agents can act on them automatically. agent-deck-1.16.35> agent-deck-1.16.35> Commands: agent-deck-1.16.35> create --name Create a new watcher (types: webhook, ntfy, github, slack) agent-deck-1.16.35> start Mark a watcher as running (run by the profile's watcher engine) agent-deck-1.16.35> stop Mark a watcher as stopped agent-deck-1.16.35> reload [--json] Apply watcher and clients.json changes to the running engine now agent-deck-1.16.35> list [--json] List all watchers with status and event rate agent-deck-1.16.35> status [--json] Show watcher info, recent events and events not delivered yet agent-deck-1.16.35> test Route a synthetic event to verify routing config agent-deck-1.16.35> routes [--json] Show all routing rules from clients.json agent-deck-1.16.35> import Migrate bash issue-watcher channels.json to Go watcher config agent-deck-1.16.35> install-skill Install a skill to ~/config/agent-deck/skills/pool (e.g. watcher-creator) agent-deck-1.16.35> agent-deck-1.16.35> Examples (one per adapter type): agent-deck-1.16.35> agent-deck-1.16.35> # Generic HTTP webhook on 127.0.0.1:9000. Requests must be signed with a agent-deck-1.16.35> # secret: generated and stored in its watcher.toml unless given by agent-deck-1.16.35> # $WEBHOOK_SECRET or --secret-file (chmod 600): agent-deck-1.16.35> agent-deck watcher create webhook --name my-webhook --port 9000 agent-deck-1.16.35> agent-deck-1.16.35> # GitHub repository webhook with HMAC-SHA256 verification agent-deck-1.16.35> # Secret comes from the environment or a chmod-600 file, never a CLI arg: agent-deck-1.16.35> GITHUB_WEBHOOK_SECRET=... agent-deck watcher create github --name gh-alerts agent-deck-1.16.35> agent-deck watcher create github --name gh-alerts --secret-file ~/.gh-webhook-secret agent-deck-1.16.35> agent-deck-1.16.35> # ntfy push-notification topic. On the public https://ntfy.sh anyone who agent-deck-1.16.35> # knows the topic can read and post to it, so use a random topic: agent-deck-1.16.35> agent-deck watcher create ntfy --name phone-alerts --random-topic agent-deck-1.16.35> # or an access-protected topic on your own ntfy server (token from the agent-deck-1.16.35> # environment or a chmod-600 file, never a CLI arg): agent-deck-1.16.35> NTFY_TOKEN=... agent-deck watcher create ntfy --name phone-alerts \ agent-deck-1.16.35> --server https://ntfy.example.com --topic phone-alerts agent-deck-1.16.35> agent-deck-1.16.35> # Slack-bridged via ntfy topic (see skill for Cloudflare Worker setup) agent-deck-1.16.35> agent-deck watcher create slack --name team-slack --random-topic agent-deck-1.16.35> agent-deck-1.16.35> After creating, activate and inspect: agent-deck-1.16.35> agent-deck watcher start agent-deck-1.16.35> agent-deck watcher list # see health + events/hour agent-deck-1.16.35> agent-deck watcher test # fire a synthetic event agent-deck-1.16.35> agent-deck-1.16.35> Routing: edit ~/data/agent-deck/watcher/clients.json to pick which agent-deck-1.16.35> conductor / group receives events. See `agent-deck watcher routes` for agent-deck-1.16.35> the currently-loaded rules across all watchers. agent-deck-1.16.35> agent-deck-1.16.35> Conversational setup (recommended for first-time use): agent-deck-1.16.35> agent-deck watcher install-skill watcher-creator agent-deck-1.16.35> # Then inside Claude Code in an agent-deck session, ask: agent-deck-1.16.35> # "Use the watcher-creator skill to set up a GitHub watcher" agent-deck-1.16.35> agent-deck-1.16.35> Full reference: https://github.com/asheshgoplani/agent-deck#watchers agent-deck-1.16.35> No routing rules configured. agent-deck-1.16.35> No watchers configured. agent-deck-1.16.35> Run 'agent-deck watcher create --name ' to create one. agent-deck-1.16.35> Installed skill: watcher-creator -> /tmp/nix-7mCBE3/TestXDGTask6_WatcherInstallSkillUsesConfiguredPoolPath2477053638/001/xdg-config/agent-deck/skills/pool/watcher-creator agent-deck-1.16.35> FAIL agent-deck-1.16.35> FAIL github.com/asheshgoplani/agent-deck/cmd/agent-deck 320.218s agent-deck-1.16.35> FAIL error: dependency '1w5hbhiygv99n15j75vcc4c6ylqf9csw-agent-deck-1.16.35.drv' failed