continue
continue copied to clipboard
Minor improvements for @locals context provider (report stacktrace in more languages and other things)
Validations
- [X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
- [X] I'm not able to find an open issue that requests the same enhancement
Problem
- I think my previous implementation does not give the callstack in some debug sessions, for example this python debug session. Sorry had to mask some part of the code. I think I will investigate this and try to improve it.
- Some variables are shown as unknown but if you click on the variable in the debug window it can be further inspected, I want to somehow enable LLMs to inspect that kind of variable too but not exactly sure how I should feed it into LLMs (should I let the LLMs decide whether to expand/inspect the variable or I should write a manual rule or smth)
- Apart from the local scope in a paused thread, there are also other type of scopes like global variables and registers (in some languages)
- Also I am thinking a
@expr
provider that kind of evaluates a expression and feed it into the llm, I think some really badly written code may have too much local variables that could overwhelm the LLM, while the@expr
provider can only provide the variables/expression you want to feed, but I might need to figure out how to solve the problem of having multiple threads in the session. And also potentially make a seperate@stacktrace
provider.
Solution
No response