[QUESTION] Conda environment workflow guidance needed - inherited environment but missing shell functions

Environment

• Platform: Anthropic API
• Claude CLI version: Latest
• Operating System: Windows + VS Code SSH + Docker Desktop Ubuntu container
• Terminal: bash
• Conda version: 25.3.1

Background

We're seeking guidance on the recommended workflow for using conda environments with Claude Code, as the current behavior seems inconsistent and undocumented.

Current Situation

Scenario 1: VS Code Terminal → Claude Code

1. Activate conda environment in VS Code terminal: conda activate thuts28x
2. Launch Claude Code from activated terminal
3. Claude Code inherits environment variables (CONDA_DEFAULT_ENV=thuts28x) but loses conda shell functions

Scenario 2: Docker Container → Claude Code

1. Enter Docker container via Docker Desktop exec
2. Launch Claude Code directly
3. Same issue: conda environment variables present but shell functions missing

Problem Description

Claude Code inherits conda environment variables but cannot use conda activate:

echo $CONDA_DEFAULT_ENV
# Output: thuts28x ✅ (inherited correctly)

which conda  
# Output: /opt/miniconda3/condabin/conda ✅ (conda available)

conda activate thuts28x
# Output: CondaError: Run 'conda init' before 'conda activate' ❌

Current Workaround

The only working approach requires shell hook injection in each command:

eval "$(conda shell.bash hook)" && conda activate thuts28x && python script.py

However, this doesn't persist between commands (related to issue #2508 about environment variables).

Root Cause Analysis

Based on conda documentation and community analysis:

1. Environment variables are inherited from parent shell (✅ working)
2. Conda shell functions are missing because Claude Code's bash processes don't load ~/.bashrc
3. conda activate requires both environment variables AND shell functions

This is similar to issues in:

• Docker containers (RUN conda activate failures)
• Non-interactive shells in CI/CD
• Jupyter notebook \! commands

Questions for Anthropic Team

1. What's the recommended conda workflow for Claude Code users?
2. Should users rely on the workaround (eval hook && activate) for each command?
3. Are there plans to support conda environments more natively?
4. Would persistent shell sessions (addressing environment variable persistence) help with conda workflows?

Potential Solutions to Consider

1. Documentation update: Add conda workflow best practices
2. Shell configuration: Load conda hooks automatically in Claude Code bash sessions
3. Alternative approaches: Recommend conda run -n env_name command instead of activate
4. Environment detection: Auto-detect and configure inherited conda environments

Impact on Development

This affects many Python developers using:

• Data science workflows with conda environments
• Package management via conda/mamba
• Environment-specific tooling and dependencies
• Cross-platform development (Windows + Docker + SSH scenarios)

Additional Context

This issue is distinct from #2508 (environment variable persistence) but related - solving environment variable persistence might also help conda workflows, but the missing shell functions would still need to be addressed.

Thank you for guidance on the recommended conda workflow\!"