one requirement with very high ROI

Trigger is excellent feature which includes much more possibility.
WindTerm already has feature quick command. But this quick command is only to send text.
How about to combine them? or extend them with some reuse.

Some other terminal tool can use quick command to call third-party tool. For example, xshell can call winscp with current session parameter(ip/username/password). Then winscp can be opened with automate connection.

To WindTerm, current I don't find any session parameters for current active session. For some special requirement/or due to some limitations or bugs, we need use other tools when we are running WindTerm. How can we build one automate bridge between third-party tools and WindTerm?
The whole solution can be added to quick command. If "run app" which already in "trigger" can be reused in quick command, also with current session parameters, that would be very useful.
The effort is not big, but I think it is also not small. Due to your work situation, I know this effort may have big impact to you.
So, there is one workaround, with less and less effort. In trigger tool, it already can run third-party app. Can you make possibility/way to add current session parameters for trigger. Then we can add command into trigger, like "winscp.exe {user}:{password}@{ip}", also can call other third-party tools. **I think the effort is not big, you only need to add work to "save current session parameters into memory" and "replace it when calling command"**. For this trigger workaround, users can use quick command to send special text to trigger it. Or set Triggers can be manual triggered to completely instead of quick command.

This can take much more power and possibility into WindTerm.
It can extend WindTerm's life cycle with less bugfix and less feature dev. WindTerm can focus on pure terminal's feature. For other work which WindTerm not suitable to do, users can do it with other tools via the bridges.

Some parameter examples:
1. username
2. password
3. IP
4. port
5. protocol
6. current session screen output

At the end, I still strongly hope you to consider this requirement. It's very very useful.

Start by tracing WindTerm's existing Quick Command and Trigger features, especially how Trigger runs third-party applications and how the active session is represented. Define the supported session parameters and invocation behavior before implementation; done should include a documented bridge from a Trigger or Quick Command to a third-party tool using the current session context.

Written by the indexing model from the issue text.