Skip to content
Jorli CLI

Install

Jorli Agent targets .NET 10 and installs alongside both broker CLIs. The broker binaries must exist even if you normally use only one account.

From a repository checkout

Section titled “From a repository checkout”

The current distribution path is the checked-out Jorli repository. Release installers may later wrap the same build, but do not download an unofficial jorli binary.

Terminal window
export PATH="$HOME/.dotnet:$PATH"
cd jorli-agent
./install/install.sh

Windows PowerShell:

Terminal window
cd jorli-agent
./install/install.ps1

The scripts install or upgrade kite and dhan, build and bundle the Angular dashboard, publish a platform-specific self-contained single-file jorli, and place it in the user-level binary directory. The .NET 10 SDK and Node.js are build-time requirements for this source distribution; the installed jorli does not require a separate .NET runtime. The scripts never configure broker credentials.

Development run

Section titled “Development run”
Terminal window
export PATH="$HOME/.dotnet:$PATH"
cd jorli-agent
dotnet run --project src/Jorli.Agent.Cli -- doctor
dotnet run --project src/Jorli.Agent.Cli --

First setup

Section titled “First setup”
Terminal window
jorli setup
jorli doctor

Interactive setup can store an AI provider key without echoing it. The --api-key command flag is intentionally rejected because command arguments leak into shell history and process listings. You may instead set JORLI_AI_API_KEY for the current process.

Authenticate brokers independently:

Terminal window
kite auth login --json --no-color
dhan auth status --json --no-color

See the Kite auth guide and Dhan auth guide for credential setup.

Doctor checks

Section titled “Doctor checks”

jorli doctor reports the data directory, SQLite migration, supported Kite/Dhan versions, authentication state, AI configuration, global kill state, and background-worker heartbeat. It exits non-zero when a required binary is missing, below the configured version floor, or the local database is unusable. Authentication and a stopped worker are warnings until the corresponding workflow needs them.