Skip to content

[Bug]: CLI channel factory not registered — call register_cli_channel_fn at startup #5685

@NiuBlibing

Description

@NiuBlibing

Affected component

runtime/daemon

Severity

S1 - workflow blocked

Current behavior

The agent mode is crash.

Expected behavior

chat with agent success.

Steps to reproduce

1. zeroclaw onboard
2. zeroclaw agent

Impact

No response

Logs / stack traces

./target/debug/zeroclaw agent
2026-04-13T03:20:11.008472Z  INFO zeroclaw_config::schema: Config loaded path=/home/test/.zeroclaw/config.toml workspace=/home/test/.zeroclaw/workspace source="default" initialized=true
2026-04-13T03:20:11.009326Z  INFO zeroclaw_runtime::agent::loop_: Memory initialized backend="markdown"
2026-04-13T03:20:11.047131Z  INFO zeroclaw_runtime::security::detect: Docker sandbox enabled
🦀 ZeroClaw Interactive Mode
Type /help for commands.


thread 'main' (1082457) panicked at crates/zeroclaw-runtime/src/agent/loop_.rs:2591:14:
CLI channel factory not registered — call register_cli_channel_fn at startup
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

ZeroClaw version

c7bc6ef

Rust version

No response

Operating system

manjaro

Regression?

Yes, it worked before

Pre-flight checks

  • I reproduced this on the latest master branch or latest release.
  • I redacted secrets, tokens, and personal data from all submitted content.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingstatus:in-progressAn open PR is actively targeting this issue.

    Type

    No type

    Projects

    Status

    In Progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions