<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>エージェント on nsys.dev Tech Blog</title>
		<link>https://blog.nsys.dev/en/tags/%E3%82%A8%E3%83%BC%E3%82%B8%E3%82%A7%E3%83%B3%E3%83%88/</link>
		<description>Recent content in エージェント on nsys.dev Tech Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 15 Jun 2026 15:00:00 +0900</lastBuildDate>
		
			<atom:link href="https://blog.nsys.dev/en/tags/%E3%82%A8%E3%83%BC%E3%82%B8%E3%82%A7%E3%83%B3%E3%83%88/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Designing a CLI on the premise that an AI will drive it</title>
				<link>https://blog.nsys.dev/en/posts/cli-for-agents/</link>
				<pubDate>Mon, 15 Jun 2026 15:00:00 +0900</pubDate>
				<guid>https://blog.nsys.dev/en/posts/cli-for-agents/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Part 5 of 5 (finale)&lt;/strong&gt; — series: &lt;em&gt;Building a publishing tool, and shipping it&lt;/em&gt;. Last time was &lt;a href=&#34;https://blog.nsys.dev/en/posts/brew-scoop-release/&#34;&gt;shipping with brew and scoop&lt;/a&gt;. See the &lt;a href=&#34;https://blog.nsys.dev/en/tags/crofty/&#34;&gt;series index&lt;/a&gt;. This time: designing the CLI on the premise that an AI drives it.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;crofty is a plain CLI you type at the terminal. But one premise of its design is a little different.&lt;/p&gt;&#xA;&lt;p&gt;&amp;ldquo;A person installs crofty and does the first setup; after that, their AI (an agent) runs it.&amp;rdquo; That&amp;rsquo;s the usage it assumes. Rather than a person remembering and typing commands every time, an agent drives crofty on their behalf — and the build is meant not to get in the way when it does.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
