Family Co-Managed Web Tasks
A family member can guide a parent through a web task on the parent’s own computer, while both approve sensitive steps and passwords, verification codes, and final control remain local.
When adult children want to help their parents request a refund, cancel a subscription, or change account settings, they first write down the task and send a co-management invitation. Their parent opens the invitation on their own computer; the agent browses and fills in forms only on that device, while passwords, verification codes, and identity information always remain local.
The page visualizes every step: which website is opening, what will be entered, and who must confirm next. The remote family member sees only the necessary progress and page explanations, while the parent can always see the cursor and take over at any time. If the agent encounters an unfamiliar page or a changed flow, it stops and identifies the blocked step rather than guessing what to click.
Payments, identity information, account unlinking, and final submission are set as joint-confirmation checkpoints. After the agent explains the outcome about to occur, the parent confirms locally and the assisting family member confirms that the intended goal is correct before the task can continue. When it is complete, both receive the submission receipt, refund reference number, or a list of items that still require the parent to handle personally.
The first version focuses on a small number of high-frequency web tasks, starting with renewals, refunds, and appointments. It does not turn a parent’s browser into a remotely controllable screen-sharing session, and it does not store any site credentials.
Why now
As of August 14, 2026, Pickle Browser ranked No. 4 in Product Hunt’s new-product feed, and locally visible agent browsers are drawing immediate attention. S1 That makes an interaction model for handling web tasks without handing over account access more concrete, and easier for families to understand and try.
Target user
The core user is an adult child who lives apart from their parents. The parent can log in independently but gets lost on refund, subscription-cancellation, or appointment pages. When a charge, deadline, or appointment opening is imminent, neither person can reliably work through buttons one by one over the phone. The adult child needs visibility into progress without gaining control of the entire computer. The parent needs to retain their passwords, verification codes, and final decision-making authority.
Minimal entry point
On desktop, use Electron to host a dedicated Chromium instance, with Playwright executing locally. Prefer role, label, and visible-text locators to reduce script breakage when pages change. S2 The first release should maintain a site whitelist only for refunds, renewals, and appointments. Model every flow as an explicit state machine and pause immediately on unknown pages. Passwords, verification codes, and identity fields exist only in local memory. The remote participant receives only step names, redacted descriptions, and confirmation requests. Payments, account unlinking, and final submission enter a two-person confirmation state. After submission, capture the page receipt and ask users to verify the reference number.
Punching above its weight
Find the first users among adult children caring for parents from a distance. Create short demos around specific tasks, such as the step where a subscription cancellation gets stuck. Publish reusable flows as a public directory and place them in caregiver communities and discussions where older adults seek technical help. Every demo should emphasize local entry of verification codes, confirmation by both people, and the ability to take over at any time. Build search landing pages around combinations of specific sites with “refund” or “cancel subscription” to reach people already seeking help.
Competitors & gaps
- Chrome Remote DesktopGoogle
- Chrome Remote Desktop lets family members provide remote support with a one-time code. Once the recipient agrees, the other person can fully access apps, files, email, and browsing history. Users can stop sharing, and remote sessions are encrypted. S3 It works well for direct troubleshooting between people who know each other, with a mature installation and connection flow. Its limitation is that permission is granted to the entire computer rather than to a defined task. It does not explain the consequences of a refund or account unlinking before acting, nor does it split payments, identity documents, and final submission into confirmations from both people. Older adults must continually assess what the remote family member is doing. Once the task is done, it also lacks a structured record of refund numbers and outstanding actions. This product should retain local visibility and the ability to take over at any time, while sending only necessary progress updates to the remote family member.
- Browser UseGoogle
- Browser Use can already have agents perform web tasks and provides a live browser view. Users can take over the browser for payments, authentication, or review. It also supports saving browser state, including cookies, local storage, and saved passwords. S4 These capabilities suit developers building general-purpose web automation. The gap is that it is designed for one user working with an agent, not for two family members handling a task together. Its existing human-in-the-loop controls mainly address pausing and resuming an agent. It has no built-in family roles, two-person confirmations, or selective disclosure to a remote participant. Saving login state also conflicts with the choice not to retain site credentials. Refunds, subscription cancellations, and appointments would still require the product team to build dedicated flows. The real opening is to narrow a general-purpose agent into family tasks that are explainable and easy to hand off.
How it makes money
Charge a monthly family subscription that covers a small number of household members and co-managed tasks. Refund, renewal, and appointment templates are included. Do not take a percentage of successful complex tasks, so the product has no incentive to push users into granting excessive access.
The case against
Changing web flows can stop scripts outright. Refund and cancellation pages often contain pop-ups, retention steps, and dynamic forms, so maintenance costs rise with the number of sites. If the agent interprets “pause service” as “cancel account,” a single mistake can damage family trust. Two-person confirmation can also create delays and missed deadlines. If remote progress is too heavily redacted, the adult child cannot tell whether the goal is correct; if it is insufficiently redacted, it can expose order, health, or identity information. The first version must strictly limit sites and task types, or support costs will quickly exceed subscription revenue.