Skip to main content

MINERVA · YOUR PERSONAL BITTENSOR AGENT

Your personal agent.
Built for Bittensor.

Explore subnets, understand metagraphs and stake, and get help with your Bittensor workflow. Minerva works on your machine, with your keys, and asks for your approval before btcli signs a transaction.

This documentation describes engine v0.23.2. Get Minerva →

MORE THAN A CHAT WINDOW

A personal agent for your Bittensor workflow.

For miners, validators, subnet owners, and people finding their way around Bittensor. Start with a question. Keep useful workflows as skills. Return with the context you have built.

Explore the Bittensor tools →
01 / UNDERSTAND THE NETWORK

Research before you act.

Read subnet and metagraph information, inspect wallets and stake, and turn chain data into a useful next question.

02 / KEEP CONTROL

Your machine. Your keys.

Read-only chain tools do not sign transactions. When your workflow reaches btcli signing, Minerva asks for your approval.

03 / BUILD YOUR WAY OF WORKING

Make useful work repeatable.

Use skills, tools, and scheduled jobs to support your own workflow. Review what runs and which credentials it can use.

YOUR AGENT, WHERE YOU NEED IT

Bittensor work. Your way.

Reach your personal agent from your terminal, editor, desktop, or local dashboard. Your profiles, skills, and stored conversations stay with the same engine.

01

Terminal

Ask about subnets, metagraphs, wallets, and stake. Work interactively or automate a repeatable research task.

minervaInstall the engine ↗
02

Editor

Keep your conversation beside your code. Select the same installed engine in the extension settings.

Minerva: Refresh StatusVS Code installation ↗
03

Desktop

A Tauri companion with engine discovery, Quick Chat, and a direct route to your local dashboard.

Select engine → ConnectDesktop downloads and setup ↗
04

Dashboard

Your local control room for conversations, profiles, skills, MCP servers, schedules, and updates.

minerva dashboardDashboard guide ↗

KEEP MOVING FORWARD

Update once.
Bring the engine along.

Check before making changes. The shared engine updater handles your installation type, checks admission, and records an update receipt. Finish active work before updating.

Read the update guide →

01 / Check availability

minerva update --check

02 / Update the shared engine

minerva update

03 / Or use the local update screen

minerva dashboard
Open Updates & account. Container and managed installations show instructions for their own distribution channel.

Keep each package current

The engine, desktop app, and editor extension have separate release packages. An engine update does not install a new desktop app or VS Code extension.

Engine & dashboard

Use minerva update or the local dashboard’s update screen. The dashboard ships with the engine.

Desktop app

Install a published package for your operating system. Use your original package channel for subsequent app updates.

Published desktop packages →

VS Code extension

Use VS Code’s extension update flow for your installation channel. For a locally installed VSIX, install the newer VSIX and reload the extension.

Install the extension →

Release availability

Download the published Linux desktop and VS Code packages from this website. Package checksums are provided; native macOS and Windows app packages are not published yet.

Check available packages →