Aven

Aven CLI · The local execution runtime

Navigate work that changes as you act.

Aven CLI is the runtime at the center of Aven. It gives people and AI agents a controlled way to move through incomplete, shifting problem spaces—one bounded, observable and reconstructable move at a time.

Download Aven CLI Explore the runtime

01 · The problem

Plans assume a stable map. Real work rarely provides one.

In complex work, the starting state is only partly observed, the goal begins as intent, and each intervention changes the conditions for the next decision.

Static path

Define the destination. Execute the plan.

Useful when the terrain is known and remains sufficiently stable.

Adaptive navigation

Act with intent. Observe the effect. Revise the map.

Required when action reveals or changes the problem itself.

02 · Penbleth

A tabletop model for navigating a changing problem space.

Penbleth is a gamification layer on top of Aven CLI: a project-management board and role-playing model. It makes a bounded part of a tangled real-world problem playable without pretending the whole route is already known.

  1. 01ObserveState, uncertainty and constraints
  2. 02Form intentThe effect worth pursuing
  3. 03ExpectA fallible model of the next effect
  4. 04MoveBounded, authorized and observable
  5. 05CompareExpected effect against reality
  6. 06ReviseMap, claims and the next move

The process remains stable. The scope can narrow. The structure stays open to new evidence.

03 · Aven CLI

The runtime that makes each move controlled.

Aven CLI is not the player. It binds the conditions under which a person or a concrete AI agent may act, produces permitted local effects and keeps the path reconstructable.

01

Scope

What may be observed, changed, claimed and integrated.

02

Context

Only the bounded information required for the selected capability.

03

Tools

Concrete operations exposed through a stable local command layer.

04

Permissions

Explicit permission for a specific operation on a specific target.

05

Gates

Deterministic controls and responsible decisions before effect.

06

Evidence & Memento

Separate records for supportable claims and technical workflow history.

04 · Human and AI

Intelligence chooses a move. Control decides whether it may take effect.

The player

Human or concrete AI agent

Interprets the situation, forms an expectation and proposes the next bounded move.

The environment

Aven

Binds context and tools, checks controls, executes permitted local effects and records the path.

The authority

Owner or delegated gate

Grants decisions and approvals. Capability, model intelligence and recursion create no authority.

05 · Available today

Start with the local Aven CLI.

The current public installer provides the stable command and local effect layer. It can work through your configured Inference Gateway and operate deterministic Workspace tooling within its documented scope.

Available now

Local Session Agent

Run and continue prompt sessions through your configured Inference Gateway while keeping local history.

aven run · continue · history · show · tui

Available now

Local Workspace tooling

Set up, inspect and validate repository-native governance artifacts and execute supported lifecycle commands.

aven workspace setup · overview · validate · create · move

Current boundary: licensed Workspace Agent capabilities and governed sessions require Aven Backend support.

Aven in practice

The CLI turns intent into an explicit next move.

Begin with what is observable. Understand the local workspace. Make a bounded move. Then check the state again. The runtime makes this discipline explicit in each command.

  1. 01 · Observe aven status

    See package identity and workspace readiness.

  2. 02 · Orient aven workspace overview

    Read the governed terrain before choosing a move.

  3. 03 · Act aven workspace move <id> <target>

    Apply one explicit lifecycle change to one item.

  4. 04 · Verify aven workspace validate

    Check the resulting workspace controls for drift.

Explore the current CLI surface Local sessions, workspace navigation and runtime operations

Know where you stand

  • aven statusPackage and workspace readiness
  • aven dependenciesLocal dependency readiness
  • aven rulesGovernance and workflow orientation
  • aven configRuntime configuration

Work through a session

  • aven run <prompt>Begin a local prompt session
  • aven continue <session-id> <prompt>Continue with a follow-up move
  • aven historyList recorded sessions
  • aven show <session-id>Inspect one recorded path
  • aven tuiOpen the keyboard-first interface

Navigate a workspace

  • aven workspace overviewOrient within local governance
  • aven workspace list <type>List governed artifacts
  • aven workspace show <id>Inspect one artifact
  • aven workspace create <type> <title>Create a governed work item
  • aven workspace move <id> <target>Apply a lifecycle transition

Check and govern the move

  • aven workspace validateValidate workspace controls
  • aven workspace sanityDetect Markdown artifact drift
  • aven workspace submit <id>Submit tested work for approval
  • aven workspace accept <id>Record Owner acceptance
  • aven workspace cycleManage Delivery Cycles

06 · Target state

One command layer. More ways to enter. Stronger governed capabilities.

Aven's target architecture extends the same bounded execution model without turning an interface, a model or an agent role into automatic authority.

Target

Backend-supported agents

Planner, Implementation and Reviewer capabilities with controlled system context and governance decisions.

Target

Additional surfaces

Web, IDE, API, CI and job interfaces that resolve to an explicit existing capability path.

Strategic horizon

Evidence-backed improvement

Independent evaluation, complete lineage, exact-build binding and external rollback before stronger claims.

07 · Download and install

Put the command layer in your terminal.

Install Aven CLI, inspect its status, then choose whether to use local sessions or prepare a repository workspace.

Linux / WSL

Shell installer

curl -fsSL {origin}/install.sh | AVEN_DOWNLOAD_BASE={origin}/downloads bash

Windows

PowerShell installer

$env:AVEN_DOWNLOAD_BASE="{origin}/downloads"; irm {origin}/install.ps1 | iex
Direct downloads install.sh install.ps1 aven-cli.tar.gz