Use the console

The console at console.nodus-compute.ai shows the same objects the CLI and the Python SDK work with. Every page has the command that does the same thing, so you can move between them at any time.

Sign in

1. Open the console and sign in with your email and password, or with GitHub or Google.
2. New accounts confirm their email with a 6-digit code.
3. If someone invited you, the console shows the invite first. Accept it to join their organization.
4. Otherwise create your organization. Its URL name (for example research) appears in every link.

Your first organization receives starter credit once your email is verified.

Sign in the CLI from the browser

Run nodus login. The CLI opens the console, which asks which organizations the CLI may use and names the key it creates, for example cli-laptop-2026-09-30. Choose Authorize and return to your terminal. On a machine without a browser, run nodus login --device and enter the code it prints on the console’s device page.

If you have no organization yet, authorizing creates one for you. If someone invited you, both pages show the invite first: accept it, and the CLI signs in to their organization.

Find your work

• The URL always names the organization and project: /research/default/jobs/lora-fine-tune/logs. Links you share open in the same place for anyone with access, and two browser tabs can work in two organizations.
• Switch organization or project from the top bar.
• Press Cmd+K (or Ctrl+K) to search objects, pages and actions. Type job/ or sb/ and a name to jump straight to an object.
• Press ? for every keyboard shortcut. g then a letter goes to a section, for example g b for Billing.

Follow runs live

Lists and detail pages update as things change, without reloading. The note Live · 12s ago shows the time since the last update. Choose it and Pause live updates to freeze what you are reading; Resume applies the changes at once. Running work shows its cost so far, marked with ≈ between updates.

Copy the command

The terminal icon in each page header copies the command for what you are looking at, with the project and organization spelled out:

nodus describe job/lora-fine-tune -p default --org research

View YAML in the actions menu shows the live object as a manifest you can download and apply elsewhere.

Create something

Create pages show four tabs: Form, YAML, CLI and Python. They always show the same manifest. Before you launch, the estimate shows the expected cost range, the hourly rate, the first hold and how long the price holds. Launch uses exactly that estimate; if prices move first, the console estimates again and asks you to confirm. Your form is saved as a draft in this browser until you launch or discard it.

If the network drops while you launch, the console says it could not confirm the result. Check status looks for the object by name, and Retry is safe: it can never create a second copy.

When credits run out

If your balance cannot fund the next renewal, running work stops at its funded edge. The project Overview then shows Paused for funds, grouped by what adding credits does:

• Resumes automatically: jobs and agent runs continue by themselves once a hold fits.
• Needs a start: workspaces stay stopped until you choose Start (or Start all).
• Wakes on next use: sandboxes start again on the next command, file request or preview.
• Rejecting requests: inference endpoints answer with 402 until funded.
• Failed imports: choose Retry import on the volume.
• Needs a higher limit: work that reached its own spend limit resumes only when you raise that limit.

Choose Add credits on the panel to top up.

Appearance

Choose System, Light or Dark, and Comfortable or Compact density, from the account menu. The theme follows you across the console and the docs.