Instagram accounts, browser sessions and account matching
How the extension knows which Instagram account you are, and why viewing one account's data and acting as that account are different things.
What this helps you do
Ins Autopilot does not have its own login. It borrows the Instagram session your browser already holds, and that one design choice explains most of the questions people ask about accounts: why there is no password field, why the extension stops when you sign out, and why an action can be refused even when you are clearly signed in.
Understanding the model takes two minutes and saves a lot of confusion later.
The browser session is the only credential
Everything the extension does happens in your own browser, inside the Instagram tab you already have open. It never receives your Instagram password, so there is no credential for it to store, leak or rotate.
The consequence is that it cannot work in the background. This is a browser workflow driven from a live, signed-in session, not a cloud service holding your account.
How the extension knows who you are
- It reads the numeric Instagram account ID from the session cookie the page already holds. That number is what identifies you in the product. It is not your username and not your email.
- You can see it in the footer of the panel. An empty footer means you are not on an Instagram page, or you are signed out.
- The contact ledger is kept per Instagram account in local browser storage and is not uploaded. Tracked links are the exception, where the destination URL and an opaque contact reference go to the server so a click can be recorded.
What happens when you switch Instagram accounts
Sign out and sign in as a different account, and the extension re-resolves everything against the new account. Entitlements and allowances, including the Outreach Trial, which is counted per Instagram sender account, are decided for whoever is signed in now.
A running session cannot carry across. A Follow run, a Bulk queue or a sequence started as one account will not continue under another, because the actions would be attributed to the wrong person.
Viewing data and acting are two different things
Two questions get mixed up constantly. Whose data am I looking at is about the ledger: records are kept per account, so an account's contacts, History and outcomes belong to it alone.
Whose account will perform this action is about execution: a Follow, a Like, a DM or a Comment is always executed by whoever is signed in at that moment. That is why an action can be refused when the account changed after the task was prepared.
When an action is refused
If the account that would have to execute an action is not the account the action was prepared for, the extension refuses it before anything is sent.
That refusal is a protection rather than a fault. Sending as the wrong account would put your message in front of the wrong audience and mix two accounts' records together, and neither is reversible.
If a task is refused right after you switched accounts, the guard is doing its job. Check the footer, then start the task again as the account you actually want to act as.
Limits and important behavior
- Free binds 1 Instagram account. Monthly Pro and Annual each bind up to 3.
- Multi-account management is a Pro capability. On Free, the account you are signed in as is the account you work with.
- Allowances are per account, not per browser. Two Instagram accounts in the same browser each get their own daily caps and their own Outreach Trial.
- The ledger lives in your browser. Clearing site data for instagram.com, or moving to another browser profile, does not carry records over.
Troubleshooting
- The footer shows a different account than the one I meant to use.
- The extension reports what the page reports. Sign in to the account you want, reload Instagram, and reopen the panel before starting any task.
- My task stopped and told me the account changed.
- The task was prepared for one account and would have run as another. Nothing was sent. Confirm the footer, then start the task again.
- Can I run two accounts at the same time?
- Not in one browser session. An action always executes as whoever is signed in, so work one account at a time and switch deliberately.
- I signed in on a second browser. Do I see the same data?
- No. Each browser profile keeps its own local records, even when the Instagram account is the same.
Ready to try it? Ins Autopilot runs in your own browser session — no password, no remote control.
Not installed yet? Start with the setup guide.
