sestinj

7 ms·

31.
by sestinj 2y ago
Agreed! If there's value here, they'll definitely follow behind and have already taken their own creative steps. One interesting note is that rather than a pivot, the hub was just a continuation of work we'd already been doin
32.
by sestinj 2y ago
The goal of hub.continue.dev isn't to pre-build exactly what people will need (this might not be possible). We've started with a few examples for inspiration, but the hope is that hub.continue.dev makes it easier for developers to
33.
by sestinj 2y ago
Auth definitely seems like the biggest outstanding question with MCP. Local is a great first solution to make it simple, but maybe OAuth integration in the future makes this easier
34.
by sestinj 2y ago
I think Copilot plays an important role in the world of code assistants, and it's great that they've implemented Agent mode as well. We'd actually love for them to take part in the standard we're building here—the more p
35.
by sestinj 2y ago
I was actually talking to someone the other day who was building an MCP for Continue that could call the Elixir type checker / compiler (which I've heard is quite powerful). I'll need to find this and share—they were saying i
36.
by sestinj 2y ago
This is fair feedback—we're so early in building an ecosystem here that the prompts we've shared as starting points are relatively general. But already we've seen people start to build much more carefully-crafted and specific
37.
by sestinj 2y ago
Excited to hear how it goes for you! Our Models Add-On is intended to give the same flat monthly fee as you’re accustomed to with other products. What did you mean by leaning into pooled, just making it more front-and-center?
38.
by sestinj 2y ago
On one hand, I think it would be useful to have a couple of benchmarks for super common tech stacks like Python, React, etc. that allowed comparing variants of rules to find the best ones. On the other hand, if something can be turned into
39.
by sestinj 2y ago
On another note, this rang true to me: > Basically knowledge packs should be specified in each npm package.json or similar. Our YAML-based file format for assistants ( https://docs.continue.dev/reference ) is hoping to do
40.
by sestinj 2y ago
Languages, libraries, internal company codebases, common tasks (e.g. writing unit tests in your style, scaffolding a CRUD backend, etc.), personal preferences, and much more. Language models are so general that I probably haven't thoug
41.
by sestinj 2y ago
We think about this a lot, and I think there are merits to the viewpoint. If I were to write a rule that said "make sure all code you write uses best practices", it should already be obvious enough to a good language model that th
42.
by sestinj 2y ago
Right now they are defined as a command (typically npx, uvx, docker or another way of running code) and run as a subprocess in VS Code, which is the same starting point that tools like Claude Desktop have used. We're also going to supp
43.
by sestinj 2y ago
Thanks for the report, we should be able to fix this in the next hour or so. A workaround would be to copy the YAML definition displayed on the page of the assistant / block you want to remix. Will keep you updated!
44.
by sestinj 2y ago
Yeah we think that MCP was a really solid building block at a lower level but ultimately a higher level abstraction is what will make customization really accessible. Being able to define rules, models, MCP servers, docs, prompts, data flow
45.
by sestinj 2y ago
Appreciate it!!
46.
by sestinj 2y ago
Thank you! The biggest difference in our approach is the goal of allowing for custom assistants. What we've found is that most developers work in entirely different environments, whether that be IDE, tech stack, best practices, enterpr
47.
Launch HN: Continue (YC S23) – Create custom AI code assistants(hub.continue.dev)
178 points by sestinj 2y ago|110 comments
48.
by sestinj 2y ago
To be honest I also don't feel very good about the current title. From my perspective: the purpose of the statement was not to demand, but to protect the Continue community and show the way to open source done right. The alternative su
49.
Chat vs. Tab: What's the best way to do local AI dev?(github.com)
3 points by sestinj 3y ago|0 comments
50.
Show HN: Continue.dev releases local, open-source tab-autocomplete(continue.dev)
53 points by sestinj 3y ago|3 comments
51.
by sestinj 3y ago
My current test of image models is generating React code from a screenshot of the top of a HackerNews comment page. Llava-1.6 gave me this (over two responses), which is honestly not bad: ```ts const CommentForm = () => { //
52.
by sestinj 3y ago
We've been playing with the 1.3b model for continue.dev's autocomplete and it's quite impressive. One unclear part is whether the license really permits commercial usage, but regardless it's exciting to see the construct
53.
by sestinj 3y ago
Definitely, here is a brief reference page for the Together provider: https://continue.dev/docs/reference/Model%20Providers/togeth... , and a higher-level explanation of model configuration here: https:/
54.
by sestinj 3y ago
Personally I was testing with TogetherAI because I don't have the specs for a local 70b. Using quantized versions helps (Ollama's downloads 4-bit by default, you can get down to 2), but it would still require a higher-end Mac. Hig
55.
by sestinj 3y ago
Release coming later this week!
56.
by sestinj 3y ago
beat me to the punch : )
57.
by sestinj 3y ago
I’ve been working on continue.dev, which is completely free to use with your own Ollama instance / TogetherAI key, or for a while with ours. Was testing with Codellama-70b this morning and it’s clearly a step up from other OS models
58.
by sestinj 3y ago
Gotcha, very much appreciate the feedback
59.
by sestinj 3y ago
You'll get our GPT-4 free trial for a while, but then after that you'll also have the option to use a local model, which would be free (though of course their quality doesn't quite yet match GPT-4) Currently, we want our prod
60.
Show HN: Continue for JetBrains - how we made it IDE-agnostic(plugins.jetbrains.com)
7 points by sestinj 3y ago|4 comments

More ›