anomalyco / anomalyco/opencode
File references from Read tool show prohibited (forbidden) icon — cannot click to open/download
Open
@jlongster is already working on this.
Since Aug 5, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Version
OpenWork 1.17.11 on Linux
Description
When using the Read tool to deliver a CSV file, the file reference appears in chat but shows a prohibited/forbidden icon on hover. The file cannot be opened, previewed, or downloaded from the chat link.
Steps to reproduce
- Generate a CSV file in the workspace (e.g.,
/home/usuario/Documentos/eclipse.csv) - Use the Read tool on the file path
- Hover over the file reference in the chat → shows prohibited icon
- Click the reference → nothing happens or access denied
Details
- The workspace path is
/home/usuario/Documentos(uppercase D) - The workspace is registered in
authorizedRootscorrectly - OpenWork internally registers the workspace as
/home/usuario/documentos(lowercase) inopenwork-server-tokens.jsonandopenwork-server-state.json - A symlink was created (
/home/usuario/documentos→/home/usuario/Documentos) but the issue persists - Both uppercase and lowercase variants were added to
authorizedRootsin both.opencode/openwork.jsonand~/.config/openwork/server.json— no effect - Duplicate token entries were added for both path variants in
server-tokens.json— no effect - The opencode server (port 39085) returns HTTP 401 for file requests even with valid tokens
Expected behavior
File references from the Read tool should be clickable and allow opening/downloading the file.
Config files inspected
~/.config/com.differentai.openwork/openwork-server-state.json~/.config/com.differentai.openwork/openwork-server-tokens.json~/.config/com.differentai.openwork/openwork-ui-control.json~/.config/openwork/server.json.opencode/openwork.json
Contributor guide
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.
Assessment
This issue has not been assessed yet.