ironclaw/docs/reborn-binary.md

ironclaw-reborn standalone binary

ironclaw-reborn is the standalone executable boundary for Reborn. It is separate from the current ironclaw binary so Reborn boot, config, state, and runtime composition can evolve without accidentally invoking v1 runtime paths.

This binary is available as the workspace package ironclaw_reborn_cli and builds the executable named ironclaw-reborn.

Current status

ironclaw-reborn is an early operator/testing surface, not the default IronClaw runtime.

It currently supports:

ironclaw-reborn --help
ironclaw-reborn channels list
ironclaw-reborn channels list --json
ironclaw-reborn channels list --verbose
ironclaw-reborn completion --shell bash
ironclaw-reborn completion --shell zsh
ironclaw-reborn config path
ironclaw-reborn doctor
ironclaw-reborn hooks list
ironclaw-reborn hooks list --json
ironclaw-reborn hooks list --verbose
ironclaw-reborn logs
ironclaw-reborn logs --json
ironclaw-reborn logs --verbose
ironclaw-reborn models list
ironclaw-reborn models list --json
ironclaw-reborn models status
ironclaw-reborn models status --json
ironclaw-reborn profile list
ironclaw-reborn profile list --json
ironclaw-reborn repl
ironclaw-reborn run
ironclaw-reborn run --confirm-host-access
ironclaw-reborn serve
ironclaw-reborn serve --confirm-host-access
ironclaw-reborn skills list
ironclaw-reborn skills list --json
ironclaw-reborn skills list --verbose

It intentionally does not yet support:

• replacing ironclaw behavior;
• daemon/service installation;
• web gateway/UI startup;
• v1 config, DB, settings, or secrets migration;
• production extension/tool execution;
• long-lived Reborn runtime services.

Commands

channels list

Reports configured Reborn channels without resolving Reborn home, reading v1 channel config, or creating directories.

The Reborn channel registry is not wired yet, so the command currently reports an explicit empty surface:

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- channels list
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- channels list --json
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- channels list --verbose

Expected fields include:

• configured: 0
• status: not-wired
• v1_state: not-used

completion

Generates shell completion scripts without resolving Reborn home, reading v1 state, or creating directories.

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- completion --shell zsh > ironclaw-reborn.zsh
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- completion --shell bash > ironclaw-reborn.bash

The zsh output keeps the v1 CLI guard around compdef so the generated script is safe when zsh completion functions are not loaded yet.

config path

Shows the resolved Reborn state root, its source, selected profile, and explicit v1-state status without creating directories.

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- config path

Expected fields include:

• reborn_home
• home_source
• profile
• v1_state: not-used

doctor

Validates and reports Reborn boot configuration without creating state directories or starting runtime services.

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- doctor

Expected fields include:

• reborn_home
• home_source
• profile
• v1_state: not-used
• driver_registry: initialized

hooks list

Reports configured Reborn hooks without resolving Reborn home, reading v1 hook config, or creating directories.

The Reborn hook registry is not wired yet, so the command currently reports an explicit empty surface:

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- hooks list
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- hooks list --json
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- hooks list --verbose

Expected fields include:

• configured: 0
• status: not-wired
• v1_state: not-used

logs

Reports Reborn log availability without resolving Reborn home, reading v1 gateway logs, or creating directories.

The Reborn log source is not wired yet, so the command currently reports an explicit empty surface:

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- logs
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- logs --json
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- logs --verbose

Expected fields include:

• entries: 0
• status: not-wired
• v1_state: not-used

models list / models status

Shows Reborn model purpose slots and route status without resolving Reborn home, reading v1 provider settings, or creating directories.

Routes are not configurable through Reborn CLI yet, so the command currently reports not-configured routes for built-in slots:

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- models list
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- models list --json
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- models status
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- models status --json

Expected fields include:

• default
• mission
• routes: not-configured
• v1_state: not-used

profile list

Lists the supported Reborn boot profiles without resolving Reborn home, reading v1 state, or creating directories.

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- profile list
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- profile list --json

Supported profiles:

• local-dev (default)
• local-dev-yolo
• production
• migration-dry-run

Select a profile with IRONCLAW_REBORN_PROFILE=<profile>.

run

Starts the standalone Reborn runtime and reads messages from stdin. The no-profile path targets the planned AgentLoop runtime (reborn-planned-default). Without model provider environment variables, the runtime still starts but messages fail cleanly because no LLM gateway is wired.

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- run
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- run --message "hello"

