Make imported cURL requests populate the Auth tab automatically

[gabrieloliverio]

Summary:

When importing a request from cURL that includes authentication (e.g., a bearer token), Insomnia currently adds the token as a raw header instead of mapping it to the Auth tab.

This makes imported requests inconsistent with those created directly inside Insomnia and harder to manage later.

Problem Statement:

Currently, when a cURL request containing authentication details is imported, Insomnia places the token inside the headers.
For example:

Authorization: Bearer my-token

While this technically works, it has a few drawbacks:

• The Auth tab remains empty, which can confuse users who expect to manage credentials there.
• It’s harder to edit or update the authentication method later since it’s buried in the raw headers.
• Imported requests behave differently from manually created ones, leading to inconsistent workflows for teams.

Proposed Solution:

When importing a cURL request, Insomnia should:

1. Detect common authentication schemes (e.g., Bearer tokens, Basic Auth).
2. Populate the Auth tab automatically when possible, instead of leaving the header raw.

This would bring imported requests in line with those created natively in Insomnia and streamline authentication management.

[poojithap11]

Hi,

This feature is available in the latest versions of Insomnia. Could you check and let us know if you still face any issues?

Thank you.