-
|
I’m using the OpenCode agent as the backend. Why don’t tool calls like read/patch show file name information, and how should I configure this? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
@0xmrpeter I noticed that in the screenshot you shared, the file name is shown after “read.” |
Beta Was this translation helpful? Give feedback.
-
|
Hey! Thanks for bringing this up — it's a real gap and your report helped us identify the root cause. Why it happens: OpenACP displays file names by reading the The same issue affects What's being done: PR #203 by @hightman addresses exactly this — adding camelCase field support and improving titles for tools like In the meantime: There's no config option to work around this right now, but the fix should be in the next release once the PR is merged. If you're running OpenACP from source you can track the PR directly. Thanks again for the detailed report — the screenshot was super helpful! |
Beta Was this translation helpful? Give feedback.

Hey! Thanks for bringing this up — it's a real gap and your report helped us identify the root cause.
Why it happens: OpenACP displays file names by reading the
file_pathfield from the tool's input metadata. However, OpenCode sends this field asfilePath(camelCase) instead offile_path(snake_case), so the parser doesn't pick it up and falls back to showing just the tool name (e.g. "Read" with no file).The same issue affects
apply_patchand a few other tools that don't send a standardkind, so they show up with minimal context in the tool card.What's being done: PR #203 by @hightman addresses exactly this — adding camelCase field support and improving titles for tools like
apply_patch…