This is probably the biggest improvement I would suggest.
In debugging rounds, the problem is often not contained in a single file. There may be multiple files such as main, utility files, configuration files, components, services, etc., and the bug may depend on how these files interact with each other.
It would be very helpful if Perkite AI could support selecting or scanning multiple files/folders and then analyze the entire codebase together. This would allow it to understand dependencies, trace the flow across files, identify the root cause, and suggest the required changes instead of analyzing each file separately.
like screenrecording is the only solution i guess
I believe solving these two areas would make Perkite AI much more effective for real-world coding assessments and debugging challenges. The current experience is already promising, and these additions could take it to the next level.