Validated SDK discovery
While gjc runs, AgentPeek finds repository-local.gjc/state/sdk/<sessionId>.json discovery files. It accepts only the stable v1 discovery-file shape used by the current SDK v3 transport, a live PID, a matching file name, and a loopback WebSocket endpoint. Tokens are validated in memory and never logged or persisted.
Selected-session Direct Chat
SDK discovery replaces the temporary process row with a durable Gajae session ID and workspace. AgentPeek launches gjc acp, loads that exact session, and relays native allow-once, allow-always, and reject permission options. Gajae exposes no separate AgentPeek transcript or usage source, so those fields remain absent.
Questions
AgentPeek detects gjc and upgrades the process row when a valid local SDK discovery file appears.
No. The token is validated in memory and is never logged or written to AgentPeek storage.
Yes. Direct Chat loads the selected session through the current gjc acp transport and relays native permissions.