Hi, sorry if this is the wrong channel, I couldn't quite work out where this would fit, happy to move or delete it if it's not suitable to post here! I'm Will Cook, an undergraduate at the University of Bristol and I've been working on a set of projects called Plectis, using AI for research and software and trying to use the same AI to make that work easier for people to understand. The discussions throughout this slack seem to be a lot about agents putting changes in the wrong repository which made me think there might be some relevant overlap with OpenHands. One part is a code map frontend where you can go from the broad areas of a project into individual files and see how they connect. The descriptions follow a standardised schema in the docstrings, so agents can extract particular fields and people can see the same information through the map. You still need to check the code, but it gives you somewhere to start when you're trying to understand what an agent is changing. I'm also experimenting with mapping the rules given to agents to the folders they apply to, and showing whether there's an actual check behind a rule or it's just written guidance which is called "safety-core". With the discussions here about making review criteria clearer for both agents and people, I wondered whether something like this could be useful alongside Agent Canvas. CodeMap is still a private prototype, I'm working on releasing it. This is my current introduction, about 8 minutes: It covers the maths and video tools as well, so it's a bit broader than this, the code map is near the start. I'm planning to start rerecording this weekend. If anyone working with OpenHands could share some critical feedback on whether this makes sense, or where I'm explaining it badly, I'd really appreciate it. I'd be happy to credit people's help.