agentconnect: Skill for Claude Code

Debug AgentConnect

Work from evidence, in a fixed order, and say what each conclusion rests on. Most hours lost in past investigations were not spent on hard problems. They went to four mistakes: reading the wrong environment, reading main while the daemon ran an older release, searching the place one happens to know instead of the place the artifact must be, and treating one indirect signal as proof. The order below forces those checks before anything deeper.

0. Establish the coordinates

Take the environment coordinates from local instructions or memory, never from names or guesses: which console and Control Plane is which environment; where each self-hosted daemon runs, with its root, service form, and log source; the cluster and namespace of pool daemons; the local time zone the console renders in; and any read-only restrictions on production. A tool connector or console login bound to one environment tells you nothing about another. If the coordinates are not recorded, ask for the environment and the daemon before reading anything.

Write down, before touching data:

• the environment and the ids in the report — session, agent, daemon, hook run, check run;
• the time window in UTC (database timestamps are UTC; the console may render a local zone);
• which platform the session belongs to (session_meta.platform, hookKind), because that decides the ingress path.

1. Pin the version

Self-hosted daemons lag the release train by one or more release candidates; pool members follow it. Behavior that the current code cannot produce is usually old code, and a Control Plane table is written by daemons of several versions at once, so one odd row proves nothing about main.

Read the writer's version first (daemon: name, agentVersion, lastSeenAt, host), then read the code at that tag:

git show v<agentVersion>:packages/daemon/src/<file>

To test what main does, use an agent placed on the pool, not a self-hosted daemon. When a symptom's timestamp is within a minute of a release, read the deployment's rollout times before reading code: a Control Plane rollout leaves a window where daemons are reconnecting.