Kuyun AI · Works to try

Help · Remarks you make about kuyun

Remarks you make about kuyun

What you tell the Kuyun team, and what happens to it. Everything else Kuyun keeps of yours is Your data.

A tap on "did it help?" after something you asked for ships is a remark too, kept the same way.

To tell kuyun what you think of it, type /remark followed by what you want to say, in any chat — for example /remark the player stops on my phone; typing / alone lists it to pick — or write it in the box on Settings → Remarks. A /remark goes straight to the Kuyun team, never to the assistant you are talking to, and goes at once, even while a reply is on its way; the chat says "Your remark is sent to the Kuyun team", and you are told when they answer. The assistants do not note remarks for you: one you only say to them in passing is a message like any other. Either way, the remark is kept in your own data, where you can see it under My Files, and it is deleted with your account like everything else there. The Remarks page lists what you have said, newest first, with the team's answer under each once it comes, and the request it opened when the review filed one.

A remark says where you made it, so the team can find what you mean without asking you again. Both kinds keep the page you came from (which project or work, for instance — never what you searched for), the app's version, your browser and your screen's size, and a /remark also keeps which conversation it was typed in, with its project and assistant. It keeps nothing of the conversation itself: none of what you or the assistant said is sent with it. It is kept with the remark, in your own data, and deleted with it.

Remarks are not anonymous: the people who make kuyun read them, with your name attached. That is the point — a gripe or a compliment reaches a person who can act on it. Only you send one, so nothing reaches the team as a remark that you did not send yourself — apart from the note an assistant makes when it is stuck, below.

When an assistant gets stuck, the team hears it. If an assistant cannot do what you asked — the same step fails twice, or it has no way to do it at all — it notes that for the team itself, as one of your remarks: what you asked for, what went wrong and what it tried. It names the conversation it happened in, so a person fixing the fault can find the moment it happened (the people running kuyun look at stored data only to fix a problem, Terms of Service and Privacy Policy). The assistant tells you in a few words that the team has it, and stops trying the same thing again; it does not say so unless the note was actually made. Once a day at most five of these are noted for you. It is kept, read, answered and deleted exactly as your other remarks are. Settings → Remarks shows it by what you asked for; what went wrong and what was tried are kept with it for the team.

Your remark is also read on the machine the team works on, once a day, so it can be answered. It is read there, not stored: that machine keeps a record of what the software wrote back that day, with your account's name, and deletes it on its own seven days later — deleting your account does not reach it sooner. The software that reads your remark there cannot open anything else on that machine. It reads that day's remarks from everyone together, so it is told never to repeat one person's words or name to another, and an answer that does is held back rather than sent — your remark then waits for a person at kuyun to answer it instead. If the review turns your remark into a tracked request, the request is filed under your name, kept with kuyun's other requests, and shown to you and the people who run kuyun — never to other users; deleting your account does not remove it. A request the team files themselves from several people's remarks is theirs, not yours. Remarks, the problem reports described above, a report you send about someone's published work, and a change to Kuyun one of your projects asks the team for (How a project's work moves) are the only things you tell kuyun that leave your own data. That last is the assistant's own short description of the change and why your work needs it, with the project's name — never your conversation, never anyone's name or words. It is kept with Kuyun's other requests, read by the people who run Kuyun before anything else reads it, and withdrawn — its words taken out of what anyone reads — when you delete the project, your data or your account.

You get an answer. Every remark is read, and answered — by the review, or by a person when the review held its answer back — sometimes "we have opened this and someone will look at it", sometimes why it already works, sometimes just thank you. The answer arrives as a notification, which opens Settings → Remarks if you want to say more, and if you are mid-conversation the assistant will pass it on. Something worth building becomes a tracked request, and a person at kuyun decides whether it is built; the assistant cannot promise that and will not.

You hear what becomes of it. Under your remark on Settings → Remarks, the request it opened says where it stands, in one of four words: waiting for the team to decide, being built, shipped or not planned. When it moves to being built, ships — which is when the change is live in the app, not when it is written — or is not going to be built, you get a notification, and the assistant passes it on the next time you talk — while the team is still looking at it, nothing is sent. The team can add a sentence for you with their decision, or write to you about it at any time; it appears under the remark too. When it ships, the notification usually says in a sentence or two what changed for you and where in the app to find it — written when the change was made, and read by a person at kuyun before it went out. You never see their internal notes, reports, or anything about other people who asked. You can still ask the assistant about a request by its id.

This is a page of Kuyun's own handbook, the one its assistant answers from — ask it in the app and it will say the same.