ACP titles are non descriptive, even though they could be

Open Beginner friendly
#2,093 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@Aafimalek is already working on this.

Since Nov 11, 2026.

  • #2136 by @Aafimalek — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust

Research direction

Start in acp.rs at the serverevent:toolinput handling, where the issue says raw_input contains an intent; read how the update title is currently built and how tool_title(name) is used. Check the ACP update behavior and relevant tests, then confirm that an intent is used when present and the existing tool title is used when it is absent.

Written by the indexing model from the issue text.

Description

autonomous: likely enhancement type: feature

currently, ACP tool titles are mapped through this

fn tool_title(name: &str) -> String {
    match name {
        "bash" => "Running shell command".to_string(),
        "read" => "Reading file".to_string(),
        "write" => "Writing file".to_string(),
        "edit" | "multiedit" | "patch" | "apply_patch" | "replace" => "Editing files".to_string(),
        "agentgrep" | "grep" | "glob" | "ls" => "Searching workspace".to_string(),
        "webfetch" | "websearch" => "Fetching web content".to_string(),
        other => other.replace('_', " "),
    }
}

however, in line the serverevent:toolinput of acp.rs, we have raw_input, which contains "intent", which is a much more descriptive title.

should the ACP send the intent as the update title and only fallback to tool_title(name) mapping if there is no intent? it would be much more useful for consumers than seeing "Running shell command" 30 times in a row

Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
21h 27m
Merged PRs (30d)
7

Getting set up

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.

More from 1jehuang/jcode

All issues in 1jehuang/jcode

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.