<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-Source on AiSlackin</title><link>https://aislackin.com/tags/open-source/</link><description>Recent content in Open-Source on AiSlackin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aislackin.com/tags/open-source/index.xml" rel="self" type="application/rss+xml"/><item><title>hed: the tiny C++ editor that replaces heredocs and makes agents happy</title><link>https://aislackin.com/posts/2026-09-27-hed-text-editor/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate><guid>https://aislackin.com/posts/2026-09-27-hed-text-editor/</guid><description>&lt;p&gt;Ask a shell script to write a file and you get heredocs — which bash and zsh handle fine but fish doesn&amp;rsquo;t. Ask an agent to edit a config and you get a tangle of &lt;code&gt;sed&lt;/code&gt;, &lt;code&gt;cat &amp;gt;&lt;/code&gt;, and hope. &lt;strong&gt;hed&lt;/strong&gt; is the answer to both problems: a single C++17 binary that replaces heredocs, gives agents a machine-readable file editing API, and doubles as a nano-style interactive editor.&lt;/p&gt;&#10;&lt;h2 id="three-tools-one-binary"&gt;Three tools, one binary&lt;/h2&gt;&#10;&lt;p&gt;&lt;strong&gt;hed&lt;/strong&gt; (Heredoc Replacement · Agent File Tool · Nano-Style Editor) is a single static executable with zero runtime dependencies — no ncurses, no hunspell, no data files. Three modes:&lt;/p&gt;</description></item><item><title>MoACubed: teaching Hermes which profiles actually work</title><link>https://aislackin.com/posts/2026-09-06-moacubed/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate><guid>https://aislackin.com/posts/2026-09-06-moacubed/</guid><description>&lt;p&gt;I have been running Hermes with multiple profiles for a while. That gives me useful specialization, but it also creates an uncomfortable question:&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Which profile should handle a given kind of task?&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;It is easy to answer that question with vibes. One profile feels sharper. Another writes cleaner code. A third catches edge cases the others miss. Then one impressive run becomes a permanent routing rule.&lt;/p&gt;&#10;&lt;p&gt;That is not evaluation. That is anecdote with a config file.&lt;/p&gt;</description></item></channel></rss>