Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Human-readable approval prompts + merge Kimi and Kimi Code into one app

Abierto
  • ¿Algo no está bien?
#4,030 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
typescript
Área
accessibility, cli, design, desktop

Línea de trabajo

Start by locating the approval-dialog implementation and the separate Kimi and Kimi Code client entry points. Define the user-facing behavior and scope for both proposals before changing anything; done would require an agreed design, human-readable approval details, and a unified app experience.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
What feature would you like to see?

Hello!
I have two suggestions for improving Kimi Code.

  1. Approval prompts in human language, not terminal language.
    Right now, approval dialogs show the user a raw command and nothing else. For a person without a technical background, this is a meaningless jumble of characters: it's impossible to tell what is being proposed, where the danger is, and what happens if you agree. As a result, users either click Approve blindly (which defeats the whole purpose of confirmation) or get stuck and have to ask someone for help.
    AI coding agents are no longer used only by programmers — there's a huge army of vibe coders who solve their tasks through AI and don't read bash. For them, the current approval dialogs are a constant pain.
    Proposal: by default, the approval card should contain a human-readable explanation, with the command hidden under a "Details" toggle:
    What I want to do — one or two plain-language sentences ("I'll delete temporary files from the previous check and run the installer test").
    Where the danger is — honest and specific ("Only temporary logs will be deleted, your files are untouched" or "This command changes system settings").
    What I recommend — the agent's advice ("This is safe, go ahead" / "Better to decline, because...").
    The technical command — collapsed by default, expandable on click for those who care.
    This is a simple UI change that would make the product accessible to the mass user without taking anything away from professionals.
  2. Merge Kimi and Kimi Code into a single desktop app.
    Right now these are two separate products with two windows, two quotas, and constant confusion about where everything lives. The user shouldn't have to care whether something is "chat" or "code" — it's the same AI system, and it should be used in one place: chat, project files, agent tasks, subscription — all in one window. Two apps is unnecessary complexity for the user and, frankly, makes the product feel unfinished. Build one client with modes, not two clients with duplicated functionality.
    Thank you!
Image
Additional information

No response

Lenguaje dominante
TypeScript
Estrellas
7.7k
Forks
1.3k
Merge medio
12 h 35 min
PR fusionados (30 d)
311

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de MoonshotAI/kimi-code

Todos los issues de MoonshotAI/kimi-code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.