Terminal UI

The numes command includes a full-screen terminal workspace for everything a self-hosted provider does: sign in, set up endpoints, choose models and prices, publish, start and stop serving, answer review feedback, check failed models again, and watch usage and earnings. It runs in any terminal, including over SSH.

numes provider tui                 # open the terminal UInumes provider tui --profile NAME  # open it with an endpoint selected

Each endpoint is one local profile serving one source, such as Ollama or an upstream API, and is shown by its name, for example "Ollama on this machine". Quitting with q never stops your endpoints; they keep serving in the background. When a newer release is available, a notice shows the command to install it, numes update.

Layout

The layout matches the desktop app: a tab bar, a live ticker, the work area and, on wide terminals, an inspector pane on the right.

• Attention counter. At the right of the tab bar, for example ▲ 2 need attention, counts current problems: models with review feedback, missing names or failed checks, a failed local process, a platform state that needs action, or an operation with an uncertain outcome. Press a or click it to open the list; Enter on an item goes straight to the fix.

• Ticker. Requests in flight and capacity, tokens and requests per minute, success, time to first token, today's earnings, running endpoints and live models. Missing data reads —, never zero.

• Status bar. On terminals at least 30 rows tall: this machine, the agent version, running endpoints and when platform data last loaded.

Platform data such as statuses, measurements and earnings refreshes automatically; press r to refresh now. Session counters such as tokens per minute come from this machine and never count as earnings or health.

Endpoint workspace

Enter on an endpoint opens its workspace, with three tabs:

• Models: each model's native name, public name, status and session usage. A banner shows unpublished changes (◆) and models that still need names or prices.

• Settings: provider review, capacity, the Platform section with the actions the platform allows (Pause, Resume, Reconnect agent, Edit), the source connection, Serving (start, stop or restart), Maintenance (validate) and removal. Delete this endpoint deletes it on the platform, then the local files; Remove from this device only keeps the endpoint registered and offline.

• Details: provider and endpoint state, IDs, the local profile, connection, accepted terms and source version.

Model screen

Enter on a model opens its screen with these sections:

Until you publish, a withdrawn model keeps its place in every model list, dimmed and marked Withdrawn on publish, so the rows around it never move. Open it to undo the withdrawal.

Edits stay local until you publish. Model statuses use the labels in Review and lifecycle.

Publishing changes

p opens the publish sheet. It lists every change: + new models with their prices, ~ changed models with each changed field (for example out $2 → $4/M), and − withdrawn models with the consequence. x discards the selected model's changes; Enter publishes. If the source changed since you last looked, press r to refresh from it and review again. If a publication's outcome is unknown, for example after a lost connection, press c to check its status or Enter to retry the same submission.

Edits to a published endpoint are kept only while the terminal UI is open. Closing it discards them, and reopening loads the platform's accepted terms. Setup drafts for a new endpoint are saved to disk.

Set up an endpoint

Press n anywhere. Setup has four steps and saves a draft after every change; x saves and exits, and Continue setup on Overview or Endpoints resumes at the same step.

1. 1

   Source

   Pick a source kind. Only accounts and providers you may run endpoints for are offered; choose an existing provider or Create a new provider with the name customers will see. The connection form shows the address, API key and advanced settings: display name, concurrent requests, API dialect, capability catalog and data policy. Choose Connect and find models →.

2. 2

   Models

   Tick models with Space, search with /, tick all shown with a. Each ticked model shows a chip:

   Chip	Meaning
   ✓ named	The public name is resolved.
   ⚠ needs name	Choose a public name with e.
   ⏳ in review	The name is reviewed after you submit.
   … checking	The name is being resolved.
   – later	Kept in the draft but not published.
   ⚠ changes requested, × rejected, × name revoked	Review feedback on an earlier submission.
   − withdrawn on publish	A published model you unticked.
   ⚠ missing at source	Selected but no longer offered by the source.

   Choose Continue to review →.

3. 3

   Review

   One page for the whole endpoint (who the models are offered to, currencies, markup over upstream prices, market adjustment, capacity, hosted tools, data policy and names), then one page per model with its prices, context length, concurrency and capabilities. [ and ] switch pages; v shows every model as a spreadsheet. Prices start from upstream and market references where they exist; r regenerates missing prices. A context length or maximum output your source didn't report is labelled from catalogue or default; you can change the context length (see limits your source doesn't report). When a model fails a capability check, the page names the check and the fix; see Fixing a failed check. When the bar reads Ready to submit, press P.

4. 4

   Submit

   A progress list runs through the provider, the endpoint, the model submission and starting the endpoint, then opens the endpoint's workspace. If the platform refuses a provider or endpoint name that's already in use, Enter reopens Review on that name. A submission that stopped part-way stays under Continue setup.

   Every selected model is checked before anything is submitted. When some fail, the screen lists each model's outcome, for example 14 models checked · 13 passed · 1 failed, followed by the first failed model's report; n shows the next failed model. Enter retries, e opens the failed model in Review, and s publishes the models that passed. The failed models are kept for later with their settings; include one again from the endpoint's models checklist (m) once it passes. The publish sheet for an existing endpoint offers the same keys.

To add or remove models on an existing endpoint, open it and press m; the same Review step follows, and P opens the publish sheet.

Keys

? shows the keys for the current screen.

Enter opens, runs or continues; Space ticks and toggles; ← → step through choices. Lists move with ↑ ↓ or j k. Text fields accept Ctrl+A, Ctrl+E, Ctrl+U, Ctrl+K and Ctrl+W. The mouse works where your terminal supports it. Destructive and serving actions always ask for confirmation, and secrets are entered only in masked fields.

Status pills

Each endpoint shows one pill. The first that applies wins:

1. Provider not approved: In review, Changes requested, Rejected, Suspended or Deleted.

2. Endpoint held by the platform: Rejected, Suspended, Paused, Changes requested, Draft or In review, or Not connected when you need to choose Reconnect agent.

3. This machine:

4. Endpoint status: Serving, Not serving, Offline, Not connected or No models. Serving summarizes the models, for example "Models: 23 live · 1 check failed".

Signed out, the pill reads Local only. If platform status can't be loaded, it reads Server status unavailable, never an approval. While the terminal is still loading, it reads Loading….

Terminal size

On exit or interruption, your terminal's screen, cursor and input settings are restored.

Sign in

On first run, a Welcome screen walks you through signing in. Press Enter to sign in with the method chosen automatically, as with numes auth login, l for a browser on this machine, or d for a device code. Esc skips to Overview. With a device code, compare the code in your browser before approving it; it disappears when the dialog closes and is never saved.

Your sign-in is restored at the next launch. Sign out on the Account tab with o.

Next steps