<p align="center" <img src="assets/readme-banner.webp" alt="jeden by Wisent" width="100%" </p <!-- wisent-banner:end --
Jeden: The Ultimate Self-Improving Coding Agent with Internet Access, Embedded Secret Management, QA, and More
The Ultimate AI Agent for Autonomous Company Building.
Jeden is a harness for AI Agents built from real-life experiences. It routes your models intelligently, manages credentials, understands how to pursue, complete and verify tasks over time. Turns your AI into a 10x harness. Compatible with OpenAI, Anthropic, Kimi and any other model.
The Ultimate Self-Improving AI Harness. Delivered by the Wisent Team and incorporating our custom solutions into one agentic form. Experience the power of Weles (Browser Use), Skarbiec (Credential Management), Stado (Fleet Management), Tama (Automatic Blocks, Sandboxing and Hooks), Probierz (Autonomous QA), Most (Connectors), Brama (Model Routing) and Oko (Team Strategy Management Tool).
Problem and intended users
Wisent engineers run coding agents against production-adjacent repositories and need the agent's inference path, spend attribution, and tool permissions to remain under Wisent's control rather than a third-party hosted agent's. Hosted agent products route prompts and code through external infrastructure, bill through opaque accounts, and enforce tool policy server-side.
Jeden serves two audiences:
- Wisent engineers, who run interactive and one-shot coding tasks in the terminal with local approval over every write and command;
- Wisent tooling and automation, which drives the same harness through its machine interfaces (RPC, ACP, headless mode, SDKs) inside editors and workflows.
Product boundaries
Included capabilities are listed under Current scope. Explicit non-goals:
- Jeden is not a hosted or multi-tenant service; it is a local harness.
- Jeden's local runtime is usable without a hosted Wisent account.
- Jeden does not provide model inference itself; it uses Brama or another compatible OpenAI-style endpoint and caller-supplied credentials.
- Jeden never handles cardholder data; commercial billing is owned by Wisent Platform Billing.
- Jeden does not define autonomous objective pursuit; Pursuit owns intent distillation, outcome contracts, independent reviews, repair loops, validators, and receipts, while Jeden supplies model conversations and tools through the integration interface.
Supported promoted environments: Stado builds darwin-arm64 and linux-amd64 from .wisent-release.json. The Windows native build remains checked by CI; the release manifest does not declare a Windows fleet runner or pretend another platform produced Windows bytes.
Operator-managed and external: the Brama URL and signing credential (Stado/Skarbiec-managed), Wisent Platform Billing configuration, and MCP server configuration.
Core use cases
- Interactive task with approvals. A Wisent engineer in a project checkout wants a code change executed and reviewed. They run jeden and type the task; the agent works through jailed tools, and every file write or shell command pauses for interactive approval unless explicitly enabled. The result is the applied change with visual diffs and a full transcript under ~/.jeden/sessions/. Constraint: no write or command executes without a grant, and destructive confirmations default to Cancel.
- One-shot scripted task. Automation needs a bounded task without a terminal. It runs jeden run "<task", optionally with --allow-write or --allow-command. The result is the final answer on stdout with the session recorded. Constraint: grants are explicit per invocation, and failover never occurs after model output has become visible.
- Continuing prior work. jeden resume <session inherits both conversation history and retained requests, then inspects existing results before continuing. jeden todo list --session <session shows the same request, acceptance and verification state without running a model.
- Editor and machine integration. An editor extension or a CI job needs the same harness programmatically. It uses jeden acp, jeden rpc, jeden headless, or the TypeScript/Python SDKs. The result is protocol-level access to the same run loop; non-terminal output is deterministic text.
- Autonomous outcome pursuit. An operator has a rough objective but cannot stay present to correct each interpretation. They run jeden pursue "<objective" with explicit execution grants. Pursuit recovers and reviews the finish line; Jeden supplies its Brama-backed conversations and approval-gated tools to the accepted execution stages. The result is a durable contract, verdict, receipt, and stage-session provenance under <cwd/.pursuit/runs/.
Design contract
Jeden separates five concerns: