# What Is the Roadmap for Kimi Code? 9 Strategic Themes Driving Moonshot AI's Coding Assistant

> Discover Kimi Code's roadmap driving moonshot AI. Explore v2 agent engine, expanded SDKs, improved storage, and streamlined deployment for a unified full-stack TypeScript monorepo.

- Repository: [Moonshot AI/kimi-code](https://github.com/MoonshotAI/kimi-code)
- Tags: roadmap
- Published: 2026-08-15

---

**Kimi Code's roadmap focuses on unifying its full‑stack TypeScript monorepo around a mature v2 agent engine, expanded SDKs, improved storage backends, and streamlined deployment tooling.**

The Kimi Code repository powers Moonshot AI's "Kimi" coding assistant. Its modular architecture splits functionality across a CLI/TUI front‑end, core agent engines, server runtimes, and reusable SDKs. The project's strategic direction is documented across multiple AGENTS.md files, the CONTRIBUTING guide, and package‑specific READMEs that collectively define eight active roadmap themes.

---

## Full‑Stack UI Unification

The **web UI currently lives in a separate repository** and ships as a pre‑built bundle located at `apps/kimi-code/dist-web`. According to the root [`AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/AGENTS.md), the planned evolution brings the web interface directly into the monorepo with hot‑reloading support during development. This creates a single "Kimi Code" experience spanning CLI, TUI, and browser environments.

---

## Agent‑Core v2 Maturity

The **v2 engine** in `packages/agent-core-v2` introduces several architectural improvements over the legacy v1 implementation:

- **DI‑based lifecycle scopes** for dependency injection
- **Flag system** for runtime feature toggles
- **Flexible service layer** for extensibility

As documented in [`packages/agent-core-v2/AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/agent-core-v2/AGENTS.md), the roadmap calls for hardening this infrastructure, completing the feature‑flag framework, and eventually deprecating v1 in favor of a stable public API.

---

## Enhanced SDKs and Language Bindings

The public SDK resides in `packages/node-sdk` with a client façade in `packages/klient`. The [`packages/node-sdk/AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/node-sdk/AGENTS.md) outlines plans for first‑class TypeScript typings, automated changeset versioning, and generated bindings for additional languages including Python and Go.

```ts
import { KimiClient } from '@moonshot-ai/kimi-code-sdk';

const client = new KimiClient({ apiKey: process.env.KIMI_API_KEY });
const session = await client.createSession();

const reply = await session.runPrompt('Write a TypeScript debounce utility.');
console.log(reply);

```

---

## MiniDB Storage Improvements

The search index layer in `packages/minidb` includes an explicit "Caveats / roadmap" section per its README. Planned enhancements include:

- Pluggable storage backends (SQLite, Postgres)
- Incremental indexing capabilities
- Query API exposure for external tool integration

---

## Experimental Feature‑Flag Framework

Flags are currently declared per‑package, such as the `search_worker` flag referenced in [`packages/agent-core/AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/agent-core/AGENTS.md). The roadmap targets:

1. Consolidating definitions into a central registry
2. Adding UI toggles for runtime configuration
3. Adopting a "stable‑by‑default" policy for new flags

Runtime flag activation works through the registry at [`packages/agent-core/src/flags/registry.ts`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/agent-core/src/flags/registry.ts):

```ts
import { flags } from '@moonshot-ai/agent-core';

flags.enable('search_worker');

```

---

## CLI/TUI Ergonomics

The CLI in `apps/kimi-code` drives the engine through the SDK. The [`apps/kimi-code/README.md`](https://github.com/MoonshotAI/kimi-code/blob/main/apps/kimi-code/README.md) documents planned improvements:

- Richer command set for session management and multi‑agent orchestration
- Enhanced TUI rendering performance
- Scripting‑friendly REPL interface

Install the current release via the official distribution script:

```bash
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash
kimi --version

```

---

## Observability and Telemetry

The `packages/telemetry` module will expand to export structured logs, integrate OpenTelemetry tracing, and provide a dashboard for session analytics according to its README.

---

## Testing and CI Enhancements

The repository currently runs a full test matrix via Vitest and GitHub Actions defined in [`.github/workflows/ci.yml`](https://github.com/MoonshotAI/kimi-code/blob/main/.github/workflows/ci.yml). Future work targets:

- End‑to‑end tests for the complete stack
- Flaky‑test detection improvements
- Workspace‑sync enforcement for `flake.nix`

---

## Packaging and Deployment

The server implementation in `packages/kap-server` will produce Docker images, Helm charts, and a SaaS‑ready deployment pipeline supporting zero‑downtime upgrades, as detailed in [`packages/kap-server/AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/kap-server/AGENTS.md).

Start the development server with hot‑reloading:

```bash
pnpm dev:server

```

---

## Key Source Files Defining the Roadmap

| File | Purpose |
|------|---------|
| [`AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/AGENTS.md) (root) | High‑level project map and workflow requirements |
| [`packages/agent-core-v2/AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/agent-core-v2/AGENTS.md) | v2 lifecycle scopes, flag system, design docs |
| [`packages/minidb/README.md`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/minidb/README.md) | Storage layer roadmap and caveats |
| [`apps/kimi-code/README.md`](https://github.com/MoonshotAI/kimi-code/blob/main/apps/kimi-code/README.md) | CLI/TUI usage and development commands |
| [`packages/node-sdk/AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/node-sdk/AGENTS.md) | Public API surface and versioning policy |
| [`packages/kap-server/AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/kap-server/AGENTS.md) | Server RPC surface and endpoints |
| [`CONTRIBUTING.md`](https://github.com/MoonshotAI/kimi-code/blob/main/CONTRIBUTING.md) | Contribution guidelines with roadmap alignment requirements |

---

## Summary

- **Kimi Code's roadmap** spans nine active themes from UI unification to deployment automation, all documented across the monorepo's AGENTS.md files.
- **Agent‑core v2** represents the future engine architecture, replacing legacy v1 with DI‑based scopes and a formal flag system.
- **SDK expansion** targets multi‑language bindings and automated versioning through changesets.
- **Storage evolution** moves MiniDB toward pluggable backends with incremental indexing.
- **Contribution alignment** is mandatory—per [`CONTRIBUTING.md`](https://github.com/MoonshotAI/kimi-code/blob/main/CONTRIBUTING.md), only roadmap‑aligned PRs are accepted for merge.

---

## Frequently Asked Questions

### How does Kimi Code's roadmap affect external contributors?

The [`CONTRIBUTING.md`](https://github.com/MoonshotAI/kimi-code/blob/main/CONTRIBUTING.md) file explicitly states that pull requests must align with documented roadmap themes to be considered for merge. Contributors should review the relevant AGENTS.md files for their target package before submitting changes.

### When will the v1 agent engine be deprecated?

No specific timeline is published. The v2 engine in `packages/agent-core-v2` is actively being hardened with scoped services and persistence layers. Deprecation of v1 will follow once the v2 public API reaches stability.

### What languages will Kimi Code SDKs support beyond TypeScript?

The [`packages/node-sdk/AGENTS.md`](https://github.com/MoonshotAI/kimi-code/blob/main/packages/node-sdk/AGENTS.md) identifies Python and Go as priority targets for generated language bindings, though implementation sequencing is not specified.

### Can I run Kimi Code's web UI in development mode today?

Not within the monorepo. The web UI currently ships as a pre‑built bundle at `apps/kimi-code/dist-web` from a separate repository. The roadmap includes monorepo integration with hot‑reload support as a planned enhancement.