RDC by Rose
Authorized remote-computer access, file and process workflows, with permission-aware execution.
🌹 Rose & Etta · Development started · not released
See whether RDC by Rose fits your workflow
RDC by Rose — problem, solution and source-backed project history from Rose & Etta.
What it aims to address
Remote computer tasks can be fiddly and easy to lose track of. RDC is designed to make authorized workflows clearer and more manageable.
Scope being explored
- Less network overhead for local calls: a supported client on the same PC can call the local listener directly. The timings above cover local HTTP…
- Permission-aware access: the development listener binds to 127.0.0.1, authenticates requests with an ephemeral bearer token and exposes a restricted…
- Local operation without a remote endpoint: localhost tests ran without a remote service. The PC, local client/model and required local services still…
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
- Remote computer tasks can be fiddly and easy to lose track of. RDC is designed to make authorized workflows clearer and more manageable.
- The project was created in response to a problem John encountered while using ChatGPT. This is the problem statement preserved in the available project brief; no unverified personal incident is added.
📘 Read RDC by Rose instructions →
Read the measured troubleshooting workflow and copyable diagnostic prompt. It does not promise a universal fix.
Intelligent remote desktop control, designed local-first
RDC by Rose is exploring a local-first option for supported computer operations. In the current development build, a compatible local client can call an authenticated MCP server on the same PC over loopback, without sending that operation through a hosted MCP endpoint.
Local benchmark visual
What local-first testing supports today
- Less network overhead for local calls: a supported client on the same PC can call the local listener directly. The timings above cover local HTTP operations only.
- Permission-aware access: the development listener binds to 127.0.0.1, authenticates requests with an ephemeral bearer token and exposes a restricted tool allowlist. Remote pairing is disabled.
- Local operation without a remote endpoint: localhost tests ran without a remote service. The PC, local client/model and required local services still need to be available; cloud AI services need an internet connection.
- Clear data boundaries: file and device operations can remain on the PC, while prompts or other information sent to an AI provider remain subject to that client’s settings and policies.
- Infrastructure: operations handled entirely on the PC do not require a hosted MCP server. Any future remote relay could add hosting costs; pricing and customer limits are not established.
One project, two separate connection paths
The existing RDC connection uses an authorised remote PC agent. RDC Lite Superspeed is a separate local-development prototype. It does not yet connect directly to ChatGPT, and the optional remote gateway shown in the concept artwork is not enabled for this prototype. A local request is executed by the PC; an AI client may still depend on its own network connection.
Rose API integration is in progress
The development bundle includes ROSE-related modules, but the full Rose API integration is not complete and several planned tools are not exposed by the current launcher. This is not yet a general-purpose replacement for the existing RDC connection or a feature available across all Rose Petals.
RDC by Rose — serious technology, ridiculous personality, unexpected magic.
Performance depends on the client, host and workload. Local-first removes the hosted MCP hop for compatible local calls; it does not make cloud-based ChatGPT work offline or establish an end-to-end product speed advantage.
What the project explores
Bring authorized remote-computer, file and process workflows into a clearer, permission-aware experience.
⚙️ How it works
The design uses an outbound authenticated PC connection, typed allowlisted capabilities and bounded receipts. It expressly excludes an internet-facing local MCP server and arbitrary shell in the initial remote capability set.
- Authorized remote-computer access
- File workflows
- Process workflows
- Permission-aware execution
🗂️ Project history and versions
Milestones below are taken from dated project records that were available for this review. They are not a complete transcript or a release history.
- 2026-10-06 · Remote bridge design
The design keeps the PC connection outbound-only and local MCP off the public internet; remote actions are typed capabilities, not arbitrary shell. This document is design-only.
Source record: ROSE_ETTA_PRO_REMOTE_BRIDGE_DESIGN.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 RDC 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 / gated · 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 RDC 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 ↓