Nate Sesti

@FabianHertwig This is a mistake in the docs since we removed the /config slash command and I'll be sure to fix it. You can now access config.json either by clicking...

@FabianHertwig I'm not certain of their state as of the old Python server versions, but these are two of the remaining pieces that I still need to implement in the...

@FabianHertwig the issue context provider is now completed: https://continue.dev/docs/customization/context-providers#github-issues

@jaresty by code search do you mean the @ codebase context provider, cmd+enter, @ files, or something else? The mapping here is for tree-sitter wasm files, and there happens to...

@jaresty true that .jsx should probably have it's own grammar, I think this is probably just because there wasn't a readily available jsx grammar found and jsx is slightly less...

@justinmilner1 Part of the goal with generating a link was to give users a chance to modify the issue before it originally gets published. When you create via API, I...

@justinmilner1 it's not a direct API that they have, but you can create a URL that opens up a draft of an issue when clicked. This is what I was...

@justinmilner1 Oooh this explains everything, I hadn't realized that at all. A bit unfortunate, but nevertheless I think the larger point about user confirmation/input is important. I would say this...

Open questions: - Haven't had luck pinning this down yet: Does accept/reject buttons not working mean they don't show up, that clicking them doesn't affect anything, or that clicking them...

Improvements made so far: - I [added an output channel](https://github.com/continuedev/continue/commit/d080c8ed30f15a4acca98bbb70e5989e6dbf7d60) that will show you every prompt/completion to/from the LLM - Error messages for fetch failures will now [actually tell you...