Settings
Instance configuration, verification, model pricing, and agent identity.
Needs attention
DashClaw can partially verify this instance, but some follow-up is required before normal use is trustworthy.
This page separates what has already been verified from live validation that is still pending.
Last checked Mar 26, 04:37:02 PM (server time)
Test your connection
This page is intentionally safe to open before login. Some operator details stay hidden until you sign in.
OKCore Readiness
All checks passed
Confirms that DashClaw is serving the verify surface and the app process is alive.
DashClaw responded to the verification request.
What was checked: The /setup page rendered and the server runtime reported process metadata.
Evidence: Behavior verified: the app process responded and exposed runtime metadata.
Verify surface reachable
The Setup & Verify page rendered successfully.
Runtime metadata
Application runtime is available.
OKDatabase Verification
All checks passed
Checks whether DashClaw can reach its database and confirm the core schema exists.
Database connection and core schema checks passed.
What was checked: DATABASE_URL presence, a live connection from this deployment, and all required core tables.
Evidence: Database verified: connection succeeded and required core tables were present.
DATABASE_URL
DATABASE_URL is present.
Connection test
Database connection succeeded.
Core schema
All 6 required tables are present.
!Configuration
Verifies required settings and highlights recommended follow-up configuration.
1 recommended setting(s) still missing.
What was checked: Presence of required and advisory environment variables. Values are never shown here.
Evidence: Required settings are present, but some recommended configuration is still pending.
Still pending: Recommended configuration is still pending for a stronger operator setup.
DATABASE_URL
DATABASE_URL is present.
Postgres connection string
NEXTAUTH_SECRET
NEXTAUTH_SECRET is present.
Session signing secret
NEXTAUTH_URL
NEXTAUTH_URL is present.
Public URL of this DashClaw instance
DASHCLAW_API_KEY
DASHCLAW_API_KEY is present.
Default API key for agent authentication
CRON_SECRET
Recommended setting is missing.
Likely cause: This environment variable has not been added to the current deployment.
Next action: Generate with: openssl rand -hex 32 — then add to Vercel → Settings → Environment Variables.
!Auth Readiness
Checks whether operators can sign in and whether agents have an authentication path.
DashClaw cannot be signed into normally until auth setup is completed.
What was checked: Whether at least one complete sign-in method exists and whether agent API authentication has a configured path.
Evidence: Auth is still inferred as incomplete because no sign-in method is fully configured.
Sign-in readiness
No complete sign-in method is configured yet.
Likely cause: No dashboard sign-in method is configured. Set DASHCLAW_LOCAL_ADMIN_PASSWORD for solo access, or configure GitHub, Google, or OIDC.
Next action: Configure DASHCLAW_LOCAL_ADMIN_PASSWORD for local access, or finish GitHub, Google, or OIDC setup.
Local admin password
Local password login is not configured.
Likely cause: Local admin password has not been set for this deployment.
Next action: Set DASHCLAW_LOCAL_ADMIN_PASSWORD if you want password-based setup access without OAuth.
Agent API access
Agent API authentication appears configured.
!Deploy Readiness
Vercel-specific configuration checks for production readiness.
Deploy configuration has recommendations.
What was checked: NEXTAUTH_URL vs current host, realtime backend on serverless.
Evidence: Deploy checks passed.
NEXTAUTH_URL does not match deployment host
Configured: dash-claw.vercel.app — current: www.dashclaw.io
Next action: In Vercel, set NEXTAUTH_URL to https://www.dashclaw.io and redeploy.
Live stream requires Redis on serverless
Running in-memory mode. Each serverless invocation has a fresh event bus — Mission Control will not show live decisions.
Next action: Create a free Upstash Redis instance at upstash.com and add UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN to Vercel environment variables.
!SDK and Integration Verification
Provides guided live validation paths for Node and Python once core verification is in place.
Finish core verification first, then run live SDK checks.
What was checked: This section does not execute SDK calls. It verifies whether a live validation path is available and documents the exact next commands.
Evidence: Live SDK proof is pending because core instance verification is not complete yet.
Still pending: Use the "Run test" button above to validate your API key and capture proof.
Live validation proof
No live validation proof has been captured yet.
Click "Run test" above with your API key to capture proof and upgrade to verified.
Core verification gate
Core verification is still incomplete, so validation should wait.
Likely cause: Database, required configuration, or auth readiness still needs attention.
Next action: Fix the blocked or warning checks above first.
API key available
An API authentication path is available.
Fix the blocked core checks above first, then use the test button to validate.
Recommended next steps
Configure a sign-in method
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=<set-a-strong-password>
Validate your connection
Core verification passed. Use the "Run test" button at the top of this page to validate and capture proof.
What this proves: real API ingress, authentication, and a live request path.
Next action: paste your API key in the test panel above and click "Run test".
⋯Verification workflow
Core instance verification
DashClaw rendered, required config is present, and database checks completed.
Proof: Verified by page reachability, config presence checks, database connectivity, and core schema inspection.
Operator and auth verification
Normal operator sign-in still needs setup.
Proof: Only inferred as incomplete because no complete sign-in method was found.
Next action: Finish local password or OAuth setup before relying on dashboard access.
SDK and integration verification
Paste your API key above and click "Run test" to capture live proof.
Proof: Use the connection test above to prove authenticated API access.
Next action: Use the "Run test" button at the top of this page to validate and capture proof automatically.
Verification proof artifact
A structured JSON artifact is available for the current verification view.
Proof: The artifact records timestamp, mode, overall state, categories checked, per-check status, and next steps.
Next action: Download the proof artifact once you are ready to share or archive the current verification state.
Verification proof
Download JSONPreview artifact
{
"overall": "needs_attention",
"label": "Needs attention",
"summary": "DashClaw can partially verify this instance, but some follow-up is required before normal use is trustworthy.",
"ready": false,
"fully_verified": false,
"readiness_status": "needs_attention"
}