agent-deck-1.16.36
checks.x86_64-linux.pkgs-agent-deck
· build #9737
· raw
1bld1: building z90qvm3xacgd8lvkck1mf0jgll85nv00-agent-deck-1.16.36.drv2Using versionCheckHook
unpackPhase
3unpacking source archive /nix/store/3yq2390qf9xp0g09qg6g6m0r6kx4rbmw-source4source root is sourcebuildPhase
5Building subPackage ./cmd/agent-deck6buildPhase completed in 1 minutes 29 secondscheckPhase
72026/11/02 09:18:56 WARN codex_hook_status_unreadable instance=partial path=/tmp/nix-a3b3OI/TestWriteCodexHookStatus_PartialPriorFailsClosed96870826/001/.local/share/agent-deck/hooks/partial.json bytes=108Codex notify hook installed successfully.9Config: /tmp/nix-a3b3OI/TestCodexHooksInstallUninstall579222647/001/.codex/config.toml10Codex notify hook removed successfully.11Codex notify hook upgraded successfully.12Config: /tmp/nix-a3b3OI/TestCodexHooksInstall_UpgradesLegacyTableWithoutMarkers1474934750/001/.codex/config.toml13Codex notify hook upgraded successfully.14Config: /tmp/nix-a3b3OI/TestCodexHooksInstall_UpgradesLegacyMarkerBlock2537775260/001/.codex/config.toml15Codex notify hook upgraded successfully.16Config: /tmp/nix-a3b3OI/TestCodexHooksInstall_ReplacesBlockInPlaceAndKeepsMode3959732442/001/.codex/config.toml17Codex notify hook removed successfully.18Error reading codex config: open /tmp/nix-a3b3OI/TestCodexHooksInstall_UnreadableConfigIsNotOverwritten4164779424/001/.codex/config.toml: permission denied19Error writing codex config: open /tmp/nix-a3b3OI/TestCodexHooksInstall_ReadOnlyConfigIsNotReplaced1195475155/001/.codex/config.toml: permission denied20Codex notify hook upgraded successfully.21Config: /tmp/nix-a3b3OI/TestCodexHooksUninstall_KeepsLineEndingscrlf588841785/001/.codex/config.toml22Codex notify hook removed successfully.23Codex notify hook upgraded successfully.24Config: /tmp/nix-a3b3OI/TestCodexHooksUninstall_KeepsLineEndingsno_final_newline561186878/001/.codex/config.toml25Codex notify hook removed successfully.26Error: the agent-deck notify block in /tmp/nix-a3b3OI/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.work598232864/001/.codex/config.toml sits below a [table], where notify belongs to that table.27Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'.28Error: the agent-deck notify block in /tmp/nix-a3b3OI/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.qa,wes727186351/001/.codex/config.toml sits below a [table], where notify belongs to that table.29Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'.30Error: the agent-deck notify block in /tmp/nix-a3b3OI/TestCodexHooksInstall_BlockBelowTableIsRefused_hooks_._a=b4236158000/001/.codex/config.toml sits below a [table], where notify belongs to that table.31Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'.32agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-a3b3OI/TestEventProfileUsesStorageFallbackForMissingInference737148592/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.33Gemini hooks installed successfully.34Config: /tmp/nix-a3b3OI/TestGeminiHooksInstallUninstall1897217429/001/.gemini/settings.json35Gemini hooks removed successfully.36✓ Reordered group 'Beta': position 1 → 037✓ Reordered group 'Beta': position 1 → 238✓ Reordered group 'Gamma': position 2 → 039✓ Reordered group 'Alpha': position 0 → 040✓ Reordered group 'Gamma': position 2 → 241✓ Reordered group 'Alpha': position 0 → 242agentpaths: resolved agent-deck path under the real home (/tmp/nix-r1Gx27/.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).43WARNING: 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).44WARNING: 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).45agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-a3b3OI/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG1988861599/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.46agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-a3b3OI/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG1988861599/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.47agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-a3b3OI/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG1988861599/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.48--- FAIL: TestIssue2921ClaudeLikeFakeIsGoneWhenItsCleanupReturns (0.00s)49 issue2921_guarded_fake_cleanup_test.go:36: fixture did not start50notify-daemon: binary upgraded (running 1.16.36, on-disk 1.16.36-next); recycling51notify-daemon: binary upgraded (running 1.16.36, on-disk 1.16.36-next); recycling52Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)...53Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)...54Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)...55remote-agent: probe: storage gone56remote-agent: binary upgraded (running v1.16.36); exiting so the controller reconnects57remote-agent: probe produced no listing (Error: database is locked)58remote-agent: probe produced no listing ([])59remote-agent: no input for 300ms, exiting60remote-agent: the host now selects another profile; exiting so the controller reconnects6162═══ Remote: offline (a@offline) ═══63 – Skipped: agent-deck not found on remote or host unreachable6465═══ Remote: offline (a@offline) ═══66 ✗ Failed: stub: no platform67A remote sweep is already running on this controller (pid 26772, started 9:20AM); waiting for it...6869═══ Remote: lab (a@lab) ═══70 – Skipped: sweep already in progress, remote lab is being updated by 267727172═══ Remote: other (a@other) ═══73 ✓ Up to date (v1.16.0)7475═══ Remote: lab (a@lab) ═══76 ✓ Up to date (v1.16.0)7778═══ Remote: other (a@other) ═══79 ✓ Up to date (v1.16.0)80Warning: the session restarted, but its new tmux name could not be recorded: record restart outcome for tmux session "agentdeck_cli-restart-target_cc4476ce": record restart outcome for "3b1c79bb-1793611240": instance row not found81 The session is running; agent-deck may show it as errored until the name is saved.82Handed 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 f61aed3b-1793611272` once the session is back.83Warning: output freshness timeout (300ms) — response may be stale84Warning: output freshness timeout (300ms) — response may be stale85Warning: output freshness timeout (300ms) — response may be stale86Launch agent re-registration deferred: a remote sweep (pid 12345, started 09:21:51) is still running87Imported 2 channel(s)88 C0AABSF5GKD -> si-bugs/watcher.toml89 C1BBCDF6HLE -> feat-req/watcher.toml9091Note: Set the ntfy topic in each watcher.toml (all Slack channels92share one ntfy topic from the Cloudflare Worker).93Clients written to: /tmp/nix-a3b3OI/TestImportChannels_EndToEnd3558489600/002/clients.json94Imported 1 channel(s)95 C0AABSF5GKD -> si-bugs/watcher.toml9697Note: Set the ntfy topic in each watcher.toml (all Slack channels98share one ntfy topic from the Cloudflare Worker).99Clients written to: /tmp/nix-a3b3OI/TestImportChannels_Idempotent1242128203/002/clients.json100Imported 1 channel(s)101 C0AABSF5GKD -> si-bugs/watcher.toml102103Note: Set the ntfy topic in each watcher.toml (all Slack channels104share one ntfy topic from the Cloudflare Worker).105Clients written to: /tmp/nix-a3b3OI/TestImportChannels_Idempotent1242128203/002/clients.json106Imported 0 channel(s)107Clients written to: /tmp/nix-a3b3OI/TestImportChannels_EmptyChannels2621808336/002/clients.json108Installed skill: watcher-creator -> /tmp/nix-a3b3OI/TestWatcherInstallSkill3290981885/001/xdg-config/agent-deck/skills/pool/watcher-creator109Installed skill: watcher-creator -> /tmp/nix-a3b3OI/TestWatcherInstallSkill_DirMode1047025317/001/xdg-config/agent-deck/skills/pool/watcher-creator110Created watcher: create-topic-ntfy (type: ntfy)111Warning: 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 <name> --random-topic); set an access token ($NTFY_TOKEN or --token-file <path> 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]).112Created watcher: create-topic-slack (type: slack)113Warning: 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 <name> --random-topic); set an access token ($NTFY_TOKEN or --token-file <path> 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]).114Usage: agent-deck watcher <command> [args]115116Watchers listen for inbound events (webhooks, push notifications,117GitHub events, Slack messages) and route them to conductor sessions118so your running agents can act on them automatically.119120Commands:121 create <type> --name <name> Create a new watcher (types: webhook, ntfy, github, slack)122 start <name> Mark a watcher as running (run by the profile's watcher engine)123 stop <name> Mark a watcher as stopped124 reload [--json] Apply watcher and clients.json changes to the running engine now125 list [--json] List all watchers with status and event rate126 status <name> [--json] Show watcher info, recent events and events not delivered yet127 test <name> Route a synthetic event to verify routing config128 routes [--json] Show all routing rules from clients.json129 import <path> Migrate bash issue-watcher channels.json to Go watcher config130 install-skill <skill-name> Install a skill to ~/config/agent-deck/skills/pool (e.g. watcher-creator)131132Examples (one per adapter type):133134 # Generic HTTP webhook on 127.0.0.1:9000. Requests must be signed with a135 # secret: generated and stored in its watcher.toml unless given by136 # $WEBHOOK_SECRET or --secret-file (chmod 600):137 agent-deck watcher create webhook --name my-webhook --port 9000138139 # GitHub repository webhook with HMAC-SHA256 verification140 # Secret comes from the environment or a chmod-600 file, never a CLI arg:141 GITHUB_WEBHOOK_SECRET=... agent-deck watcher create github --name gh-alerts142 agent-deck watcher create github --name gh-alerts --secret-file ~/.gh-webhook-secret143144 # ntfy push-notification topic. On the public https://ntfy.sh anyone who145 # knows the topic can read and post to it, so use a random topic:146 agent-deck watcher create ntfy --name phone-alerts --random-topic147 # or an access-protected topic on your own ntfy server (token from the148 # environment or a chmod-600 file, never a CLI arg):149 NTFY_TOKEN=... agent-deck watcher create ntfy --name phone-alerts \150 --server https://ntfy.example.com --topic phone-alerts151152 # Slack-bridged via ntfy topic (see skill for Cloudflare Worker setup)153 agent-deck watcher create slack --name team-slack --random-topic154155After creating, activate and inspect:156 agent-deck watcher start <name>157 agent-deck watcher list # see health + events/hour158 agent-deck watcher test <name> # fire a synthetic event159160Routing: edit ~/data/agent-deck/watcher/clients.json to pick which161conductor / group receives events. See `agent-deck watcher routes` for162the currently-loaded rules across all watchers.163164Conversational setup (recommended for first-time use):165 agent-deck watcher install-skill watcher-creator166 # Then inside Claude Code in an agent-deck session, ask:167 # "Use the watcher-creator skill to set up a GitHub watcher"168169Full reference: https://github.com/asheshgoplani/agent-deck#watchers170No routing rules configured.171No watchers configured.172Run 'agent-deck watcher create <type> --name <name>' to create one.173Installed skill: watcher-creator -> /tmp/nix-a3b3OI/TestXDGTask6_WatcherInstallSkillUsesConfiguredPoolPath1304968627/001/xdg-config/agent-deck/skills/pool/watcher-creator174FAIL175FAIL github.com/asheshgoplani/agent-deck/cmd/agent-deck 222.901s176FAIL