`mutagen sync create` failing - agent binaries copied to remote/beta not executable

[Tomasvrba]

running mutagen sync create fails because binaries copied to beta are not executable:

mutagen daemon is running on a Debian 13 system

remote device is an Arch linux system

ssh connection is running over Tailscale

Installing agent...
Error: unable to connect to beta: unable to connect to endpoint: unable to dial agent endpoint: unable to
 install agent: unable to invoke agent installation: remote error: zsh:1: permission denied: ./.mutagen-a
gent29d06cd9-a54a-4712-8863-f272b238bc05

The binaries get copied to the remote user's home directory ./.mutagen-agent{uuid} as -rw-r--r-- according to the remote's 022 umask, but shouldn't mutagen preserve the executability bit from what I understand from the docs?
Or make it executable if it gets copied over without x

[Tomasvrba]

I would set up the agent manually, but I don't see how to do this anymore in Mutagen 0.18+, even if I have a ~/.mutagen directory set up with executable agent binaries, the daemon still tries to copy over and install its own binaries

[Tomasvrba]

if anyone has a similar issue, the simplest fix I could come up with is to just poll the remote's home dir for the agent binary and make it executable before the daemon tries to install the agent:

#!/bin/bash

echo "Watching for new mutagen agent files..."
while true; do
  for f in ~/.mutagen-agent*; do
    # Check if the file exists and is a regular file, but not executable
    if [ -f "$f" ] && [ ! -x "$f" ]; then
      chmod +x "$f"
      echo "Made $f executable"
    fi
  done
  sleep 0.1
done