MoonshotAI / MoonshotAI/kimi-cli

feat(git): official Co-authored-by trailer with branded GitHub avatar

Open
#2,256 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
11.4k
Forks
1.3k
Avg merge
9h 47m
Merged PRs (30d)
2

Description

Feature Request: Official Co-authored-by trailer for Kimi Code CLI commits

What feature would you like to see?

Add support for automatically appending an official Co-authored-by git trailer to commits created by Kimi Code CLI, backed by a dedicated GitHub account with a verified email and a branded Kimi avatar.

Motivation

I am an active user of multiple AI coding agents — Claude Code, Codex CLI, Amp, and now Kimi Code CLI. One thing I deeply appreciate about Claude Code is that every commit it helps produce carries:

Co-authored-by: Claude <noreply@anthropic.com>

This renders a recognizable avatar on GitHub:

Claude avatar

It makes the provenance of every change transparent. When I look at my repositories, I can immediately see which agent contributed to which commit. This is valuable for:

  1. Transparency — anyone reviewing my code knows when AI assistance was involved
  2. Attribution — giving credit to the tool that actually produced the work
  3. Community learning — showing which agents excel at which tasks helps others choose the right tool for their workflow
  4. Personal tracking — I can look back and see which model solved a particular problem best
Current state

Kimi Code CLI does not append any Co-authored-by trailer. I have searched extensively and found:

  • No official Kimi GitHub user account with a verified email
  • No documented co-author convention from Moonshot
  • MoonshotAI/Kimi-K2.5#2 — an open question asking for the correct trailer format, with zero response since February 2026
  • The MoonshotAI organization itself uses Claude co-authors in the kimi-help-center repo (Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>)

Because there is no official account or email, every commit I make with Kimi Code CLI appears as my own work alone. I would much rather show that Kimi was my collaborator.

Desired behavior

When Kimi Code CLI creates or amends a commit, it should append a standard git trailer:

Co-authored-by: Kimi <noreply@moonshot.ai>

(or whatever email Moonshot chooses to verify on the official account).

To make this work, Moonshot would need to:

  1. Create a GitHub user account for Kimi (e.g. github.com/kimi or github.com/kimi-code — currently both are taken by unrelated users, so github.com/kimi-ai or similar could work)
  2. Upload a branded Kimi logo as the account avatar
  3. Verify the co-author email on that account
  4. Document the chosen email so the community knows which trailer to use
  5. Add an opt-in config flag in Kimi CLI (e.g. git_coauthor = true in ~/.kimi/config.toml) that appends the trailer to commits
Why this matters for the ecosystem

I am the maintainer of jackin' — a Docker orchestrator for AI coding agents. jackin' currently supports Claude Code, Codex CLI, and Amp as first-class agents, and we are actively adding Kimi Code CLI (jackin'#333).

One of our design principles is transparent attribution: every agent should leave a clear trail of its contributions. Claude does this beautifully. Codex has the github.com/codex account ready for it. Kimi is the odd one out.

For users like me who run multiple agents in parallel — sometimes Claude handles architecture, Codex handles API design, and Kimi handles implementation — being able to see at a glance which agent did what is not vanity. It is valuable metadata about model capabilities.

Proposed implementation (non-breaking)
# ~/.kimi/config.toml
[git]
co_author = true
# Optional: override the default trailer
co_author_email = "noreply@moonshot.ai"

When co_author = true, Kimi CLI appends the trailer to any commit it creates or amends. Default should be false until Moonshot publishes the official account, then it can become true by default.

Environment
  • kimi-cli version: latest (1.43.0)
  • OS: all platforms

功能请求:为 Kimi Code CLI 提交添加官方的 Co-authored-by 署名

期望的功能

为 Kimi Code CLI 自动添加官方的 Co-authored-by Git 署名尾部(trailer),并配套一个带有认证邮箱和品牌头像的专属 GitHub 账户。

动机

我是多个 AI 编程代理的活跃用户——Claude CodeCodex CLIAmp,以及现在的 Kimi Code CLI。我非常欣赏 Claude Code 的一点是,它帮助的每一个提交都会附带:

Co-authored-by: Claude <noreply@anthropic.com>

这在 GitHub 上会显示一个可识别的头像:

Claude avatar

它让每个变更的来源都一目了然。当我查看自己的仓库时,我可以立即看到哪个代理贡献了哪个提交。这对以下方面很有价值:

  1. 透明度 — 任何审查我代码的人都知道何时使用了 AI 辅助
  2. 署名 — 给予实际产生工作的工具以credit
  3. 社区学习 — 展示哪个代理擅长哪种任务,帮助其他人选择正确的工具
  4. 个人追踪 — 我可以回顾并查看哪个模型在解决特定问题时表现最好
当前状态

Kimi Code CLI 没有附加任何 Co-authored-by 署名。我已经广泛搜索并发现:

  • 没有带有认证邮箱的官方 Kimi GitHub 用户账户
  • Moonshot 没有 documented 的合著者惯例
  • MoonshotAI/Kimi-K2.5#2 — 一个自 2026 年 2 月以来零回复的开放问题
  • MoonshotAI 组织本身在 kimi-help-center 仓库中使用 Claude 的合著者 (Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>)

因为没有官方账户或邮箱,我用 Kimi Code CLI 进行的每一次提交都只显示为我个人的工作。我非常希望能显示 Kimi 是我的协作者。

期望的行为

当 Kimi Code CLI 创建或修改提交时,它应该附加一个标准的 Git 署名:

Co-authored-by: Kimi <noreply@moonshot.ai>

(或 Moonshot 选择在官方账户上验证的任何邮箱)。

为了实现这一点,Moonshot 需要:

  1. 为 Kimi 创建一个 GitHub 用户账户(例如 github.com/kimigithub.com/kimi-code — 目前两者都被无关用户占用,所以 github.com/kimi-ai 或类似的可以工作)
  2. 上传一个品牌化的 Kimi logo 作为账户头像
  3. 在该账户上验证合著者邮箱
  4. 记录所选择的邮箱,以便社区知道使用哪个署名
  5. 在 Kimi CLI 中添加一个可选配置标志(例如 ~/.kimi/config.toml 中的 git_coauthor = true),将署名附加到提交中
为什么这对生态系统很重要

我是 jackin' 的维护者 — 一个用于 AI 编程代理的 Docker 编排器。jackin' 目前将 Claude Code、Codex CLI 和 Amp 作为一等公民支持,我们正在积极添加 Kimi Code CLI (jackin'#333)。

我们的设计原则之一是透明署名:每个代理都应该留下其贡献的清晰痕迹。Claude 在这方面做得非常出色。Codex 已经准备好了 github.com/codex 账户。Kimi 是例外。

对于像我这样并行运行多个代理的用户 — 有时 Claude 处理架构,Codex 处理 API 设计,Kimi 处理实现 — 能够一目了然地看到哪个代理做了什么,这不是虚荣。这是关于模型能力的有价值的元数据

建议的实现方式(非破坏性)
# ~/.kimi/config.toml
[git]
co_author = true
# 可选:覆盖默认署名
co_author_email = "noreply@moonshot.ai"

co_author = true 时,Kimi CLI 将它创建或修改的任何提交的署名附加到末尾。默认值应为 false,直到 Moonshot 发布官方账户,然后可以默认变为 true

环境
  • kimi-cli 版本: 最新 (1.43.0)
  • 操作系统: 所有平台

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 with the CLI's existing commit creation and amendment path and the configuration represented by ~/.kimi/config.toml. Resolve the official GitHub account and verified email, then define the opt-in behavior for created and amended commits; done means the trailer convention and configuration are documented and implemented.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.