[GH-ISSUE #935] Can't edit and save previously saved sessions #930

New issue

Open

opened 2026-03-03 19:23:06 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 19:23:06 +03:00

Owner

Originally created by @cameroncooke on GitHub (Jul 15, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/935

Originally assigned to: @NghiaTranUIT on GitHub.

Proxyman version? (Ex. Proxyman 1.4.3)

2.29.0 (22900)

macOS Version? (Ex. mac 10.14)

12.0 Beta (21A5284e)

Steps to reproduce

Open Proxyman
Record some traffic
Save the session to disk and name it "A"
Close all the Proxyman tabs and windows
Quit Proxyman using Cmd+Q
Open the file named "A.proxymansession"
Edit the recorded history by deleting some requests
Attempt to save changes by tapping Cmd+S
Observe beep sound
Go to File -> Save Session
Give the session a new name "A1"
Close all the Proxyman tabs and windows
Quit Proxyman using Cmd+Q
Open the file named "A1.proxymansession"
Observe that the saved session isn't the one that was being viewed and edited and is in fact an entirely new recording

Expected behavior

Saved sessions should act like documents, opening viewing, and editing and saving should be possible. When the only tab open is a saved session Proxyman shouldn't be recording network traffic.

The current behaviour is unintuitive and it doesn't feel like the tab behaviour has really been thought through.

Further info

The use-case is that I want to debug an issue with another app and they have asked for network recording logs. When I record in Proxyman it records more than just the app or domain I care about, when I save a session it saves all traffic not just the filtered view I'm seeing in the interface.

I want to then open the saved session and remove all the redundant requests so that I've just got the ones I care about and save the session before sending it to the app provider to debug the issue with me.

Originally created by @cameroncooke on GitHub (Jul 15, 2021). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/935 Originally assigned to: @NghiaTranUIT on GitHub. ### Proxyman version? (Ex. Proxyman 1.4.3) 2.29.0 (22900) ### macOS Version? (Ex. mac 10.14) 12.0 Beta (21A5284e) ### Steps to reproduce 1. Open Proxyman 2. Record some traffic 3. Save the session to disk and name it "A" 4. Close all the Proxyman tabs and windows 5. Quit Proxyman using Cmd+Q 6. Open the file named "A.proxymansession" 7. Edit the recorded history by deleting some requests 8. Attempt to save changes by tapping Cmd+S 9. Observe beep sound 10. Go to File -> Save Session 11. Give the session a new name "A1" 12. Close all the Proxyman tabs and windows 13. Quit Proxyman using Cmd+Q 14. Open the file named "A1.proxymansession" 15. Observe that the saved session isn't the one that was being viewed and edited and is in fact an entirely new recording ### Expected behavior Saved sessions should act like documents, opening viewing, and editing and saving should be possible. When the only tab open is a saved session Proxyman shouldn't be recording network traffic. The current behaviour is unintuitive and it doesn't feel like the tab behaviour has really been thought through. ### Further info The use-case is that I want to debug an issue with another app and they have asked for network recording logs. When I record in Proxyman it records more than just the app or domain I care about, when I save a session it saves all traffic not just the filtered view I'm seeing in the interface. I want to then open the saved session and remove all the redundant requests so that I've just got the ones I care about and save the session before sending it to the app provider to debug the issue with me.

kerem added the

Feature request

label

2026-03-03 19:23:06 +03:00

kerem commented

2026-03-03 19:23:07 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Jul 15, 2021):

Saved sessions should act like documents, opening viewing, and editing and saving should be possible.

It's a big obstacle that Proxyman is facing. We implement the document-based app incorrectly. Therefore, when we open a Session file, it doesn't support Auto-Save, or all native features of the Document-based app could benefit.

In order to fix it, we have to refactor how we implement this feature.

When I record in Proxyman it records more than just the app or domain I care about, when I save a session it saves all traffic, not just the filtered view I'm seeing in the interface.

I highly recommend exporting as a ProxymanLog (Select your requests -> Right Click -> Export -> ProxymanLog), because you can select what domains/apps you would like to export (Not the entire session). You can also export entire Domain Node too (on the left panel).

I will bump this problem to the team and see how we can tackle it. Ideally, it should be the same as you mention 👍 😄

@NghiaTranUIT commented on GitHub (Jul 15, 2021): > Saved sessions should act like documents, opening viewing, and editing and saving should be possible. It's a big obstacle that Proxyman is facing. We implement the document-based app incorrectly. Therefore, when we open a Session file, it doesn't support Auto-Save, or all native features of the Document-based app could benefit. In order to fix it, we have to refactor how we implement this feature. > When I record in Proxyman it records more than just the app or domain I care about, when I save a session it saves all traffic, not just the filtered view I'm seeing in the interface. I highly recommend exporting as a ProxymanLog (Select your requests -> Right Click -> Export -> ProxymanLog), because you can select what domains/apps you would like to export (Not the entire session). You can also export entire Domain Node too (on the left panel). ------------------------- I will bump this problem to the team and see how we can tackle it. Ideally, it should be the same as you mention 👍 😄

kerem commented

2026-03-03 19:23:07 +03:00

Author

Owner

@cameroncooke commented on GitHub (Jul 15, 2021):

Yeah, I think the document-based app design needs some work ;-) but it's all good. Great work on Proxyman I'm love it, hence all the feedback!

@cameroncooke commented on GitHub (Jul 15, 2021): Yeah, I think the document-based app design needs some work ;-) but it's all good. Great work on Proxyman I'm love it, hence all the feedback!