Got rid of the old single-shot Q&A, that was really just a plain text generator and built an actual conversational chat panel today — persistent input box, Enter-to-send, the whole thing. Biggest win: markdown rendering for JARVIS’s responses (headers, bold text, syntax-highlighted code blocks), except VS Code’s webview CSP silently blocked the CDN script I was using for it, so nothing rendered and gave zero errors to go off of. Fixed it by bundling the library locally instead of pulling from a CDN — annoying to debug, but it actually made JARVIS more offline-capable in the process (since now itll render code through my machine, instead of loading the JS library from vs code), which is the whole point of this project anyway. Also learned the hard way that when your code looks right but VS Code is acting like it isn’t even running your changes, nuke dist/ and recompile before you waste an hour debugging code that was never the problem.
Comments 2
looks fun!
Sign in to join the conversation.