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.
- Delivery notes, beside Output once you have said how the work should be delivered: how the viewer's chat takes people through it — the pace, the way through each part, what it answers from and refuses. Yours to write in the Creation Console or edit here; viewers never see it.
- The Cover folder, beside Output on a project you have made a cover for (Sharing a project, "Publishing"): the tagline as a small file you can edit, and the picture. Yours, never a viewer's. The cover's title is the project's name: rename the project to change it.
- The conversation, in the middle. As the project's creator you talk to Kuyun here: ask what it found, redirect the effort, correct the goal, say that you did your part. It narrates what happened while you were away, and when Kuyun has questions for you, they arrive as a message in this conversation, each with its own answer box. Ask it where the work is and it tells you. A second tab opens the viewer's chat — the one the people you share with get — so you can take your own course exactly as they will; what you do there is your own rehearsal and touches no viewer. For more room, ⤢ at the end of the tabs fills the whole window with the conversation; the round ✕ at the top, or the Escape key, puts the page back, and nothing you were typing is lost. People you share with have the same ⤢ on their chat.
- Where the work is, above the conversation. The Creation Console is a chat with work going on behind it, and it looks the part: a dark surface, and a one-line strip across its top: which step the work is on; anything waiting on you, flagged ⚑ — your own steps by number and how many questions are yours — which is always on the line, whatever else is going on; the one thing that matters most of the rest — what Kuyun is working on, else something stuck, else what Kuyun will do next — with a count of the rest; and at its end what the project has cost you in tokens. A step of yours is finished by telling the chat it is done, in a sentence: it records your words. Notes your viewers sent about the work are counted on the same ⚑ and listed under the strip, for you and every contributor, each with its sender's @handle, a reply box and Done; a reply reaches the viewer with a notice. Ask the chat about a note and it offers a fix, and makes it when you say so. When none of those is true, the line just says which step the work is on. Click the line (▸) to see the rest: what is waiting on you, what is stuck, and what Kuyun will do next and when; what it is working on stays on the line. It stays opened or folded, the way you last left it. A question Kuyun asked you shows there with the time its own assumed answer will be adopted if you have not answered — nothing waits on you, but you can see how long you have. "Recent", in the opened strip, shows the last things the work did, with the reviewer's own words. The viewer's chat keeps the plain look: nothing runs behind it. The "Kuyun worked" line under a reply opens onto its notes as a block you can read.
- The files, on the right. Everything the project holds, as files and directories, each with a line saying what it holds — Kuyun writes the line once the file has changed, and until then the file's own first heading stands in. What Kuyun files while you are on the page appears in the list by itself, within a minute at most and about fifteen seconds while work is running, with no need to reload. Output comes first: what the project delivers, and everything its viewers can see once you publish it (they see these files at the top of their list, with no Output folder, and read the chapters in the reader — Studying with a project, "Reading a work") — its README (what it delivers and how to use it), the deliverables in the kind of project's own word (lessons, chapters, entries, digests), maps where the kind of project delivers them, the tables that are part of the work, and the files you shared. At first the list shows the lessons and folds the rest: a lesson's practice sets are under the ▸ beside its name — press it to list them, indented beneath the lesson — and the other folders (tables, files, maps, the making of the work) open when you press them. Every lesson's name starts in the same place, with or without practice. Opening a lesson shows the whole of it on one page: the text, and under it each practice set with its items. A practice set that belongs to no lesson sits in a Practice folder of its own; one the lesson's text does not yet place is marked so on the lesson's page. The deliverables are listed in the order its viewers are taken through them: by their number (lesson 2 before lesson 10), with an introduction, a preface or a foreword first and a conclusion, an appendix or a glossary last, unless you have asked the chat for another order. Ask, and the chat also moves one elsewhere in Output — a test into Output itself or into a folder of its own: it can still be read and downloaded, but it is no longer one of the lessons a viewer is taken through, and only those are marked as read or not. Moving or reordering changes no text and no viewer's place. You and the people you invited to work on it can delete anything in Output: open it and choose Delete. Nothing in Output has a delete beside its name, so a click meant for a file cannot remove it. Kuyun says first what happens to the people who read it. A deleted lesson leaves their list, and each viewer's place and progress on it is cleared. A deleted table can no longer be looked things up in. Without the README, viewers see the files with no introduction. Undo stays on the page until you leave the project, and brings the thing back as it was and where it was, though not anyone's place or progress in it. Only the person who deleted something can undo it. Once Kuyun has finished a lesson, it will not write it again after you delete it unless you ask in the chat, so a course you cut to 29 lessons stays at
- A lesson its plan is still writing is finished as planned. A moment later Kuyun says in the chat what the change touches: a later lesson that refers back to it, or a README that still names it. It suggests a follow-up only when one is worth doing, and changes nothing until you ask. The same people can edit what is written as text in Output — the README, a lesson or chapter, a digest, a .md or .txt file you shared — with ✎ Edit in the file once it is open; its Preview shows it the way viewers will see it. While editing you can add a picture of your own: 🖼 Add a picture, under the text, takes a JPEG, PNG or WebP photo (up to 15 MB) and puts it where your cursor is. You can say what it shows in the box beside the button first; that line appears under the picture. Kuyun turns the photo upright, trims it to a 3:2 shape, keeps it at 1200×800 at most and removes everything a camera wrote into the file, such as where it was taken. Under the picture it says "uploaded by its owner". A photo smaller than 600×400 is refused. Adding one costs no tokens. The picture is kept with the project as soon as it uploads, and it appears on the page once you press Save. It counts toward the owner's storage and the 300 pictures a project can hold, even if you cancel the edit or later take it out of the text; to remove a picture for good, ask in the project's chat. A picture a collaborator adds says "uploaded by a contributor" instead. Upload only pictures you have the right to share: viewers of a published work see them. Your version is marked as yours ("edited" beside it), and if Kuyun later rewrites that lesson it starts from your version and keeps your changes. A lesson's practice stays as exercises: a blank goes inside a fill-in box, and the page says so if it isn't. If Kuyun changed the file while you were editing, your save is refused and your text stays in the box, so you can copy it into the new version. Practice sets (read on the lesson's page), maps and tables are changed through the chat. After an edit, too, Kuyun says in the chat what it touches. The same people can save a written file of Output — a lesson or chapter, the README, a .md file you shared — as a PDF: open it and choose ⬇ Export PDF, beside Edit and Delete. Your browser's print window opens with the whole file in it, every part of a long one, and nothing else of the page; choose "Save as PDF" there. Viewers do not have this button. Beside it is what makes the work, which viewers never see: the goal and context, the brief (what the work is judged against), the plan, the writing guide (the house style the material is written to), the working summary, the findings (one per step, each citing its sources), the files you keep to yourself and the web pages Kuyun collected. Click any of them and it opens over the conversation, with when it last changed at the top; a long one comes a part at a time. A web page Kuyun collected shows when it was fetched and a link to the page itself, and reads with its headings, lists and tables; pages collected before 2026-10-13 were kept as plain text and still read as one paragraph. A page that turned out not to be the page — a site's "page not found", a check that the visitor is not a robot, or a page that shows nothing without a browser, as a Google News link does — is not kept: Kuyun looks for the same thing elsewhere instead. A page that is empty only because it needs a browser to draw it is read once more through Linkup, Kuyun's search service, and kept when that works. Upload files, at the top of the panel beside its name, keeps a file to you and your contributors. To share one with viewers, the → beside it moves it into Output, and ↩ moves it back out; you can also ask the chat to share a file. A sound file — a chapter's narration, a recording — plays in place: open it and you get a player with play, pause and seek, at your listening speed, and when you come back it picks up where you stopped on that device. A sound file in Output named like a chapter —
chapter-3.mp3beside the chapterchapter-3— is that chapter's narration: the chapter shows 🎧 in the files, its page opens with the player above the text, and where you stopped is kept with your account, so your phone picks up where your computer left off; when it reaches the end, the next play starts over. Kuyun can make these recordings for you — Narrate… in the ⚙ menu, or 🎧 Narrate on a chapter's page (Talking instead of typing). For creators, each file has a download and a delete beside it while it is yours alone (viewers download nothing — Sharing a project); once it is in Output, it is deleted from the file itself when opened, like everything there. On a phone the 📁 button opens the files. On a desktop the explorer's edge drags to the width you like; the arrow keys move it too, and a double-click puts it back.
- A lesson its plan is still writing is finished as planned. A moment later Kuyun says in the chat what the change touches: a later lesson that refers back to it, or a README that still names it. It suggests a follow-up only when one is worth doing, and changes nothing until you ask. The same people can edit what is written as text in Output — the README, a lesson or chapter, a digest, a .md or .txt file you shared — with ✎ Edit in the file once it is open; its Preview shows it the way viewers will see it. While editing you can add a picture of your own: 🖼 Add a picture, under the text, takes a JPEG, PNG or WebP photo (up to 15 MB) and puts it where your cursor is. You can say what it shows in the box beside the button first; that line appears under the picture. Kuyun turns the photo upright, trims it to a 3:2 shape, keeps it at 1200×800 at most and removes everything a camera wrote into the file, such as where it was taken. Under the picture it says "uploaded by its owner". A photo smaller than 600×400 is refused. Adding one costs no tokens. The picture is kept with the project as soon as it uploads, and it appears on the page once you press Save. It counts toward the owner's storage and the 300 pictures a project can hold, even if you cancel the edit or later take it out of the text; to remove a picture for good, ask in the project's chat. A picture a collaborator adds says "uploaded by a contributor" instead. Upload only pictures you have the right to share: viewers of a published work see them. Your version is marked as yours ("edited" beside it), and if Kuyun later rewrites that lesson it starts from your version and keeps your changes. A lesson's practice stays as exercises: a blank goes inside a fill-in box, and the page says so if it isn't. If Kuyun changed the file while you were editing, your save is refused and your text stays in the box, so you can copy it into the new version. Practice sets (read on the lesson's page), maps and tables are changed through the chat. After an edit, too, Kuyun says in the chat what it touches. The same people can save a written file of Output — a lesson or chapter, the README, a .md file you shared — as a PDF: open it and choose ⬇ Export PDF, beside Edit and Delete. Your browser's print window opens with the whole file in it, every part of a long one, and nothing else of the page; choose "Save as PDF" there. Viewers do not have this button. Beside it is what makes the work, which viewers never see: the goal and context, the brief (what the work is judged against), the plan, the writing guide (the house style the material is written to), the working summary, the findings (one per step, each citing its sources), the files you keep to yourself and the web pages Kuyun collected. Click any of them and it opens over the conversation, with when it last changed at the top; a long one comes a part at a time. A web page Kuyun collected shows when it was fetched and a link to the page itself, and reads with its headings, lists and tables; pages collected before 2026-10-13 were kept as plain text and still read as one paragraph. A page that turned out not to be the page — a site's "page not found", a check that the visitor is not a robot, or a page that shows nothing without a browser, as a Google News link does — is not kept: Kuyun looks for the same thing elsewhere instead. A page that is empty only because it needs a browser to draw it is read once more through Linkup, Kuyun's search service, and kept when that works. Upload files, at the top of the panel beside its name, keeps a file to you and your contributors. To share one with viewers, the → beside it moves it into Output, and ↩ moves it back out; you can also ask the chat to share a file. A sound file — a chapter's narration, a recording — plays in place: open it and you get a player with play, pause and seek, at your listening speed, and when you come back it picks up where you stopped on that device. A sound file in Output named like a chapter —
- Its tables — when the work is a collection of things you look up (places, terms, records, products), Kuyun keeps it as tables: each row says where its values came from and when they were true, every change is kept in the project's history, and the project's chats answer from them. A chat looks rows up by a value, a range, a word in the text or how near they are to a place, and sorts them; it does not combine two tables in one question, so for something like "which castles are near a station" it reads both and works it out. A table opens from the files as its rows, with only the columns your kind of access allows; once a project is shared, its Creation Console reads them the way the people it is shared with may, because what it writes is what they read. Not every table is part of the work. A table Kuyun keeps while making it — a checklist, a tally — sits beside the findings under Working tables, where only you and the people you invited to work on it see it. A library's tables are part of the work, so they go in Output. A table you ask for in the chat goes where you say. The → beside a working table puts it in Output for your viewers, and ↩ beside a table in Output takes it back out.
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.