Posit Assistant bash shell environment variable inheritance #13610
|
Not sure if this is a bug or intended behavior, but I've noticed that when Posit Assistant launches a bash shell, it does not inherit user or workspace environment variables configured in Positron's settings. My team relies heavily on environment variables to configure code behavior and target deployment environments. This creates a meaningful discrepancy between the data scientist's environment and the AI agent's environment, which limits how effectively we can use Posit Assistant for real workflows. If I'm not mistaken, Positron Assistant did not have this limitation. Is this a known issue, or is there a recommended workaround? |
Replies: 1 comment
|
Yes, this is a known issue. Posit Assistant runs bash directly, whereas Positron Assistant runs bash commands in the Terminal tab. The Terminal tab is wired up to all of the environment variable settings (see the Show Environment Contributions command), but plain bash isn't. We'll make sure this has the attention of the Assistant team. In the meantime, you'd probably need to set things in a place in a plain old |
Yes, this is a known issue. Posit Assistant runs bash directly, whereas Positron Assistant runs bash commands in the Terminal tab. The Terminal tab is wired up to all of the environment variable settings (see the Show Environment Contributions command), but plain bash isn't.
We'll make sure this has the attention of the Assistant team. In the meantime, you'd probably need to set things in a place in a plain old
.bashrcto make them visible to Assistant.