Add known ACP server paths to `$PATH` automatically?

[cmarmo]

Description

I would like to configure a opencode client with some custom parameters so it can be used with jupyter-ai. Everything works fine as far as I am managing my local linux (Ubuntu) installation:

• installing opencode with curl (as user, not systemwide)
• editing .config/opencode/opencode.json
• creating and activating a mamba env
• installing jupyterlab and jupyter-ai via conda-forge

Launching jupyter lab I'm able to run opencode via terminal or in the chat.
🥳
Note that, locally, installing and configuring opencode after jupyter-ai doesn't change anything: I am still able to run the chat as expected.

I tried to containerize all that without success using either quay.io/jupyter/minimal-notebook or mambaorg/micromamba:latest : nothing worked... I have re-ordered the installs and the copy of the configuration files in any possible combination (out of desperation) and I always have:

[PersonaManagerExtension]  - AI persona from entry point 'opencode-acp' has unmet requirements: This persona requires `opencode` to be installed. See https://opencode.ai for installation instructions.

I know opencode is installed as I am able to launch it with the right configuration, from the jupyter lab terminal.

Reproduce

1. Clone https://github.com/cmarmo/minimal-undetect-persona/
2. Build the image with docker build . -t <your image name>
3. Run the image with docker run -it --rm -p 8888:8888 <your image name>
4. Connect to the jupyter lab interface
5. Open a chat : no opencode persona is detected and the log says :

AI persona from entry point 'opencode-acp' has unmet requirements: This persona requires `opencode` to be installed. See https://opencode.ai for installation instructions.

6. Open a terminal and run opencode : the agent is there

Expected behavior

Opencode agent is usable both via terminal and chat.

[dlqqq]

@cmarmo Hey, thanks for opening this issue. I got the image cloned on my Linux machine, and yes, this is a PATH issue as suspected.

The problem is that the opencode installer installs it to ~/.opencode/bin and adds tries appending it to the $PATH in .bashrc :

   # opencode
   export PATH=/home/jovyan/.opencode/bin:$PATH

But your .bashrc exits early if not running interactively:

   # If not running interactively, don't do anything
   case $- in
       *i*) ;;
         *) return;;
   esac

The fix is to just add this to the Dockerfile itself:

ENV PATH=/home/jovyan/.opencode/bin:$PATH

It's worth considering whether Jupyter AI should search under ~/.opencode/bin to find the opencode executable. But this may be a security concern as now we're running binaries outside the user/system-specified $PATH, running some binary under $HOME that someone else could have maliciously added... would really want an opinion from someone else on this.

[cmarmo]

Thank you @dlqqq ! This saved my day! 🚀

[dlqqq]

@cmarmo Just a heads up , there may be a pretty serious bug where files open can be lost in rare instances in the current latest version. Please please back up your files regularly. Sorry about this, this will be fixed as soon as possible. See #1642.