MoonshotAI / MoonshotAI/kimi-code

Feature request: image/file attachments in Remote Control sessions (kimi rc web UI + Kimi Work mobile remote)

Open
#3,576 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?

Please add support for image / file attachments in Remote Control sessions — both in the kimi rc web interface and in the Kimi mobile app when remotely controlling Kimi Work (added in Kimi Work 3.2.5).

Right now, when I control my desktop session from my phone, the input box has no attachment button — I can only send text. This is a significant gap, because a huge share of "show, don't tell" moments happen exactly when you're away from the computer:

  • sending a screenshot of a broken UI / error message so the agent can see the problem;
  • sending a photo of a document, whiteboard, or hardware for the agent to read or analyze;
  • attaching a file (log, PDF, CSV) from the phone for the agent to process on the desktop.

The desktop app and the regular Kimi mobile chat already support attachments (up to 100 MB), so this would bring remote sessions to parity.

Suggested behavior:

  1. An attachment button in the remote session input (mobile app + rc web page).
  2. The attached image/file is transferred to the host machine (e.g., into the session workspace) and passed to the model as a normal vision/file input.
  3. Works for both existing sessions being followed remotely and new tasks started from the phone.
Additional information
  • Kimi Work version: 3.2.5 (2026-09-04), the release that introduced remote control from the phone.
  • Text messaging, approvals, and session sync already work well remotely — attachments are the main missing piece.
  • Related: issue #2269 and #1282 discussed remote control generally; this request is specifically about media/file input in remote sessions.

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 locating the remote-session input in the kimi rc web UI and the Kimi mobile remote-control flow, then compare them with attachment handling in the desktop app and regular Kimi mobile chat. Done means existing and newly started remote sessions can send images and files from both clients, transfer them to the host, and pass them to the model.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.