ironclaw. Every command is a subcommand — running
ironclaw on its own prints usage and exits without starting anything.
Running the Agent
doctor is the first thing to run when something isn’t working. It reports your home
directory, active profile, whether configuration files were found, and whether each
driver initialized.
Setup and Configuration
config init refuses to overwrite existing files unless you pass --force.
config list and config get read every key. config set is narrower: it accepts only
<provider>.api_key, google.client_id, google.client_secret, google.redirect_uri,
slack.enabled, and webui.token --rotate, routing each to the configuration file, the
encrypted secret store, or the web token file. Everything else is edited in config.toml
directly.
config set does not restart the running instance — it prints to apply: ironclaw service restart. See Configuration.
Models and Providers
Extensions and Skills
Add
--verbose to skills list for extra detail.
Activating an extension that needs credentials starts its setup flow. Complete that from
Extensions in the web interface, which is also where you connect
channels while channels list remains unimplemented.
For service logs, read the files directly — see Run as a Service.
Running as a Service
See Run as a Service.
service subcommands do not work on a NEAR AI hosted instance — there is no user service
manager for them to drive. Restart a hosted agent from the
Agent Dashboard instead.Trace Commons
ironclaw traces manages optional, redacted contribution of your agent traces. It is off
until you explicitly opt in.
See Trace Commons.