Intelligent Webmail by Rose
Local Gmail development candidate; not approved for live mailbox use. The current source includes a confirmed send route, so this must not be described as drafts-only.
🌹 Rose & Etta · Development started · not released
See whether Intelligent Webmail by Rose fits your workflow
Intelligent Webmail by Rose — problem, solution and source-backed project history from Rose & Etta.
What it aims to address
Email work can pull attention between a ChatGPT task and a separate inbox and drafting workflow. The available project records describe this as a local Gmail workspace candidate; they do not preserve a more specific original…
Scope being explored
- OAuth begins only after a person chooses Connect Gmail
- Gmail read, compose and modify permissions are requested
- Draft creation/editing and a separately confirmed send route exist in source
This page separates documented scope from release claims. Check the status, evidence, privacy notes and limitations below; development progress alone does not mean the Petal is available.
What this Petal is trying to solve
- Email work can pull attention between a ChatGPT task and a separate inbox and drafting workflow. The available project records describe this as a local Gmail workspace candidate; they do not preserve a more specific original incident, so this page does not invent one.
- The project began with a problem John encountered while using ChatGPT. The exact incident is not recorded in the reviewed product brief.
📘 Read Intelligent Webmail by Rose instructions →
What the project explores
A local Gmail workspace candidate brings message browsing, search and drafting actions into one interface after the person starts Google consent. It is not released or approved for a real mailbox. The current candidate also contains a confirmed send route, so it is not accurately described as drafts-only.
⚙️ How it works
The development candidate runs on the local computer. Gmail access begins only after a person chooses Connect Gmail and completes Google consent. The project guide identifies gmail.readonly, gmail.compose and gmail.modify scopes; gmail.compose is send-capable. The interface includes browse/search, archive/move/label/mark-read, thread summaries, inbox digests, limited attachment preview/download, follow-ups, draft create/edit, and a confirmed Send now flow for messages, replies and forwards.
- OAuth begins only after a person chooses Connect Gmail
- Gmail read, compose and modify permissions are requested
- Draft creation/editing and a separately confirmed send route exist in source
- Inbox timers are user-triggered; there is no background poller
- Message text summaries are deterministic/local; the candidate guide says message text is not sent to a third-party model
- Disconnect clears app-local state, but does not undo Gmail changes or remove provider-side drafts/sent messages
Release blocker: the candidate guide documents a mismatch between its in-app privacy message and the actual send route. Do not connect a real mailbox or use Send now until the owner approves corrected disclosures and release status.
Longer-term plans, not current features
- Long-term direction: explore supported providers beyond Gmail, including Outlook, Hotmail, Microsoft 365 and Yahoo, only where each provider API and permission model allows.
- Planned capabilities include inbox reading and search, summaries, composition and drafts, user-authorized sending or replies, attachments, scheduling, follow-ups, customer-configured auto-replies and recurring routines through approved scheduling. Natural-language Rose controls are also a goal.
- These are plans, not current features. The inspected local Gmail candidate uses mocked transports in automated checks; replies remain drafts and no live mailbox send is verified.
🗂️ Project history and versions
These milestones come from the dated local candidate guide, not a complete chat transcript or release history.
- Local Gmail candidate documented
The guide records local-only operation, user-started Google consent, Gmail read/compose/modify scopes, and draft handling. The checked implementation also exposes a separately confirmed send route, so the older drafts-only description is incomplete.
Source record: webmail-by-rose-candidate/CUSTOMER_GUIDE.md - Verification boundary
Automated checks use mocked Google transports; they do not validate access to a live Google account or mailbox.
Source record: webmail-by-rose-candidate/CUSTOMER_GUIDE.md
📷 Screenshot evidence
No verified live Petal screenshot was available in the inspected project records. Artwork on this page is concept art. Add an authentic interface capture here when one is available; no interface image has been fabricated.
This Petal is not sold separately. the only proposed customer product is one £8.99/month subscription for unlimited standard Petals, with no 50-Petal cap; This is not an active offer or checkout. No checkout is active. See subscription proposal.
💬 Help improve Intelligent Webmail by Rose
Share feedback, a bug report or a feature idea by email. No website comment form is active.
Open the Instructions child page for source-backed setup notes and current availability. If a released customer workflow is not verified, that page says so clearly instead of presenting development steps as a public install manual.
Petal information
Availability: Development · unreleased / availability unverified. Check this project page; availability is not independently verified.
- How-to and intended usage
- Installation and setup — planned or unavailable while this Petal remains unreleased.
- Troubleshooting — no release-specific fixes verified.
- FAQ — no additional verified answers recorded.
- Compatibility and requirements — not verified.
- Privacy, permissions, and safety — consult the source page; implementation details unverified.
- Release status and evidence — no release evidence is asserted by this index.
- Support and feedback — support@kingding.co.uk.
🌱 Help shape Rose & Etta
Interested in Intelligent Webmail by Rose?
Beta enrolment is not open yet. Use the early adopter details below to register interest by email and follow the product as it develops. This records interest only; it does not reserve access or start a subscription.
See early adopter details ↓