PRODUCT GUIDE / LVCT 0.1.0

CLI reference

Everyday commands, their effect and completion behaviour.

Start, inspect, stop

Start retains running containers. Stop and restart ask for confirmation because position management pauses. They do not close broker positions or remove broker-side SL/TP. The CLI has no test-order command.

Terminal

lvct start
lvct status --json
lvct open
lvct stop
lvct restart

Health and logs

Doctor checks dependencies and configuration. Health checks component readiness. Errors groups recent failures with guidance. Logs can filter severity, service, time and text. JSON output is available for automation.

Terminal

lvct doctor --json
lvct health --json
lvct errors --since 2h --json
lvct logs --service app --level error --since 30m
lvct logs --level critical --contains timeout

Commands that stay open

logs -f, health --watch and remote open stay in the foreground until Ctrl+C. Builds can exceed 40 minutes on first installation. Do not interrupt a healthy build with a short automation timeout. Most bounded diagnostic calls take seconds, but Docker/SSH checks can total several minutes.

Terminal

lvct logs -f --service app
lvct health --watch --interval 10