Tag flows from a monitored terminal session (launch marker, not an HTTP header)

[voidfreud]

Description

When capturing several terminals at once (Automatic Setup → Open New Terminal, Manual Setup, proxyman-cli, or MCP inject_terminal), there is no way to mark which terminal a flow came from.

Two Terminal.app / iTerm windows that run the same binary show up as the same Client. There is no PID on the flow (#2307). Adding a fake request header just to label the session would send that header to the server, which we do not want.

Why this feature/change is important?

Debugging two agent/CLI sessions side by side is common. Right now the only workarounds are coloring/commenting after the fact from body content, or injecting headers that leak to the origin.

Suggested behavior

When launching a tracked terminal (GUI, CLI, or MCP), accept a display-only session marker (name and/or color), e.g. session=A.

Stamp every flow from that process/window with the marker. Show it:

• as a column on the main table
• optionally as Comment / color
• on MCP (get_flows / get_flow_detail) so agents can filter without re-parsing bodies

Do not add an HTTP header. The origin must not see the marker.

Related: query-key columns in #2736 already moved columns past headers; this is the terminal-origin equivalent.

[NghiaTranUIT]

ok, I see your problem. I will add

• support pid in client
• pid column
• Scripting that can access PID, so you can highlight it with color

I don't want to show multiple Terminal Clients (different pid) in the left panel, because it's a bad UX. For example: If I re-open the same app, which already appeared in the source list -> This app will has the new PID, and appear twice -> Look like a bug ❌

[voidfreud]

Thanks for the super quick reply, and for getting the problem.

PID on the client, a PID column, and letting Scripting see the PID so I can color rows is exactly what I needed. Totally understand not showing each PID as its own client in the left panel. That would be a mess.

I'm really happy with Proxyman. It's one of the best apps I've used. Thank you for agreeing to implement this, and for the JSON body columns too. Wish you all the best with the app. Happy to send more feedback as I keep using it.

[NghiaTranUIT]

You can use this Beta build: https://assets.proxyman.com/beta/Proxyman_6.16.0_Support_pid.dmg

• ✅ Add Process ID (pid) in the column
• ✅ MCP: get_flows / get_flow_detail can filter flows by pid
• ✅ Scripting: can read the pid

console.log("PID = ", context.flow.clientPid);

[voidfreud]

Thanks! This is super handy! I have no more wishes, it's perfect now. 6.17 will ROCK.