SetupNeeds attention

Deployment truth surface

DashClaw can partially verify this instance, but some follow-up is required before normal use is trustworthy.

Checked at Jun 10, 2026, 7:00 AM

Readiness
needs_attention

Overall state projected from database, config, auth, deploy, and SDK checks.

Live verification
Pending

A setup page can be healthy without live proof. Proof becomes attached after a successful validation flow.

Proof artifact
Ready

Use /api/setup/status for machine checks and this page for operator truth.

Core Readiness

DashClaw responded to the verification request.

pass

Checked: The /setup page rendered and the server runtime reported process metadata.

  • Verify surface reachable
    The Setup & Verify page rendered successfully.
    pass
  • Runtime metadata
    Node.js v24.14.1 running in production.
    pass

Database Verification

Database connection and core schema checks passed.

pass

Checked: DATABASE_URL presence, a live connection from this deployment, and all required core tables.

  • DATABASE_URL
    DATABASE_URL is present.
    pass
  • Connection test
    Database connection succeeded.
    pass
  • Core schema
    All 6 required tables are present.
    action_records, guard_decisions, api_keys, users, settings, guard_policies
    pass

Configuration

1 recommended setting(s) still missing.

warn

Checked: Presence of required and advisory environment variables. Values are never shown here.

  • DATABASE_URL
    DATABASE_URL is present.
    Postgres connection string
    pass
  • NEXTAUTH_SECRET
    NEXTAUTH_SECRET is present.
    Session signing secret
    pass
  • NEXTAUTH_URL
    NEXTAUTH_URL is present.
    Public URL of this DashClaw instance
    pass
  • DASHCLAW_API_KEY
    DASHCLAW_API_KEY is present.
    Default API key for agent authentication
    pass
  • CRON_SECRET
    Recommended setting is missing.
    Next: Generate with: openssl rand -hex 32, then add it to your deployment environment variables.
    warn

Auth Readiness

DashClaw cannot be signed into normally until auth setup is completed.

warn

Checked: Whether at least one complete sign-in method exists and whether agent API authentication has a configured path.

  • Sign-in readiness
    No complete sign-in method is configured yet.
    Next: Configure DASHCLAW_LOCAL_ADMIN_PASSWORD for local access, or finish GitHub, Google, or OIDC setup.
    warn
  • Local admin password
    Local password login is not configured.
    Next: Set DASHCLAW_LOCAL_ADMIN_PASSWORD if you want password-based setup access without OAuth.
    warn
  • Agent API access
    A default agent API key is configured.
    pass

Deploy Readiness

Deploy configuration has recommendations.

warn

Checked: NEXTAUTH_URL vs current host, realtime backend on serverless.

  • NEXTAUTH_URL does not match deployment host
    Configured: dash-claw.vercel.app — current:
    Next: In Vercel, set NEXTAUTH_URL to https:// and redeploy.
    warn
  • Realtime backend: Redis
    Mission Control live stream is active.
    pass

SDK and Integration Verification

Finish core verification first, then run live SDK checks.

warn

Checked: This section does not execute SDK calls. It verifies whether a live validation path is available and documents the exact next commands.

  • Live validation proof
    No live validation proof has been captured yet.
    On the Settings page, paste your API key into the "Test your connection" panel and click "Run test" to capture proof and upgrade to verified.
    warn
  • Core verification gate
    Core verification is still incomplete, so validation should wait.
    Next: Fix the blocked or warning checks above first.
    warn
  • API key available
    An API authentication path is available.
    pass

Workflow

Core instance verification
pass

DashClaw rendered, required config is present, and database checks completed.

Operator and auth verification
warn

Normal operator sign-in still needs setup.

Next: Finish local password or OAuth setup before relying on dashboard access.

SDK and integration verification
pending

Open the Settings page and use the "Test your connection" panel — paste your API key and click "Run test" — to capture live proof.

Next: On the Settings page, paste your API key into the "Test your connection" panel and click "Run test" to validate and capture proof.

Verification proof artifact
pass

A structured JSON artifact is available for the current verification view.

Next: Download the proof artifact once you are ready to share or archive the current verification state.

Recommended next steps

Configure a sign-in method

warn

Operators need at least one complete sign-in method before normal dashboard access will work.

  • What failed: no complete operator sign-in path is configured.
  • Likely cause: neither local password login nor a fully configured OAuth provider is available yet.
  • Next action: set DASHCLAW_LOCAL_ADMIN_PASSWORD for solo access, or finish GitHub, Google, or OIDC setup.
DASHCLAW_LOCAL_ADMIN_PASSWORD=change-me
NEXTAUTH_SECRET=$(openssl rand -base64 32)

Validate your connection

info

Core verification passed. On the Settings page, use the "Test your connection" panel to validate and capture proof.

  • What this proves: real API ingress, authentication, and a live request path.
  • Next action: open the Settings page, paste your API key into the "Test your connection" panel, and click "Run test".