Skip to content

Roadmap

OpenLoop is pre-1.0 and develops in the open; the repository is the source of truth. The current direction, roughly in order:

  • Approval packets hardening: richer review context (diffs, validation output) in approval artifacts. Packets exist today (approval); the goal is making them self-sufficient for review without leaving the terminal.
  • Context packs: precomputed repository context to make agent runs cheaper and more consistent across repeated tasks.
  • Scheduled execution, expanded: cron schedules exist per project today; the roadmap adds fleet-level scheduling windows (e.g. “nights and weekends only”) and per-schedule budget caps.
  • Inline OPENLOOP: task markers: define tasks inside code comments and docs, harvested by the daemon as first-class ledger entries.

These were roadmap entries not long ago and are now part of the product, a fair reminder that this page dates fast:

  • Approval packets (approval list / show)
  • Confidence digest (openloop digest)
  • Cron schedules (project.jsonschedule)
  • MCP server (openloop mcp)
  • Web dashboard (openloop dashboard)
  • Issue sync for GitHub and GitLab

Issues and PRs live at github.com/jaltez/openloop. The repo carries a solid test suite (npm test), behavior changes come with tests.