Connect INT-AI tools while keeping your official IDE login

Official IDE login and INT-AI tool authorization are separate identities. Installing model tools does not replace the host's default model or login. Native OAuth hosts can authorize an existing INT-AI account; other supported paths use a dedicated key. The INT-AI Client bridge reads protected configuration for the same Windows user; official login does not grant INT-AI access.

Safe authorization

Native OAuth uses your existing account and owned key. Manual credentials belong only in protected host configuration, not skills, tool arguments or chat.

INT-AI Client state

Previously injected protected credentials may persist. Switching official accounts does not revoke the key; revoke it through INT-AI when needed.

Validation limits

Shared protocol tests and one existing successful session do not validate every device or IDE authentication flow.

Next step

Choose one authentication path in the host guide; avoid same-name mixed OAuth and static-key installations.