[GH-ISSUE #550] Support Scripting and Breakpoint Execution After Map Local #546

New issue

Open

opened 2026-03-03 19:51:16 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 19:51:16 +03:00

Owner

Originally created by @kics223w1 on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/550

Originally assigned to: @kics223w1 on GitHub.

✨ Feature Description

We should support Scripting and Breakpoint execution after Map Local.
This ensures a request can flow through multiple tools in a predictable order.

✅ Acceptance Criteria

General Flow

Request matches Map Local
→ If it also matches Scripting → Let Scripting continue handling.
→ If it also matches Breakpoint → Let Breakpoint continue handling.

Map Local + Scripting

Case 1:
- Map Local executes successfully
- Scripting executes successfully
- ✅ Response returned from Scripting.
Case 2:
- Map Local executes successfully
- Scripting fails
- ✅ Response returned from Map Local.
Case 3:
- Map Local fails
- Scripting executes successfully
- ✅ Response returned from Scripting.
Case 4:
- Map Local fails
- Scripting fails
- ✅ Request continues to the server as normal.

Map Local + Breakpoint

Same logic applies as above:
- Map Local executes first.
- Breakpoint handles next (if applicable).
- If both fail → Request goes to the server.

🔄 Summary

Order of execution: Map Local → (Scripting or Breakpoint)
Failover behavior: If the next tool fails, fallback to previous tool’s response.
Final fallback: If all fail → Forward request to the server.

Originally created by @kics223w1 on GitHub (Oct 8, 2025). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/550 Originally assigned to: @kics223w1 on GitHub. ## ✨ Feature Description We should support **Scripting** and **Breakpoint** execution after **Map Local**. This ensures a request can flow through multiple tools in a predictable order. --- ## ✅ Acceptance Criteria ### General Flow - Request matches **Map Local** → If it also matches **Scripting** → Let **Scripting** continue handling. → If it also matches **Breakpoint** → Let **Breakpoint** continue handling. --- ### Map Local + Scripting - **Case 1:** - Map Local executes successfully - Scripting executes successfully - ✅ Response returned from Scripting. - **Case 2:** - Map Local executes successfully - Scripting fails - ✅ Response returned from Map Local. - **Case 3:** - Map Local fails - Scripting executes successfully - ✅ Response returned from Scripting. - **Case 4:** - Map Local fails - Scripting fails - ✅ Request continues to the server as normal. --- ### Map Local + Breakpoint - Same logic applies as above: - **Map Local executes first**. - Breakpoint handles next (if applicable). - If both fail → Request goes to the server. --- ## 🔄 Summary - **Order of execution:** `Map Local → (Scripting or Breakpoint)` - **Failover behavior:** If the next tool fails, fallback to previous tool’s response. - **Final fallback:** If all fail → Forward request to the server.