Roven

Version 1.0.0.

Roven is a native terminal project-memory assistant. The shipped executable is roven. It keeps conversations scoped to the trusted project directory and can register that project for future resume and portfolio work.

Roven is provider-neutral: each user chooses a provider endpoint, model, and API key through a named provider profile. It supports OpenAI-compatible chat-completions endpoints and Ollama Cloud's native HTTPS API. It does not silently choose a provider, append an endpoint path, or execute arbitrary commands.

Current capabilities

• roven auth set creates a named provider profile.
• roven auth list shows saved names, endpoints, models, and the default marker.
• roven auth use lets you choose the default profile by its displayed number.
• roven auth status reports the selected profile without revealing its key.
• roven auth remove <name> removes a profile and its operating-system credential.
• Native Ollama Cloud profiles use https://ollama.com/api/chat and report the provider's real context-window usage as a percentage.
• Bare roven asks whether to trust the canonical current directory for the current launch. Trust is not persisted between launches.
• After trust, the optional root ROVEN.md is loaded as project instructions.
• /register submits the built-in project-registration prompt, prepares the current trusted workspace, reads the codebase, and stores a concise report.
• /generate-resume <job description> generates a Markdown project section using only the job description and stored project summaries. It does not read the workspace or repository, expose provider tools, or invent achievements, metrics, technologies, or responsibilities. Output is stored at %LOCALAPPDATA%\Roven\data\resumes\<uuid>.md.
• /resume opens sessions for the current workspace. Esc cancels an active provider stream while retaining received content.

Agent tools

The Rust harness exposes five local tools:

Tool	Capability	Writes data?
list_directory	Lists immediate entries inside the trusted workspace. It cannot recurse, read file contents, or escape the workspace.	No
read_file	Reads a regular UTF-8 text file up to 50 KiB using a workspace-relative path inside the trusted workspace.	No
prepare_project	Independently canonicalizes and authorizes the requested path, then registers it or replaces its local summary section.	Yes, after validation
list_tools	Returns the available tool names, descriptions, and input schemas.	No
list_project	Returns the names of stored projects in alphabetical order.	No

prepare_project rejects paths outside the launch-time trusted workspace before any Git command, project lookup, or registration write. A successful registration is stored as:

%LOCALAPPDATA%\Roven\data\projects\<project-name>.json

Local data

Roven stores data in the operating-system application-data directory. On Windows the default root is %LOCALAPPDATA%\Roven\data:

provider-profiles.json
projects\<project-name>.json
sessions\<workspace-sha256>\<session-uuid>\meta.json
sessions\<workspace-sha256>\<session-uuid>\events.jsonl
log.md
ollama-stream-failures.log  (created only when an Ollama stream fails)
resumes\<uuid>.md

API keys are stored only in the operating-system credential store. Session events.jsonl contains user, assistant, reasoning, error, and structured function_call_output records with the tool name, input, and output. Successful read_file results are therefore persisted as part of session history and can be sent back to the selected provider on later turns or resume. Do not place secrets in project files. log.md contains operational diagnostics only; the separate Ollama failure log can contain raw model output and tool-call arguments.

Current boundaries

Roven can load the optional root ROVEN.md and read regular UTF-8 project files up to 50 KiB through read_file, using workspace-relative paths inside the trusted workspace. It does not provide arbitrary command execution, automatic provider retries, or automatic project-context summarization. The agent only receives data returned by the available tools and the optional root ROVEN.md. Resume project-section generation uses stored project summaries as its sole project evidence and performs no workspace/repository reads or provider-tool calls.

Install

Install a released Windows build

Download roven-windows-x86_64.zip from the latest GitHub release, verify its SHA-256 checksum, and place roven.exe in a directory on your user PATH. Open a new PowerShell session, then run roven --version.

Build and install from source

From this repository in PowerShell:

powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1

Open a new PowerShell session, change to the project directory, and run:

roven

See docs/SETUP.md for provider profiles and API-key setup. See docs/PROVIDERS.md for exact Ollama Cloud and OpenRouter commands, endpoint selection, and context-usage troubleshooting. See docs/TOOLS.md for the local tool reference.