Start

Getting started

Validate your private preview package, point Jeden at a repository, and complete a first read-only task before granting additional authority.

Prerequisites

A signed Jeden release supplied through the private preview channel.
An approved Wisent model entitlement or an operator-provided route through Brama.
A project directory the current user can read.

Safe default

Jeden starts with always-ask approval policy. Begin read-only. Grant writes or commands only when the task requires them.

Validate the runtime

Confirm the binary

Print the installed release identity.

Terminal

$ jeden --version

Check the environment

Run diagnostics for the current workspace. JSON mode is suitable for automation.

Terminal

$ jeden doctor --cwd .
$ jeden doctor --json --cwd .

Inspect the capability registry

Confirm which tools, commands, views, services, plugins, and MCP servers are healthy.

Terminal

$ jeden capabilities --json --cwd .

Configure a managed route

Operator-managed installations provide these values without putting them in project files. A direct deployment requires the following runtime environment:

Environment

BRAMA_URL=<brama-url>
WISENT_APP_AGENT_ID=wisent-app
WISENT_APP_AGENT_AUTH_SECRET=<signing-credential>

ENTITLEMENTS_ROUTER_BIN optionally overrides the executable used by authentication status and reauthorization commands.

Run the first task

Interactive

$ jeden --cwd ../content-platform

One shot

$ jeden run "summarize package.json" --cwd .
$ jeden run "create notes.txt" --cwd . --allow-write

The second command exposes write-capable tools but does not bypass the configured approval mode. Use --yolo or --auto-approve only in an already isolated environment.

Add project context

Create a JEDEN.md or AGENTS.md in the repository. Jeden discovers context from the project ancestor down to --cwd. Keep requirements concrete: commands, boundaries, architecture, and verification rules.