Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • UI looks great
  • Oh thanks that's made my day haha!
  • Forced dark theme -- please don't punish me for having astigmatism--can't do dark mode
  • not to mention that light themes produce less eye fatigue and strain. but who cares about that
  • Haha fair enough, my colleague always says the same! Actually the theme's already separated into a JSON file so this will be trivial.
  • Ignore all the negative comments, this is really cool. Looks a lot like a JetBrains IDE. One suggestion is to integrate claude code as a code editing window tab rather than a terminal window. If you'd like checkout https://github.com/sajithdilshan/agent-cli-plugin on how I did it for JetBrains IDEs as a plugin
  • Oh man, that's a great idea. Well done.
  • Cheers! I'll be improving it as I use it every day, refusing to open old IDE haha.
  • You didn't wrote this. Generating code from AI is NOT programming.
  • OP doesn't say they wrote it. They say they built it. This seems to be the word that people have settled on to describe having the llm put something together according to your requirements.
    by tom_
  • I'm with the other comments here, but what's the deal with the '120 fps scrolling' blah blah blah? This clearly isn't a game or movie -- why are we talking about frames?
  • Hey, I should have maybe made this more clear - I definitely don't care that it's 120fps more that the frame rate doesn't drop and we aren't seeing freezes. Initially the project was, with large files, with syntax highlighting especially or switching very large branches. The built-in FPS counter actually proved really helpful in observing these.
  • This is amazing and I will use this! Does it support git submodules? I like how VSCode divides changes into buckets across all git repos in current workspace, I can commit each separately from one sidebar.
  • Hey! That's actually something I haven't checked, none of my active projects use them. I expect it won't break but I haven't designed the diff to account for that. I will take a look though it's a great point.
  • What models and tools did you use to create this?

    What were your biggest challenges in making this?

  • > What models and tools did you use to create this?

    Opus 4.8.

    > What were your biggest challenges in making this?

    UI that had to react due to things such as the window size changing, specifically with horizontal and vertical scrolling and getting it to work with mouse drag + text selection via shift and arrow keys. It was a lot of back and forth. In the end after getting it working for the main editor I (Claude) turned it into a with_scrollbars decorator method.

    Knowing to splitting god functions before they sprawl / emphasising regression tests, and specifically frame rate regression has helped me a lot so far I think.

  • The code is...quite bad...

    It seems the AI coding is just the software version of Temu. Lots of cheap stuff but none of it is very good and it breaks pretty easily when you try to do anything outside of a very very small list of uses.

  • Hey, have you got any fundamental examples of why? I get pessimism towards AI, I've battled against using it after programming for so long, but I do intend to keep building on this and I'd genuinely appreciate things you saw that are icebergs.
  • I like how it looks.

    But the terminal already has excellent diff and commit tools.

  • Fair enough. I always switch to my IDE for a big branch, actually that's why I never switched VSCode, I liked my original IDEs Git UI. But maybe that's just muscle memory using the same IDE from Java to web over the years.
  • I'm curious, what's some user-friendly terminal based tool to say stage only a couple of discontiguous lines from changes in a single file to commit in Git?

    I think I've tried the git command line "interactive" mode, and is really painful. I find myself going to an IDE, selecting the line and right-clicking + "stage selected ranges" to achieve that.

  • What might you build when you let Claude take care of commits? :-)
  • A garden.
  • Pretty good, and I think I could definitely use it. One thing that I immediately missed is syntax coloring. For Markdown and other known extensions. I am sure it will be trivial to add it.

    Another possible useful feature would be to add "open in system" or similar in the right-click menu for a file, to open the file with whatever application the OS has bound to it.

    EDIT: I see there's a plugin thing that when clicked installs the highlighting. Cool!

    EDIT: Also missing is selectively staging lines of a changed file to commit. I would actually change the behaviour of the Git UI so that it matches the VSCode one, to reduce the learning curve. Most people already know how that works, no need to make them learn a new UX.

  • Yep of course, Syntax colouring will come. And it was intentionally left out first couple days due to critical path for me, I imagine I'll add intelisense too but I'm glad I decided to make language support installable - goal is fast + great Git.

    >open in system:

    Isn't that reveal in finder? I did add this if so :).

    > selectively staging lines

    Oh I've never actually done this! But I think I understand, so just pushing a few lines in a changed file. Fun! I've always used a different IDE where I don't think that's a thing. I'll add an issue.