[GH-ISSUE #5836] [feature]: Add user choice for cURL import target - New Tab or Active Tab #2288

Open
opened 2026-03-16 23:51:34 +03:00 by kerem · 0 comments
Owner

Originally created by @chhaviG22 on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5836

Is there an existing issue for this?

  • I have searched the existing issues

Summary

Currently, when importing a cURL command, it overwrites the content of the active tab without warning, which can lead to accidental loss of unsaved work. This feature adds two import options in the cURL import modal: "Import in New Tab" (primary action) and "Import in Active Tab" (secondary action), giving users control over where the imported request is placed.

Why should this be worked on?

Problem Statement

When users import a cURL command into Hoppscotch, the current behavior automatically overwrites the active tab's content. This creates several UX issues:

  1. Data Loss Risk: Users lose unsaved work in the current tab without warning
  2. No User Control: Users cannot choose whether to replace or preserve their current work
  3. Workflow Disruption: Forces users to manually create a new tab before importing if they want to preserve their current request

Use Cases

Scenario 1: Testing Multiple Variations
A developer is testing an API endpoint and wants to import several cURL examples from documentation while keeping their original request for comparison. Currently, they must manually duplicate the tab before each import.

Scenario 2: Exploring APIs
When exploring a new API with multiple cURL examples, users want to import each one into separate tabs to compare headers, parameters, and request bodies side-by-side.

Scenario 3: Avoiding Accidental Overwrites
Users accidentally paste a cURL command and lose their carefully crafted request with custom headers and authentication that wasn't saved to a collection yet.

This enhancement aligns with user expectations from other development tools (Postman, Insomnia) where importing typically creates new items rather than overwriting existing work.

Originally created by @chhaviG22 on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5836 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Currently, when importing a cURL command, it overwrites the content of the active tab without warning, which can lead to accidental loss of unsaved work. This feature adds two import options in the cURL import modal: "Import in New Tab" (primary action) and "Import in Active Tab" (secondary action), giving users control over where the imported request is placed. ### Why should this be worked on? ### Problem Statement When users import a cURL command into Hoppscotch, the current behavior automatically overwrites the active tab's content. This creates several UX issues: 1. **Data Loss Risk**: Users lose unsaved work in the current tab without warning 2. **No User Control**: Users cannot choose whether to replace or preserve their current work 3. **Workflow Disruption**: Forces users to manually create a new tab before importing if they want to preserve their current request ### Use Cases **Scenario 1: Testing Multiple Variations** A developer is testing an API endpoint and wants to import several cURL examples from documentation while keeping their original request for comparison. Currently, they must manually duplicate the tab before each import. **Scenario 2: Exploring APIs** When exploring a new API with multiple cURL examples, users want to import each one into separate tabs to compare headers, parameters, and request bodies side-by-side. **Scenario 3: Avoiding Accidental Overwrites** Users accidentally paste a cURL command and lose their carefully crafted request with custom headers and authentication that wasn't saved to a collection yet. This enhancement aligns with user expectations from other development tools (Postman, Insomnia) where importing typically creates new items rather than overwriting existing work.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#2288
No description provided.