Strixa AI
TopicsSearchPricing
Sign inStart tracking

Signal Detail

Loading signal detail

Reading this signal card's judgment, risks, and evidence.

Strixa AI
TopicsSearchPricing
Sign inStart tracking
Back to Signal Feed
CodeTracked since May 19, 2026

Add `crush acp` server mode for ACP session and tool interoperability

This change introduces a new `crush acp` command that enables Crush to run as an ACP server, adding core session and prompt flow support (initialize/authenticate/new session/prompt/model switching) plus lifecycle translation for permissions, tool calls, plans, and notifications. It consolidates prior ACP attempts and aligns the branch with current `main` while exposing ACP-compatible built-in and custom prompt/tool commands.

CrushACPcrush acpacp.Agent

Signal Intelligence

Confidence Level92%
Worth Continued TrackingFinal score 78% with 1 evidence item.
Primary Impact Areas
CrushACPcrush acp

What Happened

  • This change introduces a new `crush acp` command that enables Crush to run as an ACP server, adding core session and prompt flow support (initialize/authenticate/new session/prompt/model switching) plus lifecycle translation for permissions, tool calls, plans, and notifications. It consolidates prior ACP attempts and aligns the branch with current `main` while exposing ACP-compatible built-in and custom prompt/tool commands.
  • This change introduces a new `crush acp` command that enables Crush to run as an ACP server, adding core session and prompt flow support (initialize/authenticate/new session/prompt/model switching) plus lifecycle translation for permissions, tool calls, plans, and notifications. It consolidates prior ACP attempts and aligns the branch with current `main` while exposing ACP-compatible built-in and custom prompt/tool commands.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implements ACP protocol integration in Crush by wiring session lifecycle and prompt handling through the new server command and translating pubsub events (messages, permissions, tools, plans, sessions) into ACP streamable session notifications, so external controllers can orchestrate Crush agents without adapter-specific protocol logic.

Why Track This

Why It Matters

Developers and operators can now connect ACP-compatible clients directly to Crush as a server, which should reduce custom adapter work and simplify multi-tool orchestration of prompts, permissions, and tool actions during agent workflows. Technically, the PR completes ACP interface coverage (`acp.Agent`, `acp.AgentLoader`, `acp.AgentExperimental`) and publishes unified command/tool/session events via the Sink path, but adopters should continue monitoring for missing embedded-context support, unsupported media inputs, session-mode behavior gaps, and hidden startup errors from suppressed `NewAgentSideConnection` failures as rollout progresses.

Impact

Developers and operators can now connect ACP-compatible clients directly to Crush as a server, which should reduce custom adapter work and simplify multi-tool orchestration of prompts, permissions, and tool actions during agent workflows. Technically, the PR completes ACP interface coverage (`acp.Agent`, `acp.AgentLoader`, `acp.AgentExperimental`) and publishes unified command/tool/session events via the Sink path, but adopters should continue monitoring for missing embedded-context support, unsupported media inputs, session-mode behavior gaps, and hidden startup errors from suppressed `NewAgentSideConnection` failures as rollout progresses.

What To Watch Next

  • Watch whether Crush becomes a repeated pattern.
  • Track follow-up changes around Agent Orchestration Platforms.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: embedded_context_capability_declared_but_unimplemented, non_text_media_input_lacks_graceful_handling.
Open Topic TimelineOpen Technical EventOpen Original Sourceembedded_context_capability_declared_but_unimplemented / non_text_media_input_lacks_graceful_handling / session_mode_flags_not_enforced_in_permissions / no_integration_test_for_std_io_json_rpc / sink_subcomponents_without_test_coverage / server_run_masks_connection_initialization_errors

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

charmbracelet/crush PR #2450: feat: run Crush as an ACP server

Adds ACP server support in Crush (`crush acp`) with end-to-end `acp.Agent` interface coverage and Sink-based translation of internal events into ACP `SessionNotification`s.