The integration reuses browser sessions across runs; TinyFish had described its underlying Context Profiles feature in June.
By [Ryan Merket](https://runtimewire.com/author/ryan-merket)
· Published
Primary source: [X](https://x.com/shengkunye/status/2105382345092264390)
Why it matters #
Persistent browser sessions let agents work through logged-in sites without a fresh human sign-in on every run, extending agent access beyond APIs. They also give those agents continued access to private accounts, making session isolation, revocation and limits on what an agent can do central product questions.
Monid has added a TinyFish-powered workflow that lets AI agents reuse authenticated browser sessions across runs, with LinkedIn, Amazon, Workday, Facebook and Instagram among the examples. Shengkun Ye, Monid's co-founder, described the integration in a September 30th post on X: users sign in once in a browser, and later agent runs start with that account already logged in.
https://x.com/shengkunye/status/2105382345092264390 The operational change is narrow but useful: instead of an agent confronting a login page every time it opens a fresh browser, a person signs into a managed browser session and saves the authenticated state. Monid's guide to the TinyFish integration walks through the flow using LinkedIn, and lists Amazon, Workday, Facebook and Instagram as additional examples. Monid says the password does not reach the agent. Its post shows a human completing the initial sign-in in the browser that Monid opens, after which an agent can continue the task in an authenticated session.
The capability underneath is older than Ye's announcement. TinyFish described Browser Context Profiles in a June 11th post, saying the feature captures a session after one-time authentication and restores it at the start of later runs. That earlier description also says a profile can be used by parallel agents, with one run able to update the saved session while others read from it. Monid's September post is therefore best understood as making TinyFish's persistent-session mechanism available through Monid's agent-facing tool layer, rather than as the first appearance of the underlying browser feature.
Ye's product history makes the integration fit Monid's broader pitch. Before Monid, he led payments-risk products at TabaPay and says he built its first real-time monitoring product; his personal site also lists A01, a personal news agent, and Dim, a note-taking product that links related concepts. Monid's premise is that agents should be able to find and pay for tools as needed instead of relying on people to create accounts and manage separate subscriptions. Persistent browser access extends that idea to sites that expose useful data or actions through a logged-in web interface rather than an API.
The pricing on Monid's guide is specific: it lists a signed-in browser action at $0.015, a browser session that a developer drives directly at $0.002 per minute, and creating and saving a login profile at no charge. Monid says charges are settled from a single balance. These are Monid's published rates, not an independently tested comparison; the guide's comparison with other browser services uses prices from their respective pricing pages.
Persistent sessions also change the risk profile. An agent with a saved login can reach private account data and may be able to take actions as the user. TinyFish's documentation says its separate Vault product keeps credential values out of the model's context and can be used to re-authenticate when a session expires. The vendor also cautions that a saved profile does not prevent a site from expiring a session, requiring multifactor authentication or presenting a CAPTCHA. Those safeguards do not remove the risk of an agent misusing a session it already holds, including after being manipulated by hostile page content.
Monid's public guide does not spell out how long saved sessions persist, how a user revokes a profile, how profiles are isolated between accounts, or which actions require human confirmation. Those details determine whether the feature is suitable for sensitive accounts, beyond the convenience of skipping repeat logins. For now, Monid's stated setup is explicit: the person signs into each account in the browser once, and each later run can reuse that saved state.