Apps

The Apps screen (/apps) lists the apps deployed in your workspace — the front ends that surface a Nexa agent to end users, such as a Streamlit dashboard or a Slack app. From here you see each app’s status, start or stop its compute, open the running app, and refresh the list. Use it when you want to bring an app online, pause it to save compute, or check whether it is currently reachable.

What an app is

An app is a deployed front end backed by an agent. Each app in the list shows:

Field	Meaning
App name	The deployed app’s identifier
Type	The app front end, for example Streamlit or Slack
Agent	The agent the app is backed by, with its version if set
Deployment	Whether the app is Deployed, Deployment Running, or Deployment Failed
Compute status	The runtime state of the app’s compute (see below)

Apps are created from an agent rather than from scratch on this screen; the Apps screen is where you operate apps that already exist. To build the agent behind an app, see Agents.

Compute states

The status badge on each app reflects the state of its underlying compute. Start and stop actions move an app between the active and stopped states, with transient states in between.

State	Badge	Meaning
ACTIVE	Active	App compute is running and the app is reachable
STOPPED	Stopped	Compute is paused; the app is not serving
STARTING	Starting…	Start requested; compute is coming up
STOPPING	Stopping…	Stop requested; compute is shutting down
DELETING	Deleting…	Compute is being removed
UNKNOWN	Unknown	Status has not synced yet — refresh in a moment

Note

Start and stop actions are disabled while an app is in a transient state (STARTING, STOPPING, DELETING) or UNKNOWN. Wait for it to settle into ACTIVE or STOPPED before acting again.

View the app list

1. Open Apps from the sidebar.
2. Switch between Card view and List view using the view toggle in the top bar. Both show the same apps and actions.
3. Search by app name using the search box; the list filters as you type.
4. Page through results with the pagination controls, and change the page size (12, 24, 36, or 48 per page).

Refresh status

App status is fetched when the screen loads. To pull the latest state — for example after a deploy or while an app is starting — use the Refresh apps button in the top bar. The button shows a spinner while it reloads the list.

Start or stop an app

Starting brings the app’s compute online; stopping pauses it to free compute.

1. On an app card or row, choose the start control (play icon) or, if the app is ACTIVE, the pause control. In list view this is the Start / Pause button.
2. Confirm in the dialog. Nexa sends the request and the badge moves to STARTING or STOPPING, then to ACTIVE or STOPPED once the transition completes.

Caution

Starting an app may also start its associated agent if that agent is currently stopped — both start together. Pausing an app does not stop the agent; the agent can keep running after the app is paused. Manage the agent separately from Agents if you need to stop it too.

Open an app

To open the running app in a new browser tab, use the Open App control (external-link icon) on the card, or click the app name in list view. The control is available only when the app has a URL, which requires the app to be deployed. If an app is stopped, start it first so it becomes reachable.

Related

• Agents — build and deploy the agent behind an app.
• Agent lifecycle — how agents move from draft to deployed across environments.
• Usage & costs — track the compute cost of running apps.