How abd19990044-commits/pynexus works
PyNexus is a recovered Android app overlay that preserves the original Python-script runtime and adds a token-protected HTTP API. The main workflow is: a user views the token and toggles the API in the dashboard; an API client sends authenticated requests to the server, which is documented to restrict access to registered app-folder Python scripts. The tree and excerpts do not expose the smali implementations, so internal wiring is shown only where the README supports it; unverified links are dashed.
Main entry points: ApiServer.smali HTTP API server · ScriptsFragment.smali Registered Python scripts · MainActivity.smali Main activity · ApiControl.smali API controls
Components 10
App interface
- Main activity
overlay/smali_classes3/com/pyscript/manager/MainActivity.smali - Dashboard
overlay/smali_classes3/com/pyscript/manager/DashboardFragment.smali - Scripts screen
overlay/smali_classes3/com/pyscript/manager/ScriptsFragment.smali
API access
- API controls
overlay/smali_classes3/com/pyscript/manager/ApiControl.smali - HTTP API server
overlay/smali_classes3/com/pyscript/manager/ApiServer.smali
Script runtime
- App initialization
overlay/smali_classes3/com/pyscript/manager/App.smali - Registered Python scripts
overlay/smali_classes3/com/pyscript/manager/ScriptsFragment.smali - Python runtime
Other components
- App user
- API client
Connections 10
- App user → Main activity: opens app
- Main activity → Dashboard: shows dashboard
- App user → Dashboard: views token
README.md - App user → API controls: toggles API
README.md - API controls → HTTP API server: starts or stops
- API client → HTTP API server: sends requests
README.md - HTTP API server → Registered Python scripts: restricts routes to
README.md - Scripts screen → Registered Python scripts: manages scripts
- Registered Python scripts → Python runtime: runs scripts on
README.md - App initialization → Python runtime: preserves runtime
README.md