@ symbols in Commands that dont resolve to files cause command failure

Looks like the command function will blindly try to map any @ ref into a file and push it straight to the read tool. This is problematic when combined with !shell commands or just random uses of an @ symbol will cause ENOENT failure at some point in the chat function.

One thought is to check if the path resolves to an actual path, before turning it into a file part.

Although it may also be a better idea to do file part matching before bash eval expansion so that bash commands are not subject to file inclusion.

This issue might be a duplicate of existing issues. Please check:

Shell commands don't appear to expand in custom commands #2233: Similar command processing issues with shell command expansion not working properly in custom commands
Some (weird right) commands in the global directory, do not do anything #2231: Related ENOENT errors when commands fail to resolve files/directories correctly
bug: drag & drop text file results in error #1330: File path resolution ENOENT errors with path handling issues

Feel free to ignore if none of these address your specific case.

closing in favor of:

Navigation Menu

Repository navigation

@ symbols in Commands that dont resolve to files cause command failure #2261

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

@ symbols in Commands that dont resolve to files cause command failure #2261

Description

Activity

github-actions commented on Aug 26, 2025

rekram1-node commented on Aug 26, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions