The issue arises because Cantor cannot automatically detect the SageMath binary when it is siloed inside a Conda/Mamba environment. To fix this, first identify the exact path to your Sage executable by running ‘which sage’ inside your activated sage environment (usually residing in ~/mambaforge/envs/sage/bin/sage (or similar). Once you have that path, open Cantor, go to Settings → Configure Cantor, and select the ‘Backends’ page. Find the ‘Sage’ backend in the list and click ‘Configure’. In the Path field, manually input the full path to your Mamba-installed sage executable instead of leaving it as sage. Apply the changes and restart Cantor; it should now successfully initialize the backend using the correct environment.