As someone who has done a lot of work with agentic coding I am not sure specialized agents are the best solution. I think standardizing knowledge packs would be better that any agent can read to understand a domain or library is more useful. In particular this allows for an agent to know multiple domains at the same time. Basically knowledge packs could be specified in each npm package.json or similar. And we should…
Launch HN: Continue (YC S23) – Create custom AI code assistants
111–113 of 113 posts
Re: Launch HN: Continue (YC S23) – Create custom AI code assistants
#112Earlier quoted context omitted.
What broke on you when using Cody? Sorry to hear about that and want to fix it for you.
Thanks for asking. This may be more information than you were expecting, but here goes! I tried to use it one day and was confronted by a cryptic auth error. It looked like a raw HTML error page but it was rendering in the side panel as plain text. So I tried logging out an logging back in again. That got me a different cryptic auth error. Then I noticed I had accidentally left my VPN on, so I turned that off, but th…
Re: Launch HN: Continue (YC S23) – Create custom AI code assistants
#113Earlier quoted context omitted.
I'm of two minds. I currently use 3 MCPs regularly (Atlassian, Git, and GitHub). And I suppose if GitHub or Atlassian actually hosted first-party MCP endpoints for their services, we probably wouldn't need to self-host? But I wouldn't want to have a third party host where, all they're doing is just running the npx/uvx command themselves and I still have to give them keys, etc. At that point, I'd rather just host them…
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
The current system of generating keys and setting custom permissions will leave room for error.