Start with the task
Name the output before choosing a tool: research memo, code plan, document edit, slide outline, spreadsheet cleanup, website draft, or agent runbook.
Workspace guide
Use K3Nova as an independent Kimi-style AI workspace for long context, agent planning, research, docs, code, slides, sheets, and website tasks.
Use K3Nova when you want a Kimi-style workspace that keeps the prompt, source context, tool choice, and next action in one working surface. It is useful for long-context research, coding plans, document drafts, slide outlines, sheet cleanup, website planning, and agent handoffs.
Use official Kimi pages when the task is account login, official billing, API keys, membership, or support. K3Nova is independent, so it should help you evaluate and run a workflow without pretending to be the official Kimi account portal.
Use this section to keep the next step practical before you touch accounts, files, infrastructure, or hardware.
| Check | Look for | Why it matters |
|---|---|---|
| Read the official source | Start with the model card, help center, docs, or official product page before trusting summaries. | Model names, limits, and prices change. |
| Name the path | Decide whether you need a hosted app, API call, local client, or full self-managed deployment. | Different paths have different costs and account boundaries. |
| Check the boundary | Keep login, payment, API keys, private files, and account settings on the official surface. | A public guide should help you choose, not handle sensitive actions. |
| Keep evidence | Save the source link, date, version, and practical next step that shaped your decision. | This makes later review easier for a team. |
| Need | Use this surface | Check before acting |
|---|---|---|
| Long-context research | K3Nova or official Kimi with a source map | Whether the answer separates sources, assumptions, and next checks |
| Coding workflow | Kimi Code for terminal work, K3Nova for planning and review | Model ID, context size, permissions, and whether file writes need approval |
| Docs, slides, sheets, or websites | Kimi Agent for official generation flows, K3Nova for independent planning and review | Input files, desired output, export path, and account boundary |
| Official membership or API billing | Official Kimi pages | Domain, plan, token price, quota, and payment ownership |
| Local or self-hosting plan | K3Nova guides before hardware work | Whether you mean a local client, local workspace, hosted endpoint, or full model weights |
Name the output before choosing a tool: research memo, code plan, document edit, slide outline, spreadsheet cleanup, website draft, or agent runbook.
Use K3Nova for practical workspace evaluation, Kimi Code for terminal and IDE coding work, and official Kimi pages for account, membership, and API actions.
Paste or attach the smallest useful source bundle, then describe the reader, constraints, output format, and one follow-up check.
Before entering credentials, paying, running shell commands, or granting file access, confirm which product owns that action and whether approval is needed.
A workspace is more than a chat box. It should keep context, modes, files, output goals, and next steps visible enough that a task can continue without being rebuilt from scratch.
K3Nova fits when you want to test a Kimi-style flow for planning, research, coding, documents, slides, sheets, web pages, and safe AI-agent handoff prompts.
Official Kimi surfaces are the right place for official account login, membership, API configuration, Kimi Code entitlement, Kimi Agent, and Kimi support actions.
It is a working surface for long-context tasks, tools, source material, outputs, and follow-up actions around Kimi-style workflows.
No. K3Nova is an independent Kimi-style workspace and guide surface.
Start with the K3Nova workspace for a practical trial, then use the Kimi K3 guide hub when you need model, local, hardware, or account-boundary details.