Hey! Your PR title Add symlink setting doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

The following comment was made by an LLM, it may be inaccurate:

No duplicate PRs found

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

Note that this just adds a setting for reverting to the original behavior from 2 weeks ago, as it was changed in PR #11415

rebased everything on top of dev
EDIT: rebased again 05-03-2026

Am running version opencode 1.2.18 on Fedora. The @ does not detect the symlink in the workspace, but if I explicitly ask the agent "what do you see" in the folder symlink, it is able to list out the content in it.

Nice work @jeroenev . Perhaps solve the merge conflict, so the anomaly team can merge this PR.

( I am not part of anomaly or anyhing, just like to have this fixed as well 🙃 )

Rebased and fixed all conflicts, I hope this can get merged soon.
but yeah it can take a while until someone looks at this PR
they're probably getting overloaded 🙃
there are so many changes this PR gets conflicts every week, but I'm happy to keep rebasing until someone looks at it to merge