Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Command compatibility: New vibe-viewer and vibe-sketcher launchers require rename-aware builds. For current published archives or available public snapshots, use vibe-view and vibe-sketch; these deprecated commands remain supported with no removal date. vq is unchanged. Compatibility guide.
vibe-scheduler (vq) 1.0.2
Light Logo Dark Logo
vibe-scheduler (vq) 1.0.2

By audience

  • Running jobs
    • Tutorials
    • Asking for CPUs, memory and time
    • Arrays, dependencies, chains and reruns
    • Managing jobs: names, pausing, stopping, rerunning and cleaning up
    • Machines with and without a batch scheduler
    • Adding programs
    • Running vibe-qc calculations
    • vibe-sketcher and vibe-viewer with the queue
    • Running ORCA and CRYSTAL
    • Troubleshooting
    • vq ABORTED_BY_QUEUE — when the queue ends a job
    • vq retry — automatic re-enqueue on failure
    • vq throttle — soft CPU priority control
    • TREXIO export and READ through vq
    • Read-only resource estimates
    • Calculation campaigns
    • Running VASP
  • Running a host
    • Installing vq on machines and clusters
    • Compute hosts — what to record about one, and why
    • Reaching the queue from the internet
    • vq daemon lifecycle contract
    • vq web dashboard – access + auth
    • vq cgroup setup - delegation and fallback detection
    • Managed local Docker jobs
    • vq drain - temporary dispatch gate
    • vq auto-cleanup
    • The vq fleet console
    • Operating the public fleet snapshot
    • Multi-user deployment runbook
    • Retiring multi-user mode on compute-d and compute-a
    • Repair recorded paths after a state-root move
    • One directory layout for every host
    • Scheduler runtime deployment
    • Retained managed generations
    • Limiting scheduler load
    • Build once: portable runtime bundles
    • Runtime benchmark campaigns
    • Submission gateway (#163)
    • Explainable placement plans
    • Runtime slots: moving a program to verified generations
    • Refreshing scheduler runtime admission
    • Native install seeding for runtime slots
    • Operations runbook
    • Driving vq from a script
    • Host recovery channels — the 3-tier contract
  • The agent contract
    • Agent interaction protocol – compute-d / compute-a (and any other vq-managed host)
    • Driving vq from a script
    • vq Long-Term Design Specification
    • Operator prompts for the release + upgrade chats

Reference

  • Clone, download, and install
  • Driving vq from a script
  • vq ↔ vibe-qc version compatibility
  • Release codenames and artwork
  • Release process
  • Distribution builds
  • Tests and validation
Back to top
Copyright © 2026, Michael F. Peintinger
Made with Sphinx and @pradyunsg's Furo