<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cli on Restish</title><link>https://rest.sh/tags/cli/</link><description>Recent content in Cli on Restish</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jun 2026 11:40:07 -0700</lastBuildDate><atom:link href="https://rest.sh/tags/cli/index.xml" rel="self" type="application/rss+xml"/><item><title>Restish v2: A CLI for REST APIs, Rebuilt</title><link>https://rest.sh/blog/restish-v2-a-cli-for-rest-apis-rebuilt/</link><pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate><guid>https://rest.sh/blog/restish-v2-a-cli-for-rest-apis-rebuilt/</guid><description>&lt;p&gt;Most APIs already know more about themselves than the command line does. They
have schemas, auth rules, pagination links, content types, examples, and often a
full OpenAPI description. Then we copy a &lt;code&gt;curl&lt;/code&gt; command into a terminal and
teach all of that context back to the shell one flag at a time.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;curl&lt;/code&gt; is still the universal primitive. Restish is for the moment after that:
when a URL becomes a workflow, and the API should start feeling like a small
native CLI instead of a string you keep rebuilding.&lt;/p&gt;</description></item></channel></rss>