Skip to main content

Your Minerva account

Minerva runs as your Minerva account. Create one at minerva-bittensor.duckdns.org with an emailed code, Google or Microsoft. The Free plan needs no payment details.

Sign in​

minerva login

minerva login shows a one-time code and opens the approval page in your browser. Approve it there and the terminal finishes signing in. Your password never reaches the CLI; the device gets its own token, which your account page lists and can revoke.

minerva login and minerva account login are the same command. minerva whoami (or minerva account whoami) shows which account this profile uses.

Use --no-browser on a server or over SSH: it prints the approval link instead of opening it.

One sign-in for every app​

The CLI, the terminal UI, the dashboard, the desktop app and the VS Code extension all use the engine's profile, so they share one sign-in. Sign in from any of them and the others are signed in too; sign out from any of them and they are all signed out.

Several accounts on one computer​

A browser keeps several people signed in with separate browser profiles. Minerva does the same with profiles: each profile has its own sign-in, MCP connections, settings and history.

minerva profile create work          # a second, empty profile
minerva -p work login                # sign it in as another account
minerva -p work                      # chat as that account
minerva profile use work             # or make it the default for new terminals

The dashboard has a profile picker. The desktop app and VS Code use the profile of the engine they connect to.

A profile cloned from another (--clone, --clone-all) starts signed out, so two profiles never share one device token.

Plan and usage​

Your account page shows your plan, your research connections and your devices. The VS Code status panel shows the same plan and your research calls today and over 30 days.

Sign out​

minerva account logout

Signing out (here, or Sign out in the dashboard, desktop app or VS Code):

  • revokes this device's token on the service,
  • removes the sign-in from this profile,
  • removes and revokes this profile's Bittensor MCP connection.

Signing in as a different account in the same profile does the same to the previous account's connection, so nobody ever reaches another person's research. Run minerva account connect-mcp again for the new account.

minerva logout (without account) is different: it removes model provider credentials such as an OpenAI sign-in, not your Minerva account.

What Minerva sends to the account service​

While you are signed in, Minerva keeps the account service up to date with your profile (memory, the subnets and public wallet addresses it mentions, your model), the skills on your profile that did not ship with Minerva, and a short summary of each session. The service's managers can review these and can ask for a full conversation, which your Minerva then sends. Every such access is recorded in an activity log.

Passwords, private keys, seed phrases and API keys are removed on your computer before anything is sent, and again on the service. Other files on your computer are never sent. See the privacy policy.

Lost a device?​

Open your account page and revoke the device, or the research connection, there. A revoked token stops working immediately.