Keep a task’s position and evidence between runs.

A local JSON pipeline for task lanes, alignment, progress checks and readable state updates.

MIT

Software use follows the repository’s terms. Installation, integration and model usage are separate considerations.

View source & setup guide ↗Discuss setup or integration ↗

Usage pattern

Task lane
Evidence check
Saved position

A guide to how the project is used. Read its requirements and limits before installation.

Your starting point

A long-running task spread across several agent sessions.

Repeated summaries can describe activity without recording concrete progress.

The capability to add

Resume with a clear position and a record of what actually changed.

The pipeline assigns a task lane, checks evidence signals and writes structured position and progress artifacts.

What’s in the project

A tool you can inspect.

Capabilities

Configurable task lanes
A progress gate that rejects summary-only updates
Saved position and readable history

Requirements

Python and a source checkout; not published on PyPI in the reviewed README
Concrete evidence signals for progress checks

Important limits

The published comparison found no next-action-quality improvement over a plain-summary baseline.
Its documented roadmap items are not completed features.

A useful fit

Consider this when…

Developers who need explicit task position and auditable progress records.

A different starting point

Choose another approach when…

Buyers expecting proven reasoning-quality gains from state tracking alone.

Inspect the implementation

Public source, with a specific scope.

The repository and the files below show the implementation available to inspect. They do not establish results for your workflow.

Reviewed source snapshot: 0eb5344dd78d.

Compatibility and behavior must be checked in your environment. No customer-result or quality-improvement guarantee is implied.

Code and implementation help

Choose the help you need.

Software. MIT. Read the repository’s terms and installation guide.

Setup and integration. Bring your current tools, a workflow and your desired result. Scope, fees, delivery and support are confirmed before work starts.

Operating costs. Existing CLI subscriptions, model-provider usage and hosting may apply depending on the tool and your configuration.

Compare published service scopes and prices ↗

Your next step

Inspect it. Then decide what to add.

Use the source and requirements to judge fit. If you want help adapting it to your workflow, start with a scoped conversation.

Discuss Journey Map Thinking setup ↗

No setup fee is agreed or payment taken on this page.