For many OpenShift users, the oc CLI is more than just a command-line tool—it’s their primary workspace. Over 60% of OpenShift users access their clusters through the CLI.
To meet users where they are, OLS introduces a CLI plugin that can be installed into the oc client.

This plugin allows users to:

• Access OLS directly from their terminal without switching to the console.

• Use cluster-aware AI features from the CLI.

• User able to ask openhsift or BYOK question in the CLI
  • CLi able to display the answer
  • user is able to ask follow up question 

Installation Experience

The OLS CLI plugin installation experience will be similar to other Red Hat CLI tools such as kn (Serverless CLI):
🔗[ Installing kn CLI|https://docs.redhat.com/en/documentation/red_hat_openshift_serverless/1.29/html/installing_serverless/installing-kn]

Download Location

Users can download the OLS CLI binary from the Red Hat Customer Portal:
🔗[ Download OLS CLI|https://access.redhat.com/downloads/content/290/ver=4.19/rhel---9/4.19.14/x86_64/product-software]

User Experience

The experience will be similar to kubectl-ai from Google Cloud:
 

Usage Syntax

oc ols [flags]

oc ols [command]

Telemetry

Telemetry will be enabled to help the OLS team understand how customers are interacting with Lightspeed:

• Using CLI only
• Using Console only
• Using both CLI and Console

This data will help improve the user experience and prioritize feature development across both access methods.

Notes from experimenting RHEL LS CLI “c” https://play.instruqt.com/rhel/invite/yhoxpo1y1xf6 

• It does not maintain the session; it's a one-question output.
• It does not allow the user to ask follow-up questions.

• More design is focused on OS system admins.
• In OCP, RHCOS is a black box, and users usually don't perform OS system admin tasks

• Do not provide color coding for text, to differentiate text from code.
• No support for MCP client 
• They are considering moving their CLI to something else (still in the exploration phase).