agent-deck-1.16.36
checks.x86_64-linux.pkgs-agent-deck
· build #9815
· 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-deckcheckPhase
62026/11/03 00:48:00 WARN codex_hook_status_unreadable instance=partial path=/tmp/nix-MhjS7a/TestWriteCodexHookStatus_PartialPriorFailsClosed1850123007/001/.local/share/agent-deck/hooks/partial.json bytes=107Codex notify hook installed successfully.8Config: /tmp/nix-MhjS7a/TestCodexHooksInstallUninstall3124719687/001/.codex/config.toml9Codex notify hook removed successfully.10Codex notify hook upgraded successfully.11Config: /tmp/nix-MhjS7a/TestCodexHooksInstall_UpgradesLegacyTableWithoutMarkers226411326/001/.codex/config.toml12Codex notify hook upgraded successfully.13Config: /tmp/nix-MhjS7a/TestCodexHooksInstall_UpgradesLegacyMarkerBlock3977537062/001/.codex/config.toml14Codex notify hook upgraded successfully.15Config: /tmp/nix-MhjS7a/TestCodexHooksInstall_ReplacesBlockInPlaceAndKeepsMode1718304449/001/.codex/config.toml16Codex notify hook removed successfully.17Error reading codex config: open /tmp/nix-MhjS7a/TestCodexHooksInstall_UnreadableConfigIsNotOverwritten234090709/001/.codex/config.toml: permission denied18Error writing codex config: open /tmp/nix-MhjS7a/TestCodexHooksInstall_ReadOnlyConfigIsNotReplaced4116764307/001/.codex/config.toml: permission denied19Codex notify hook upgraded successfully.20Config: /tmp/nix-MhjS7a/TestCodexHooksUninstall_KeepsLineEndingsno_final_newline3839911889/001/.codex/config.toml21Codex notify hook removed successfully.22Codex notify hook upgraded successfully.23Config: /tmp/nix-MhjS7a/TestCodexHooksUninstall_KeepsLineEndingscrlf2755383969/001/.codex/config.toml24Codex notify hook removed successfully.25Error: the agent-deck notify block in /tmp/nix-MhjS7a/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.work688506798/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-MhjS7a/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.qa,wes54249705/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-MhjS7a/TestCodexHooksInstall_BlockBelowTableIsRefused_hooks_._a=b799263172/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-MhjS7a/TestEventProfileUsesStorageFallbackForMissingInference535654940/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-MhjS7a/TestGeminiHooksInstallUninstall775891517/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-WA4ywk/.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-MhjS7a/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG2482132329/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-MhjS7a/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG2482132329/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-MhjS7a/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG2482132329/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:36: fixture did not start49notify-daemon: binary upgraded (running 1.16.36, on-disk 1.16.36-next); recycling50notify-daemon: binary upgraded (running 1.16.36, on-disk 1.16.36-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.36); 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 33362, started 12:49AM); waiting for it...6768═══ Remote: lab (a@lab) ═══69 – Skipped: sweep already in progress, remote lab is being updated by 333627071═══ 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)79Warning: the session restarted, but its new tmux name could not be recorded: record restart outcome for tmux session "agentdeck_cli-restart-target_1e4db99f": record restart outcome for "5d3a98f5-1793666953": instance row not found80 The session is running; agent-deck may show it as errored until the name is saved.81Handed 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 6499297e-1793666979` once the session is back.82Warning: output freshness timeout (300ms) — response may be stale83Warning: output freshness timeout (300ms) — response may be stale84Warning: output freshness timeout (300ms) — response may be stale85Launch agent re-registration deferred: a remote sweep (pid 12345, started 00:50:16) is still running86Imported 2 channel(s)87 C0AABSF5GKD -> si-bugs/watcher.toml88 C1BBCDF6HLE -> feat-req/watcher.toml8990Note: Set the ntfy topic in each watcher.toml (all Slack channels91share one ntfy topic from the Cloudflare Worker).92Clients written to: /tmp/nix-MhjS7a/TestImportChannels_EndToEnd2910660900/002/clients.json93Imported 1 channel(s)94 C0AABSF5GKD -> si-bugs/watcher.toml9596Note: Set the ntfy topic in each watcher.toml (all Slack channels97share one ntfy topic from the Cloudflare Worker).98Clients written to: /tmp/nix-MhjS7a/TestImportChannels_Idempotent1428531118/002/clients.json99Imported 1 channel(s)100 C0AABSF5GKD -> si-bugs/watcher.toml101102Note: Set the ntfy topic in each watcher.toml (all Slack channels103share one ntfy topic from the Cloudflare Worker).104Clients written to: /tmp/nix-MhjS7a/TestImportChannels_Idempotent1428531118/002/clients.json105Imported 0 channel(s)106Clients written to: /tmp/nix-MhjS7a/TestImportChannels_EmptyChannels2662568606/002/clients.json107Installed skill: watcher-creator -> /tmp/nix-MhjS7a/TestWatcherInstallSkill1770954527/001/xdg-config/agent-deck/skills/pool/watcher-creator108Installed skill: watcher-creator -> /tmp/nix-MhjS7a/TestWatcherInstallSkill_DirMode4067096685/001/xdg-config/agent-deck/skills/pool/watcher-creator109Created watcher: create-topic-ntfy (type: ntfy)110Warning: 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]).111Created watcher: create-topic-slack (type: slack)112Warning: 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]).113Usage: agent-deck watcher <command> [args]114115Watchers listen for inbound events (webhooks, push notifications,116GitHub events, Slack messages) and route them to conductor sessions117so your running agents can act on them automatically.118119Commands:120 create <type> --name <name> Create a new watcher (types: webhook, ntfy, github, slack)121 start <name> Mark a watcher as running (run by the profile's watcher engine)122 stop <name> Mark a watcher as stopped123 reload [--json] Apply watcher and clients.json changes to the running engine now124 list [--json] List all watchers with status and event rate125 status <name> [--json] Show watcher info, recent events and events not delivered yet126 test <name> Route a synthetic event to verify routing config127 routes [--json] Show all routing rules from clients.json128 import <path> Migrate bash issue-watcher channels.json to Go watcher config129 install-skill <skill-name> Install a skill to ~/config/agent-deck/skills/pool (e.g. watcher-creator)130131Examples (one per adapter type):132133 # Generic HTTP webhook on 127.0.0.1:9000. Requests must be signed with a134 # secret: generated and stored in its watcher.toml unless given by135 # $WEBHOOK_SECRET or --secret-file (chmod 600):136 agent-deck watcher create webhook --name my-webhook --port 9000137138 # GitHub repository webhook with HMAC-SHA256 verification139 # Secret comes from the environment or a chmod-600 file, never a CLI arg:140 GITHUB_WEBHOOK_SECRET=... agent-deck watcher create github --name gh-alerts141 agent-deck watcher create github --name gh-alerts --secret-file ~/.gh-webhook-secret142143 # ntfy push-notification topic. On the public https://ntfy.sh anyone who144 # knows the topic can read and post to it, so use a random topic:145 agent-deck watcher create ntfy --name phone-alerts --random-topic146 # or an access-protected topic on your own ntfy server (token from the147 # environment or a chmod-600 file, never a CLI arg):148 NTFY_TOKEN=... agent-deck watcher create ntfy --name phone-alerts \149 --server https://ntfy.example.com --topic phone-alerts150151 # Slack-bridged via ntfy topic (see skill for Cloudflare Worker setup)152 agent-deck watcher create slack --name team-slack --random-topic153154After creating, activate and inspect:155 agent-deck watcher start <name>156 agent-deck watcher list # see health + events/hour157 agent-deck watcher test <name> # fire a synthetic event158159Routing: edit ~/data/agent-deck/watcher/clients.json to pick which160conductor / group receives events. See `agent-deck watcher routes` for161the currently-loaded rules across all watchers.162163Conversational setup (recommended for first-time use):164 agent-deck watcher install-skill watcher-creator165 # Then inside Claude Code in an agent-deck session, ask:166 # "Use the watcher-creator skill to set up a GitHub watcher"167168Full reference: https://github.com/asheshgoplani/agent-deck#watchers169No routing rules configured.170No watchers configured.171Run 'agent-deck watcher create <type> --name <name>' to create one.172Installed skill: watcher-creator -> /tmp/nix-MhjS7a/TestXDGTask6_WatcherInstallSkillUsesConfiguredPoolPath1983445248/001/xdg-config/agent-deck/skills/pool/watcher-creator173FAIL174FAIL github.com/asheshgoplani/agent-deck/cmd/agent-deck 163.553s175FAIL