K3Nova
Inspect the saved file tree
Run this inside the folder where you saved the HTML, CSS, JavaScript, and assets.
cd <project-folder>
find . -maxdepth 2 -type f | sortGoal and short answer
Yes, but the exact method depends on where the website was created. If Kimi generated source files in a coding workspace, save the HTML, CSS, JavaScript, assets, and package files as a local project. If you are in Kimi Code, the kimi export command packages a session; that is useful evidence, but it is not the same as a production-ready website folder.
Ask Kimi for a clean file tree and a run command, then test the site locally before publishing it anywhere.
Copyable commands
Copy the website files into a real folder first. A Kimi Code session ZIP is useful backup, not the website itself.
Serve a static site locally
Use this for plain HTML/CSS/JavaScript output.
cd <project-folder>
python3 -m http.server 4178Run a framework site locally
Use this when the export includes package.json and a documented dev script.
cd <project-folder>
npm install
npm run devArchive the Kimi Code session separately
Keep this ZIP as context, not as the production website folder.
mkdir -p "$HOME/kimi-site-archives"
kimi export -y -o "$HOME/kimi-site-archives/kimi-site-session.zip"AI handoff prompt and permissions
Copy this prompt into Kimi Code, K3Nova, or another AI agent. Keep approval manual for file writes, shell commands, account actions, and secrets.
Copyable AI prompt
Use this to give the agent the task and safety boundary in one message.
You are my AI agent for this task: turn a Kimi-generated website into a local project folder, run it locally, and list what still needs manual review before publishing.
Start by restating the goal and the permissions you need.
Use official docs or the files I provide before making claims.
Give me a direct answer first, then a short table or checklist.
If commands are needed, show exact copyable commands without a shell prompt.
Ask before writing files, running shell commands, deleting or moving data, logging in, spending money, changing account settings, or handling API keys.
Stop and ask me when a step requires secrets, payment, account access, destructive cleanup, or a permission broader than the task.Recommended AI permissions
| Permission | Give AI | Why |
|---|---|---|
| Read-only project access | Allow Read, Grep, and Glob only in the selected project or config folder. | Lets the agent inspect state before acting. |
| Shell commands | Ask before Bash or any CLI command; run one command at a time. | Commands can change files, packages, sessions, or network state. |
| File edits | Ask before Write or Edit, and require a diff before applying changes. | Prevents hidden config or source edits. |
| Hard stops | Deny payment, login, secret exposure, account changes, and destructive delete commands. | These are not safe to automate casually. |
Runbook
Ask for the file tree
Request separate index.html, style files, scripts, assets, and any package.json needed to run the site.
Save assets with paths intact
Images, fonts, and videos must stay in the same relative folders used by the HTML and CSS.
Run locally
For static pages, open index.html or serve the folder with a simple local server. For frameworks, install dependencies and run the documented dev command.
Export the session only as backup
Use Kimi Code export to archive the conversation and context, then keep the actual site files in a project folder or Git repository.
Website export choices
| Situation | Best action | Check before handoff |
|---|---|---|
| Kimi wrote plain files | Save the file tree locally | Open the page and confirm every asset loads |
| Kimi Code changed a repo | Commit or archive the changed files | Run the local dev command and targeted checks |
| You only have a chat answer | Ask for complete files and folder names | Do not publish until files exist locally |
| You need a record of the session | Use kimi export | Remember that a session archive is not the site itself |
Notes before you continue
What to request from Kimi
Ask for a complete project with file names, folder structure, setup command, local test command, and deployment notes.
What to inspect before publishing
Check responsive layout, broken asset paths, form behavior, console errors, metadata, favicon, sitemap needs, and whether any placeholder copy remains.
What not to assume
A screenshot or chat answer is not a website export. You need the actual files or a repository change.
FAQ
Can Kimi export a website as one HTML file?
It can produce a single-file static page when you ask for that format, but larger sites are easier to maintain as a folder.
Is kimi export the website export command?
No. It packages a Kimi Code session for sharing or archiving. Keep the actual website files separately.
What is the safest first local test?
Serve the folder locally, open the homepage, resize the browser, and check console errors and missing assets.