In the last few years, Insomnia has reaffirmed its commitment to allowing developers to own their own tools, their workflows, and their data. With Insomnia 12.6, we’re taking this a step further: your collections and workspaces are now stored in a file format that plays nicely with Git, whether you’re working in the Insomnia app or the command line. 

Insomnia 12.6 now auto-syncs changes from the local file system in real time. Edit a file in your terminal, save it, and Insomnia reflects it instantly, no import/export, no copy-paste, no manual refresh.

We built this because we already know you have a version control workflow that works. Now your Insomnia API workspace fits into it…not the other way around.

Insomnia gives devs the power of choice. We think developers should be able to work how and where they want (locally, git, cloud, UI vs terminal), flying solo or with different size teams. We’re not here to gate your workflow behind an upgrade; we’re not even here to make you sign in if you’d rather not with Scratchpad. 

When collections live as files in your repo, collaboration is easy. You already know how to review a pull request, resolve a merge conflict, and enforce standards. Now that applies to your API workflow, too. 

This also means that Insomnia fits naturally into your existing CI/CD setup. Run hooks on push. Validate collections before merge. Keep your environments in sync across a team without anyone installing a plugin or paying extra for collaboration.  

Meanwhile, other vendors, like Postman, require a paid plan just to collaborate with a collaboration plan starting at $19/user/month. For a small team of three using Postman, that’s nearly $700 per year. With Insomnia, small teams work the way they want to work, with the tools they already know, but without the bill at the end of the month.

*Considering making the move from Postman? Check out our post on *[*evaluating API testing tools*](https://konghq.com/blog/enterprise/insomnia-vs-postman-evaluating-api-testing-tools)*evaluating API testing tools** to see how Insomnia stacks up. Or learn more about *[*migrating collections and requests from Postman to Insomnia.*](https://konghq.com/blog/engineering/migrating-collections-and-requests-from-postman-to-insomnia)*migrating collections and requests from Postman to Insomnia.*

Insomnia 12.6 introduces **Native Git CLI support**, giving developers direct access to the Git repository backing their Insomnia projects.

Instead of working only through the built-in Git Sync UI, you can now navigate to your project’s local files and use standard Git commands directly from your terminal or editor of choice.

That means workflows like:

git status
git diff
git commit
git pull
git push

Now, work naturally with Insomnia projects. This makes it easier to:

• - Edit OpenAPI specs in VS Code
• - Review API changes with standard Git diffs
• - Collaborate through branches and pull requests
• - Integrate API workflows into existing CI/CD pipelines

Once Git Sync is enabled, Insomnia stores the project locally on disk. You can open the project folder in your editor, modify the specification files, and watch the changes instantly appear inside Insomnia -  no manual import or refresh required.

For example, after locating your project’s local path in **Project Settings**...

...you can open it directly in VS Code. From there, edit your API specification, commit changes with Git, and push them to your remote repository just like any other development workflow.

The workflow also works both ways: changes made inside Insomnia are immediately reflected in your local files and Git diff output. This gives teams a much more natural Git-native API development experience using the tools they already know.

Dynamic mocking has been available in Insomnia's self-hosted mock servers for a while, but Insomnia 12.6 brings that same capability to cloud-hosted mock servers, too. 

If you’re already using dynamic mocks locally, everything will work the same, template logic evaluated at request time, faker tags for generated data, etc. The only difference is you have the choice of where your mock server lives, locally or cloud-hosted and you can get started with just a click because there is no setting up Mockbin. 

If you haven’t tried dynamic mocking yet… rather than returning a static, predefined payload on every request, a dynamic mock evaluates the response at request time. That means your mock can read what came in and shape what goes out. This could be echoing an identifier from a request header, switching a field based on input, or generating a fresh email or UUID on every call instead of returning the same hardcoded value.

**Try in Insomnia: Instant MCP server and API testing**

We’ve reimagined how developers discovered and try APIs with Insomnia. The new “Try in Insomnia” experience lets you click a single link and immediately begin MCP server and API testing. No hunting. No manual imports. Instant access.

[_Try it out_](https://developer.konghq.com/insomnia/run-in-insomnia/#overview)_Try it out_

**1. Construct your deep-link URL. **Start with https//app.insomnia.res/run and append your endpoint url, spec url, or MCP server address as a query parameter. Insomnia’s documentation includes a full parameter reference. 

**2. Embed the link where developers read. **Paste it as a markdown badge in your README, a button in API reference docs, or a link in a blog post…the choice is yours. The URL works anywhere HTML or markdown renders.

**3. Users click. Let Insomnia handle the rest. **If Insomnia is installed, the app opens and navigates to the imported request. If not, users are guided through a streamlined download and the request is waiting for them upon launch. 

**Why instant API testing and MCP server testing matters**

✔️ Faster API adoption: Reduce the steps between “I found this API” and “I made my first request” to a single click

✔️ Works on any docs platform: Embed in GitHub READMEs, Notion pages, or any static site, no plugin required. 

✔️MCP-ready from day one: as the ecosystem of MCP servers grows, developers can share and try them with the same one-click experience as testing traditional APIs with Insomnia

For administrators managing large organizations, auditing unmanaged users can be time-consuming as you scroll through row after row of unmanaged users. In Insomnia 12.5, you can now export a full list of unmanaged users for any domain as a CSV, making it easy to reconcile against your identity provider, review license usage, or share with your team for cleanup.

Deleting a project now gives you precise control over what gets removed and where. Whether you're cleaning up a local copy of outdated cloud data or wiping a project entirely, 12.5 puts the decision in your hands.

This is especially valuable when synced cloud data gets out of date; you can now reset your local state cleanly without any unintended side effects on the shared remote project.

Insomnia 12.6 gives you control over your data, your workflow, and where you run your infrastructure. Whether you’re a solo developer living in the terminal or a large enterprise team needing to collaborate, Insomnia 12.6 is built around how you already work. 

Get started for [_free_](https://insomnia.rest/pricing)_free_ — and let us know what you think.