agent-deck-1.16.35
checks.x86_64-linux.pkgs-agent-deck
· build #9652
· raw
1bld1: building 1w5hbhiygv99n15j75vcc4c6ylqf9csw-agent-deck-1.16.35.drv2Using versionCheckHook
unpackPhase
3unpacking source archive /nix/store/k1s5z7sm1gl0gavln4pl53w4fi2k0yvk-source4source root is sourcebuildPhase
5Building subPackage ./cmd/agent-deckcheckPhase
62026/10/31 21:11:35 WARN codex_hook_status_unreadable instance=partial path=/tmp/nix-XYzbVp/TestWriteCodexHookStatus_PartialPriorFailsClosed3365897924/001/.local/share/agent-deck/hooks/partial.json bytes=107Codex notify hook installed successfully.8Config: /tmp/nix-XYzbVp/TestCodexHooksInstallUninstall4159177266/001/.codex/config.toml9Codex notify hook removed successfully.10Codex notify hook upgraded successfully.11Config: /tmp/nix-XYzbVp/TestCodexHooksInstall_UpgradesLegacyTableWithoutMarkers1786916413/001/.codex/config.toml12Codex notify hook upgraded successfully.13Config: /tmp/nix-XYzbVp/TestCodexHooksInstall_UpgradesLegacyMarkerBlock2597310970/001/.codex/config.toml14Codex notify hook upgraded successfully.15Config: /tmp/nix-XYzbVp/TestCodexHooksInstall_ReplacesBlockInPlaceAndKeepsMode1498069583/001/.codex/config.toml16Codex notify hook removed successfully.17Error reading codex config: open /tmp/nix-XYzbVp/TestCodexHooksInstall_UnreadableConfigIsNotOverwritten2371187649/001/.codex/config.toml: permission denied18Error writing codex config: open /tmp/nix-XYzbVp/TestCodexHooksInstall_ReadOnlyConfigIsNotReplaced3173737398/001/.codex/config.toml: permission denied19Codex notify hook upgraded successfully.20Config: /tmp/nix-XYzbVp/TestCodexHooksUninstall_KeepsLineEndingscrlf3404447309/001/.codex/config.toml21Codex notify hook removed successfully.22Codex notify hook upgraded successfully.23Config: /tmp/nix-XYzbVp/TestCodexHooksUninstall_KeepsLineEndingsno_final_newline2209301373/001/.codex/config.toml24Codex notify hook removed successfully.25Error: the agent-deck notify block in /tmp/nix-XYzbVp/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.work3709016864/001/.codex/config.toml sits below a [table], where notify belongs to that table.26Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'.27Error: the agent-deck notify block in /tmp/nix-XYzbVp/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.qa,wes3022140012/001/.codex/config.toml sits below a [table], where notify belongs to that table.28Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'.29Error: the agent-deck notify block in /tmp/nix-XYzbVp/TestCodexHooksInstall_BlockBelowTableIsRefused_hooks_._a=b2154199076/001/.codex/config.toml sits below a [table], where notify belongs to that table.30Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'.31agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-XYzbVp/TestEventProfileUsesStorageFallbackForMissingInference2045323226/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.32Gemini hooks installed successfully.33Config: /tmp/nix-XYzbVp/TestGeminiHooksInstallUninstall1866440173/001/.gemini/settings.json34Gemini hooks removed successfully.35✓ Reordered group 'Beta': position 1 → 036✓ Reordered group 'Beta': position 1 → 237✓ Reordered group 'Gamma': position 2 → 038✓ Reordered group 'Alpha': position 0 → 039✓ Reordered group 'Gamma': position 2 → 240✓ Reordered group 'Alpha': position 0 → 241agentpaths: resolved agent-deck path under the real home (/tmp/nix-zUWWCT/.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).42WARNING: 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).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).44agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-XYzbVp/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG1949300629/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.45agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-XYzbVp/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG1949300629/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.46agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-XYzbVp/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG1949300629/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.47--- FAIL: TestIssue2921ClaudeLikeFakeIsGoneWhenItsCleanupReturns (0.00s)48 issue2921_guarded_fake_cleanup_test.go:33: fixture did not start49notify-daemon: binary upgraded (running 1.16.35, on-disk 1.16.35-next); recycling50notify-daemon: binary upgraded (running 1.16.35, on-disk 1.16.35-next); recycling51Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)...52Waiting 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)...54remote-agent: probe: storage gone55remote-agent: binary upgraded (running v1.16.35); exiting so the controller reconnects56remote-agent: probe produced no listing (Error: database is locked)57remote-agent: probe produced no listing ([])58remote-agent: no input for 300ms, exiting59remote-agent: the host now selects another profile; exiting so the controller reconnects6061═══ Remote: offline (a@offline) ═══62 – Skipped: agent-deck not found on remote or host unreachable6364═══ Remote: offline (a@offline) ═══65 ✗ Failed: stub: no platform66A remote sweep is already running on this controller (pid 25651, started 9:14PM); waiting for it...6768═══ Remote: lab (a@lab) ═══69 – Skipped: sweep already in progress, remote lab is being updated by 256517071═══ Remote: other (a@other) ═══72 ✓ Up to date (v1.16.0)7374═══ Remote: lab (a@lab) ═══75 ✓ Up to date (v1.16.0)7677═══ Remote: other (a@other) ═══78 ✓ Up to date (v1.16.0)79--- FAIL: TestRemoteFollowEndsOnStdinClose (16.57s)80 --- FAIL: TestRemoteFollowEndsOnStdinClose/recall (15.33s)81 remote_read_cli_test.go:207: follow kept running after stdin closed; stderr: 82Warning: the session restarted, but its new tmux name could not be recorded: record restart outcome for tmux session "agentdeck_cli-restart-target_ec0ea91e": record restart outcome for "a701f2ed-1793481276": instance row not found83 The session is running; agent-deck may show it as errored until the name is saved.84Handed 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 b141a22c-1793481305` once the session is back.85Warning: output freshness timeout (300ms) — response may be stale86Warning: output freshness timeout (300ms) — response may be stale87Warning: output freshness timeout (300ms) — response may be stale88Launch agent re-registration deferred: a remote sweep (pid 12345, started 21:15:59) is still running89Imported 2 channel(s)90 C0AABSF5GKD -> si-bugs/watcher.toml91 C1BBCDF6HLE -> feat-req/watcher.toml9293Note: Set the ntfy topic in each watcher.toml (all Slack channels94share one ntfy topic from the Cloudflare Worker).95Clients written to: /tmp/nix-XYzbVp/TestImportChannels_EndToEnd2011210033/002/clients.json96Imported 1 channel(s)97 C0AABSF5GKD -> si-bugs/watcher.toml9899Note: Set the ntfy topic in each watcher.toml (all Slack channels100share one ntfy topic from the Cloudflare Worker).101Clients written to: /tmp/nix-XYzbVp/TestImportChannels_Idempotent3418362130/002/clients.json102Imported 1 channel(s)103 C0AABSF5GKD -> si-bugs/watcher.toml104105Note: Set the ntfy topic in each watcher.toml (all Slack channels106share one ntfy topic from the Cloudflare Worker).107Clients written to: /tmp/nix-XYzbVp/TestImportChannels_Idempotent3418362130/002/clients.json108Imported 0 channel(s)109Clients written to: /tmp/nix-XYzbVp/TestImportChannels_EmptyChannels1831446909/002/clients.json110Installed skill: watcher-creator -> /tmp/nix-XYzbVp/TestWatcherInstallSkill427772344/001/xdg-config/agent-deck/skills/pool/watcher-creator111Installed skill: watcher-creator -> /tmp/nix-XYzbVp/TestWatcherInstallSkill_DirMode3835837447/001/xdg-config/agent-deck/skills/pool/watcher-creator112Created watcher: create-topic-ntfy (type: ntfy)113Warning: 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]).114Created watcher: create-topic-slack (type: slack)115Warning: 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]).116Usage: agent-deck watcher <command> [args]117118Watchers listen for inbound events (webhooks, push notifications,119GitHub events, Slack messages) and route them to conductor sessions120so your running agents can act on them automatically.121122Commands:123 create <type> --name <name> Create a new watcher (types: webhook, ntfy, github, slack)124 start <name> Mark a watcher as running (run by the profile's watcher engine)125 stop <name> Mark a watcher as stopped126 reload [--json] Apply watcher and clients.json changes to the running engine now127 list [--json] List all watchers with status and event rate128 status <name> [--json] Show watcher info, recent events and events not delivered yet129 test <name> Route a synthetic event to verify routing config130 routes [--json] Show all routing rules from clients.json131 import <path> Migrate bash issue-watcher channels.json to Go watcher config132 install-skill <skill-name> Install a skill to ~/config/agent-deck/skills/pool (e.g. watcher-creator)133134Examples (one per adapter type):135136 # Generic HTTP webhook on 127.0.0.1:9000. Requests must be signed with a137 # secret: generated and stored in its watcher.toml unless given by138 # $WEBHOOK_SECRET or --secret-file (chmod 600):139 agent-deck watcher create webhook --name my-webhook --port 9000140141 # GitHub repository webhook with HMAC-SHA256 verification142 # Secret comes from the environment or a chmod-600 file, never a CLI arg:143 GITHUB_WEBHOOK_SECRET=... agent-deck watcher create github --name gh-alerts144 agent-deck watcher create github --name gh-alerts --secret-file ~/.gh-webhook-secret145146 # ntfy push-notification topic. On the public https://ntfy.sh anyone who147 # knows the topic can read and post to it, so use a random topic:148 agent-deck watcher create ntfy --name phone-alerts --random-topic149 # or an access-protected topic on your own ntfy server (token from the150 # environment or a chmod-600 file, never a CLI arg):151 NTFY_TOKEN=... agent-deck watcher create ntfy --name phone-alerts \152 --server https://ntfy.example.com --topic phone-alerts153154 # Slack-bridged via ntfy topic (see skill for Cloudflare Worker setup)155 agent-deck watcher create slack --name team-slack --random-topic156157After creating, activate and inspect:158 agent-deck watcher start <name>159 agent-deck watcher list # see health + events/hour160 agent-deck watcher test <name> # fire a synthetic event161162Routing: edit ~/data/agent-deck/watcher/clients.json to pick which163conductor / group receives events. See `agent-deck watcher routes` for164the currently-loaded rules across all watchers.165166Conversational setup (recommended for first-time use):167 agent-deck watcher install-skill watcher-creator168 # Then inside Claude Code in an agent-deck session, ask:169 # "Use the watcher-creator skill to set up a GitHub watcher"170171Full reference: https://github.com/asheshgoplani/agent-deck#watchers172No routing rules configured.173No watchers configured.174Run 'agent-deck watcher create <type> --name <name>' to create one.175Installed skill: watcher-creator -> /tmp/nix-XYzbVp/TestXDGTask6_WatcherInstallSkillUsesConfiguredPoolPath2352962728/001/xdg-config/agent-deck/skills/pool/watcher-creator176FAIL177FAIL github.com/asheshgoplani/agent-deck/cmd/agent-deck 320.018s178FAIL