looper logo

looper

Free

Cron-style manager for AI agent loops: cheap checks, fresh agent sessions only when there is work, one agent per task.

Visit Website
Related by shared tags and keywordschrome-bridgemolipanoma
ai-toolsaiai-agentsai-loopsautomationai assistant

Overview

Looper is a manager for agentic loops that schedules AI agents like cron jobs, allows users to watch them work in real terminals, and aims to stop burning tokens on idle polling. It inverts the typical loop by using a cheap check script and optionally a small classifier model to decide whether there is work, and only then starts a fresh agent session. This design avoids idle token burn and context rot, ensuring at most one agent per task.

The system supports cron-style scheduling with wall-clock slots, timezones, and schedule end dates, as well as manual tasks. Each run starts a fresh session, preventing context accumulation; the agent signals completion with 'looper-done', files a report, and the loop resumes. Monitoring is built in, with per-task run logs, live status, and a real terminal tab that can be watched and typed into mid-run. System notifications can be configured per task, from errors-only to every run.

Looper is compatible with any harness or environment, including Claude Code, Codex, or custom agent CLIs, and can run on Windows driving agents inside WSL, or Linux/WSL directly. Task setup is done through an editor with Schedule, Check, Classifier, and Agent tabs, templates, import/export, and agents or scripts can register tasks by dropping a JSON file in the inbox. The check and classifier are optional; without them, every slot goes straight to the agent.

Pricing

Free

Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.

Visit Website

Prices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.

Use Cases

  • Teams use Looper to schedule AI agents like cron jobs for periodic tasks.
  • Developers use Looper to avoid wasting tokens on idle polling by gating agent runs with a check script.
  • Operators use Looper to monitor agent runs in real terminals and interact with them mid-run.
  • Users use Looper to receive system notifications for task runs, from errors-only to every run.
  • Teams use Looper with various agent harnesses like Claude Code, Codex, or custom agent CLIs.
  • Scripts and other agents use the looper CLI and inbox drop-folder to register and control tasks.

Features

Schedule agents with cron style triggers

Start tasks through watcher commands

Check for work before launching agents

Use fresh agent sessions per run

Keep at most one agent per task

Inspect runs reports and full conversations

Watch and type into live terminals

Run Claude Code Codex or custom CLIs

Reviews

No reviews yet. Be the first to share your experience!