Pi Boomerang

What it does

Pi Boomerang starts an agent task from a command or an optional model-callable tool, then collapses the completed exchange to a generated summary at an earlier session-tree point.

It can expand one prompt template, run an ordered template chain, or repeat a task through bounded rethrow passes with a collapse between passes.

Session context is rewritten, but workspace changes made by the task remain in place.

When to reach for it

Invocation: Run /boomerang with a task. Enable its optional agent tool only when model-initiated boomerang work is wanted.

A long autonomous task should leave a compact record in future context

Run one boomerang task and continue from its generated summary.

Several prompt templates should run in a fixed order

Build a template chain so each step completes before the next and collapse once after the chain.

A full task should receive several independent improvement passes

Choose a rethrow count so each pass starts after the preceding pass has been summarized.

What it adds

• Manual and task-scoped anchors for selecting the session-tree point that receives the compacted branch.
• Template argument expansion plus optional per-template model, thinking-level, and skill selection.
• A heuristic completion summary built from assistant text, file-tool activity, and Bash tool-call counts.

How it fits

No related catalog surfaces are recorded.

Common questions

Does a collapse undo file changes?

• No. Collapse changes retained session context, not workspace state. Edits and other task side effects remain.

Is the model-callable tool enabled automatically?

• No. Tool registration is disabled by default and must be enabled through the boomerang command. Its enabled state and guidance are stored in user configuration.

What can be lost in the compacted record?

• The generated summary is heuristic. It counts recognized tool activity and preserves the last assistant text, so it may omit semantic details not represented there.

It’s working if

• A started task shows boomerang status and returns control after its completed exchange is collapsed.
• Template chains advance in order and restore any saved model or thinking configuration afterward.
• Rethrow passes preserve workspace changes while carrying accumulated summaries into later passes.

Source and setup

Provenance

Project

Pi Boomerang

Origin

Nico Bailon

Current maintainer

Vedang Manerikar

Relationship

fork

Installed source

git:github.com/vedang/pi-boomerang

Source path

View source (index.ts)

Upstream

https://github.com/nicobailon/pi-boomerang

Compatibility

• Pi extension, command, tool, and session-tree APIs
• Pi prompt templates for template and chain execution
• Available Pi models and skills when selected by template frontmatter

License

All rights reserved (no license declared)

License publication scope

Independently written factual prose, source links, and full fork attribution only; no source reuse permission is asserted.

Reviewed revision

12c1b2997c7acc3baa0ee2a88eaa241dafa9cfca

Catalog revision

e0c035a297462c519315abfa1af31a1ed3bd9eef

Setup notes

• Nico Bailon is original author of the upstream nicobailon/pi-boomerang project. This record covers Vedang Manerikar's vedang/pi-boomerang fork and identifies him as current fork maintainer.
• The reviewed fork revision has no license file, and its package manifest has no license field. Treat source and documentation as all rights reserved unless a separate permission applies.
• This guide contains independently written factual prose, source links, and fork attribution only. It does not grant or assert permission to reuse project source or documentation.
• The package manifest exposes one Pi extension entry point and no other installable Pi surface.