Agent-friendly CLI, JSON Comments, and Redirect Warnings

📦 2026.3.1

Don’t fail app launch on plugin init failures

This release brings JSON comment support in request bodies and an all new agent-friendly CLI, allowing tools like Claude and Codex interact with Yaak workspaces directly.

🤖 New agent-friendly CLI

The new yaak CLI lets you manage workspaces, send requests, and inspect responses from the command line. It can be used directly by you, but is primarily designed for AI agents like Claude and Codex. Simply say “use the yaak CLI to…” and it will figure out the rest.

Install it with NPM and point your favorite agent at it:

npm install -g @yaakapp/cli

Yaak CLI — Use the CLI to interact with your Yaak workspaces

The CLI connects to the same local database as the desktop app, so any changes made are reflected immediately in both directions. The best part? It’s self-describing, so agents can use it without installing any skills.

JSON Schemas use schema subcommands to get exact data structure
Structured CRUD with --json '{...}' for complete data manipulation
Send anything with --parallel and --fail-fast flags
Troubleshoot with --verbose mode for debugging

Give it a try by asking Claude or Codex something like “Scan my API routes and create a Yaak workspace with all the requests I need for manual testing.”

Check out the CLI and Agents docs to get started.

📝 Allow commenting JSON body

You can now use Cmd+/ to comment out lines in JSON request bodies instead of deleting them when you want to temporarily disable part of a payload.

This works across HTTP, WebSocket, gRPC, and the GraphQL variables editor. When Yaak sends the request, it strips comments and removes trailing commas left behind by commented lines.

Commented JSON request body — Comment out part of a JSON body without deleting it

If you need to send the body exactly as written, disable Automatically Fix JSON in the editor. With that off, linting becomes strict again and Yaak stops rewriting the payload before sending it.

⚠️ Warn on HTTP redirects

Redirects can change a request in ways that are easy to miss, especially when a body or headers are dropped on the way to the final URL.

Yaak now shows a warning badge in the response pane when that happens. The timeline also includes the dropped header and body details so you can see which redirect caused the change.

Redirect warning badge in the response pane — See when a redirect dropped request data before the final response

This makes it easier to tell whether a failed request is caused by the destination server or by redirect handling before the final hop.

Other fixes and improvements

🛠️ Fixed

Fix macOS Tahoe stoplight positioning and build on macOS 26
🧩 Deduplicate plugins caused by CLI usage(#414 )
📋 Fix Copy as gRPCurl with template-tag payloads(feedback , #413 )
Fix request descriptions after OpenAPI import(feedback , #412 )
Preserve drive letter in Windows plugin paths(#410 )
Fix “Send All” folder action(feedback , #405 )
Fix request chaining for more than two dependencies
Fix NTLM challenge parsing when WWW-Authenticate has Negotiate first(feedback , #402 )
Fix plugin settings layout

💄 Improved

Comment-preserving GraphQL formatting
Better external OAuth callback format
Detect CLI availability and add command palette copy action