npx workos: コードベースに直接認証を書き込むAIエージェント

Integrate AuthKit with one command, manage resources, provision environments, and equip your coding agents — all from the WorkOS CLI.

はじめに

The WorkOS CLI is a comprehensive tool for integrating and managing WorkOS from the terminal. Its headline feature is the AI Installer – run one command and it handles framework detection, SDK installation, route creation, environment setup, and build validation. Beyond the installer, the CLI also manages resources, provisions environments, and equips your coding agents with WorkOS knowledge.

JavaScript

AI Installer

Run one command, the CLI handles the rest. Your app goes from zero auth to full AuthKit integration in about two minutes.

What the installer handles

The installer takes care of everything you would normally do manually:

• Detects your framework – Identifies your framework and version from your project’s dependencies and file structure

• Authenticates your account – Opens your browser for secure WorkOS sign-in

• Configures your dashboard – Sets redirect URIs, CORS origins, and homepage URL automatically

• Installs the right SDK – Adds the correct AuthKit package for your framework

• Analyzes your project – Reads your project structure to understand routing, existing middleware, and configuration

• Creates routes and middleware – Writes OAuth callback routes, auth middleware/proxy, and provider wrappers

• Sets up environment variables – Writes API keys and configuration to .env.local

• Validates the integration – Runs your build to verify everything compiles without errors

The installer understands framework-specific nuances – like Next.js App Router vs Pages Router, Vite vs Create React App, and React Router nuances – and generates the appropriate code for your setup. If you have existing middleware or configuration, it composes with it rather than replacing it.

Supported frameworks

How the installer works

The CLI uses an AI agent with restricted permissions to integrate AuthKit into your project:

• Local analysis – The agent reads your project files locally to detect frameworks and understand your project structure.

• Restricted execution – The agent can only run a limited set of commands: package installation, builds, type-checking, and formatting. It cannot run arbitrary shell commands.

• File modifications – The agent creates and edits files in your project to set up the AuthKit integration. Use git diff after installation to review every change.

• Dashboard configuration – The CLI configures your WorkOS dashboard settings (redirect URIs, CORS) using your authenticated session.

Install options

Coding agent skills

Install WorkOS knowledge directly into your AI coding agent so it understands AuthKit when helping you write code. Skills give agents context about WorkOS APIs, SDKs, and integration patterns – so they produce correct integration code without you having to explain WorkOS concepts.

Supported agents:

Use workos skills list to see available and installed skills, and workos skills uninstall to remove them.

Manage resources

The CLI provides full CRUD operations for WorkOS resources directly from the terminal – organizations, users, roles, permissions, connections, directories, webhooks, vault secrets, feature flags, and more.

All resource commands support --json for scripting and CI pipelines. In non-TTY environments (pipes, CI runners, coding agents), JSON output is enabled automatically.

Workflow commands

Compound commands that compose multiple API calls for common tasks.

Declarative provisioning with seed

Define your permissions, roles, organizations, and config in a YAML file and provision them in one command. The CLI tracks state so you can tear everything down cleanly with --clean.

workos-seed.yaml

Other workflow commands

Environments

Manage multiple WorkOS environments, switch between them, and authenticate – all from the terminal.

Use workos env switch to change environments and workos env add to configure new ones. Run workos doctor to diagnose integration issues in the current project – it checks your SDK version, environment configuration, connectivity, dashboard settings, and auth patterns.

Troubleshooting

The installer didn’t detect my framework

Use the --integration flag to specify your framework manually:

Build validation failed

Run the installer with --debug for detailed output. Make sure your project builds cleanly before running the installer – pre-existing build errors will cause validation to fail.

I want to see what changed