LuumenAI is the assistant built into Luumen. It connects to your hosts, pulls context from your connected tools, and runs commands on one server or a whole group, all from your actual environment rather than from general knowledge.
Everything LuumenAI does is governed and recorded: administrators decide what it can and cannot do in each connected tool, actions run with the user's identity and permissions, commands wait for the user's approval, and activity is captured in the audit log. Teams get the speed of an assistant without losing control of their landscape or the record of what happened in it.
What Luumen Can See
LuumenAI can be found at the top of the left hand navigation.
When you are connected to a host, LuumenAI has that machine's live state: the operating system and version, the public and private IP addresses, the installed packages, and the session you are working in.
LuumenAI uses that live state to answer from your actual environment. Ask why a service will not start and it reasons about the host in front of you, not a generic Linux box. It also reads the output of every command you approve, so an investigation builds on each result.
Session Context
When you are connected to a host, LuumenAI has that machine's live state: the operating system and version, the public and private IP addresses, the installed packages, and the session you are working in. The connection badge above the message box shows which host LuumenAI is connected to, so you always know what context it is working with. With no session open, the badge reads No active terminal context and LuumenAI can answer general questions but cannot inspect anything.
Connected Tools
When your organization has enabled integrations, LuumenAI can also pull context from the tools your team already uses: a ticket from ServiceNow or Jira, logs from your observability tool, or an SOP from Confluence. That context comes into the session alongside the host state, so an investigation can move between a ticket, the logs, and the server without leaving the conversation.
What Luumen Cannot See
Your terminal scrollback. What you type by hand is not sent to it.
Tools you have not connected. LuumenAI has not read your wiki, your ticketing system, or your internal documentation unless your organization connects them through integrations. See Integrations to connect your tools.
Other conversations. Each one starts fresh, apart from the Skills you have saved.
Other hosts. Its context is the Host or Host Group connected in that conversation.
Credentials. It works inside sessions you opened, as you.
LuumenAI Conversations
Selecting LuumenAI in the left navigation starts a fresh conversation, titled New chat until you rename it. The composer reads "What should we work on?" Every conversation is saved to your workspace and listed beneath Sessions in the left navigation, so you can pick up yesterday's work from any machine you sign in on.
From a conversation's menu you can Rename it or choose Close Session. Closing removes the conversation and its messages and disconnects any hosts that only it was using. If one contains something you need to keep, copy it out first.
Slash Commands
Type / in the composer to open the command menu.
/skill createcreates a new reusable Skill from scratch, through a conversation./skill runruns an existing Skill on the connected host. A picker lists your Skills as you type./skill manageopens the Skills library to edit, delete, or share your Skills.
How LuumenAI Runs Commands
LuumenAI has no access of its own. When it runs a command it does so over the session you opened, using the credential you supplied, with exactly the permissions your account has on that host. Every command waits for your approval first.
The same applies to integrations. When LuumenAI acts in a connected tool such as ServiceNow or Jira, it uses the account you connected, with that account's permissions, and the action is attributed to you in that tool. What it can do there is set by your administrator's tool permissions: some actions run automatically, some ask for your approval, and some are not available to it at all. See Integrations.
On Enterprise, this activity is recorded in the audit log: LuumenAI conversations, runs, approval decisions, and actions, each attributed to the person LuumenAI acted for.
What Using LuumenAI Costs
Conversations consume AI credits, metered per task.
Connecting to Hosts, browsing your Host list, managing credentials, and copying snippets do not. See How AI credits work.