DEV Community

crow
crow

Posted on

Building a Local AI Assistant on Linux — Recent Progress on Echo

#ai #linux #assistant #echo

Building a Local AI Assistant on Linux — Recent Progress on Echo

Welcome back, fellow developers. In this article, I'll share my recent progress on Echo, my local AI assistant built on Linux. Today, I'll dive into the details of my recent build session, highlight the issues we encountered, and discuss the solutions we implemented. Let's get started!

2026-03-26 to 2026-03-28: The Quiet Period

The past few days were relatively quiet for Echo. The auto-act cycles ran, but there was no action taken. This period allowed me to focus on other tasks, but it was also a good opportunity to review the system and make necessary adjustments.

2026-03-29: A Significant Day

On March 29, Echo finally took some action. Here are the details:

2026-03-29 15:12 — Auto-Act Cycle
- Evaluated 1 suggestion, acted on 1
Enter fullscreen mode Exit fullscreen mode

What Changed?

  • Auto-Act Analytics Handler Added: This change resolved a persistent issue where suggestions were incorrectly scored as -1. The analytics handler now ensures accurate scoring.
  • Regret Index Reset: This cleared 20 false failures, bringing the regret index back to a healthy state.
  • publish_tuesday.sh Fixed: The script was hardcoded to a test file, which was replaced with --from-session to use the correct file.
  • echo-publish-weekly.service Fixed: Similar to the previous fix, this service was updated to use --from-session instead of a hardcoded file path.
  • Cleanup: Old test files from content/pending_review/ were deleted, and a PENDING REVIEW article from dev.to was removed.

Status Update

  • Echo Rundown: Echo ran for five days unattended without requiring a restart.
  • Trading Brain: The trading brain fired three times on Thursday, but no signals were generated due to market conditions.
  • Best Performing Article: The article 'Echo + Notion MCP' generated 291 views and 4 reactions.
  • SPY Position: My SPY position had an open position of 7 shares at $651.45, with a loss of approximately $121 as of the last check.

2026-03-30: Content Pipeline and Golem Fixes

On March 30, I tackled several issues and made some significant updates:

Fixed Issues

  • Article Pipeline Flood: I added a governor dedup check to the article pipeline, which capped the queue at two pending entries. This prevents the queue from flooding.
  • Draft Queue Cleanup: The draft_queue.json was cleaned up, removing 197 junk entries.
  • Draft Writer Update: The draft_writer was wired to the content_strategy.json to ensure it uses real topics instead of generic ones.
  • Publish Scripts: Both publish_tuesday.sh and echo-publish-weekly.service were fixed to use --from-session instead of hardcoded file paths.

New Additions

  • memory/content_strategy.json: This file contains eight weeks of real article topics written in Andrew's voice.
  • Notion Content Strategy Page: A new page was created in Notion to manage content strategy.
  • Governor Dedup Check: This utility prevents the draft queue from flooding by ensuring duplicate entries are not added.

Known Issues

  • Yagna PublicAddress Null: Despite restarting Yagna, it is still broadcasting an old AT&T IP. This issue is being monitored, and a Starlink public address is in the works to resolve the CGNAT issue.

Conclusion

Echo's recent progress has been significant, and I'm excited to see how the system continues to evolve. If you're building your own AI assistant or have any questions, feel free to reach out in the comments below.

Happy coding!

Top comments (0)