MolSuite Toolbox
An independent desktop app for MolSuite applications, projects and settings. Shared
project APIs stay in ms_flow; project and settings widgets stay in ms_components.
AMDockVS does not need Toolbox installed to create or open its projects.
Install and run
Python 3.12 or newer is required:
python -m pip install molsuite
molsuite
From a checkout, python -m pip install . instead. The package installs as molsuite
and imports as ms_toolbox; the module entry point works too: python -m ms_toolbox.
This installs a graphical launcher in the selected Python environment, rather than
a standalone binary with its own Python runtime.
On Linux, add a shortcut to the desktop's application menu:
molsuite --install-desktop-entry
The shortcut points to that environment's Python, so it works even when the
environment is not on the desktop's PATH. Windows and macOS use the installed
molsuite launcher; native application bundles are not provided yet.
Applications and installations
The catalog is bundled with the package and updated through reviewed pull requests. There is no GitHub search, arbitrary plugin discovery, or scanning of users' conda environments. An application is available for project creation only when its distribution and launch module are present in one of these places:
- A Python interpreter explicitly linked for that app in Apps → Link Python….
- The app's Toolbox-managed environment.
- The Python environment running Toolbox.
An explicitly linked interpreter takes priority. A broken link is shown as an error
instead of silently switching to another installation. A source checkout without
installed distribution metadata is not an installed app. Launching uses -I, so a
neighboring repository or inherited PYTHONPATH cannot masquerade as an installation.
Install catalog version uses ms_env to install the reviewed, pinned release
into a separate managed environment. ms_env supplies/downloads micromamba as needed.
This operation needs network access and may download substantial scientific dependencies.
It does not install into or modify an environment linked by the user.
Uninstall managed app also delegates to ms_env: an environment without its
ownership stamp is left untouched. Unlinking only removes the registration. Neither
operation deletes projects or app settings.
Close every instance of an app before replacing or removing its managed environment. Toolbox blocks changes for app processes started in its current session; processes started elsewhere or surviving an earlier Toolbox session are not tracked yet.
Projects
Toolbox uses ProjectCatalogBackend and ProjectsMenuWidget, with automatic workspace
discovery disabled. The shared MolSuite project catalog remains the source of truth.
In All apps, the table shows an Application column and stable app colors.
Selecting an app hides that redundant column. Apps absent from the reviewed catalog
still retain their projects and can be filtered by their stored app id.
Double-clicking a project starts its app with the selected interpreter and
--project-id. Toolbox stays open, watches the process and reports later failures
with the log path. If the app is missing, the error takes the user to its Apps
entry to install or link it. Process creation is not treated as proof of successful
app initialization.
Settings and themes
The Settings page reuses AppSettingsPanel. It groups MolSuite and Toolbox settings
separately from each catalog app's settings. Toolbox uses the existing ms_components
themes without a fixed violet shell.
The shared Hosts and Executors pages use KeptPage and the MolSuite Workspace
APIs, including local CPU/GPU limits. They do not start execution pools merely by
opening the settings page. Close apps before changing their shared resource settings.
App providers run in their registered Python environment, using a small subprocess bridge. The Toolbox package does not have to be installed there. Values are validated, saved and reset by the app's own MolSuite configuration provider. Toolbox does not rewrite another app's TOML itself or start its scientific runtime to load preferences. The initial AMDockVS entry exposes its AMDock and contact-map configuration providers. App-specific UI pages such as downloads or tool installation stay in their app.
Only global settings are edited here. Project-specific overrides remain in their projects. Changing MolSuite's project catalog path takes effect after restarting Toolbox.
Contributing an app
Add one TOML file to src/ms_toolbox/catalog, following
amdockvs.toml. The entry declares:
- A stable app id, name, scope and launch package.
- Its published distribution and the exact release reviewed for installation.
- An HTTPS repository URL, stable color and single-character icon.
- Optional configuration factories, written as
module:callable.
Each configuration factory takes no arguments and returns a MolSuite configuration
provider, such as PydanticConfiguration. It must be lightweight and work without an
open project. The app must accept python -m <package> --project-id <id>.
A PR must identify the maintained repository, release, license and supported platforms, and show that opening a project and editing global settings work. Review confirms the declared integration, not every behavior of the contributed application. Catalog entries execute installed app code when opening apps or settings and must be reviewed accordingly. Updating an app's approved release uses another PR; Toolbox does not guess whether a newer release is compatible.
Compatibility before v1
This first version deliberately does not invent a project migration policy. The app and MolSuite components remain responsible for validating their data formats. Toolbox neither claims that an older app can open a newer project nor downgrades projects. The catalog's approved app version is an installation choice, not the recorded creator version of a project. A full format/migration contract remains shared work before v1.
The shared UI and runtime dependencies are bounded to the tested pre-v1 minor versions. Widening those bounds requires running the tests against the new releases.
Development
In the project's MSDD_312 environment:
python -m pip install -e '.[dev]'
QT_QPA_PLATFORM=offscreen python -m pytest -q
python -m build
Tests cover curated catalog validation, explicit interpreter linking, late launch failures, preserving projects after uninstall, the All-apps column, missing-app navigation, and provider-based settings validation/persistence. They do not perform real scientific-app installations or modify user environments.
Metadata
Release files for molsuite 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| molsuite-0.1.0.tar.gz | 24.4 kB | With provenance | Details for molsuite-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| molsuite-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for molsuite-0.1.0-py3-none-any.whl |
Total release size: 46.2 kB
Release files / molsuite-0.1.0.tar.gz
| Download URL | molsuite-0.1.0.tar.gz |
|---|---|
| Size | 24.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
51c4bf167b2eb934f152974629138fa720151ce5fe920b8caa50ca2265f71fe6
|
|
BLAKE2b-256 checksum How to use checksums |
1f17b566f4ed6828c951df17eb342714e2a1d1e1f3720dd83fd250bddac45bcd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / molsuite-0.1.0-py3-none-any.whl
| Download URL | molsuite-0.1.0-py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0bc0a987b7afdd5d31be736f7efe1d4dc0e0434ea5bd5046e7081d492c995afe
|
|
BLAKE2b-256 checksum How to use checksums |
9d3dbd81f8165a3246a25b09480c64df41327faf36162887f597ec771bff6d23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logSecurity for molsuite 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for molsuite-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.