Repository navigation
v2.2.0 — Instagram cookie imports and reliable account states
karilaa-dev
Kyryl Andreiev
Instagram accounts can now use browser cookies with saved password/2FA recovery. Ambiguous failures no longer permanently exclude working accounts.
Changes
- Import browser cookie exports directly, or include cookies with username, password and TOTP credentials in JSON/CSV. Working cookies take priority over password login.
- Update existing accounts through either credential format. A verified replacement cookie session can reactivate an account; login-only updates retain its existing session and dead status.
- Recover explicitly expired sessions using saved password/2FA credentials on the same device and proxy. Concurrent requests share one recovery attempt, and replacement sessions are saved before use.
- Retry bare HTTP 401/403 responses, network errors, malformed metadata and unknown API failures on another eligible account without marking the failed account dead. Retries do not revisit accounts already tried for that request.
- Continue disabling accounts for explicit restrictions/challenges or unrecoverable session/credential failures, with specific persisted reasons. Rate limits use temporary cooldowns; ambiguous login/bootstrap failures preserve the account.
- Prevent late failures from an old session from disabling its verified replacement.
Upgrade
Startup adds cookie and login-credential columns and makes stored Android authorization nullable. Keep the existing database/schema and proxy configuration; stop the previous instance before starting its replacement. Older releases cannot load cookie-only rows, so account for this before rolling back after cookie imports.
Password/TOTP backups are retained privately for recovery and are not returned by the account API. Existing dead flags are not automatically cleared: import a verified replacement cookie session to reactivate an account. Adding login credentials alone does not reactivate it.
Account import and update guide · Configuration and failure handling
Validation
The release tree matches the reviewed and tested PR #27 head. Regression tests reproduce the original failures on the previous implementation and pass with the fix. Local make check and make lint passed, including PostgreSQL integration and race tests. PR CI passed tests, Docker and Railpack checks, with no unresolved review findings.