AINIQ for Claude

    Give Claude continuity, priorities, and memory.

    This connect flow keeps Claude closer to your actual working style instead of starting fresh from a single thread.

    Recommended: Hosted sign-in
    Same account, billing, and revocation

    1. Sign in

    Sign in first so the connection stays tied to your AINIQ account and can be managed later from one place.

    2. Hosted sign-in

    Recommended path: hosted sign-in.

    3. Use with Claude

    Use pairing only when the client cannot complete the normal OAuth flow.

    Why connect

    Carry one AINIQ context layer across Claude sessions.
    Start with the hosted sign-in path.
    Keep manual credentials as an advanced fallback instead of the default.

    Channel guide

    Recommended path: hosted sign-in.

    Use pairing only when the client cannot complete the normal OAuth flow.

    API keys stay available for legacy or script-only hosts.

    Sign in to connect

    Your setup state will resume after login

    This connect URL preserves the channel, recommendation trigger, and campaign context. After sign-in, you will land back on the same guided setup page instead of a generic settings dead end.