Skip to content
Dovik logo Dovik

Getting started

Install

Section titled “Install”

Install Dovik and the matching native package with npm:

Terminal window
npm install --global dovik

The npm package exposes dovik and dovikd. It does not replace or configure your gh command.

Dovik 1.1.0 also provides four portable archives on the GitHub Release page:

  • dovik-v1.1.0-windows-x64.zip
  • dovik-v1.1.0-linux-x64.tar.gz
  • dovik-v1.1.0-macos-x64.tar.gz
  • dovik-v1.1.0-macos-arm64.tar.gz

Unpack the archive and place dovik and dovikd on your PATH. Keep the bundled gh proxy outside your normal PATH until you intentionally configure identity enforcement.

Confirm the binaries before starting anything:

Terminal window
dovik --version
dovikd --version
dovik --help
dovikd --help

Start the daemon

Section titled “Start the daemon”

Run dovikd in a terminal or through your user-level service manager. It owns the registry and every managed process until it exits.

Terminal window
dovikd

Native Windows clients use a current-user Named Pipe. Linux and macOS clients use a private Unix Domain Socket. Dovik does not listen on a TCP port.

Register your first process

Section titled “Register your first process”

Use an absolute project root and the executable you normally run for that project:

Terminal window
dovik project add --id storefront --root /absolute/path/to/storefront
dovik process add --project storefront --id web --command npm --arg run --arg dev

Start it and inspect the daemon-owned result:

Terminal window
dovik process start --project storefront --process web
dovik process status --project storefront --process web
dovik process logs --project storefront --process web --tail 100

Stop the complete process tree with:

Terminal window
dovik process stop --project storefront --process web

Next, open dovik tui or connect an agent through dovik mcp.