Kuyun AI · Works to try

Help · The project page

The project page

What a project holds and what it may draw on, in detail. The overview is Projects.

Your list of projects

Your projects are on the Create page. The list down the left keeps a steady order: your projects, newest first, then the ones shared with you to work on together, then the Archive, folded away. A project shared with you to VIEW is not here: it is on your Shelf (Shelf). A project moves only when you start, archive or delete one, or choose Work on this first in its ⚙ menu — not because work happened in it — so it stays where you last saw it. A project you chose Work on this first for is at the top and is also worked first; after those, Kuyun works the rest oldest first, one at a time, while the list shows them newest first (How a project's work moves). A project with a question waiting for you, a step of the plan that is yours to do, or a note from a viewer you have not marked done, is gathered at the top under Needs you, flagged with what it wants ("answer 1 question", "do 2 steps of yours", "read 1 note from viewers"), until you answer, tell the chat the step is done, or mark the note done; every other row says in its own line what is new (●) or what Kuyun is doing. A row also says whom the project reaches: 🌐 published when it is in Explore and on the works page, and 👥 shared with 2 when you have invited people, to view or to edit — counts, never names, which the ⚙ menu's Invite people has.

What a project holds

The project's page is a conversation with the files beside it.

Nothing on the page is a control over the work: steps complete on Kuyun's reviewer's say, a plan is adopted or sent back by its reviewer, and anything you want changed you say in the conversation.

Your project as files

A project's words can leave Kuyun as plain files and come back. Download the files in the project's ⚙ menu gives you a zip: a small project.yaml with the title, the kind, the statement, the cover's words and, on a course or a role-play practice, whether it is locked (locks: true or false, which an imported zip may say too), the README.md, and one Markdown file per lesson, chapter or entry with its practice sets inside it, written the way Kuyun writes them. Open them in any editor, keep them, or change them.

To bring a project in, choose import a project (.zip) under the kinds on the New project page. The zip can be one you downloaded, or a folder of files you wrote yourself: the README.md and the entries are enough, and without a project.yaml the project is Custom, named by the README's heading. Every practice set is checked the way Kuyun checks its own, a long chapter arrives whole however long it is, and a problem in any file stops the whole import with nothing made. What arrives is a finished project, ready to publish: Kuyun does not plan or write over it, then or later, however you change it. When you want more of it, ask in its Creation Console — another chapter, a practice set, a rewrite — and Kuyun plans from there. The cover's picture does not travel; its description does, so the picture is drawn again in a moment on the publish steps. The chapters' narrations travel too, in a files folder, named like their chapters; a zip with them may be up to 256 MB, and they count against your storage when they arrive. Your other uploads, tables, chats and the people you shared with stay with the original.

What a project may draw on

A project works only from what you give it and what it finds on the open web: the problem you state, your answers to its questions, the files you upload to it, the pages it collects, and the chat you have with it. It never uses what Kuyun knows about you — your memory, your documents, your other conversations — and the New project flow says so where you write the problem. That is the promise that lets a project be shared, published or linked without carrying anything of yours with it; there is no longer a choice to make at creation (there was a "personal" option until 26 October 2026; projects made with it keep working as they did).

One thing is still about you: a question you ask Home to keep an eye on is a watch of your own, since it is about you.

That promise is the owner's. If someone shares a generic project WITH you — a course you are taking, say — your own conversation in it is not kept apart yet: Kuyun learns from it the way it learns from any conversation, and adds that to what it knows about you. Walling a shared generic project off for the person it was shared with is planned, not built. What it has already learned that way cannot be picked out and removed afterwards, short of deleting all your data.

A project can ask another. Tell a project's chat to link another project you can read — your own, or one shared with you — and from then on it may ask that project questions as it works: a trip plan asking your castles library which castles are near Kyoto, say. The other project's own assistant answers from its own material, briefly, and only what a viewer of it may see; its answer is kept with the asking project — in its conversation, or with the step of the plan that asked — not in the other one, and nothing in the other project changes. Only a project's owner can link one, and only when they ask for it. A project made with the old "personal" option can be linked by nobody but you, and someone else's project can be linked only when it is generic. If a share is taken back, or the other project is deleted, its answers stop — but answers already given stay where they were asked. Asking costs the asking project's usage, not the other one's.

A map of a trip

When a project is about a journey — a few days in Athens and Santorini, say — ask its chat to make a map of the itinerary once the days and stops are settled. The map is drawn right there in the conversation: a marker for each stop, each day as a coloured route, a scale bar, and a link from every stop that opens the real map in Google Maps or 高德. Stops Kuyun could not find a position for are listed beside the map rather than guessed onto it. It is a sketch of the trip, not a street map.

The map belongs to the project, so everyone the project is shared with sees it, and it appears in the project's Output folder as a map. Asking for a change files a new version; the map in the chat always shows the latest.

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.