← RendemoCONTENT HISTORY

Update to Rendemo

Snapshot Oct 24, 2026 · 13:15 UTC · version 1.0.0

WHAT CHANGED

Package or technical metadata updated

Package or technical metadata updated

Observed in package metadata. These changes alone do not establish a new customer-facing feature.

Save Rendemo and check future changes in Following.

Up to 5 plugins free · no card required.

All fields and original values.

Is template instance

Before

Sep 30, 2026 · 23:08 UTC

Not present

After

Oct 24, 2026 · 13:15 UTC

false

Compare saved observations

Download comparison JSON
Full technical diff · 1 changed fields

added /is_template_instance

BEFORE
Field was absent
AFTER
false
Full snapshot data
{
  "canonical_app_id": "asdk_app_6a8e5c09f7788191b376df6d421b1ca8",
  "connector_id": "asdk_app_6a8e5c09f7788191b376df6d421b1ca8",
  "created_at": "2026-08-26T03:22:50.187521Z",
  "discoverability": "LISTED",
  "id": "plugin_asdk_app_6a8e5c09f7788191b376df6d421b1ca8",
  "is_template": false,
  "is_template_instance": false,
  "name": "app-6a8e5c09f7788191b376df6d421b1ca8",
  "release": {
    "app_ids": [
      "asdk_app_6a8e5c09f7788191b376df6d421b1ca8"
    ],
    "app_manifest": {
      "apps": {
        "app-6a8e5c09f7788191b376df6d421b1ca8": {
          "id": "asdk_app_6a8e5c09f7788191b376df6d421b1ca8",
          "required": true
        }
      }
    },
    "app_templates": [],
    "description": "Rendemo turns product recordings into interactive demos. Polish and publish the demos you record with the Rendemo browser extension, turn any website into a hosted click-through sandbox demo, and build interactive product tours that run inside your own live app — then embed any of them on your site with one script tag.",
    "display_name": "Rendemo",
    "id": "pluginrel_f2353154ec908191b6a021c9533cfeb7",
    "interface": {
      "brand_color": null,
      "capabilities": [],
      "category": "Creativity",
      "composer_icon_dark_url": "https://files.openai.com/content?id=file_00000000061081f5a3ebc8a3cb50b1f6",
      "composer_icon_url": "https://files.openai.com/content?id=file_00000000061081f5a3ebc8a3cb50b1f6",
      "default_prompt": "Polish my latest recording into an interactive demo and publish it when I approve.",
      "default_prompts": [
        "Polish my latest recording into an interactive demo and publish it when I approve.",
        "Crawl our website into a click-through sandbox demo I can share.",
        "Where do viewers drop off in my published demo? Fix the weakest steps."
      ],
      "developer_name": "JACOB LAWRENCE GARGARO",
      "logo_url": "https://files.openai.com/content?id=file_00000000ffe081f59cac116f6083f26f",
      "logo_url_dark": "https://files.openai.com/content?id=file_00000000ffe081f59cac116f6083f26f",
      "long_description": "Rendemo turns product recordings into interactive demos. Polish and publish the demos you record with the Rendemo browser extension, turn any website into a hosted click-through sandbox demo, and build interactive product tours that run inside your own live app — then embed any of them on your site with one script tag.",
      "plugin_category_id": "creativity",
      "privacy_policy_url": "https://rendemo.com/privacy",
      "screenshot_urls": [],
      "short_description": "Interactive product demos",
      "terms_of_service_url": "https://rendemo.com/terms",
      "website_url": "https://rendemo.com"
    },
    "keywords": [],
    "mcp_servers": [],
    "onboarding_skill_name": null,
    "requires_local_executor": false,
    "skills": [
      {
        "description": "Use when the user asks to create or change a CODEBASE TOUR inside their own live product, or mentions data-rendemo markers, rendemo.tours.json, rendemo_create_tour, rendemo_add_tour_step, rendemo_list_tours, rendemo_probe_tour_targets, or the tour lockfile. A tour always runs in customer code and requires source markers. A crawled hosted replica is a sandbox demo and must use the sandbox-demos skill instead.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "author-a-tour",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "Use when the user asks to create or change a CODEBASE TOUR inside their own live product, or mentions data-rendemo markers, rendemo.tours.json, rendemo_create_tour, rendemo_add_tour_step, rendemo_list_tours, rendemo_probe_tour_targets, or the tour lockfile. A tour always runs in customer code and requires source markers. A crawled hosted replica is a sandbox demo and must use the sandbox-demos skill instead."
        },
        "name": "author-a-tour",
        "plugin_release_skill_id": "pluginrsk_6a9b1935cc548191a3767f614d8e139f"
      },
      {
        "description": "Use when the user wants a demo of their signed-in product and wants YOU to do the walkthrough rather than record it themselves or tell you which buttons to click — \"make a demo of my app and you drive it\", \"record a demo of my product without me clicking\", \"walk through my dashboard yourself and record it\", \"drive my signed-in session and build the demo\". The agent REHEARSES the workflow unrecorded on the user's own signed-in tab through the Rendemo Chrome extension, PROPOSES the take as a numbered plan the user approves in chat, then RECORDS that plan as one clean take that auto-directs — no free-roam replica to leak, so it is the right route for a data-dense product (CRM, inbox, leads). Read it BEFORE rendemo_start_drive_session / rendemo_drive / rendemo_propose_drive_plan / rendemo_record_drive_plan: it covers the intake questions to ask first, the paste steps to hand the user, the unrecorded read→decide→act rehearsal, how to write the plan and get a yes, the Record click, and the hand-off to the build pass. A user who would rather click through it themselves wants a plain recording (`new-demo`).",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "drive-and-record",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "cursor",
          "short_description": "Use when the user wants a demo of their signed-in product and wants YOU to do the walkthrough rather than record it themselves or tell you which buttons to click — \"make a demo of my app and you drive it\", \"record a demo of my product without me clicking\", \"walk through my dashboard yourself and record it\", \"drive my signed-in session and build the demo\". The agent REHEARSES the workflow unrecorded on the user's own signed-in tab through the Rendemo Chrome extension, PROPOSES the take as a numbered plan the user approves in chat, then RECORDS that plan as one clean take that auto-directs — no free-roam replica to leak, so it is the right route for a data-dense product (CRM, inbox, leads). Read it BEFORE rendemo_start_drive_session / rendemo_drive / rendemo_propose_drive_plan / rendemo_record_drive_plan: it covers the intake questions to ask first, the paste steps to hand the user, the unrecorded read→decide→act rehearsal, how to write the plan and get a yes, the Record click, and the hand-off to the build pass. A user who would rather click through it themselves wants a plain recording (`new-demo`)."
        },
        "name": "drive-and-record",
        "plugin_release_skill_id": "pluginrsk_6a9b19453a0481919468aaad2d2d5427"
      },
      {
        "description": "This skill should be used when the user asks to \"embed a demo\", \"add our demo to the pricing page\", \"install a Rendemo demo\", \"put the product demo on the site\", mentions `<rendemo-demo>`, `embed.js`, or `rendemo_get_embed`, or wants an interactive Rendemo demo rendered inside their own app or marketing site. Sequences the whole install: pick the demo, detect the framework, write the wrapper, place the script tag.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "embed-a-demo",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "This skill should be used when the user asks to \"embed a demo\", \"add our demo to the pricing page\", \"install a Rendemo demo\", \"put the product demo on the site\", mentions `<rendemo-demo>`, `embed.js`, or `rendemo_get_embed`, or wants an interactive Rendemo demo rendered inside their own app or marketing site. Sequences the whole install: pick the demo, detect the framework, write the wrapper, place the script tag."
        },
        "name": "embed-a-demo",
        "plugin_release_skill_id": "pluginrsk_6a9b19de880881918bbfa0dcd4a7c3f5"
      },
      {
        "description": "This skill should be used when someone asks for a product demo, walkthrough, tutorial, onboarding flow or \"show how my product works\" and there is no Rendemo project yet — including \"make me a demo\", \"demo my app\", \"turn this into an interactive demo\", \"record a walkthrough of X\", or a bare product URL with a request to demo it. Read it BEFORE choosing how to capture (a user recording with the Rendemo Chrome extension beats a browser capture code, which beats a headless crawl) and before rendemo_crawl_site, rendemo_start_browser_crawl or rendemo_list_projects on an empty workspace. Covers the two questions to ask first, the intent-to-theme recipes, the extension handoff script to hand the user verbatim, the build pass from auto-directed draft to published link, and translating plain-words feedback into edits — so the user never has to open Rendemo at all.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "new-demo",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "cursor",
          "short_description": "This skill should be used when someone asks for a product demo, walkthrough, tutorial, onboarding flow or \"show how my product works\" and there is no Rendemo project yet — including \"make me a demo\", \"demo my app\", \"turn this into an interactive demo\", \"record a walkthrough of X\", or a bare product URL with a request to demo it. Read it BEFORE choosing how to capture (a user recording with the Rendemo Chrome extension beats a browser capture code, which beats a headless crawl) and before rendemo_crawl_site, rendemo_start_browser_crawl or rendemo_list_projects on an empty workspace. Covers the two questions to ask first, the intent-to-theme recipes, the extension handoff script to hand the user verbatim, the build pass from auto-directed draft to published link, and translating plain-words feedback into edits — so the user never has to open Rendemo at all."
        },
        "name": "new-demo",
        "plugin_release_skill_id": "pluginrsk_6a9b19f2906c8191bf2cf92edd02d747"
      },
      {
        "description": "This skill should be used when creating or editing a SANDBOX DEMO — a hosted, autoplayable demo built from a site Rendemo crawled into a replica — rather than a codebase tour. Use it when the user says \"make a demo of <some website>\", gives a URL and no codebase, mentions `rendemo_crawl_site`, a crawl, a sandbox or a replica, or is authoring against an existing sandbox demo — and before `rendemo_add_sandbox_demo_step`, `rendemo_list_sandbox_pages`, `rendemo_find_in_sandbox` or `rendemo_check_sandbox_demo`. A sandbox demo writes no markers into customer source and has no lockfile to commit. Tours are reserved for codebase guidance authored with `author-a-tour`. Covers surveying what the crawl actually captured, choosing steps and target elements that survive a rebuild, writing the step card, and verifying before publish.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "sandbox-demos",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "cursor",
          "short_description": "This skill should be used when creating or editing a SANDBOX DEMO — a hosted, autoplayable demo built from a site Rendemo crawled into a replica — rather than a codebase tour. Use it when the user says \"make a demo of <some website>\", gives a URL and no codebase, mentions `rendemo_crawl_site`, a crawl, a sandbox or a replica, or is authoring against an existing sandbox demo — and before `rendemo_add_sandbox_demo_step`, `rendemo_list_sandbox_pages`, `rendemo_find_in_sandbox` or `rendemo_check_sandbox_demo`. A sandbox demo writes no markers into customer source and has no lockfile to commit. Tours are reserved for codebase guidance authored with `author-a-tour`. Covers surveying what the crawl actually captured, choosing steps and target elements that survive a rebuild, writing the step card, and verifying before publish."
        },
        "name": "sandbox-demos",
        "plugin_release_skill_id": "pluginrsk_6a9b1a0350dc81918d9c4b0c0d5c0821"
      }
    ],
    "version": "1.0.0"
  },
  "scope": "GLOBAL",
  "share_url": "https://chatgpt.com/plugins/plugin_asdk_app_6a8e5c09f7788191b376df6d421b1ca8?open_in_app",
  "status": "ENABLED"
}

SHA-256 of public snapshot: 52dfd25b4051741609d6535bedad1a7d496b34a1af1853891de669f75c93a2b5