​
Overview

The vibekit local status command displays comprehensive status information about sandbox environments, including health checks, resource usage, and configuration details.

​
Syntax

vibekit local status [options]

​
Options

OptionAliasDescriptionDefault
--env <name>-eShow status for specific environmentAll environments summary
--verbose-vShow detailed informationBasic info only

​
Examples

​
Summary View

Show status of all environments: 
vibekit local status
Output: 
📊 Environment Status Summary

📦 Total Environments: 5
🟢 running: 3
⚪ stopped: 1
🟡 paused: 1

🕑 Most Recently Used:
  • dev-env (just now)
  • test-env (2h ago)
  • prod-debug (1d ago)

​
Specific Environment

Check single environment: 
vibekit local status -e my-env
Output: 
📊 Environment Status: my-env

🆔 ID: abc123def456
📦 Sandbox ID: sandbox_789
📊 Status: 🟢 running
🤖 Agent: claude
🧠 Model: claude-3-5-sonnet-20241022
📁 Working Directory: /vibe0
🕐 Created: 2024-01-15 10:30:00
🕑 Last Used: 2024-01-15 14:45:00
✅ Sandbox is healthy and responsive

​
Verbose Output

Detailed information: 
vibekit local status -e my-env --verbose
Additional output includes: 
🔧 Environment Variables:
   NODE_ENV=development
   PORT=3000
   DEBUG=true...
   GITHUB_TOKEN=ghp_xxxx...
   
📊 Resource Allocation:
   CPU: 2 cores
   Memory: 2048 MB
   Disk: 20 GB

🔌 Connections:
   GitHub: ✓ Configured
   API Key: ✓ Set

​
Status Information

​
Basic Information

Every status check shows:
  • ID: Unique environment identifier
  • Sandbox ID: Internal sandbox reference
  • Status: Current state with color coding
  • Agent: AI agent type
  • Model: Specific AI model in use
  • Working Directory: Default path for operations
  • Created: When environment was created
  • Last Used: Most recent activity

​
Status Types

StatusIconDescription
running🟢Active and ready for commands
stopped⚪Inactive but preserved
paused🟡Temporarily suspended
error🔴Failed state requiring attention

​
Health Check

For running environments, performs: 
# Internally runs
echo "ping"
Results:
  • ✅ Healthy - Responds within 5 seconds
  • ⚠️ Unresponsive - Slow or partial response
  • ❌ Failed - No response or error

​
Verbose Mode Details

​
Environment Variables

Shows configured variables (truncated for security): 
🔧 Environment Variables:
   API_KEY=sk-ant-xxxx... (truncated)
   DATABASE_URL=postgres://... (truncated)
   FEATURE_FLAG=enabled

​
Resource Information

Displays allocated resources: 
📊 Resource Allocation:
   CPU: 4 cores
   Memory: 4096 MB
   Disk: 50 GB
   Network: Bridge mode

​
Integration Status

Shows configured integrations: 
🔌 Integrations:
   GitHub Token: ✓ Configured
   Repository: owner/repo
   API Keys: ✓ Claude configured
   Telemetry: ✗ Disabled

​
Use Cases

​
Pre-Operation Checks

Before running commands: 
# Check if environment is ready
vibekit local status -e my-env

# If healthy, proceed
vibekit local exec -e my-env -c "npm test"

​
Troubleshooting

Diagnose issues: 
# Full details for debugging
vibekit local status -e problematic-env -v

# Check all environments for errors
vibekit local status | grep "error"

​
Resource Monitoring

Track resource usage: 
# Check all environments
vibekit local status

# Look for resource-heavy environments
vibekit local status -v | grep -A 3 "Resource"

​
Automation Scripts

Use in scripts: 
#!/bin/bash
# Check if specific environment is running
if vibekit local status -e my-env | grep -q "running"; then
  echo "Environment is ready"
  vibekit local exec -e my-env -c "npm start"
else
  echo "Environment not running"
  vibekit local create --name my-env --agent claude
fi

​
Output Parsing

​
Extracting Information

Get specific fields: 
# Get status only
vibekit local status -e my-env | grep "Status:" | awk '{print $3}'

# Check if healthy
vibekit local status -e my-env | grep -q "healthy" && echo "OK"

# Count running environments
vibekit local status | grep "🟢 running:" | awk '{print $3}'

​
JSON Alternative

For structured data, use list command: 
# Get status as JSON
vibekit local list --json | jq '.[] | select(.name=="my-env") | .status'

​
Status Monitoring

​
Continuous Monitoring

Watch status changes: 
# Check every 5 seconds
watch -n 5 vibekit local status

# Monitor specific environment
while true; do
  clear
  vibekit local status -e my-env
  sleep 10
done

​
Health Dashboards

Create simple dashboard: 
#!/bin/bash
echo "=== VibeKit Environment Dashboard ==="
echo "Time: $(date)"
echo ""
vibekit local status
echo ""
echo "Detailed Status:"
for env in $(vibekit local list --json | jq -r '.[].name'); do
  echo "--- $env ---"
  vibekit local status -e "$env" | grep -E "(Status:|healthy)"
done

​
Troubleshooting

​
Environment Not Found

# List all environments
vibekit local list --all

# Check if name is correct
vibekit local list | grep "my-env"

​
Health Check Fails

# Try manual check
vibekit local exec -e my-env -c "echo 'test'"

# Check Docker container
docker ps | grep my-env

# Restart environment
vibekit local delete my-env --force
vibekit local create --name my-env --agent claude

​
Incomplete Information

# Force refresh
vibekit local exec -e my-env -c "echo 'refresh'" > /dev/null

# Check storage file
cat ~/.vibekit/environments.json | jq '.[] | select(.name=="my-env")'

​
Best Practices

​
Regular Monitoring

  1. Check before operations - Ensure environment is healthy
  2. Monitor long-running tasks - Watch for status changes
  3. Clean up errors - Remove environments in error state
  4. Track usage - Monitor last used times

​
Automation Integration

# Pre-flight check function
check_env() {
  local env=$1
  if vibekit local status -e "$env" 2>&1 | grep -q "healthy"; then
    return 0
  else
    echo "Environment $env is not healthy"
    return 1
  fi
}

# Use in scripts
if check_env "my-env"; then
  vibekit local exec -e my-env -c "npm run deploy"
fi

​
Status Alerts

Simple alerting: 
# Check for errors
if vibekit local status | grep -q "🔴 error:"; then
  echo "ALERT: Some environments are in error state" | mail -s "VibeKit Alert" admin@example.com
fi

​
Performance Considerations

​
Command Speed

  • Summary view: Instant (reads from cache)
  • Specific environment: ~1-2 seconds (includes health check)
  • Verbose mode: ~2-3 seconds (gathers additional info)

​
Optimization

For faster checks: 
# Skip health check (less accurate but faster)
vibekit local list --json | jq '.[] | select(.name=="my-env")'

# Batch checks
vibekit local status  # One call for all

​
Integration with Other Commands

​
Workflow Example

# 1. Check status
vibekit local status -e dev-env

# 2. If healthy, generate code
if [ $? -eq 0 ]; then
  vibekit local generate -e dev-env -p "Add feature"
fi

# 3. Verify still healthy
vibekit local status -e dev-env

# 4. Create PR
vibekit local pr -e dev-env