<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Hermes Labs</title>
    <description>The latest articles on DEV Community by Hermes Labs (@hermeslabsai).</description>
    <link>https://dev.to/hermeslabsai</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4123607%2Fbe4579a0-08b1-4735-a1ef-e8a5388ecfd8.png</url>
      <title>DEV Community: Hermes Labs</title>
      <link>https://dev.to/hermeslabsai</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hermeslabsai"/>
    <language>en</language>
    <item>
      <title>Hermeneutic turns your AI corrections into context for the next task</title>
      <dc:creator>Hermes Labs</dc:creator>
      <pubDate>Sun, 27 Sep 2026 05:33:58 +0000</pubDate>
      <link>https://dev.to/hermeslabsai/hermeneutic-turns-your-ai-corrections-into-context-for-the-next-task-2o8o</link>
      <guid>https://dev.to/hermeslabsai/hermeneutic-turns-your-ai-corrections-into-context-for-the-next-task-2o8o</guid>
      <description>&lt;p&gt;You ask a coding agent to review a function. It starts refactoring. You steer it back to the review you requested.&lt;/p&gt;

&lt;p&gt;That exchange contains useful information about your intended scope.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/hermes-labs-ai/hermeneutic" rel="noopener noreferrer"&gt;Hermeneutic&lt;/a&gt;, built by Hermes Labs, mines corrections from agent conversations and surfaces relevant guidance when similar tasks come up.&lt;/strong&gt; In this example, a later code-review request could receive guidance about staying within the requested scope—drawn from your earlier corrections.&lt;/p&gt;

&lt;p&gt;Your conversation history becomes a source of context for new work.&lt;/p&gt;

&lt;h2&gt;
  
  
  How correction memory works
&lt;/h2&gt;

&lt;p&gt;Hermeneutic reads supported Claude Code, Codex, and OpenAI-format logs. It recognizes correction-shaped user turns and records the surrounding exchange when available:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;your request → agent response → your correction → repaired response
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The resulting local corpus preserves the episode around each correction. The &lt;code&gt;bucket&lt;/code&gt; command lets you inspect recurring categories, including missed constraints, wrong targets, unnecessary confirmation, and scope expansion.&lt;/p&gt;

&lt;p&gt;Retrieval makes those records useful during another task. Using Ollama embeddings, Hermeneutic matches a new prompt against earlier prompts in the corpus. Relevant matches supply correction categories, which become a compact guidance preamble through category templates. Each advice bullet cites its supporting correction records.&lt;/p&gt;

&lt;p&gt;For a release task, that might surface your prior guidance to cite command output when reporting completion. For a similar review task, it might surface guidance about respecting the requested scope.&lt;/p&gt;

&lt;h2&gt;
  
  
  Put your own history to work
&lt;/h2&gt;

&lt;p&gt;With Python 3.10+ and Ollama available:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python &lt;span class="nt"&gt;-m&lt;/span&gt; pip &lt;span class="nb"&gt;install &lt;/span&gt;&lt;span class="nv"&gt;hermeneutic&lt;/span&gt;&lt;span class="o"&gt;==&lt;/span&gt;0.1.12

hermeneutic mine ~/.claude/projects &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--format&lt;/span&gt; claude-code &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--glob&lt;/span&gt; &lt;span class="s1"&gt;'**/*.jsonl'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--out&lt;/span&gt; ~/.hermeneutic/triples.jsonl

hermeneutic bucket ~/.hermeneutic/triples.jsonl

ollama pull nomic-embed-text
hermeneutic compile-index &lt;span class="nt"&gt;--triples&lt;/span&gt; ~/.hermeneutic/triples.jsonl

hermeneutic compile &lt;span class="s1"&gt;'Review this function and report your findings.'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;When matching corrections meet the relevance threshold, the final command emits guidance for that prompt. Use it directly in your workflow, or install the optional Claude Code hook to supply retrieved guidance as prompt context:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;hermeneutic install-compile-hook
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Start with the corrections you already made. &lt;a href="https://github.com/hermes-labs-ai/hermeneutic" rel="noopener noreferrer"&gt;Try Hermeneutic on GitHub&lt;/a&gt;, follow the &lt;a href="https://github.com/hermes-labs-ai/hermeneutic#hermeneutic-memory" rel="noopener noreferrer"&gt;memory setup&lt;/a&gt;, and star the repository to follow its development.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;What correction do you keep repeating to your coding agent?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Built by &lt;a href="https://hermes-labs.ai" rel="noopener noreferrer"&gt;Hermes Labs&lt;/a&gt;. Prepared by our agent infrastructure from the project README and documentation.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>python</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
