For developers

Security and production launch

A practical checklist before enabling an external application for real users.

Updated: August 7, 2026

Keys and tokens

Generate the context JWT only on the external product’s server.
Store the private key and tool credentials in the standard secret store.
Publish only the public PEM or JWKS.
Use a unique jti and a lifetime of no more than five minutes.
Do not pass the external product’s user JWT instead of a dedicated context token.

Send only the information required to support the current scenario.
Use an opaque subject instead of an email address or phone number when the agent does not need them.
Mark PII and internal fields as sensitive or hidden.
Do not include passwords, OTPs, API keys, tokens, or raw logs.

1Test desktop and a 390×844 screen on the real Origin.
2Create a session with valid context and replace it after the selected object changes.
3Confirm that reusing a jti in another session is rejected.
4Test invalid and expired JWTs: chat must continue working.
5Run a real read-only tool call and verify the server-side subject.
6For a draft action, confirm that the endpoint is not called without confirmation and that a retry does not create a second operation.
7Confirm that the operator sees only allowed fields and a safe audit trail.
8Test handoff and the operator’s reply in the original channel.