Hacker Newsnew | past | comments | ask | show | jobs | submit | Zambyte's commentslogin

People in this thread seem to be too focused on the agent creating a git log. This seems to be solving a different problem than that does.

When you're interacting with agents, multiple prompts may reasonable culminate in a single commit. It may be useful to track or undo things between commits - at the prompt level. I personally have a workflow when I use Jujutsu (jj) for git already, and this slotted in very nicely to solve this problem. The auto-committing in jj makes it very easy and natural to compare diffs between prompts, and undo specific chunks or restore previous states without making a new commit every prompt. I only finish a commit, giving it a message and advancing the branch, once I've iteratively dialed in the changes I want.

I probably won't use this tool since I already have a flow that works for me, but maybe this will help people see why such a tool can be helpful.

Edit: fixed typo


Also https://github.com/timescale/timescaledb

I've found it very useful for storing geospatial data over time.


MobilityDB might also be of interest, for people handling trajectories.

Everything made by Google is a liability.

> the app will now be called “NextPad++,” an homage to NeXT Computer, and uses a frog icon rather than the Notepad++ lizard.

Very interesting. I've been using org-roam for a while without too much trouble, but I do think a ripgrep backed system over a sqlite based one sounds interesting. I will have to see if I can port my notes over and try it out.

Already out of stock. Been waiting 4 years for this, and I was busy eith work for 45 minutes and I missed this batch :\

Then use one. There are so many.

I don't know about that. Women really scare men.


I've been using Qwen 3.5 and then 3.6 27b Q4 on Ollama with a single 7900 XTX with the codex cli, and I have been blown away by how genuinely useful it is. I've been able to ask it to do long, multi step problems, and it's able to do things that would have likely taken me days to iron out in a matter of hours, or even minutes sometimes.

I get about 30 tok/s, which is far from blazing, but given the capability it has it is absolutely viable for accelerating my work.


Kagi has done a good job of making it easy to cut through slop so far. I never really deal with slop search results

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: