HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
acrotron
aye-chat
Python2025–2026
acrotron / aye-chat

aye-chat

Aye Chat: AI-powered terminal workspace

2Distinct people
9Mentions
0Explicit recommenders
64GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Aye Chat: AI-powered terminal workspace

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:01:57 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week9 dated mentions

Observed mentions: 2025-10-30 13:23:21 UTC to 2026-04-09 12:42:41 UTC. Weeks start Monday, UTC.

0122025-10-27 00:00:00 UTC to 2025-11-03 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsOct 272025-11-03 00:00:00 UTC to 2025-11-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-10 00:00:00 UTC to 2025-11-17 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-11-17 00:00:00 UTC to 2025-11-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-24 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-12-01 00:00:00 UTC to 2025-12-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-08 00:00:00 UTC to 2025-12-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-15 00:00:00 UTC to 2025-12-22 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-12-22 00:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-12-29 00:00:00 UTC to 2026-01-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-05 00:00:00 UTC to 2026-01-12 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-01-12 00:00:00 UTC to 2026-01-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 122026-01-19 00:00:00 UTC to 2026-01-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-26 00:00:00 UTC to 2026-02-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 00:00:00 UTC to 2026-02-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-09 00:00:00 UTC to 2026-02-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-16 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-23 00:00:00 UTC to 2026-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-02 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 00:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-16 00:00:00 UTC to 2026-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 00:00:00 UTC to 2026-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-30 00:00:00 UTC to 2026-04-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-06 00:00:00 UTC to 2026-04-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 6

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 272025-10-27 00:00:00 UTC2025-11-03 00:00:00 UTC110
Nov 32025-11-03 00:00:00 UTC2025-11-10 00:00:00 UTC000
Nov 102025-11-10 00:00:00 UTC2025-11-17 00:00:00 UTC202
Nov 172025-11-17 00:00:00 UTC2025-11-24 00:00:00 UTC000
Nov 242025-11-24 00:00:00 UTC2025-12-01 00:00:00 UTC211
Dec 12025-12-01 00:00:00 UTC2025-12-08 00:00:00 UTC000
Dec 82025-12-08 00:00:00 UTC2025-12-15 00:00:00 UTC000
Dec 152025-12-15 00:00:00 UTC2025-12-22 00:00:00 UTC101
Dec 222025-12-22 00:00:00 UTC2025-12-29 00:00:00 UTC110
Dec 292025-12-29 00:00:00 UTC2026-01-05 00:00:00 UTC000
Jan 52026-01-05 00:00:00 UTC2026-01-12 00:00:00 UTC110
Jan 122026-01-12 00:00:00 UTC2026-01-19 00:00:00 UTC000
Jan 192026-01-19 00:00:00 UTC2026-01-26 00:00:00 UTC000
Jan 262026-01-26 00:00:00 UTC2026-02-02 00:00:00 UTC000
Feb 22026-02-02 00:00:00 UTC2026-02-09 00:00:00 UTC000
Feb 92026-02-09 00:00:00 UTC2026-02-16 00:00:00 UTC000
Feb 162026-02-16 00:00:00 UTC2026-02-23 00:00:00 UTC000
Feb 232026-02-23 00:00:00 UTC2026-03-02 00:00:00 UTC000
Mar 22026-03-02 00:00:00 UTC2026-03-09 00:00:00 UTC000
Mar 92026-03-09 00:00:00 UTC2026-03-16 00:00:00 UTC000
Mar 162026-03-16 00:00:00 UTC2026-03-23 00:00:00 UTC000
Mar 232026-03-23 00:00:00 UTC2026-03-30 00:00:00 UTC000
Mar 302026-03-30 00:00:00 UTC2026-04-06 00:00:00 UTC000
Apr 62026-04-06 00:00:00 UTC2026-04-13 00:00:00 UTC101

What Hacker News says

1 sources
acro-v·Jan 6, 2026Submission

Show HN: AI that edits your files directly, no approvals [demo]

Hey HN, I am building Aye Chat, an open-source terminal workspace that integrates AI code generator directly into your shell, allowing you to edit files and run commands as well as prompt AI seamlessly. The AI writes code directly to your files immediately, eliminating the "review and approve" out of the loop. At the same time, every AI edit is snapshotted locally, so you can instantly undo any change with a single command. This automatic file update with a safety net is the core idea. Also, in the same session, you can run shell commands, open Vim, and ask the AI to modify your code, turning it into an AI-powered terminal. I built this because I got tired of the "suggest -> review -> approve -> changes applied" loop in existing AI coding tools. As models improve and generate proper code more often than not, manual approval started to fee
Read the rest
l unnecessary as long as there is a strong safety net to allow easy rollback of the changes. Yes, the idea is not exactly groundbreaking: other tools already offer "set a dangerous flag and remember to recover later" settings, but what I am exploring is defaults, not capability. With Aye Chat, the default is the opposite: apply immediately and make undo trivial. There are no flags to remember, no mode switches, and you don't need to exit the tool to roll back. You can watch a 1-minute demo here: https://youtu.be/h5laV5y4IrM Basically, the typical workflow goes like this (instead of a chat window, you stay in your terminal): $ aye chat # starts the session > fix the bug in server.py Fixed undefined variable on line 42 > vim server.py [opens real Vim, returns to chat after] > refactor: make it async Updated server.py with async/await > pytest Tests fail > restore Reverted last changes I use Aye Chat both in my work projects and to build Aye Chat itself. Recently, I used it to implement a local vector search engine in just a few days. Lower-level technical details that went into the tool: The snapshot engine is a Python-based implementation that serves as a lightweight version control layer. For retrieval, we intentionally avoided PyTorch to keep installs lightweight. Instead, we use ChromaDB with ONNXMiniLM-L6_V2 running on onnxruntime. File indexing runs in the background using a fast coarse pass followed by AST-based refinement. What I learned: The key realization was that the bottleneck in AI coding is often the interface, not the model. By shifting to the AI writing code immediately with users still maintaining full control to undo those changes - we eliminate the cognitive load of the review-and-approve loop. I also learned that early users do not accept a custom snapshot engine, so to make it professional-grade we are now integrating it with git refs. What I’d love feedback on: - After using it for a while, did replacing approvals with undo actually change how you work, or did it feel no different from existing terminal-based AI tools (GitHub Copilot CLI, Claude Code)? - Was there a moment when this started to feel natural to use, or did it never quite click? There is a 1-line quick install: pip install ayechat Homebrew and Windows installer are also available. Repo: https://github.com/acrotron/aye-chat. If you find it interesting, a repo star would mean a lot! It's early days, but Aye Chat is working well for me. I would love to get your feedback. Feel free to hop into the Discord (https://discord.gg/ZexraQYH77) and let me know how it goes.
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.