MoonshotAI / MoonshotAI/kimi-code

Feature request: launch Kimi Code Desktop from the CLI

Open
#1,936 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

What feature would you like to see?

Add a kimi app command that opens Kimi Code Desktop from the terminal. When the Desktop app is missing, it should be able to obtain the matching official installer through a versioned release manifest, verify the artifact checksum, install only in a user-owned location without replacing an existing installation, and then launch the app.

The initial command shape is:

kimi app
kimi app --yes
kimi app --no-install

kimi app would ask for confirmation in an interactive terminal before a first install. --yes enables managed or non-interactive setup, and --no-install opens only an app that is already present. The CLI and Desktop would continue to use the same local Kimi server and session data.

Additional information

The release contract needs maintainer direction before implementation is proposed upstream:

  1. The command itself naturally belongs in the Kimi Code CLI, but the compatible Desktop installer and its versioned manifest need an agreed release owner.
  2. macOS can require code-signature and Gatekeeper validation; Windows and Linux distribution expectations need a documented policy as well.
  3. PR #1733 is moving Web/Desktop sources and Desktop release CI out of this repository. Please confirm whether the Desktop side of this feature should instead live in the destination code-app repository, while the CLI command remains here.

I have a local prototype and tests, but will wait for maintainer guidance on repository ownership and release integration before opening a PR.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the local prototype and tests, then review PR #1733 and the proposed destination code-app repository to establish ownership of the CLI and Desktop portions. The work is ready only after maintainers agree on the release owner, versioned manifest, installer verification and platform distribution policy.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.