Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vers.sh/llms.txt

Use this file to discover all available pages before exploring further.

​
vers status

Get status of VMs.

​
Usage

vers status                          # Show all VMs status
vers status [vm-id|alias]            # Show specific VM information

​
Examples

​
Show all VMs (default)

vers status
HEAD status: vm-abc123 (State: Running)

Fetching list of VMs...
Available VMs:

VM: web-server
State: Running

VM: vm-def456
State: Paused

VM: feature-auth
State: Running

​
Show specific VM details

vers status vm-abc123
Getting status for VM: web-server

VM details:
VM: web-server
State: Running

​
How it works

The status command has two modes:

​
Default mode (no arguments)

  1. Shows HEAD status: Displays current HEAD VM and its state
  2. Lists all VMs: Shows VM names and their states

​
VM mode (VM argument)

  1. Resolves VM: Finds VM by ID or alias
  2. Shows VM details: Displays VM name and state

​
HEAD status variations

​
Normal HEAD with running VM

HEAD status: vm-abc123 (State: Running)

​
HEAD with VM alias

HEAD status: web-server (State: Paused)

​
No .vers repository

HEAD status: Not a vers repository (run 'vers init' first)

​
Empty HEAD

HEAD status: Empty (create a VM with 'vers run')

​
HEAD verification failed

HEAD status: vm-abc123 (unable to verify)

​
Output format

​
VM list format

  • VM name: Shows alias if available, otherwise VM ID
  • State: Current VM state (Running, Paused, Stopped, etc.)

​
Error handling

​
VM not found

vers status nonexistent-vm
Error: failed to find VM 'nonexistent-vm': not found

​
No VMs exist

vers status
HEAD status: Empty (create a VM with 'vers run')

Fetching list of VMs...
No VMs found.

​
API failures

vers status
Error: failed to list VMs: connection timeout

​
Use cases

​
Environment overview

# Check what's available
vers status

# Check specific VM
vers status my-vm

​
VM monitoring

# Check specific VM state
vers status my-web-server

​
Debugging

# Check HEAD status
vers status

# Verify specific VM
vers status problematic-vm

​
Prerequisites

  • For VM details: Network connectivity to query API
  • For HEAD status: .vers directory (optional, shows warning if missing)

​
See Also