https://blog.ast.moe/en/tags/developer-tools/Recent posts: GorimuchuHugohttps://blog.ast.moe/en/blog/2026-09-23/Wed, 23 Sep 2026 07:55:00 +0900https://blog.ast.moe/en/blog/2026-09-23/<p>I updated the <span> <a target="_blank" href="https://github.com/ieee0824/visual-store"> Visual Store </a> <img class="external-link-icon" src="https://blog.ast.moe/images/outer-link.png" width="12" height="12" alt="" aria-hidden="true" loading="lazy"> </span> .</p> <p>In the previous article “Added the ability to retain judgment results in Visual Store” (linked to 2026-09-21-2.md), I wrote about the new Judgment Layer that saves the decisions and verification results before an image is opened. This time, rather than introducing a new feature, I’m addressing the issue where the default build with VP9 enabled fails to compile on Debian 12 ARM64, and I’ve revised the procedure for reporting bugs in the Visual Store Skill. (<a href="https://blog.ast.moe/en/blog/2026-09-21-2/">related article</a>)</p>https://blog.ast.moe/en/blog/2026-09-21-2/Mon, 21 Sep 2026 19:55:00 +0900https://blog.ast.moe/en/blog/2026-09-21-2/<p>I updated the <span> <a target="_blank" href="https://github.com/ieee0824/visual-store"> Visual Store </a> <img class="external-link-icon" src="https://blog.ast.moe/images/outer-link.png" width="12" height="12" alt="" aria-hidden="true" loading="lazy"> </span> .</p> <p>This time, I added a Judgment Layer that records, for each image, the decision made before actually opening the screenshot and the verification results after it is opened.</p> <p>In the previous article “I created a Visual Store to prevent coding agents from hoarding images” (see 2026‑09‑16.md), I described a mechanism for saving images and retrieving only the ones needed. (<a href="https://blog.ast.moe/en/blog/2026-09-16/">related article</a>)</p> <h2 id="background">Background</h2> <p>The Visual Store was created to store debugging screenshots locally instead of embedding them directly into conversations, so that only the necessary screenshot can be retrieved later.</p>https://blog.ast.moe/en/blog/2026-09-19/Sat, 19 Sep 2026 20:05:53 +0900https://blog.ast.moe/en/blog/2026-09-19/<p>I have released a compatible simulator for testing SQS locally, <span> <a target="_blank" href="https://github.com/ieee0824/lqs"> lqs </a> <img class="external-link-icon" src="https://blog.ast.moe/images/outer-link.png" width="12" height="12" alt="" aria-hidden="true" loading="lazy"> </span> . The name is an abbreviation of <strong>local queue service</strong>.</p> <p>It provides an HTTP API that can be accessed from the AWS SDK, allowing you to test locally operations such as sending and receiving messages for both Standard and FIFO queues, visibility timeouts, and moving messages to a DLQ.</p> <p>Since all the issues I had prepared have been resolved, I decided to make it public.</p>https://blog.ast.moe/en/blog/2026-09-16/Wed, 16 Sep 2026 18:55:53 +0900https://blog.ast.moe/en/blog/2026-09-16/<p>I created a local image storage called Visual Store (<a href="https://github.com/ieee0824/visual-store">source</a>).</p> <p>When implementing UIs or checking browser rendering with a coding agent, I often end up taking many screenshots. Displaying all those images in the conversation not only adds the images themselves but also increases the amount of data in the conversation history.</p> <p>This time, I built a system that separates the act of saving images from showing the images to the AI.</p>