Getting Started with the OpenClaw TUI

I often feel that switching contexts between my terminal and a browser window slows me down. When I am debugging or monitoring a system, I want my tools to stay right where my eyes already are.

Using a terminal UI allows me to keep my workflow in one place. It is faster and keeps me focused on the task at hand without the distraction of extra tabs.

What You’ll Need

• The OpenClaw CLI installed
• A running Gateway to connect to

Quick Start

The fastest way to see what is happening with your Gateway is to run the default TUI command. I recommend starting here to ensure your environment is set up correctly.

openclaw tui

If you are working with a remote Gateway or a specific local port, you can specify the connection details using the URL and token flags:

openclaw tui --url ws://127.0.0.1:18789 --token <token>

For cases where you need to attach to a specific session, use the session and deliver flags:

openclaw tui --session main --deliver

Troubleshooting

If the TUI fails to open or connect, check your connection parameters. Ensure the URL provided to the --url flag is reachable and that your <token> is valid for that Gateway instance.

If you have more questions about specific configurations, check the AI Setup Assistant.

What’s Next

• TUI Guide
• Gateway Documentation