Hey, thanks for the report. This is a known issue with worktrees in remote environments. The agent uses a file:// URI to check the config, and it doesn’t resolve correctly over SSH.
The same bug is already tracked here: Agent “Worktree Setup” fails to find config file in Remote SSH sessions
I’ll reply in that thread when there’s any news.