Development preview — not released

Review Task History and Export Results

Planned workflow: Review local task results, inspect activity logs, and export CSV files. See confirmed, skipped, failed, and unknown outcomes without hiding uncertainty.

Are task history, action records and followed memory the same data?

No. History is an ended-task display archive. Execution records describe attempts and outcomes; action memory prevents unsafe duplicate writes; followed memory records tool-confirmed follows. History capacity or deletion must not erase those safety records.

Read each result status

Confirmed records an acknowledged success; Rejected records a known unexecuted attempt; Unknown preserves uncertainty. Skipped explains why a candidate did not proceed.

Search completed tasks

Task History is the ended-task archive, with planned capacities of 50 for Free and 10,000 for Pro per actor. Search and capacity behavior still need full UI acceptance.

Copy or clear diagnostic logs

Diagnostic log cleanup is separate from execution evidence. Clearing logs must not remove an unknown-action guard or create permission to retry a write.

Export and manage local storage

Export reviewed results as CSV and create a local backup for broader data recovery. History deletion must preserve Followed Memory and unresolved safety records.

Official sources & scopeChrome: storage and cookies — Local extension storage and service workersChrome: extension service worker lifecycle — Worker termination and persistent state

These sources explain platform behavior. Product-specific scope and limits come from our implementation registry; they are not an endorsement by Instagram, Google, or Stripe.

Current Instagram settings and live source behavior are not yet verified. These links support only the topics named beside them.

Your next step

View release status