Build and update Chirps with your AI app

Once your AI app is connected, you can manage Chirps by asking it in plain words, as you'd ask a colleague.

Who can do this: the account owner, on any plan.

What you'll need: a connected AI app: Connect Claude, ChatGPT or another AI app.

Things you can ask

• "List my Chirps." / "Show me the instructions of Recipe Coach."
• "Create a Chirp called Study Buddy that quizzes students on biology. Use Claude Haiku."
• "Add the PDF in my Documents folder as a knowledge file to Study Buddy."
• "Give Study Buddy three conversation starters."
• "Test Study Buddy with the question: what is photosynthesis?"
• "Publish Study Buddy as unlisted."

New Chirps always start as drafts. Changes appear in the Chirp's history, marked AI app (or Import for imported GPTs): see See what changed in a Chirp.

What needs your say-so

• Publishing, deleting and changing who can open a Chirp need Create, edit and publish access. Chirp Builder tells the app to check with you first, but it can't see your chat, so only give this level to apps you trust. To delete, the app has to give the Chirp's exact name.
• Testing sends a real message to the Chirp, so it's charged to your OpenRouter account like any chat.

What it can never do

• See or set API keys, your password or billing details. Add Actions' API keys in the editor yourself, never in the chat.
• Turn on Actions that move money.
• Password-protect a Chirp, or manage leads, webhooks or email services. Do those in Chirp Builder. (It can set or remove a simple access code.)

Change what it may do

In Settings, under Connected apps, choose what the app may do (1), or click Disconnect (2) to cut it off straight away.

If it doesn't work

• The app says it doesn't have permission. It needs more access: change it under Connected apps.
• "Choose a Chirp Builder plan to create or change Chirps." Building needs an active plan.
• A test says your OpenRouter key isn't working, or has no credit. See Connect your OpenRouter key.