atch preserves old terminal environment variables after reattaching from a newly started kitty instance

[hoarse-boy]

atch preserves old terminal environment variables after reattaching from a newly started kitty instance.

This breaks kitty remote control integration because KITTY_LISTEN_ON inside the persistent shell still points to the old kitty socket from the previous terminal instance.

Reproduction

1. Open kitty
2. Create an atch session:

atch test

3. Verify kitty remote works:

kitty @ ls

4. Close kitty completely
5. Open a new kitty instance
6. Reattach to the existing atch session:

atch -A test

7. Run:

kitty @ ls

Behavior

The shell inside the persistent atch session still contains the old KITTY_LISTEN_ON value from the previous kitty instance.

Example error:

Error: Failed to connect to unix:/tmp/kitty-52081 with error: dial unix /tmp/kitty-52081: connect: no such file or directory

Is this intended behavior?

Notes

This is reproducible consistently with:

• kitty
• fish shell
• Arch Linux