MoonshotAI / MoonshotAI/kimi-code

VS Code: open a Kimi tab beside the active editor

Open
#2,867 1 comment 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 VS Code command, kimi.openInTabBeside, that opens a new Kimi Code editor panel beside the active editor group.

The extension already supports the Activity Bar sidebar and kimi.openInTab, but the existing tab command always targets ViewColumn.One. Users who keep AI conversations in a dedicated adjacent editor group currently have to move each new Kimi panel manually or rely on workspace-specific helper extensions.

The proposed command would call the existing panel creation path with vscode.ViewColumn.Beside. The current kimi.openInTab and kimi.openInSideBar behavior would remain unchanged.

Additional information

A focused implementation is ready locally for discussion. It:

  • adds only the new command and Command Palette entry;
  • makes createPanel accept an optional view column while preserving ViewColumn.One as its default;
  • uses the native ViewColumn.Beside placement instead of moving tabs or manipulating editor groups;
  • includes provider unit tests, an Extension Host smoke check, and a kimi-code changeset;
  • contains no workspace paths, Claude integration, startup restoration, or machine-specific heuristics.

Local validation passed for the new tests, VS Code extension typecheck/build, lint, VSIX packaging, and a real Extension Host smoke run. I would like maintainer feedback on the command name and whether this placement option fits the extension roadmap before opening a PR, as required by CONTRIBUTING.md.

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 existing kimi.openInTab and kimi.openInSideBar commands and the createPanel path in the TypeScript extension code. Add the kimi.openInTabBeside command using the existing provider tests and Extension Host smoke check as guides, then run the listed typecheck, build, lint, packaging, and smoke validations; done also requires a kimi-code changeset and maintainer agreement on the command name.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.