Let your agent go into your portals with your session and bring back the data

Who it is for

Administrators and owners who every week log in to five different portals (bank, suppliers, invoicing, sales platforms) to pull the same report or fill in the same form.

The problem

AI agents can reason but cannot get into your portals: they do not have your session, captchas stop them and sharing passwords with them is a terrible idea. So you keep doing the repetitive work yourself.

Ingredients

• An agent that runs commands: Claude Code, Cursor, Codex or another compatible one
• The browser where you already have your sessions signed in
• The repository's CLI and extension (bsk)
• A repetitive read-only task to start with: pulling a report, checking a status

Step by step

1. 1

   Choose a read-only task

   The first task never writes or pays: "go into portal X and bring me the balance" or "download this week's sales report". That way you learn the flow without risk.

2. 2

   Install the CLI and the extension

   Follow the README for your system. The extension installs in the browser you use every day; the CLI is what the agent runs.

3. 3

   Open a session and ask for the first task

   From the agent, ask for the task in plain language. You will see a separate window where the agent browses with your session. According to the README, if a captcha or a login appears, it asks you to take control and then continues.

4. 4

   Verify the result against the portal

   During the first week, compare what it brought you with what you see yourself. When it matches ten times in a row, trust it.

5. 5

   Write the task down as a routine

   Save the exact request that worked. Next time it is one sentence. If you want, schedule a weekly reminder to trigger it.

Replace what is in brackets with your company details, or use the guided mode above: it asks you and fills it in for you.

# Role
You are my operations assistant at [COMPANY NAME]. You have access to my browser with my sessions signed in, through the connected browser tool. You only read and download; you never submit payment forms or change settings without my confirmation.

# Context
The portal is [PORTAL NAME AND WHAT YOU USE IT FOR, FOR EXAMPLE "the Mercado Libre sales dashboard"]. The data or report I need: [WHAT YOU NEED TO PULL]. Frequency: [HOW OFTEN YOU NEED IT].

# Task
Go into the portal with my session, navigate to the indicated data or report, download or copy it, and give it back to me in an orderly way. If a captcha, a login or any confirmation appears, stop and ask me to take control; when I hand it back, continue.

# Output format
First, the requested data or table. Then, one line with the date and time you pulled it and the exact URL it came from. If something does not match what was expected (for example, the report is empty), say so before delivering it.

# Examples
Request: "Pull this week's sales". Expected output: a table with day · orders · amount, followed by "Extracted on 2026-09-22 at 10:14 from https://…".

What usually goes wrong

• ✕Starting with a task that writes or pays. The first mistake costs you your trust; start by looking.
• ✕Not verifying during the first week. A portal changes a menu and the agent can bring back the wrong report with total confidence.
• ✕Automating sites that forbid it. Read the portal's terms; if they do not allow automation, the convenience is not worth the risk of losing the account.