Kuyun AI · Works to try

Help · Renaming, copying, archiving and deleting a project

Renaming, copying, archiving and deleting a project

The overview is Projects.

Renaming one

Kuyun names a new project for you: the first line of what you asked, then a short headline once it has read your goal. If you would call it something else, click its name at the top of the project, type the new one (up to 80 characters) and press Enter — or click away; Escape keeps the old name. From then on the name is yours, and Kuyun never changes it again. Only the project's owner can rename it, and only while it is active. People it is shared with see the new name the next time they open it.

Copying one

To take a project in a different direction without changing the one you have — a shorter version of a course, the same trip with another budget — choose Make a copy… from the ⚙ on the project's header and give the copy a name (it offers the project's own, with "(copy)" after it). The copy opens, and from then on the two are separate projects: what you change in one never reaches the other.

The copy is YOURS, even when the project you copied is someone else's and you are a contributor in it: it is in your list, it counts toward your limit of active projects, its files count toward your storage, and the work Kuyun does on it is paid from your tokens.

What comes along is the work: the goal and what you answered, the brief, the plan and where it stands, every finding and chapter, the writing guide, the tables as they are now, the pictures, and the uploaded files — the ones in Output still in Output. What stays behind is everything about other people and about the original's life: nobody it was shared with is in the copy, nobody's progress or notes come along, every conversation stays where it was, the tables' history stays with the original, and the copy is not published, even when the original was. A contributor's copy also leaves what only the owner sees: anything the work drew from the owner's own saved pages and documents, and the models an administrator picked for it. An archived project can be copied too; the copy starts active.

Files that come with a copy are not read for facts about you: someone else may have put them there.

Viewers cannot make a copy. The owner and contributors can.

Ending one: archive, or delete

Both live behind the ⚙ on the project's header, along with Make a copy, Invite people and Publish. They are not the same thing, and the menu keeps them apart on purpose: archiving keeps everything, deleting keeps nothing.

Archive

Archive a project when you have what you came for. Archived projects fold away under Archive in the list but are not deleted; everything they found stays readable.

Archive in the ⚙ menu opens a dialog that says what happens to this project before anything does: to the work, and, when it has them, to its publishing, its viewers and its contributors. Archive this project there archives it; Cancel leaves it as it was. What it tells you is below.

If the project is published, it leaves Explore while it is archived, and its link says there is no such project. It stays published: reopening it lists it again and opens the link (Sharing a project).

Readable, but the WORK takes no more changes. Ask its chat to revise the plan, add a step or reword the goal and it will tell you the project is archived rather than doing it, and the buttons for those are gone from the page. If Kuyun had asked you something and you never answered, it stops asking — the question stays in the history, but it is no longer waiting on you and nothing is flagged. Nothing runs on it either: no daily research, no new writing. On an archived COURSE, that reaches the viewer too — the chapters stay there to read, and the Start button on their practice does not: a practice run is recorded against the course, and an archived course records no more progress — the conversation itself is still kept and still reads back. Your FILES are still yours — you can add and remove them on an archived project, because they are your documents rather than the project's work. If you want the work to go on, start a project from what this one found.

Archiving frees a slot. Your plan sets how many projects you can have active (Tokens), and when you hit it Kuyun asks you to archive one before starting another — the archived ones stay in the list and stay readable, they just no longer count.

Reopen undoes it: the ⚙ menu on an archived project you own has ↺ Reopen, and the work picks up where it stopped. It counts toward the limit again, so if you are at the limit, archive another first.

Only you archive it. Kuyun never archives a project by itself, however long it sits untouched. A project it archived for being idle before 31 October 2026 carries the note "No activity for 14 days — reopen it any time", and Reopen brings it back like any other.

Delete

Delete removes the project and everything that was only ever about it: the goal and the plan, every finding and chapter, the files you uploaded TO it and their contents, the conversation and anything spoken in it, any pictures it kept, its tables and their history, any reminders you set on it, and — for a published course — its public page. It cannot be undone, and Kuyun keeps no copy you could restore it from.

One small exception, for honesty rather than because you need to act on it: if Kuyun ever had to escalate a problem with this project to the people who run it, a line recording that an escalation happened stays in their operations log. When you delete, your project's title and what you wrote are hidden from anyone reading that log — though the original entry is not erased from it.

A second exception, because it lives in another project: if another project was linked to this one and asked it questions, the answers it was given stay where they were asked — in that project's conversation or plan. That project may be someone else's, so deleting yours does not reach those answers.

Because of that it asks you to type the project's title before it will go ahead. If you shared the project, the dialog says how many people have it: their access ends and their side of the conversation goes too, so a course you delete is a course its viewers lose.

Only the person who created a project can delete it. Anyone you shared it with can leave it by asking you to revoke their access, which takes nothing away from you.

Files you uploaded to a project live in My Files under that project's folder — the ones you shared in its Output folder too — and deleting the project deletes them. Replacing a shared file, from here or from My Files, keeps the new one private until you share it again. A file you want to keep should be downloaded first, from My Files.

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.