Recognized SDK coding agents

Copilot sessions appear as GitHub Copilot CLI in session views and new alerts. Other registered SDK agents also appear by name. Older sessions gain that name when their adapter ID is still retained. Gateway hook sessions other than Aperture show Gateway, Watcher SDK or Hooks API as their source.

What's new?

• Agent filters match the reported name before counting or paginating results.
• Other excludes sessions recognized as another coding agent.
• A non-Aperture gateway hook session's source follows its conversation ID. Gateway (watcher-gateway) covers gateway example prefixes such as litellm:. Watcher SDK (watcher-sdk) covers registered SDK agent prefixes such as github-copilot-cli:. Hooks API (watcher-hook) covers any other ID or none, including your own agent sending gateway hooks through the Watcher SDK with its own conversation ID.
• Recording, stored identities, ownership and tool rules remain unchanged.

Required upgrade steps

For self-hosted deployments and Watcher Cloud, update saved searches or API queries that use Other to find SDK sessions. Select the agent by name instead; for Copilot, use agent_platforms=["github_copilot_cli"]. Clients must accept additional strings in session responses. Verify that a known Copilot session appears in that filter and no longer appears in Other.

If a saved Analyzer Source filter or API query uses watcher-hook to find every non-Aperture gateway hook session, add watcher-gateway and watcher-sdk, for example sources=["watcher-gateway", "watcher-sdk", "watcher-hook"]. Then check that a known LiteLLM or Copilot session still appears.

Follow the server update procedure for self-hosted deployments. No hook reinstall or new sign-in is needed. Rolling back the server restores its previous reporting behavior without changing recorded sessions. Exports and alerts already delivered elsewhere stay as they were.