Tell us what to change in Chips.
Chips doesn't take pull requests. Instead, write the change you want as a feedback prompt, the way you'd ask a coding agent to make it, and send it to us.
Write it with your agent.
In Chips, open You, then Send feedback. Your Main agent asks what happened and writes the prompt. You check it on GitHub before you post it.
Paste this to the agent you use.
Read https://chipschat.ai/feedback.md and help me write a feedback prompt for Chips.It asks you a few questions and gives you a link with the prompt filled in.
Open a feedback prompt.
It's a short form with three boxes. It's public, and you need a GitHub account.
A good prompt says three things.
- What you sawWhat you were doing, and what Chips did.
- What you'd changeThe change itself, in your own words. You don't need to know the code.
- How to tell it's doneWhat someone would do to check that it works.
Let one space through quiet hours What I saw. Quiet hours hold banners for every space at once. My Release space needs to reach me at night, and the others don't. What I'd change. Add "Let through quiet hours" to a space's Notifications row. It's off for every space until you turn it on. How to tell it's done. Turn on quiet hours, and turn on "Let through quiet hours" for Release. A message in Release still shows a banner at 11 PM, and a message in any other space doesn't.
Why prompts
A prompt is quicker to read than a patch.
It says what you want in your own words, so nobody has to work it out from a diff.
The code stays in one style.
The change is built and tested the same way as everything else in Chips, by the people who look after it.
Nobody signs an agreement.
There's no contributor licence to sign. You agree that your prompt can be used, and that's all.
When a change comes from your prompt, the release notes say so.
They name you the way you asked, or not at all if you'd rather. If someone has already asked for the same thing, a thumbs up on theirs counts too.