Red Hat System Administration I · RH124

Chapter 5

Getting AI-Assisted Help with RHEL Lightspeed
The c command · Installing the assistant · Using it responsibly
CIS126RH — Mesa Community College

Chapter Objective

Install and use the command-line assistant powered by RHEL Lightspeed to get natural-language help understanding, configuring, and troubleshooting a RHEL system — and understand its limits.

Key Commands

  • dnf install command-line-assistant
  • c
  • c history
  • systemctl status clad

What Is RHEL Lightspeed?

RHEL Lightspeed is a generative-AI service, included with a RHEL subscription, that answers natural-language questions about managing Red Hat Enterprise Linux. Its responses are grounded in RHEL product documentation and the Red Hat Knowledgebase rather than generic internet text.

On the system itself, you interact with Lightspeed through the command-line assistant — a small client you invoke with the c command. Behind the scenes, a background daemon called clad (Command Line Assistant Daemon) is the only part of the system that talks to the network; it forwards your question to the Lightspeed service and prints the response back in your terminal.

Why It Matters — Instead of leaving the terminal to search the web for a command's syntax or the meaning of an error message, you can ask directly at the prompt and get an answer scoped specifically to RHEL.

How a Request Flows

1cThe client you type your question into
2clad.serviceLocal daemon that brokers the request — the only part that reaches the network
3RHEL LightspeedRed Hat's hosted AI service that generates the answer
4cPrints the response back in your terminal
Warning — Requires a Registered System — Because the assistant is delivered as part of your subscription, it only works on a system that is already registered to Red Hat with subscription-manager (see Chapter 4). An unregistered system cannot install or use it.

Installing the Assistant

The assistant ships as a package you install with dnf, available on registered RHEL 9 (9.6+) and RHEL 10 systems.

# Install the command-line assistant package
sudo dnf install command-line-assistant

# Confirm the clad daemon is running
systemctl status clad

Configuring the Assistant

The assistant's configuration file lives at /etc/xdg/command-line-assistant/config.toml. In most classroom and standard-subscription setups you won't need to touch it — it matters mainly in enterprise environments that route through Red Hat Satellite or a custom endpoint.

# After changing config.toml, restart the daemon to apply it
sudo systemctl restart clad
Tip — man clad — Like most RHEL services, the daemon has its own man page. Run man clad for details on the service itself if you ever need to troubleshoot connectivity.

Asking Questions with c

The basic pattern is the c command followed by your question in quotation marks.

# Ask a general how-to question
c "how do I create a network bridge with nmcli"

# Ask about a specific service
c "how do I check whether firewalld is running"

# Ask it to explain a concept
c "what is the difference between a systemd service and a target"

Because the assistant understands plain English rather than exact syntax, it's especially useful when you know roughly what you want to do but don't remember (or have never learned) the specific command.

Tip — It's a Starting Point, Not a Replacement — Use the assistant the way you'd use a knowledgeable colleague: a fast way to get pointed in the right direction. Still confirm anything critical against man pages or official documentation before running it on a production system.

Feeding It Command Output

You can pipe the output of a command — or the contents of a log file — directly into the assistant so it can help interpret what you're looking at.

# Ask the assistant to help interpret a log file
cat /var/log/messages | c

# Pipe a command's output straight in
systemctl status sshd | c

This turns troubleshooting into a conversation: run a command, pipe the confusing output to c, read its explanation, then ask a follow-up question to keep narrowing down the problem.

Warning — Review Before You Act — Treat suggested commands as a recommendation, not an instruction to run blindly — especially anything destructive or anything touching production systems. Always verify a suggested command's effect before executing it.

Conversation History

The assistant keeps a record of your past questions and answers, which you can revisit or search with c history.

# Show your entire conversation history
c history --all

# Show only the first conversation on record
c history --first

# Show only the most recent conversation
c history --last

# Search history for questions and answers about a topic
c history --filter "podman"

# Clear all stored history
c history --clear
Note — History is stored per user. If you're sharing a lab system with classmates, keep in mind your questions (and any output you piped in) may be retained until you clear them.

Data and Trust Considerations

The command-line assistant sends your questions — and anything you pipe into it — to Red Hat's hosted Lightspeed service to generate a response. Treat it accordingly.

Warning — Not a Substitute for Judgment — The assistant is a productivity aid, not an authority. As the administrator, you remain responsible for verifying that any command it suggests is correct and safe for your specific system before you run it.

Key Terms for Chapter 5

RHEL Lightspeed
Red Hat's hosted generative-AI service for natural-language RHEL assistance
command-line assistant
The local client, invoked with c, used to interact with RHEL Lightspeed from the terminal
clad
Command Line Assistant Daemon; the background service that brokers requests between c and Lightspeed
c
The command used to ask the assistant a question, e.g. c "question"
c history
Subcommand for viewing, filtering, or clearing your saved conversation history
config.toml
The assistant's configuration file at /etc/xdg/command-line-assistant/config.toml

Review Questions

  1. What package do you install to get the RHEL Lightspeed command-line assistant, and what prerequisite must the system meet first?
  2. What is the role of the clad daemon, and why does only it — not the c client directly — talk to the network?
  3. Write a c command that would ask the assistant how to list all currently enabled systemd services.
  4. How would you pipe the output of journalctl -xe into the assistant for help interpreting it?
  5. What command shows only your most recent conversation with the assistant?
  6. What command permanently clears your entire conversation history?
  7. Why should you avoid running a command suggested by the assistant without reviewing it first?
1 / 12