Background Agent setup failing

Working through the background agent setup and have hit a wall with the secrets not being injected. They have been stored inside of the cursor settings as instructed but are not being found when needed and keeps looking for them in in .env which exists in the project directory but not the workspace directory. Does anyone have some insight on this process?

NOTE: The setup process is vastly more complex than the documentation describes, missing out critical steps for python getting the venv correctly installed. As an example feeding cursors own documentation to the agent chat while setting it up helped very little. the chat agent needed to work through various errors until it figured it out. the install command block inside the .json file provided no function. eventually all installs had to be done manually including the virtual environment and node dependencies before requirements files would actually run installs. And even now it’s not certain the setup is working due to the secrets issue that can not be resolved at present.

at this point it is just far too frustrating to set up the background agents.

1 Like

Yes i also am unable to have my secrets in the background agent setup and in the virtual machine

Were you able to figure this out? Currently trying the non-Docker setup after running into some snags with the Docker setup. Env vars were available in the install step for Docker but do not seem to be available for the install step for the non-Docker environment.

Unfortunately not and as a result have switched to using a different tool.

That’s too bad – what did you end up using?

I went back to the Docker setup and was able to get that working. I tried moving the commands that required from the install script to the setup script, but the env variables weren’t loaded at setup time either.

I switched over to windsurf as there were several issues (background agents, inline editing bugs, mounting instability from updates etc) that were consuming too much time and rapidly increasing costs were out-pacing build progress. It took a little time to tune windsurf and i would say both tools have their strengths/weaknesses, I would say I prefer cursor in a solid working state unfortunately my experience with it was rapidly degrading but maybe that could be relational to my own capabilities I’m not sure. Windsurf has been performing well after a few weeks using it and certainly has been more cost effective up-front. Cursor might have arrived at conclusions a bit faster although I would say that came at a higher up-front cost.
Hope this helps.