docs.theus.pe/docs/en/theus-code-on-the-web theus.peDocs home

Theus on the web

Your account, plan, real usage and API keys live in the Theus console at theus.pe — the web companion to the CLI.

Everything you run locally with Theus can be backed by an account on the web. The console is where you sign in, read your real plan and consumption, and mint the API keys that connect the CLI and your integrations to the Theus gateway. This page is a conceptual overview; the live product is always at theus.pe.

Signing in

Open theus.pe/login. Theus offers three ways in:

  • Continue with Google
  • Continue with Apple
  • Magic link by email — enter your address and Theus sends a one-time sign-in link. Opening it verifies your session and returns you to the console.

No password to remember. Once verified, your browser holds the session for the console.

The CLI has its own login path. Running theus login (also signin / entrar) starts a device OAuth flow against the same identity backend, so the credential you use on the web and the credential the CLI receives belong to the same account.

The console

After signing in you land in the console at theus.pe/dashboard. It is organized into sections in a side navigation. Every regular account sees three:

SectionWhat it shows
Resumen (Overview)Your real plan, your consumption for the period, gateway status, the available models, and a shortcut to connect your CLI.
API keysCreate, list and revoke the credentials used by Theus CLI and your integrations.
Uso (Usage)Requests, Theus Tokens consumed, and last activity for the current period.

Administrator accounts additionally see management sections — Clientes (customers), Suscripciones (subscriptions) and Auditoría (audit). If you are not an admin these routes stay hidden.

Plan and usage

The Overview reads your actual plan from the backend — there is no fictional demo plan. When a plan is assigned it reports your Theus Tokens as included, used and remaining, with a meter that flags when you go over the allowance. If the server reports no plan for your account, the console says so plainly rather than inventing one.

The Uso section breaks the period down into three figures:

  • Solicitudes — number of requests.
  • Theus Tokens — total tokens consumed.
  • Última actividad — timestamp of your last event.

To compare or change plans, follow Ver planes disponibles from the Overview, which links to the plans section of the public site.

API keys

The API keys section is where you provision credentials for the CLI and other integrations:

  1. Give the key a label (for example, CI de mi equipo) and create it.
  2. The full key is shown once, immediately after creation — copy it right then. For security the console never displays the complete value again.
  3. Existing keys appear as a list with a preview. Any key can be revoked; revocation takes effect at once and cannot be undone, so any integration still using it stops working.
Treat an API key like a secret. Store it where the CLI reads it (Theus keeps configuration under ~/.theus/) rather than pasting it into shared files. If a key leaks, revoke it from the console and create a new one.

Connecting the CLI

The Overview includes a Conecta tu CLI panel that ties the two halves together: sign in on the web, create an API key (or complete the device login from the terminal), and the CLI talks to the Theus gateway on your account. From there the local experience — the TUI, slash commands, and your local knowledge index — runs against the plan and usage you see on the web.

The web console and the CLI are complementary, not dependent: Theus starts and runs locally without any remote service. The console adds account-level plan, usage and key management on top. Visit theus.pe for the current, live version.
Theus — local-first multimodel coding agent · Made in Peru