v2.3.7

What's Changed in v2.3.7

Bug Fixes

• Antigravity per-session Remote Control naming (#283): translate_antigravity_flags in launch-agent-sessions.sh now automatically appends --remote-control-name <session_name> whenever --remote-control (or AGY_REMOTE_CONTROL=1) is active and no explicit --remote-control-name was provided. Each tmux session now registers as a distinct named instance in the Antigravity Remote Control Web UI instead of colliding on the machine hostname.
• Antigravity launcher invocation & daemon status check (#279):
  • Removed the spurious positional <workdir> argument from agy in launch_one (tmux new-session -c "$workdir" already sets the working directory).
  • Updated the opt-in AGY_REMOTE_CONTROL_AUTOSTART=1 status check to match both Daemon status: running and Daemon status: active.
• Tilde (~) path expansion in sessions.conf flags (#284): translate_copilot_flags and translate_antigravity_flags now expand ~ / ~/* and --*=~ / --*=~/* to $HOME prior to printf %q escaping so flags like --add-dir ~/src/worktrees resolve to real directories instead of literal \~/....
• Documentation: Updated README.md, DEPLOY.md, and docs/harness-adaptation-guide.md to document per-session --remote-control --remote-control-name <name> vs. the standalone headless agy remote-control start daemon.