Stop prompting from scratch. Copy a drobek app and change the useful part

Description and use

Duplicating a drobek gallery app creates an independent copy that can be customized without inheriting sensitive data, enabling rapid adaptation of existing UI.

Problem

You want to reuse a small app that already has the desired layout and interaction but need a different calculation, extra fields, or a team‑specific version, and starting from scratch is wasteful.

Outcome

A new, independent app is created from a gallery copy, preserving the original layout but allowing custom logic and data. The copy does not inherit sensitive data or external integrations, ensuring isolation.

Workflow

• 1. Owner enables "Allow duplicates" for the app in the Gallery settings.
• 2. A user signs in, selects a workspace, and initiates a duplicate via the duplicate_app tool or set_gallery_listing API.
• 3. The new app starts unpublished with version 1 containing the published source files.
• 4. The duplicate operation returns module settings categorized as applied, pending, and skipped.
• 5. The user reviews these settings, configures any required upstreams or credentials, and tests the app.
• 6. Once satisfied, the user publishes the copy to obtain a production URL.
• 7. Optionally, the user can list the new app in the gallery.

Evidence

The copy starts with the published files. You do not inherit the original owner's users, records, or API keys.

Source

The tool response separates module settings into applied, pending, and skipped. An agent should inspect all three.

Source