#try asking "... in an environment".
plain mica
Thank for the help, tried that but its telling me to use pip
Here I only have the container-use mcp selected
Happy to file a bug report too!
frail kelp
Yes please!
hazy solstice
@plain mica just double checking ... you ran this?
curl --create-dirs -o .github/copilot-instructions.md https://raw.githubusercontent.com/dagger/container-use/main/rules/agent.md
I never tried vscode myself, @ancient parrot did / wrote those instructions
plain mica
Yeah I did
hazy solstice
@plain mica "do you have any environment specific instructions?"
the easiest way to debug is to actually ask the agent 😛
plain mica
Lmao -- My agent is stuck in a doom loop 😦
hazy solstice
try a new tab
plain mica
Ah good call, its saying it does not.
hazy solstice
once it decided that environments = python envs, it won't backtrack
ionic heron
with cline, which works very similarly to copilot, they have a default mcp enabled called "developer" that does the local dev stuff. I disabled that to make sure it only uses container-use. Not sure if copilot has a similar setup
hazy solstice
never used vscode copilot, just did this and it seems to be picking them up
weird
plain mica
Seems like something is not correct because the docs say to add it to the file we have in our docs too- but when I click on configure instructions it seems to have no configuration.
At least we know what is wrong, ill investigate a bit further
hazy solstice
frail kelp
(guillaume is not available currently)
hazy solstice
@plain mica maybe it's related to how vscode was started
@plain mica I ran it from the terminal, e.g. cd mything; curl thething; code .
maybe instructions work differently when the project is loaded through the UI
Just tried to start vscode from the macOS dock, open mything, and it seems to be working as well
frail kelp
Is your VSCode updated ?
plain mica
yeah I am on the latest version
And also I opened it via CLI
thanks for digging in! I am not sure what is going on but Ill keep investigating on my end too. Possible its a problem over here on my end
Ok I am sorry guys, this was a PEBCAK issue 🙂
I ran this in my home dir, I thought it would apply globally.
curl --create-dirs -o .github/copilot-instructions.md https://raw.githubusercontent.com/dagger/container-use/main/rules/agent.md
Running it in the actual project works, but now I am running into a new issue
failed to open environment: failed intializing worktree: git command failed (exit code 1): exit status 1
Output: error: src refspec main does not match any
error: failed to push some refs to '/Users/levlaz/.config/container-use/repos/demo'
Ah, so looks like you need at least one commit.
This feels like a bit of a foot gun to me.
The usage instructions for starting a brand new project should include all these steps IMO
mkdir project, git init, curl $instructions, git commit -m 'init commit'
Unless this is something specific to vscode handling things?
frail kelp
Fair point, i'll send a patch to make it work without a commit
if you can open an issue to keep track so that i dont forget
plain mica
Will do!