[Feature]: Support base44 login --api-key (or similar)

[kfirstri]

Problem Statement

We want to be able to login using the user base44 api key, mainly for CI purposes

Proposed Solution

Let the user run a login with the api key in CI envs

Alternatives Considered

No response

Usage Examples

No response

Additional Context

No response

[kfirstri]

@claude suggest a solution - add a new flag to the login command, and use the recieved key to make api call to get user info.. and then save it normally like other auth

[claude]

Claude finished @kfirstri's task in 6m 41s —— View job • claude/issue-277-20260219-1334 • Create PR ➔

---

Implementation Complete

• Explore the codebase - read login command and auth code
• Update schema.ts - make refreshToken optional, add isApiKey?: boolean field
• Update config.ts - skip token refresh for API key auth
• Update login-flow.ts - add loginWithApiKey() function
• Update login.ts - add --api-key <key> flag
• Run typecheck + lint (clean)
• Commit and push

Changes Made

src/core/auth/schema.ts — refreshToken made optional; isApiKey?: boolean added to AuthDataSchema. API key auth has no refresh token.

src/core/auth/config.ts — isTokenExpired() returns false for API key auth (keys don't expire). refreshAndSaveTokens() returns the API key directly when isApiKey is true, avoiding any refresh attempt.

src/cli/commands/auth/login-flow.ts — New loginWithApiKey(apiKey) function: calls getUserInfo(apiKey) to validate the key and fetch the user's email/name, then saves auth with isApiKey: true.

src/cli/commands/auth/login.ts — Added --api-key <key> option. When provided, delegates to loginWithApiKey(); otherwise falls through to the existing device code flow.

Usage

# Interactive device code flow (unchanged)
base44 login

# CI/CD — non-interactive, uses API key
base44 login --api-key <your-api-key>