Live data from Hacker News

Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

huggingface.co

121–130 of 160 posts

Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

#121
post #25

Very cool! I understand that the 1.5B is small enough to run locally... but does it actually in the Sweep AI Jetbrains plugin? That is, if I install the plugin, will I download the model automatically and the plugin doesn't phone home?

Not at the moment, if you install the hosted Sweep AI Jetbrains plugin it uses our hosted (larger) model.

Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

#122

Surprising how badly Jetbrains implemented AI. Apparently to such an extent that even after multiple years of LLM's someone felt confident enough to build a company that can do better. This looks really neat, interesting technical writeup as well!

Thanks! Let us know if you have any questions / feedback.

Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

#123

This is cool! I am more interested in how you guys generated next edit training data from repos, seems like there are lots of caveats here. Would love your insights Again amazing work! waiting for what you guys cook next

The blog post has more information: https://blog.sweep.dev/posts/oss-next-edit

Also more technical details on SFT data here:

https://blog.sweep.dev/posts/next-edit-jetbrains#building-au...

Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

#124
post #14

It's good. The blog post about it is very interesting. I hope, a plugin for neovim will be made soon. https://blog.sweep.dev/posts/oss-next-edit

Someone in this thread already built a Neovim plugin connecting to this model I believe.

Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

#125
post #62

Where is the training data? We can't keep calling those models "open source" if we have a black box and know precisely how they were made. "Open weights" are the new binary.

Woops meant to say open-weight. We put open-weight in the title and but accidentally wrote open-source in the description.

Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

#126
post #79
post #59

Hey, ollama run as suggested in hf doesn't seem to work with this model. This worked instead: ollama pull hf.co/sweepai/sweep-next-edit-1.5B

I've been using it with the Zed editor and it works quite well! Congrats. This kind of AI are the ones I like and I'm looking to run in my workstation.

Double-check if you're using the right format.

Example here: https://huggingface.co/sweepai/sweep-next-edit-1.5B/blob/mai...

Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

#127

This is so cool. What is the second order effect of model training becoming democratized? And local models becoming the norm? Tasks like agentic work are well handled by current AI as long as you know what you're doing and can stress the agent against tests/spec, etc. I am thinking that one effect is: - it will become normal for meta-models to train a model specific to a particular task/product. Also, differently, I'…

Personally, I think usable AI is more valuable than simply more intelligence. Many of the labs are pushing towards models that are 1% better on CodeForces and AIME if you just let it think and use tools for hours, instead of more user-friendly models with better coding habits, like writing shorter and more modular code.

Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

#128

This is really awesome detail. I’m very impressed by the amount of care taken to identify a good template. I started a small hook to try and do this using DSPy prompt optimizers, but haven’t had a compelling use case to try it with. This seems like an ideal case for trying DFT as well. I’m not sure if you’re using trl, but I’d suggest checking that out.

We're using an internal fork of trl for some of the steps.

Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

#129

This is actually a game changer. I’ve been meaning to want to run models to accomplish exactly this, but don’t have enough VRAM on my GPU for the conventional LLM-method for the most part. This seems to be a far more efficient method of accomplishing a more scoped problem. Thank you for making it open source!

Let me know if you have any questions! What hardware are you on?
Post reply on HN