vtcode 0.98.7

A Rust-based terminal coding agent with modular architecture supporting multiple LLM providers
use anyhow::{Result, bail};
use vtcode::acp::{StandardAcpAdapter, ZedAcpAdapter};
use vtcode_core::cli::args::AgentClientProtocolTarget;
use vtcode_core::config::types::AgentConfig as CoreAgentConfig;
use vtcode_core::config::{AgentClientProtocolTransport, VTCodeConfig};
use vtcode_core::core::interfaces::acp::{AcpClientAdapter, AcpLaunchParams};

pub async fn handle_acp_command(
    config: &CoreAgentConfig,
    vt_cfg: &VTCodeConfig,
    target: AgentClientProtocolTarget,
) -> Result<()> {
    if !vt_cfg.acp.enabled {
        bail!(
            "Agent Client Protocol integration is disabled. Enable it via [acp] in vtcode.toml or set VT_ACP_ENABLED=1."
        );
    }

    match target {
        AgentClientProtocolTarget::Zed => {
            if !vt_cfg.acp.zed.enabled {
                bail!(
                    "Zed integration is disabled. Enable it via [acp.zed] in vtcode.toml or set VT_ACP_ZED_ENABLED=1."
                );
            }

            if vt_cfg.acp.zed.transport != AgentClientProtocolTransport::Stdio {
                bail!("Only the stdio transport is currently supported for Zed ACP integration.");
            }

            let adapter = ZedAcpAdapter;
            let params = AcpLaunchParams::new(config, vt_cfg);
            adapter.serve(params).await?
        }
        AgentClientProtocolTarget::Standard => {
            let adapter = StandardAcpAdapter;
            let params = AcpLaunchParams::new(config, vt_cfg);
            adapter.serve(params).await?
        }
    }

    Ok(())
}