Starter prompt
This is Changelog, a public changelog page. Merged pull requests arrive as drafts and you, my agent, turn them into release notes I publish. Step 1. If this is the Template, copy it for me with copy_app and work on my copy. If my copy shows a Claim button, have me click it so the app is mine. Read it with get_app_source. It shows a sample changelog until the first change. Step 2. Ask me one at a time: my product name, which GitHub repo to collect pull requests from, how often we ship, and whether to keep the sample entries or start clean. Step 3. Set it up. If I want it clean, call startFresh with confirm true. Save my product name and tagline with saveSettings. Make the app Public with set_public so anyone can read it. Step 4. Collect pull requests: create a Webhook on the addShipped op. Call getWorkflow with mutate_app for the exact GitHub Actions file and add it to my repo at .github/workflows/changelog.yml. It reads repo secrets CHANGELOG_HOOK_URL and CHANGELOG_HOOK_KEY. If you cannot set repo secrets, tell me where to paste the Webhook secret myself. Open it as a pull request for me to review. Step 5. Create a weekly Routine on rollupWeek. When it runs, a draft and a ping wait for you in getAgentInbox (call it with mutate_app). Rewrite the draft with saveEntry for customers: one short paragraph on what they can do now, then Improvements and Fixes bullets. Never publish unless I ask. Then call ackPing. Step 6. Ask me about the last thing we shipped and write the first entry with me now. Step 7 (optional). For instant pings, save your webhook URL with saveSettings, then use update_app to add charming:secrets/[email protected] to capabilities.imports and its origin to manifest.permissions.server.fetch. Create an hourly Routine on retryPings. Finish with the public link.
What it does
A changelog page for your product, with dated entries, versions, New, Improved, Fixed, and Security tags, pictures, and a permalink for every update.
- A public page anyone can read, with filters by tag, that works on a phone
- An editor with a live preview, and drafts only your team sees
- A Shipped inbox that collects merged pull requests from your repo
- Sample entries for a made-up product called Northwind, so you can see it filled in before you write anything
Your agent writes it
Merged pull requests land in the Shipped inbox through a Webhook. Once a week the app bundles them into a draft and hands it to your agent, which rewrites it for customers: one short paragraph on what they can do now, then Improvements and Fixes bullets. You read it and press Publish. Your agent never publishes unless you ask.
How to use it
- Copy the starter prompt at the top of this page, or click Use template to make your own copy.
- Paste the prompt into your agent (Claude, ChatGPT, Codex, or any agent that connects to Charming). The agent connects to Charming over MCP, copies the app to your account, and opens it.
- Answer its questions: your product name, the GitHub repo to collect pull requests from, how often you ship, and whether to keep the sample entries or start clean.
- Let the agent make the app Public and give you the link. Share it with your customers.
- Approve the pull request where the agent adds a small GitHub Actions file to your repo. From then on every merged pull request shows up in Shipped.
- Each week, tell your agent to check the Changelog draft, or let the weekly Routine nudge it. Read the draft, edit it if you like, and press Publish.
What you need
- A Charming account and an agent that can connect to it
- For the page itself, nothing else: make the app Public and share the link
- To collect pull requests, a GitHub repo where you can merge a workflow file and add two repo secrets (the agent gives you the Webhook URL and key)
What comes next
- Instant pings: add a webhook URL in Settings so a new draft pings your agent right away instead of waiting for the next check
- A Follow link on the page that points to your social account, set in Settings
- Your own pictures on any entry, in place of the four built-in illustrations
More from Tambo
A public status page for small teams, in place of a paid Statuspage plan. 90-day uptime bars,…
Status
A public status page for small teams, in place of a paid Statuspage plan. 90-day uptime bars, incident updates, and hourly checks that open an incident when a site goes down.
A to-do list you and your AI agent both work from. It replaces the markdown file, sync script, and…
To-Do Board
A to-do list you and your AI agent both work from. It replaces the markdown file, sync script, and chat relay you would wire up so an agent can see and tick your list. For anyone who runs their week through an agent.
FreshBooks-style invoicing for freelancers: build an invoice in a minute, send your client a link,…
Invoices
FreshBooks-style invoicing for freelancers: build an invoice in a minute, send your client a link, see when they open it, and let your agent chase late ones.