Development preview — not released

Connect Follow and Unfollow Workflows in One Workspace

Planned workflow: Plan follow and unfollow tasks in one Chrome workspace. Reuse filters, keep local task history, and review tool-followed accounts before unfollowing.

How do Follow and Unfollow work together in one workspace?

They use separate, explicitly started tasks with shared local history and tool-followed memory. Completing Follow never silently launches Unfollow; a later cleanup needs a fresh preview and current relationship evidence. Live actions remain unreleased.

Concept illustration of anonymous profile tokens, opposing arrows and a review checklist
Concept illustration of the planned workflow, not an Instagram screenshot or evidence of live compatibility.

Move between tasks in one workspace

Use one task workspace to plan a Follow task and later review an Unfollow task. They remain separate, explicitly started tasks; completing one must never silently launch the other.

We do not sell followers or guarantee follower growth. Live sources, including Location, remain unavailable until real permission and compatibility checks pass.

Use recorded follow memory for later review

Tool-followed rules depend on this extension recording a confirmed Follow. They do not reconstruct activity from other products or infer that a later relationship change was caused by this tool.

Read shared history without losing action context

Shared history lets you compare task configurations and outcomes. Keep action context visible: a confirmed Follow and a confirmed Unfollow describe different events, even for the same person.

Keep each task under your control

For a later cleanup, first choose recorded users, protect exceptions, and create a fresh relationship preview. There is no unattended follow-then-unfollow campaign or cloud schedule in this workflow.

Planned workflow example

Illustration only: this is not a live Instagram execution.

  1. Choose the source and current actor.
  2. Review exclusions and unknown evidence.
  3. Regenerate the preview after any configuration change.
  4. Start only after live capability verification and explicit confirmation.

Is this workflow available for live use?

No. The live adapter is unavailable. Pro cannot guarantee platform permission or successful execution.

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