Short answer: No. - The registration flow sets an Ory session cookie on success only if the “session” after-hook is enabled; otherwise it just returns/redirects with the created identity. It does not issue a JWT by default (cookies contain the session, not a JWT) ([Successful registration](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#successful-registration)). - For browser flows, success results in a 303 redirect; with the session hook enabled, a Set-Cookie header with the Ory session cookie is included. No JWT is placed in cookies or headers by the registration flow itself ([Successful registration – server-side](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#successful-registration), [Client-side browser clients](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#client-side-browser-clients)). - For API/native clients, with the session hook enabled, the response JSON includes session and session_token; still no JWT is issued automatically ([API clients](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#api-clients), [Actions: Sign in after registration](https://www.ory.sh/docs/actions/session)). If you need a JWT, use a tokenizer/JWT template or a proxy that converts sessions to JWTs (e.g., Ory Proxy or session-to-JWT configuration). The sources above do not show JWTs being set by the registration flow itself.