Skip to main content
This page is for the person who runs an agent from admin.heylua.ai and the desktop app rather than from code: a support lead, an operations manager, an agency’s client. After it you can name every part of an agent, change the parts that are yours, tell which changes are live at once and which wait for a release, and brief an engineer.

​
The vocabulary

​
Tasks by surface

“Yes” means the surface does the whole job; ”—” means it has no control for it. Admin dashboard labels are from the checkout used for this page; anything newer is unconfirmed. Approvals are answered in the desktop app or with lua workflows approve <runId> --approval <id> --decision approve; the admin dashboard has no approval view. A channel’s settings, and disconnecting it, are under Channels.

​
Changes that are live at once and changes that wait

These reach end users on their next message: a persona version you publish or activate, knowledge you upload or delete, feature switches, channel connections, widget settings, and the model; so do an engineer’s lua env production, MCP server activation, and lua push of the persona. None of them wait for an agent version. Code waits. A new or changed tool, skill, webhook, trigger, job, processor, or workflow reaches end users only when an engineer pushes it and then promotes an agent version. A rollback is the same promote pointed at the previous version, and it is immediate; it doesn’t undo knowledge uploads, feature switches, channel changes, or environment variables.
The model and the persona you set in the admin dashboard are replaced the next time an engineer pushes the agent, because the push sends what the code says. Tell the engineer so they put the same value in the project.

​
The brief an engineer needs

  • The agent ID (from the admin dashboard URL or the agent’s page) and the channel.
  • What the end user sent, what the agent answered, and when.
  • Whether it was production or a sandbox test.
  • What you changed yourself (persona, knowledge, a feature) and when.

​
Limits

  • An agent keeps at most 100 agent versions; older ones must be deleted to create more.
  • Finished runs are kept for 90 days by default; an organization can set 7 to 90.

​
Next steps

Add knowledge

Upload documents and switch on Knowledge Search.

Channels overview

Which channels connect from the admin dashboard and how.

Operate workflow runs

Approve, cancel, retry, and read a run.

Glossary

Every term, one line each, with the code name.