GitHub-native agent orchestration

Your agents need a quest log.

Rallypoint installs a disciplined loop of planners, workers, reviewers, testers, and fixers into the repository you already have.

npx rallypoint@latest add loop

Tap a stage to preview it, then open its role

Read stateSurvey the roadmap, issues, pull requests, and repository rules.View Planner role
Read stateSurvey the roadmap, issues, pull requests, and repository rules.View Planner role

One shared campaign board

Read state. Claim one quest. Earn the merge.

Rallypoint keeps coordination where the work already lives: GitHub issues are the quest log, branches are active expeditions, and pull requests are the gates every change must pass.

No side-channel database. No agent reviews its own work. No worker carries more than one claimed issue.

Tap a step to see what it does and open the role that owns it.

Survey the roadmap, issues, pull requests, and repository rules.

View Planner role

Assemble the party

Separate roles. Explicit powers. Fewer collisions.

Drop it into an existing repo

One command installs the whole campaign.

Powered by Rallypoint’s own registry and zero-dependency CLI: source-owned, inspectable, conflict-safe, and easy to remove.
npx rallypoint@latest add loop

Installs the campaign pack with Rallypoint’s own conflict-safe CLI.

Conflict-safe Dry-run ready Agent-agnostic

The campaign pack

  • AGENTS.md
  • AGENTIC_LOOP.md
  • docs/AGENT_LOOP.md
  • .rallypoint/LICENSE
  • .rallypoint/config.json
  • .rallypoint/roles/planner.md
  • .rallypoint/roles/worker.md
  • .rallypoint/roles/reviewer.md
  • .rallypoint/roles/tester.md
  • .rallypoint/roles/fixer.md
  • .rallypoint/roles/janitor.md
  • .rallypoint/roles/orchestrator.md

No lock-in, no subscription

You own what gets installed.

  1. Fully customizable

    Every installed file is plain text — roles, config, scripts. Edit it, delete it, rewrite it. There is no proprietary format to work around.

  2. You download the starting point

    “Add loop” writes real files into your repository once. From that moment they're yours to change, not a subscription you keep renting.

  3. The agents live in your codebase

    Every role runs inside your own repository, your own CI, your own credentials. Nothing calls home, because there is no Rallypoint server to call.

  4. Ongoing, non-exclusive MIT license

    What gets installed is MIT-licensed, permanently and non-exclusively. If Rallypoint disappears tomorrow, what's already in your repository keeps working and stays yours.

Proven in the wild

Extracted from the loop that builds Codewright.

Atomic issue claims, strict role boundaries, one-issue branches, independent review, fixer passes, and stale-state cleanup—distilled into a portable repository protocol.

Read the playbook