CommandCodeAI / CommandCodeAI/command-code

"Zed IDE integration"

Open
#644 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
4k
Forks
350
PR merge metrics
No merged PRs in 30d

Description

Summary

Zed IDE has a grown to have a rich collection of ACP coding agents like Claude, OpenCode, Codex, etc.
It would be great for Command Code to have it's presence in the Zed ecosystem for its sheer performance.

Expected Behavior

Command Code should be an in-built agent Zed's ACP registry.
OR
/ide should success.

The idea is to make the Command Code agent aware of file changes happening in the editor, as well as display diffs of changes it makes at each run.

Actual Behavior

Command Code currently NEITHER has an in-built agent Zed's ACP registry
NOR succeeds at /ide in the Zed IDE.

Steps to reproduce the issue
  1. Open Zed IDE

  2. Open Command Code in its terminal

  3. Enter \ide
    The operation will not succeed.

  4. Open Zed's ACP Registry

  5. Look for Command Code
    It currently does not exist.

Command Code Version

1.14.1

Operating System

macOS

Terminal/IDE

zed

Shell

zsh

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

OS: macOS Sequoia 15.7.7

Contributor guide

No contributing guide indexed for this repository

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 inspecting the /ide entry point and the requirements for Zed's ACP Registry. Reproduce the failure in Zed on macOS, then determine whether the integration should register Command Code as an agent or make /ide succeed. Done means Zed recognizes the agent and file changes and per-run diffs are available as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, zsh
Domain
cli, developer-experience, devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.