Browser by Rose
A separate browser for Rose Lite tasks: visit websites, take approved actions and return screenshots so you can check the result.
🌹 Rose & Etta · Development started · not released
Your AI gets its own browser. You keep yours.
Rose would use a separate browser session for an approved task, then bring back screenshots and a result you can inspect. Your own browser stays put. No mouse theft; no “done” on faith.
Problems it solves
- Browser windows interrupt your work.
- Chat lanes compete for browser sessions.
- Repetitive website tasks take time.
- Results are difficult to verify without screenshots.
What Rose provides
- Separate browser sessions
- Approved navigation and supported controls
- Screenshots and check results
- Local history controls, if implemented
- Cosmetic RPG ranks; no permission upgrades
The Brave-based development prototype works locally. The proposed bundled Chromium runtime and signed customer release are not complete.
Why this Petal exists
- Automation that grabs your normal browser is a nuisance.
- Shared sessions can collide when chat lanes browse at once.
- Repeating the same web checks is dull work. Even for a wizard.
- Without a screenshot, “it worked” is just a claim in a pointy hat.
- Customers should not need a separate Brave install.
- Updates, privacy and cleanup need a clear plan.
Rose Browser Engine (RBE)
Rather than building a browser from scratch, Rose Lite would use a maintained Chromium runtime. Browser by Rose requests a task; RBE launches an invisible browser process in an isolated profile, runs permitted steps, collects evidence and shuts it down.
No separate Brave or Chrome installation would be needed for customers. The Chromium executable and supporting files would still be bundled with Rose Lite or downloaded during setup. This is not a browser that runs without local files.
Brave remains a supported development engine. A browser-engine adapter would let the Petal use Brave or the future managed Chromium runtime without rewriting its features.
🌹 Rose Lite
Receives tasks and enforces permissions.
🧩 Browser by Rose
Controls sessions and screenshots.
⚙️ RBE
Starts and manages the engine.
🥷 Chromium
Runs invisibly in isolation.
📸 Evidence
Returns verification receipts.
🎮 What it’s being built to do
🥷 Quiet sessions
Browse off-screen, so your normal browser stays yours.
🌐 Approved controls
Visit pages and use supported clicks, typing and scrolling.
📸 Screenshots
Keep visual evidence, so you can see what happened.
🧪 Page checks
Run defined checks and return pass or fail. A green tick is not a guarantee the whole website is perfect.
🔒 Separate profiles
Keep authorised sessions apart. Browser tabs are bad enough without them fighting.
📜 Activity history
Review, export or delete local activity records. These controls are planned, not released.
🏆 Cosmetic RPG progress
Ranks and XP for fun; absolutely no bonus permissions.
📦 Installation, updates and footprint
Goal: one Rose Lite installation. When enabled, Browser by Rose would use an optional managed Chromium component without a separate browser installer, desktop shortcut or Start menu entry.
- Optional download for customers who want browser automation.
- Estimated runtime size: 200–500 MB, depending on platform and build.
- Silent startup/shutdown, isolated sessions and automatic cleanup.
- Crash recovery, timeouts and managed security updates.
- Existing Brave installation can remain an optional supported engine.
- Open-source licences and redistribution obligations must be reviewed before release.
Current state: Brave prototype tested; managed Chromium packaging planned, not implemented.
📅 Development roadmap and estimates
These are indicative engineering estimates based on reusing existing Browser by Rose code. They overlap and are not guaranteed release dates.
| Phase | Estimated effort |
|---|---|
| Managed Chromium runtime | 1–2 days |
| Silent startup/shutdown | 1 day |
| Browser controls | 1–2 days |
| Isolated sessions | 1–2 days |
| Screenshots and testing | About 1 day |
| Rose Lite integration | 2–3 days |
| Reliability and verification | 2–4 days |
Overall planning ranges: 3–5 days for a basic invisible Chromium prototype; 1–2 weeks for a usable Rose Lite development integration; 4–8 weeks for a more robust beta; potentially 2–4 months for commercial release, depending on security, packaging and approvals.
🔒 Permissions, reliability and privacy
- One shared browser engine, separate profiles for authorised chat lanes.
- No interference with customers' everyday browser sessions.
- Explicit consent for sensitive actions, logins and local/private destinations.
- No production Rose API fallback when isolated identity is unverified.
- History, screenshot retention and deletion controls.
- Browser updates, crash recovery, performance and accessibility tests.
- No bypassing website authentication, anti-bot protections or human approvals.
🎨 Artwork and development evidence
These are fantasy marketing illustrations, not screenshots of a released customer product. Local browser tests and the development dashboard have separate evidence.
❓ Frequently asked questions
Do customers have to install Brave?
Not in the proposed customer version. Rose Lite would manage a Chromium runtime itself; the current prototype uses Brave.
Is it really invisible?
Headless browsing runs without opening a normal browser window. Some websites may require visible interaction or user approval.
Can all chat lanes use it?
That is the intended shared capability. Full integration across existing lanes and supported hosts is not yet complete.
Will it run when ChatGPT isn't active?
Not by default. Direct chat work runs during active authorised turns; background execution needs a separately approved service.
Is it available to buy?
No. This Petal remains in development, and the commercial release HOLD is preserved.
Browser by Rose is not sold separately. The Rose & Etta Unlimited subscription proposal is described on the pricing page. Checkout and billing remain inactive.
💬 Help shape Browser by Rose
Have an idea or bug report? Send feedback. This is not a purchase or beta reservation.
🌱 Growing in the Rose & Etta garden
One engine. Multiple Petals. No unnecessary browser windows.
Browser by Rose aims to turn authorised browser work into verified results while keeping your desktop free. Release follows security, integration and signing checks.
Back to Petals in development ↑