openclaw - 💡(How to fix) Fix TUI entry point UX: `openclaw chat` silently does nothing, `autolab` alias gone, `tui` not discoverable [2 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70349Fetched 2026-04-23 07:25:54
View on GitHub
Comments
2
Participants
1
Timeline
6
Reactions
0
Participants
Timeline (top)
commented ×2closed ×1cross-referenced ×1mentioned ×1

The path from terminal to chat TUI is broken from a user-discovery standpoint. Three related problems:

Error Message

Running openclaw chat (or openclaw chat --help) produces zero output and exits cleanly. No error, no "unknown command", no hint. User assumes the install is broken. Expected: either alias chattui, or print an unknown-command error with a "Did you mean openclaw tui?" hint. 2. Fix the silent-exit bug on unknown subcommands (chat shouldn't be matching anything if it's not registered — it should error with a suggestion).

Root Cause

The path from terminal to chat TUI is broken from a user-discovery standpoint. Three related problems:

Code Example

$ openclaw chat
$ openclaw chat --help
$ echo $?
0

---

$ autolab chat
zsh: command not found: autolab

---

which autolab            # not found
openclaw chat            # silent, exit 0
openclaw chat --help     # silent, exit 0
openclaw tui --help      # works
RAW_BUFFERClick to expand / collapse

Summary

The path from terminal to chat TUI is broken from a user-discovery standpoint. Three related problems:

1. openclaw chat silently exits 0 with no output

Running openclaw chat (or openclaw chat --help) produces zero output and exits cleanly. No error, no "unknown command", no hint. User assumes the install is broken.

$ openclaw chat
$ openclaw chat --help
$ echo $?
0

Expected: either alias chattui, or print an unknown-command error with a "Did you mean openclaw tui?" hint.

2. autolab binary no longer exists, no back-compat shim

Lots of muscle memory + docs still reference autolab chat / autolab / node index.js chat. After rebrand, none of these work and there's no shim.

$ autolab chat
zsh: command not found: autolab

Expected: install a thin autolab shim that prints a deprecation notice and forwards to openclaw (at minimum for one or two release cycles).

3. openclaw tui is the real entry but is not discoverable

The TUI command is named tui. Nobody types tui first — they type chat, repl, or interactive. The help output also doesn't surface "this is how you start chatting with your agent in the terminal" anywhere prominent.

Expected:

  • Add chat as a top-level alias for tui
  • Mention it in the bare openclaw help output / onboarding banner
  • Doc page at /cli/chat that redirects to /cli/tui

Environment

  • OpenClaw 2026.4.12 (f9b1079)
  • macOS (Darwin 25.2.0 arm64)
  • Installed via Homebrew (/opt/homebrew/bin/openclaw)
  • Shell: zsh

Reproduction

which autolab            # not found
openclaw chat            # silent, exit 0
openclaw chat --help     # silent, exit 0
openclaw tui --help      # works

Suggested fix (in order of impact)

  1. Add chat alias for tui in the CLI command registry — one-line fix, biggest UX win.
  2. Fix the silent-exit bug on unknown subcommands (chat shouldn't be matching anything if it's not registered — it should error with a suggestion).
  3. Restore autolab shim as a deprecation forwarder for at least one release.
  4. Onboarding banner: after openclaw configure / openclaw onboard, print "➡️ Start chatting: openclaw chat".

Priority

High — this is the literal first thing a new user does after install, and it currently looks broken.


Reported via Nexus on behalf of @danvallier

extent analysis

TL;DR

The most likely fix involves adding a chat alias for the tui command in the CLI command registry to improve user discovery and experience.

Guidance

  • Add chat alias: Implement the suggested one-line fix to map chat to tui in the CLI command registry for a significant UX improvement.
  • Error handling for unknown subcommands: Modify the code to handle unknown subcommands like chat by providing an error message with a suggestion, such as "Did you mean openclaw tui?".
  • Restore autolab shim: Create a thin autolab shim that prints a deprecation notice and forwards to openclaw for backward compatibility.
  • Enhance onboarding: Update the onboarding process to include a prompt or banner that guides users to start chatting with "openclaw chat" after configuration or onboarding.

Example

No specific code example is provided due to the lack of explicit code context in the issue, but the fix would involve modifying the command registry to include the chat alias and updating error handling for unknown commands.

Notes

The suggested fixes prioritize improving the user experience and discovery of the chat functionality. However, the exact implementation details may vary based on the underlying code structure and technology stack used by OpenClaw.

Recommendation

Apply the workaround by adding the chat alias for tui and restoring the autolab shim as a deprecation forwarder. This approach addresses the immediate user experience issues and provides a clear path for users to engage with the chat functionality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING