sestinj

7 ms·

1.
by sestinj 7mo ago
Actually very similar, GitHub was also early in talking about Continuous AI. I think the biggest difference is that Continue is very focused on the use case of checks and gets a lot of the small details right that really matter because it&#
2.
by sestinj 7mo ago
just saw the follow up questions: - we do! right now you can export some metrics as images, or share a link publicly to the broader dashboard. will be curious if others are interested in other formats https://imgur.com/a&#x2
3.
by sestinj 7mo ago
I think this is a good summary! And the configurable part turns out to be the main bit One of the fundamental differences between checks and code review bots is that you trade breadth for consistency. There are two things Continue should ne
4.
by sestinj 7mo ago
That's us! I figure others will wonder the same, so we wrote about what exactly we're doing here: https://blog.continue.dev/from-extension-to-mission-control tl;dr - a _lot_ of people still use the VS Code extens
5.
Show HN: Continue – Source-controlled AI checks, enforceable in CI(docs.continue.dev)
44 points by sestinj 7mo ago|7 comments
6.
Continue (YC S23) is hiring software engineers in San Francisco(ycombinator.com)
1 points by sestinj 1y ago
7.
by sestinj 1y ago
Continue | ONSITE - San Francisco | Full-time | https://continue.dev Continue is building an open-source AI code assistant along with a hub of models, rules, and tools. Our VS Code and JetBrains extensions are primarily written
8.
by sestinj 1y ago
Continue | ONSITE - San Francisco | Full-time | https://continue.dev Continue is building an open-source AI code assistant along with a hub of models, rules, and tools. Our VS Code and JetBrains extensions are primarily written
9.
by sestinj 1y ago
If you're a user of .cursorrules or .windsurfrules, then there's a lot of great content at https://hub.continue.dev/explore/rules . They don't yet support assistant files directly so unfortunately you&#x2
10.
by sestinj 1y ago
We want Continue to always be free for individuals, and we layer on features for teams and enterprises to make money. There’s much more detail on our pricing page: https://hub.continue.dev/pricing We have opt-out telemetry
11.
by sestinj 1y ago
I'm sorry you ran into problems repeatedly, and couldn't agree more. As much as we've aimed to innovate on customization, it does not have to be an either/or. We recognized this, heard a lot from the community, and the g
12.
by sestinj 1y ago
Ooh +1 to both of these. We use shadcn as well :) and have been leveraging these docs: https://hub.continue.dev/vercel/shadcn-ui-docs , but there should totally be more in-depth rules for it and Firestore
13.
by sestinj 1y ago
It looks like people have created a few already: https://hub.continue.dev/search?q=flutter I think it would be great to have one on the front page as well if there's something you find works really well. The nice thing
14.
by sestinj 1y ago
We didn't claim to be covered by AP, but I see what you mean: the previous text ("Learn more on TechCrunch and The Associated Press") wasn't clear enough. We've updated it to say “Check out our TechCrunch coverage a
15.
by sestinj 1y ago
Totally, I actually think this would make for a really great custom assistant, probably even something we'd feature on the front page: https://hub.continue.dev/explore/assistants You could start here by adding a n
16.
by sestinj 1y ago
Rules are a subset of what we've allowed you to do on the Hub (and an important one). There are other building blocks, like models, MCP servers, docs, prompts, data, and more. We want to make all of this easy to customize
17.
by sestinj 1y ago
thanks!
18.
by sestinj 1y ago
I hear this often (I had the same gut reaction before thinking below the surface) and will share why I think that our bet is perfectly aligned with the Bitter Lesson being true 1. The Bitter Lesson extends to test-time compute (some call th
19.
by sestinj 1y ago
Fix is released! Thanks for catching this so early Should now be able to remix PyTorch rules for example: https://hub.continue.dev/starter/pytorch-rules/remix
20.
by sestinj 1y ago
I wouldn't say that's free-loader behavior :) It's exactly what we want to make possible—if you have strong reason to use your own models (price, convenience, security, remaining local, or other) then Continue is built for th
21.
by sestinj 1y ago
:D thank you!!
22.
by sestinj 1y ago
wow that was fast—some gems in there
23.
by sestinj 1y ago
If you want to keep in touch going forward, you're welcome to join our Discord or share a GitHub issue, we'll try to be quite responsive
24.
by sestinj 1y ago
I'd say rules are quite similar to a README, just tailored to LLMs, which often benefit from slightly different information than a human would. One way to think about the difference is that we as developers have the chance to build up
25.
by sestinj 1y ago
This is a good callout, we'll definitely work to improve our messaging
26.
by sestinj 1y ago
thanks!!
27.
by sestinj 1y ago
Nothing built-in yet, but if you have a service that lets users pay for API keys then you can achieve this in effect. There are already some good examples: - Models like Relace's Instant Apply ( https://hub.continue.dev/
28.
by sestinj 1y ago
We have support for text-to-speech in the chat window and have also worked with developers who code entirely through voice and have been quite successful with Continue. I don't claim that we're perfect and would love to hear how w
29.
by sestinj 1y ago
You're 100% correct, most models these days know most programming languages and will quickly learn the syntax of more niche languages. For users that end up benefitting from rules, it's typically because of encoding "personal
30.
by sestinj 1y ago
Absolutely +1 to the progress of local models! We hope Continue is and continues to be a great place to use them. Tons of blocks in the Ollama page for example that can be used: https://hub.continue.dev/ollama

More ›