Use --dry-run for the side-effect-free readiness snapshot:

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- run --dry-run

Expected fields include:

• binary: ironclaw-reborn
• version
• reborn_home
• home_source
• profile
• v1_state: not-used
• runtime_driver: planned-agent-loop
• driver_registry: initialized
• local_runtime_shell_readiness: ready
• planned_default_profile: available

For IRONCLAW_REBORN_PROFILE=local-dev-yolo, run, repl, and serve require --confirm-host-access before the runtime receives trusted-laptop host access. Confirmed access mounts the host home through /host; Unix-style raw home aliases are also accepted when they can be represented as scoped mount aliases.

When serve --confirm-host-access grants trusted-laptop access, serve refuses non-loopback listeners such as 0.0.0.0. Bind to 127.0.0.1 or ::1, or use a less privileged profile for non-loopback test listeners.

skills list

Reports configured Reborn skills without resolving Reborn home, reading v1 skill discovery paths, or creating directories.

The Reborn skill catalog is not wired yet, so the command currently reports an explicit empty surface:

cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- skills list
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- skills list --json
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- skills list --verbose

Expected fields include:

• configured: 0
• status: not-wired
• v1_state: not-used

State and config root

Reborn must not use the current v1 IronClaw state root by default.

Home resolution precedence:

1. IRONCLAW_REBORN_HOME
2. ~/.ironclaw/reborn

The resolver rejects unsafe or misleading homes, including empty paths, relative paths, filesystem root, parent-directory components, and known v1 state-root aliases such as $HOME/.ironclaw or IRONCLAW_BASE_DIR.

Profiles

Use IRONCLAW_REBORN_PROFILE to select the boot profile.

Supported values:

• local-dev (default)
• local-dev-yolo
• production
• migration-dry-run

Example:

IRONCLAW_REBORN_HOME="$PWD/.reborn-home" \
IRONCLAW_REBORN_PROFILE=production \
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- doctor

Local smoke checks

Run these before changing Reborn CLI behavior:

cargo fmt --all -- --check
cargo test -p ironclaw_reborn_cli
cargo test -p ironclaw_reborn_config
cargo test -p ironclaw_reborn model_slots_are_exposed_in_cli_display_order
cargo test -p ironclaw_architecture reborn
cargo clippy -p ironclaw_reborn_cli --all-targets -- -D warnings
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- --help
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- channels list
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- completion --shell zsh >/tmp/ironclaw-reborn.zsh
IRONCLAW_REBORN_HOME="$(mktemp -d)/reborn-home" \
  cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- config path
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- hooks list
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- logs
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- models status
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- profile list
IRONCLAW_REBORN_HOME="$(mktemp -d)/reborn-home" \
  cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- run
cargo run -q -p ironclaw_reborn_cli --bin ironclaw-reborn -- skills list

Adding commands

Future commands should follow the crate-local agent contract in:

crates/ironclaw_reborn_cli/AGENTS.md

Short version:

1. add one command module under crates/ironclaw_reborn_cli/src/commands/;
2. register it in commands::Command;
3. resolve and pass RebornCliContext from dispatch only when the command needs boot config;
4. keep pure commands independent from Reborn home resolution;
5. add a binary smoke test through env!("CARGO_BIN_EXE_ironclaw-reborn");
6. avoid v1 runtime imports and v1 state mutation unless explicitly scoped and guarded.

Do not port the current src/cli/* command tree wholesale. Port commands one at a time, starting with Reborn-owned or read-only surfaces.

Release packaging decision

ironclaw-reborn is not yet included in cargo-dist release artifacts.

Current dist plan --output-format=json with crates/ironclaw_reborn_cli marked dist = false emits only the root ironclaw package artifacts. Removing dist = false alone is not enough to ship ironclaw-reborn in the existing ironclaw-v* release workflow because that workflow is shaped around the root ironclaw package tag. Enabling a standalone ironclaw_reborn_cli release also requires cargo-dist WiX metadata/template work and an explicit tag/versioning decision.

Follow-up issue: #3483 tracks packaging ironclaw-reborn in release artifacts.

Until #3483 is resolved, keep:

[package.metadata.dist]
dist = false

in crates/ironclaw_reborn_cli/Cargo.toml so releases do not silently claim to ship an unverified Reborn binary package.