Open the ChatGPT desktop app and paste this message into a new chat. Your assistant helps install Ruthie and walks you through the rest.
Help me install and connect Ruthie in the ChatGPT desktop app. Handle the setup you can and guide me through anything that needs me; I don’t want to use a terminal.
Keep this friendly and straightforward for someone who has never installed a plugin. Use plain language and brief updates. Handle technical details quietly; explain only what I need to do, what I’m approving, and whether it worked. Avoid jargon, command names, and diagnostic output unless necessary to resolve a problem. If something fails, explain it simply without hiding the problem.
I have an invited Ruthie account. Add the official Heartbred marketplace from https://github.com/Heartbred-Media/plugins using main, then install and enable Ruthie. This is the production plugin, not a development connection.
Use the supported installation and authentication mechanisms available in this chat. If you can install the marketplace and plugin, do so with the required approval. If this chat cannot perform installation, explain the next simple step through Plugins → Add → Add a marketplace in the desktop app, or help me continue in Work or Codex if necessary. Do not claim that regular Chat cannot use plugins. Do not assume every chat has the same installation tools.
If command-line tooling is available and necessary, use the current runtime bundled with this ChatGPT desktop app—not an older, separately installed codex command. For native Codex OAuth, use the supported client-metadata (CIMD) flow rather than requiring dynamic client registration. Do not install a local Ruthie server or a substitute connection.
Before connecting, explain briefly that first use normally lets the marketplace connection read and make changes in my current Ruthie Spaces. Spaces created later stay private, and any access choices I’ve already saved still apply. I can choose narrower access first or change it later at https://account.ruthie.app/#/assistant. The current marketplace connection is labelled Codex (remote) there; do not assume a different connection identity has the same permissions. This permission is separate from any older local Codex connection.
Start supported browser authorization for me if available, otherwise guide me to the connection prompt. I’ll sign in to my Ruthie account and approve access in the browser. Remind me to check that I’m using the intended Ruthie account. Never ask me to paste passwords, verification codes, or tokens into chat. Don’t direct me to interface controls unless you’ve verified they exist.
After authorization, list my Ruthie Spaces without changing anything. If this chat cannot access the newly installed tools, don’t build a workaround or custom verification script. Explain simply that installation and sign-in have finished but the connection check needs a fresh chat. Ask whether I’d like you to create and pin a dedicated Ruthie chat, or whether I’d prefer to open a new chat myself. Only create and pin a chat after I agree. Carry forward this instruction: “Use the installed Ruthie plugin to list my Ruthie Spaces without changing anything.” If a restart is needed, give me clear instructions for continuing. Only call the connection verified after that read succeeds. If something fails, explain the problem without changing Ruthie’s security settings.
If several Spaces are listed, ask which one I want to use. Listing Spaces confirms read access, not write access. Do not make a test change unless I ask for one.
Once connected, if you haven’t already asked, offer to create a dedicated, ongoing chat named “Ruthie” and pin it in my sidebar. This is optional. Only do it after I agree, and explain that I can return to it for future Ruthie conversations. If you cannot create or pin chats here, guide me instead; don’t claim it is done. Don’t create a duplicate if we already made one. If I decline, continue without creating another chat.
