Skip to content
Talk to an Engineer Dashboard

Coding agents: Add auth to your AI agents

Let your coding agents guide you into adding auth to your agent to handle OAuth tokens and call tools on behalf of the user

Use AI coding agents like Claude Code, GitHub Copilot CLI, Cursor, and OpenCode to add Scalekit’s Agent Auth to your AI applications. This guide shows you how to configure these agents so they analyze your codebase, apply authentication patterns, and generate production-ready code for handling OAuth tokens and connecting to external services such as Gmail, Calendar, Slack, and Notion, reducing implementation time from hours to minutes while following security best practices.

  1. Add the Scalekit Auth Stack marketplace

    Not yet on Claude Code? Follow the official quickstart guide to install it.

    Register Scalekit’s plugin marketplace to access pre-configured authentication skills. This marketplace provides context-aware prompts and implementation guides that help coding agents generate correct Agent Auth code.

    Start the Claude Code REPL:

    Terminal
    claude

    Then add the marketplace:

    Claude REPL
    /plugin marketplace add scalekit-inc/claude-code-authstack

    When the marketplace registers successfully, you’ll see confirmation output:

    Terminal
    /plugin marketplace add scalekit-inc/claude-code-authstack
    Successfully added marketplace: scalekit-auth-stack

    The marketplace provides specialized authentication plugins that understand Agent Auth patterns and OAuth 2.0 security requirements. These plugins guide the coding agent to generate implementation code that matches your project structure.

    To remove the Scalekit Auth Stack marketplace, use the uninstall command:

    Claude REPL
    /plugin marketplace remove scalekit-auth-stack
  2. Enable authentication plugins

    Select which authentication capabilities to activate in your development environment. Each plugin provides specific skills that the coding agent uses to generate authentication code.

    Directly install the specific plugin:

    Claude REPL
    /plugin install agent-auth@scalekit-auth-stack
    Alternative: Enable authentication plugins via plugin wizard

    Run the plugin wizard to browse and enable available plugins:

    Claude REPL
    /plugins

    Navigate through the visual interface to enable the Agent Auth plugin.

  3. Generate authentication implementation

    Use a structured prompt to direct the coding agent. A well-formed prompt ensures the agent generates complete, production-ready Agent Auth code that includes all required security components.

    Copy the following prompt into your coding agent:

    Authentication implementation prompt
    Guide me through configuring the installed Scalekit marketplace plugin to handle agent authentication for Gmail. Provide the code to trigger the auth flow, retrieve the secure user token, and then use that authenticated session to fetch and list the last 5 unread emails. Add logging to verify the flow.

    When you submit this prompt, Claude Code loads the Agent Auth skill from the marketplace -> analyzes your existing application structure -> generates Scalekit client initialization -> creates connected account management functions -> implements OAuth authorization link generation -> adds token fetching and refresh logic.

  4. Verify just-in-time implementation

    After the coding agent completes, verify that all authentication components are properly configured:

    Check generated files:

    • Scalekit client initialization with credentials. You may need to set up a .env file with your Scalekit API credentials.
    • Connected account management functions
    • Authorization link generation
    • Token fetching and storage
    • Error handling for expired tokens

    The authorization flow should redirect users to the service’s consent page, where they grant permissions. Your application should then be able to fetch OAuth tokens and execute actions on behalf of the authenticated user.

When you connect, the agent authenticates users through the OAuth 2.0 flow you configured. Verify that protected resources require valid access tokens and that the agent can successfully execute actions on behalf of authenticated users.