Skip to main content

Prerequisites

  • Java 21+ — check with java -version. Install via SDKMAN: sdk install java 21.0.9-librca
  • An API key for at least one provider:

Install

Each release publishes two jars. The one you run is loopy-<version>-exec.jar — the self-contained executable image, attached to the GitHub Release. The plain loopy-<version>.jar on Maven Central is a library jar for embedding Loopy in Java code and is not runnable with java -jar.
1

Download the executable jar

2

Check the download

--version and --help work without an API key, so you can confirm the download before setting up a provider.
3

Run it

The TUI launches with a chat interface. Type a message and press Enter.

Launcher script

The launcher finds the jar, checks for Java, and applies the JVM flags Loopy expects:
Keep the script beside the jar, or set LOOPY_JAR to the jar’s path. Windows users want loopy.bat from the same location.

JBang

Requires Loopy 0.5.0 or newer.

Build from source

Embed the library

Your First Session

Loopy starts in interactive TUI mode by default — a terminal chat interface with real-time agent feedback and a spinner while the agent thinks. Try giving it a coding task:
The agent reads your codebase (via CLAUDE.md if present), plans the change, edits files, and verifies the result. You see token usage and estimated cost after each response:

Three Execution Modes

Slash Commands

Lines starting with / are intercepted before reaching the agent — no LLM tokens consumed.

Add Project Context

Create a CLAUDE.md file in your project root. Loopy reads it automatically and appends it to the agent’s system prompt — same convention as Claude Code.
No CLI flags needed. The agent sees your conventions on every turn.

What’s Next

Extending Loopy

Custom skills, subagents, tool profiles, and the programmatic API

CLI Reference

All flags, options, and configuration