Start

Using Jeden

A reliable run has four explicit inputs: workspace, objective, authority, and verification.

Choose the workspace

--cwd establishes the project root used by context discovery and workspace-jailed tools. Start Jeden at the narrowest directory that contains the task.

State the observable outcome

Name the behavior to change, constraints that must remain true, and the command or scenario that proves completion. Put durable project rules in JEDEN.md or AGENTS.md; keep one-off instructions in the prompt.

Grant only required authority

Read-onlyDefault; suitable for inspection, explanation, and planning.
--allow-writeExpose guarded file and structured-data mutations.
--allow-commandExpose shell, process, package, and evaluation operations.
--auto-approveSkip eligible prompts only inside an independently trusted isolation boundary.

Review the evidence

Read the final answer together with the session’s tool results, artifacts, usage, and approval events. A confident statement is not a substitute for an executed verification path.

Stay in the loop. Never miss out.

Subscribe to our newsletter and unlock Wisent insights.