Register intent.
Projects define the processes Dovik may supervise without exposing environment values to clients.
One owner for every local process.
Dovik starts, observes, and stops the development processes registered to your projects. Humans and coding agents share the same daemon-owned status, logs, and lifecycle controls.
The operator view
See the process Dovik owns before you act.
Section titled “See the process Dovik owns before you act.”dovik tui connects each project and process definition to its current runtime and retained output. The preview below recreates the current tabbed process view with anonymous sample data, without exposing project names, commands, paths, or account data from a real workstation.
- process
- api
- project
- demo
- status
- RUNNING
- command
- npm run dev
process output
earlier lines were discarded; showing the newest output
[stdout] loading configuration
[stdout] compiling application
[stdout] build completed
[stdout] watching for changes
[stdout] request completed
[stdout] change detected
[stdout] compiling update
[stdout] update applied
[stdout] ready
x stop•r restart
One local authority
Stop guessing which terminal owns the app.
Section titled “Stop guessing which terminal owns the app.”Control the whole process tree.
Start, stop, and restart through the daemon instead of signaling guessed process IDs.
Share status and output.
CLI, TUI, and MCP clients read the same current runtime and bounded stdout and stderr events.
Govern project identity.
Personas align Git authors and GitHub accounts without changing the globally active gh account.
Responsibility boundary
Dovik supervises processes. It does not route traffic.
Section titled “Dovik supervises processes. It does not route traffic.”Dovik does not provide DNS, HTTPS, reverse proxying, domains, remote execution, scheduling, or container orchestration. Cadder remains an independent future option for endpoint allocation.