try Kimi

Why not working?

A full-stack project includes frontend UI, backend services, and persistent storage. Kimi Agent can generate all three, but successful runtime depends on environment setup, auth configuration, and publish actions.

If your app isn't working as expected, the issue is usually not missing backend capability. It is typically an incomplete preview, auth, database, or publish step.

Full-stack workflow

  1. Generate: Agent creates frontend + backend + database schema and data logic.
  2. Preview: Run in sandbox for local full-stack testing (manual start may be required in some cases).
  3. Version: Agent can use version tools and create commits automatically.
  4. Rollback: You can return to any previous commit version.
  5. Publish / Share: The app is deployed to a public URL only after you manually publish.

Common failure reasons

SymptomLikely CauseWhat to Do
Frontend loads but API failsSandbox runtime not startedStart sandbox and rerun preview
Data not saved or not visibleDB not initialized or migratedRe-run DB setup or migration step
Login failsAuth flow not configured correctlyVerify Kimi Login config and callback settings
Others can't access your appApp not publishedClick Publish/Share to deploy
Recent changes broke functionalityRegression in latest versionRoll back to a stable commit

Authentication support

  • Phase 1: Supports Kimi Login.
  • Next phase: Additional OAuth providers will be added.
  • Also supported: Standard DB-based email/password account login can be generated by Agent.

Version and rollback

  • Agent supports new version tooling and can perform autonomous git commit during development.
  • You can view version history and roll back to a selected commit when needed.

Preview vs Publish

  • Preview: For development and testing in sandbox; may require manual sandbox startup in some scenarios.
  • Publish/Share: Manual user action that deploys your app to a publicly accessible environment.

Agent is best for

  • Rapid prototyping of full-stack products
  • CRUD flows with persistent storage
  • Basic admin or back-office data operations
  • End-to-end demo projects with login, data, and deployment flow

Current boundaries

  • Advanced production operations (for example, complex SRE and multi-region HA) still require manual engineering work.
  • For high-risk production scenarios, perform security review and deployment hardening before release.