Overview
Theironclaw onboard command launches an interactive wizard that guides you through initial configuration of IronClaw. This includes authentication, database setup, and channel configuration.
Run this command when setting up IronClaw for the first time, or to reconfigure your installation.
Usage
Options
Skip the authentication step and use your existing NEAR AI session.Use this if you’ve already authenticated and don’t want to log in again.
Reconfigure channels only, skipping authentication and other setup steps.Useful when you want to enable/disable specific channels without redoing the full setup.
Examples
Complete onboarding
Run the full setup wizard:Skip authentication
Use your existing session and configure the rest:Reconfigure channels only
Change which channels are enabled without touching authentication:Onboarding Steps
The onboarding wizard walks you through the following steps:1. NEAR AI Authentication
Authenticate with NEAR AI to enable LLM access:--skip-auth if you’ve already authenticated.
2. Database Configuration
Choose and configure your database backend:3. Secrets Master Key
Generate or provide a master encryption key for storing secrets:4. Channel Configuration
Choose which communication channels to enable:--channels-only.
5. Complete
Configuration Files Created
Onboarding creates or updates the following files:~/.ironclaw/.env- Environment variables and configuration~/.ironclaw/session.json- NEAR AI authentication session~/.ironclaw/ironclaw.db- Local database (if using libSQL)
The
.env file contains sensitive credentials. Keep it secure and never commit it to version control.Troubleshooting
Browser doesn't open for authentication
Browser doesn't open for authentication
If your browser doesn’t open automatically:
- Copy the authentication URL shown in the terminal
- Open it manually in your browser
- Complete the login flow
- Return to the terminal to continue
Database connection fails
Database connection fails
If PostgreSQL connection fails:
- Verify your
DATABASE_URLis correct - Check that PostgreSQL is running
- Ensure the database exists
- Verify network connectivity and firewall rules
Master key not saved
Master key not saved
If the master key fails to save to the keychain:
- The key will be saved to
.envinstead - On macOS, you may need to grant keychain access
- On Linux, ensure
libsecretis installed
SECRETS_MASTER_KEY manually in .env.Reconfiguration
You can rerun onboarding at any time to reconfigure your installation:Related Commands
ironclaw run
Start the agent after onboarding
ironclaw config
View and modify settings
ironclaw status
Verify your configuration
ironclaw doctor
Diagnose configuration issues
