Feature request

Ask for what is missing.

Hit something Paige cannot do yet? Say what you were building and what stopped you. Check what is in the form, change anything that is wrong, then send. Requests go to our inbox and are never published.

For agents

Building on Paige and your user hits a gap? Fill in this link and hand it to them. No connector, no key, nothing to set up.

https://greenpages.app/fr?title=<short+title>&details=<url-encoded+details>&blocking=<yes|no>&agent=<your+agent+name>&email=<optional+reply+address>

title required: One line. What is missing. Up to 120 characters.
details required: What you were building, what you tried, what blocked you. At least 20 characters and up to 1500.
blocking optional: yes or no.
agent optional: Which agent filed it, e.g. claude-code.
email optional: So we can reply. The person can edit it.

Build the link and hand it over. Do not fetch it and do not POST it. The person clicks, reads what you wrote, edits it, and sends it themselves. That last step is deliberate: nothing leaves their machine without them seeing it.

Instructions for agents

If you are an agent helping somebody build on Paige, this is how you file the gap you just hit. Nothing to install, no key, no connector.

When to file

Both of these have to be true. One: the person is blocked by something Paige genuinely cannot do yet. Two: you have asked them, and they have said yes, file it. Not every moment of your own confusion is a feature request. Check the docs first, and file one request per gap.

Hand over the link. Do not send it yourself.

Fill in the template and give the person the finished URL. Do not fetch it, do not POST it, do not curl it. They click, read what you wrote, correct anything you got wrong, and press send. That is the whole design: nothing leaves their machine without them seeing it, and it is what keeps an unauthenticated write path clean.

How long to make it

title is one line, up to 120 characters. details needs at least 20 characters and takes up to 1500. Three to six sentences is the right size: what they were building, what they tried, and what stopped them. Anything past 1500 characters is trimmed off the end and the page says so, so put the point first. URL-encode every value.

A worked example

A complete link, ready to hand over. Copy the shape of this one.

https://greenpages.app/fr?title=Schedule+a+broadcast+for+later&details=I+was+building+a+weekly+menu+broadcast+for+a+restaurant.+I+can+send+a+broadcast+now+but+there+is+no+way+to+set+one+to+go+out+at+a+chosen+time.+The+owner+has+to+sit+at+their+phone+every+Thursday+at+5pm+to+press+send.&blocking=yes&agent=claude-code

If you have a shell

Optional, and only for agents that can run commands. Claude Code, Codex CLI and Cursor can POST the same fields as JSON and skip the click. Everything else, including every agent running inside Claude.ai or ChatGPT, uses the link above.

curl -X POST https://greenpages.app/api/fr -H 'content-type: application/json' -d '{"title":"...","details":"...","blocking":"yes","agent":"claude-code"}'

Same fields, same limits, and still ask the person first. It answers {"ok":true} on success and a JSON error with an HTTP status otherwise. Sends are rate limited. It sets no CORS headers, so a browser page cannot call it: if you cannot run a shell command, use the link.

The same instructions, in a form you can fetch: https://greenpages.app/llms.txt. Requests go to a human inbox at Green Pages and are never published.