Fetch the current session identity token for a captain thread. The caller must have access to the project that owns the thread. The same token is also written inside the captain VM to /etc/capy/session-token with permissions 0600, so code running inside the VM can read it locally. A 410 response means the session has already ended. A 422 response with code session_not_ready means the token has not been minted yet during initial bootstrap; retry with backoff.
Documentation Index
Fetch the complete documentation index at: https://docs.capy.ai/llms.txt
Use this file to discover all available pages before exploring further.
API token (capy_xxxx). Generate at capy.ai/settings/tokens
Thread jam ID.
Success
Opaque session identity token. This value is a JWT and is typically 700-1000 bytes long.
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$