[FEATURE] Native ACP Support to Expose Console Output in IDE Integrations

Resolved 💬 1 comment Opened Apr 15, 2026 by 3uyuan1ee Closed May 24, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When integrating Claude Code within IDEs such as VS Code or Zed, users frequently encounter a frustrating limitation: the console output generated by Claude Code during task execution (e.g., command logs, errors, debugging info) is not readily visible within the IDE interface. Instead, users must switch to an external terminal or monitor background processes, which severely hampers development efficiency and debugging experience.

Proposed Solution

Add native support for the Agent Client Protocol in Claude Code, enabling it to operate as a standard ACP agent. Specifically, this could include:

Implementing the ACP JSON-RPC interface to stream runtime logs, command output, tool-call results, etc., to an ACP-compatible client.
Introducing a CLI flag (e.g., --acp) that allows an IDE to spawn Claude Code as a child process and communicate over stdio.
Ensuring that ACP-mode output formats are compatible with existing text / json output modes to facilitate parsing and presentation within IDEs.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