Skip to content

Auto conda enviroments windows activation #42

@jay377

Description

@jay377

Hello, this tool looks awesome, so I really hope you can assist with the below quickly.

A problem I usually have with all of these types of tools, even VS Code extensions like Claude Code, which I couldn't get to work at all (it would never load my conda environment and still run commands on base env), is how to make it automatically load my particular miniconda environment for the specific project I want to work on. Can you let me know if that's possible and how do I ensure that with this tool?

I found it impossible to get it to work with Claude Code VS Code extension, for example as it uses some kind of bypass terminal access, but in VS Code or anti-gravity for the main agent terminal; it worked but I was forced to write A .bashrc script to conda activate "$ENV_NAME" based on detecting the folder (ENV_FILE=".conda-env", if [ -f "$ENV_FILE" ]; then, if [ "$CONDA_DEFAULT_ENV" != "$ENV_NAME" ]; then etc), you get the idea.

Just before using it, I just want to make sure that this won't be a problem in Windows like it is for all my other specialized apps that I've tried to force it to use a conda environment automatically.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions