ACP titles are non descriptive, even though they could be
Maintainers usually reply within 2 days
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
- Domain
- ai-infra-agents, cli
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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from 1jehuang/jcode
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
`jcode run` prints streamed reasoning one chunk per linePossibly taken @theammir claimed this 5 days ago. Openautonomous: likely bug type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
1jehuang/jcode#2134 · 1 comment ·
Maintainers usually reply within 2 days
-
autonomous: no triage: needs-decision
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
1jehuang/jcode#2079 · 1 comment ·
Maintainers usually reply within 2 days
-
autonomous: no triage: needs-decision
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
1jehuang/jcode#2070 · 1 comment ·
Maintainers usually reply within 2 days
-
bug triage: fixed-pending-release
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
1jehuang/jcode#2019 · 3 comments ·
Maintainers usually reply within 2 days
Similar issues
-
Selected chart highlights only its values, not its series names and category labelsPossibly taken @Higgs32584 claimed this today. Openbug priority: low ui
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/gridcraft#4390 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug bugfix priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
quarto-dev/q2#1219 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100