**TL;DR:**
`npm install -g koh-cli`.*Be sure to stay up-to-date with all things *[_*Kong Insomnia*_](https://insomnia.rest/)_*Kong Insomnia*_.
Developers aren't writing every request by hand anymore. Claude Code, Codex, and other agentic tools have quietly taken over a job that used to belong to traditional API clients: making the request, reading the response, iterating. That shift is only increasing…
But agents are only as good as the [_context_](https://konghq.com/blog/enterprise/the-context-economy)_context_ they're given, and that's where things get messy. Ask an AI coding tool to build against an internal API and it has to guess at governance rules, testing conventions, and quality bars that live scattered across wikis, Slack threads, and someone's memory. Ask it to consume an API you didn't build, and you're stuck hunting for docs that may already be out of date. Either way, you end up hand-feeding the agent context, burning tokens, and still reviewing its output line by line.
We built [_koh-cli_](https://www.npmjs.com/package/koh-cli)_koh-cli_ to fix that gap.
Insomnia already holds a lot of the context that makes APIs usable: specs, environments, governance rules, requirements, and everything synced in from Kong Konnect (available as of [_Insomnia 13_](https://konghq.com/blog/product-releases/insomnia-13)_Insomnia 13_). Koh is a CLI that gives agents a standardized, secure way to interact with that context directly, instead of relying on whatever a developer happens to paste into a prompt.
Koh-CLI is intentionally thin. It doesn't make decisions, run business logic, or "think" on your behalf. Its whole job is to be a clean, opinionated and deterministic (i.e., non-hallucinogenic) interface between an agent and the data already living in Insomnia, so agents get consistent, structured access instead of improvising.
If you're building an API, Koh-CLI means your AI coding tool can pull governance rules and requirements straight from Insomnia instead of you having to re-explain them every session. Test generation gets sharper because the agent knows what your team actually checks for, not just generic coverage. And because Koh-CLI runs requests through Insomnia rather than handing credentials to a public LLM, you're not trading security for convenience. Less context to manually assemble also means fewer tokens burned per task, and fewer runs against your monthly limits.
If you're integrating with an API someone else built, Koh-CLI gives your agent a direct line to accurate, current context on how that API actually works, pulled from the same place your teammates documented it. No more hunting through company docs for a page that may be stale, and no more hoping the agent's assumptions about an internal API happen to be right. You get to skip straight to building the feature.
Koh-CLI doesn't replace your agent, and it doesn't replace Insomnia. It's the connective tissue between the two: a consistent, secure interface so the context you've already built up in Insomnia and Kong Konnect actually reaches the tools doing the work. As agentic development becomes the default, that context layer is what keeps agents accurate, consistent, and cheap to run, instead of reinventing their understanding of your APIs from scratch every time.
Koh installs like any other CLI:
npm install -g koh-cliFrom there, point it at your Insomnia/Kong Konnect workspace and let your agent of choice (Claude Code, Codex, or whatever you're running) call Koh to pull context as it works. No separate dashboard, no new workflow to learn, it's built to sit quietly behind the agent you're already using.
Grab it now on npm:[ _koh-cli_](https://www.npmjs.com/package/koh-cli) _koh-cli_.
[_Koh-CLI_](https://www.npmjs.com/package/koh-cli)_Koh-CLI_ is early in [_tech preview_](https://developer.konghq.com/stages-of-software-availability/#tech-preview)_tech preview_, and we'd rather be upfront about what it doesn't do yet than oversell it. Roughly, in the order we hope to address them:
Keep up with our roadmap, shared on [_npm_](https://www.npmjs.com/package/koh-cli)_npm_.
Agents are already doing the job of the API client. Insomnia’s new Koh-CLI’s bet is that the harder problem, getting them good, current, secure context to work with, is best solved by the platform that already holds that context, [_Insomnia_](http://www.insomnia.rest)_Insomnia_, not by developers hand-copying it into prompts. It's early, it's a tech preview, and it has real gaps today. But if you're building or consuming APIs with an AI coding tool, give it a try and tell us what you need next:[ _koh-cli on npm_](https://www.npmjs.com/package/koh-cli) _koh-cli on npm_.
kongctl was built with the modern development stack in mind. Developers working in a terminal want the ability to query systems quickly to verify state, behaviors, and capabilities. Coding harnesses need well defined tools and accurate schemas for
Quality is at the core of every product we build. To move fast without compromising on quality, we rely on an extensive set of test suites that tell us quickly whether a change has caused a regression. Those suites are large enough that a single ful
Modern enterprise APIs don't live in one place. They're spread across multiple gateways, deployed across regions and clouds, and accessed by a growing mix of consumers, internal developers, external partners, machine-to-machine services, and increas
You invested in Kong Konnect. You centralized your API governance, locked down your routing, enforced your security policies, and gave your organization a single source of truth for every API in your estate. That work is done, and it is working. So
Until now, KAi could tell you how to set up a service, suggest the right plugins, and point you at the docs. Useful, but you still had to do some of the work yourself. V2 changes that. With our new Code Mode MCP integration, KAi can create, update
Have you ever…. Copied an API spec out of Kong Konnect, or where you manage your APIs, pasted it into your API client, and immediately wondered if it’s the latest version? Sent an email to your platform team with the subject line “ which endpoint sh
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 f