NATIVE C17 / IN DEVELOPMENT

Desktop & CLI guide

One engine. Two ways to work.

Inspectable networking is the planned free foundation. Desktop adds a native workflow, installers and convenient updates. LaneVertex is independently developed by one person.

What exists today

The native macOS development monitor shows local interface observations and a shared C-rendered policy dropdown. AUTO / CALL / VOD changes a local selection preview; it does not activate a network provider or control CLI transfers.

Read-only LaneVertex macOS development monitor with OS interface counters, closed AUTO selector, USB observed and provider unavailable. — 12 October 2026 · Genuine native macOS development capture. Read-only OS interface counters and sampled rates, closed AUTO policy-preview selector and observed USB adapter. Provider unavailable; enforcement inactive; Internet validity unknown. This image does not demonstrate working transfer jobs, routing, product speed gains or a released application.

CLI: build from source

Source is still private. These instructions are for recipients of an authorized source checkout, not a public installer or package. Run them from the source root on macOS with an existing Apple SDK/clang, Python 3, ripgrep, otool and nm. The local verification script builds and checks the headless executable without downloading packages.

CLI: build from source

LV_CLI0_SCRATCH=/tmp/lanevertex-cli0-check sh ci/check-cli0-macos.sh

Source build and command availability are documented from the current macOS development implementation. CMake configure/build and Windows/Linux execution are not qualified here.

Existing commands

Help, version and static capabilities are offline. Status and interfaces read local OS inventory and cumulative counters once; they do not measure throughput or generate test traffic. JSON uses stable technical keys.

Existing commands

/tmp/lanevertex-cli0-check/lanevertex-release --help
/tmp/lanevertex-cli0-check/lanevertex-release version --format json
/tmp/lanevertex-cli0-check/lanevertex-release capabilities --format json
/tmp/lanevertex-cli0-check/lanevertex-release status --format json
/tmp/lanevertex-cli0-check/lanevertex-release interfaces list
/tmp/lanevertex-cli0-check/lanevertex-release interfaces show ID --format json

Optional foreground download

A separately enabled development build can run one job on one explicitly selected interface. It requires existing libcurl/OpenSSL dependencies. The GUI cannot control that job. Uploads, torrents, shared jobs, IPC, persistent configuration, pause/resume and provider commands are not available in this CLI.

Supply the HTTPS URL through a trusted nonterminal pipe or an already-open current-owner 0600 regular file with no extended ACL. Never put signed URLs or credentials in shell arguments. All three byte limits are mandatory. Computed hashes describe received content; reference-sha256 requires a trusted external digest.

The command shape below is a syntax reference, not a ready-to-run transfer. Replace PATH, ID, N and the integrity choice deliberately; provide protected stdin. This page performs no transfer.

Optional foreground download

lanevertex download run --url-stdin
  --destination PATH --interface ID
  --integrity computed|reference-sha256
  [--expected-sha256 HEX64]
  --max-object-bytes N
  --body-budget-bytes N
  --path-body-budget-bytes N

Planned shared workflow

The target is one controller and engine shared by native Desktop and headless CLI, with the same jobs, policies, budgets and immutable metrics. Current source slices do not yet provide shared-instance attachment or full platform parity.