[feature] More automation to JADX

[mostafaNazari702]

Describe your idea

I have multiple apps, the same app across multiple versions and i want the AI ( through MCP plugin ) to process them autonomously. The workflow should be: open one APK, analyze it, close it, then open the next, repeating until it's done.

Right now, the "close" and "open" steps require me to manually click through the GUI every time, which unfortunately makes that impossible.

Would it be possible for the plugin manager to run at the application scope instead of the project scope? Currently, any MCP plugin is terminated as soon as a project is closed. That means the plugin goes offline between APKs, making it impossible to automate this kind of multi-project workflow.

[mostafaNazari702]

If we were to implement this, I think the following would need to be addressed:

• A way for a plugin to open and close projects without being terminated. Currently, the plugin manager is project-scoped rather than application-scoped, so closing a project also terminates all plugins. What to return to the plugin when a "close" command was sent through MCP should there be no project open and we are basically in the "Home"/"Open project"-page.

Also, If we for example use jadx-ai-mcp, i guess we will need:

• For a potential MCP tool, add a boolean parameter that specifies whether the project should be saved when it is closed (e.g. true to save, false to close without saving).
• For a potential MCP tool, add the ability to retrieve a list of saved projects (i mean the .jadx project files that are created when a project is saved).

[skylot]

@mostafaNazari702 looks like a good idea to allow plugins to init on jadx window creation and don't unload on project close.
This will require different plugin handling, so it is better to make explicit marker for such plugins: like new interface/abstract class.
Such approach allows filtering and initialization of such plugins on jadx-gui init and also supply handle to main window via new plugin init method. I will prepare implementation for this.

P.S. I saw your PR, but it looks more like a workaround, and since plugins also should be changed it is better to implement proper approach.

[mostafaNazari702]

I will prepare implementation for this.

ETA? otherwise i might be able to get that done if we can plan and discuss!

[skylot]

@mostafaNazari702 sorry no ETA. You can implement it your way and once proper API is done, just migrate to it.