Skip to content

Self-hosted: firecrawl --status and config --api-url treat setup as unauthenticated #53

Open

Description

@jhsong233

Problem

For self-hosted users, CLI still behaves like cloud auth is required.

Repro

  1. Ensure credentials file does not exist (first-time setup):
    • macOS: ~/Library/Application Support/firecrawl-cli/credentials.json
  2. Run:
firecrawl config --api-url http://localhost:3002
  1. CLI enters cloud login flow (1/2) and empty key fails.
  2. credentials.json is not auto-created with apiUrl during this first-time self-hosted setup path.

Then:

firecrawl --status

shows:

  • Not authenticated
  • Run 'firecrawl login' to authenticate

Expected

  • config --api-url <self-host-url> should save URL without forcing login.
  • If credentials.json does not exist, config should create it and persist apiUrl.
  • --status should show self-hosted configured/ready state (not unauthenticated).
  • No Authorization: Bearer undefined header when self-hosted has no API key.

Note

Under the same self-hosted setup, firecrawl credit-usage can succeed, while firecrawl --status still reports unauthenticated.

Impact

Firecrawl skill uses --status to detect CLI readiness; this blocks self-hosted skill usage.

Activity

  1. added a commit that references this issue on Jun 3, 2026
    7799c04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions