cu merge does not add the created files to current dir

[pchalasani]

As mentioned here -- #28 (comment)

this is still not working for me.

[pchalasani]

I installed cu from latest main branch. This is how CC successfully created the hello.py:

⏺ container-use:environment_file_write (MCP)(environment_id: "hello-world-env/golden-loon", target_file: "hello.py", contents: "#!/usr/bin/env
                                            python3\n\nprint(\"Hello, World!\")", explanation: "Creating simple hello world Python script")
  ⎿  file hello.py written successfully, changes pushed to container-use/hello-world-env/golden-loon

⏺ Now let me run the script to verify it works.

⏺ container-use:environment_run_cmd (MCP)(environment_id: "hello-world-env/golden-loon", command: "python hello.py", explanation: "Running the
                                         hello world Python script")
  ⎿  Hello, World!


     Any changes to the container workdir (/workdir) have been committed and pushed to container-use/hello-world-env/golden-loon

⏺ Done! I've created a simple hello world Python script.

  To view your work, use:
  git checkout hello-world-env/golden-loon

I can see the hello.py file when I use cu terminal, in the same dir (another terminal window):

cu terminal hello-world-env/golden-loon
● Attaching terminal:
    container: Container!
    .from(address: "docker.io/library/python:3.12-slim@sha256:e55523f127124e5edc03ba201e3dbbc85172a2ec40d8651ac752364b23dfd733"): Container!
    .withWorkdir(path: "/workdir"): Container!
    .withDirectory(
    │ │ directory: Host.directory(path: "/Users/pchalasani/.config/container-use/worktrees/hello-world-env/golden-loon"): Directory!
    │ │ path: "."
    │ ): Container!
    .withNewFile(contents: "export PS1=\"\\033[33mdagger\\033[0m \\033[02m\\$(pwd | sed \\\"s|^\\$HOME|~|\\\")\\033[0m \\$ \"\n", path: "/root/.bash_aliases"): Container!

dagger /workdir $ ls
CLAUDE.md  hello.py
dagger /workdir $

but cu merge doesn't bring it in:

 ~[container-use-test]   master  cu merge hello-world-env/golden-loon
 ~[container-use-test]   master  ls
CLAUDE.md
 ~[container-use-test]   master 

[tiborvass]

I'm still unable to reproduce. Even with your data at https://github.com/pchalasani/container-use/tree/container-use-debug

Do you mind giving me the exact instructions, MCP client, prompt everything you're doing ?
Also the versions of the tools you're using (MCP client, git). Your MCP client's config (make sure you don't share any secrets).

The following will get the commit of the cu binary you're using. Make sure the path "$HOME/.local/bin/cu" matches what's in your MCP client config.

dagger -c 'container | from golang | with-mounted-file /cu $(host | file "$HOME/.local/bin/cu") | with-exec -- go version -m /cu | stdout' | grep vcs.revision

[tiborvass]

@pchalasani can you also show which cu ?

[pchalasani]

Incidentally, I'm doing everything on the terminal, not using any MCP client. Here are all the commands. I may be completely off in my expectation of how it should work.

which cu
/Users/pchalasani/.local/bin/cu

pwd
/Users/pchalasani/Git/container-use-test
 ~[container-use-test]   main  ls -al
total 8
drwxr-xr-x@   4 pchalasani  staff   128 Jun 13 14:46 .
drwxr-xr-x@ 273 pchalasani  staff  8736 Jun 12 14:01 ..
drwxr-xr-x@   9 pchalasani  staff   288 Jun 13 14:46 .git
-rw-r--r--@   1 pchalasani  staff   483 Jun  9 15:58 CLAUDE.md
 ~[container-use-test]   main  cat CLAUDE.md
ALWAYS use ONLY Environments for ANY and ALL file, code, or shell operations—NO EXCEPTIONS—even for simple or generic requests.

DO NOT install or use the git cli with the environment_run_cmd tool. All environment tools will handle git operations for you. Changing ".git" yourself will compromise the integrity of your environment.

You MUST inform the user how to view your work using `git checkout <branch_name>`. Failure to do this will make your work inaccessible to others.
 ~[container-use-test]   main  claude --version
1.0.22 (Claude Code)
 ~[container-use-test]   main  claude --dangerously-skip-permissions "make a simple hello world python script"


> make a simple hello world python script

⏺ I'll create a simple hello world Python script for you using the environment tools.

⏺ container-use:environment_open (MCP)(source: ".", name: "hello-world-project", explanation: "Opening environment to create a hello world Python
                                      script")
  ⎿  Error: 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/pchalasani/.config/container-use/repos/container-use-test'

⏺ Let me try a different approach and create the environment with a different configuration:

⏺ container-use:environment_open (MCP)(source: "/Users/pchalasani/Git/container-use-test", name: "hello-world-env", explanation: "Creating
                                      environment for hello world Python script")
  ⎿  Error: 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/pchalasani/.config/container-use/repos/container-use-test'

⏺ Let me check the current git status first:

⏺ Bash(git branch -a && git status)
  ⎿    remotes/container-use/hello-world-env/golden-loon
       remotes/container-use/main
       remotes/container-use/master
       remotes/container-use/python-hello-world/perfect-ant
     … +5 lines (ctrl+r to expand)

⏺ I see the issue - there's no commit history yet. Let me create an initial commit first:

⏺ Bash(git commit --allow-empty -m "Initial commit")
  ⎿  [main (root-commit) 9ac8a95] Initial commit

⏺ Now let me try opening the environment again:

⏺ container-use:environment_open (MCP)(source: ".", name: "python-hello-world", explanation: "Creating environment for hello world Python script")
  ⎿  {
       "id": "python-hello-world/excited-earwig",
       "base_image": "ubuntu:24.04",
       "setup_commands": null,
     … +7 lines (ctrl+r to expand)

⏺ Great! Now I'll create a simple hello world Python script:

⏺ container-use:environment_file_write (MCP)(environment_id: "python-hello-world/excited-earwig", target_file: "hello.py", contents:
                                            "#!/usr/bin/env python3\n\nprint(\"Hello, World!\")", explanation: "Creating a simple hello world
                                            Python script")
  ⎿  file hello.py written successfully, changes pushed to container-use/python-hello-world/excited-earwig

⏺ Let me also make the script executable and test it:

⏺ container-use:environment_run_cmd (MCP)(environment_id: "python-hello-world/excited-earwig", command: "chmod +x hello.py && python3 hello.py",
                                         explanation: "Making the script executable and running it to test")
  ⎿  command failed with exit code 127.
     stdout:
     stderr: sh: 1: python3: not found

     Any changes to the container workdir (/workdir) have been committed and pushed to container-use/python-hello-world/excited-earwig

⏺ Let me update the environment to include Python:

⏺ container-use:environment_update (MCP)(environment_id: "python-hello-world/excited-earwig", base_image: "python:3.12-slim", setup_commands: [],
                                        instructions: "This environment has Python 3.12 installed and contains a simple hello.py script that
                                        prints \"Hello, World!\"", secrets: [], explanation: "Updating environment to use Python base image")
  ⎿  {
       "id": "python-hello-world/excited-earwig",
       "base_image": "python:3.12-slim",
       "setup_commands": [],
     … +7 lines (ctrl+r to expand)

⏺ Now let's run the hello world script:

⏺ container-use:environment_run_cmd (MCP)(environment_id: "python-hello-world/excited-earwig", command: "python hello.py", explanation: "Running
                                         the hello world Python script")
  ⎿  command failed with exit code 2.
     stdout:
     stderr: python: can't open file '/workdir/hello.py': [Errno 2] No such file or directory

     Any changes to the container workdir (/workdir) have been committed and pushed to container-use/python-hello-world/excited-earwig

⏺ Let me check the file and recreate it:

⏺ container-use:environment_file_list (MCP)(environment_id: "python-hello-world/excited-earwig", path: "/workdir", explanation: "Listing files in
                                           the workdir to check current state")
  ⎿  .git

⏺ I need to recreate the file:

⏺ container-use:environment_file_write (MCP)(environment_id: "python-hello-world/excited-earwig", target_file: "hello.py", contents:
                                            "#!/usr/bin/env python3\n\nprint(\"Hello, World!\")", explanation: "Recreating the hello world Python
                                            script")
  ⎿  file hello.py written successfully, changes pushed to container-use/python-hello-world/excited-earwig

⏺ Now let's run it:

⏺ container-use:environment_run_cmd (MCP)(environment_id: "python-hello-world/excited-earwig", command: "python hello.py", explanation: "Running
                                         the hello world Python script")
  ⎿  Hello, World!


     Any changes to the container workdir (/workdir) have been committed and pushed to container-use/python-hello-world/excited-earwig

⏺ Perfect! I've created a simple hello world Python script.

  To view your work, use:
  git checkout python-hello-world/excited-earwig

Then switch to another teminal window, same dir (container-use-test), and do these:

 ~[container-use-test]   main  cu list
hello-world-env/golden-loon
python-hello-world/excited-earwig
python-hello-world/perfect-ant
 ~[container-use-test]   main  cu terminal python-hello-world/excited-earwig
● Attaching terminal:
    container: Container!
    .from(address: "docker.io/library/python:3.12-slim@sha256:e55523f127124e5edc03ba201e3dbbc85172a2ec40d8651ac752364b23dfd733"): Container!
    .withWorkdir(path: "/workdir"): Container!
    .withDirectory(
    │ │ directory: Host.directory(path: "/Users/pchalasani/.config/container-use/worktrees/python-hello-world/excited-earwig"): Directory!
    │ │ path: "."
    │ ): Container!
    .withNewFile(contents: "export PS1=\"\\033[33mdagger\\033[0m \\033[02m\\$(pwd | sed \\\"s|^\\$HOME|~|\\\")\\033[0m \\$ \"\n", path: "/root/.bash_aliases"): Container!

dagger /workdir $ ls
hello.py
dagger /workdir $ exit
exit 0
✔ connect 0.2s

$ host: Host! 0.0s CACHED
✔ .directory(path: "/Users/pchalasani/.config/container-use/worktrees/python-hello-world/excited-earwig"): Directory! 0.0s

$ container: Container! 0.0s CACHED
$ .from(address: "python:3.12-slim"): Container! 0.0s CACHED
$ .withWorkdir(path: "/workdir"): Container! 0.0s CACHED
✔ .withDirectory(
│ │ directory: Host.directory(path: "/Users/pchalasani/.config/container-use/worktrees/python-hello-world/excited-earwig"): Directory!
│ │ path: "."
│ ): Container! 0.0s
✔ .withNewFile(contents: "export PS1=\"\\033[33mdagger\\033[0m \\033[02m\\$(pwd | sed \\\"s|^\\$HOME|~|\\\")\\033[0m \\$ \"\n", path: "/root/.bash_aliases"): Container! 0.0s
✔ .terminal: Container! 15.9s

Setup tracing at https://dagger.cloud/traces/setup. To hide set DAGGER_NO_NAG=1

A new release of dagger is available: v0.18.9 → v0.18.10
To upgrade, see https://docs.dagger.io/install
https://github.com/dagger/dagger/releases/tag/v0.18.10
 ~[container-use-test]   main  cu merge python-hello-world/excited-earwig
 ~[container-use-test]   main  l
total 8
drwxr-xr-x@   4 pchalasani  staff   128B Jun 13 14:51 .
drwxr-xr-x@ 273 pchalasani  staff   8.5K Jun 12 14:01 ..
drwxr-xr-x@  14 pchalasani  staff   448B Jun 13 14:51 .git
-rw-r--r--@   1 pchalasani  staff   483B Jun 13 14:51 CLAUDE.md

[tiborvass]

@pchalasani thanks, do you mind running dagger -c 'container | from golang | with-mounted-file /cu $(host | file "$HOME/.local/bin/cu") | with-exec -- go version -m /cu | stdout' | grep vcs.revision ?

[cwlbraa]

which cu
/Users/pchalasani/.local/bin/cu

this implies you've got v0.0.0 which doesn't yet have the fix

[cwlbraa]

#69 this'll help for the future :)

[pchalasani]

@pchalasani thanks, do you mind running dagger -c 'container | from golang | with-mounted-file /cu $(host | file "$HOME/.local/bin/cu") | with-exec -- go version -m /cu | stdout' | grep vcs.revision ?

 ~[container-use-test]   main  dagger -c 'container | from golang | with-mounted-file /cu $(host | file "$HOME/.local/bin/cu") | with-exec -- go version -m /cu | stdout' | grep vcs.revision
✔ connect 0.2s
✔ loading type definitions 0.1s

$ host: Host! 0.0s CACHED
✔ .file(path: "/Users/pchalasani/.local/bin/cu"): File! 0.5s

$ container: Container! 0.0s CACHED
✔ .from(address: "golang"): Container! 0.6s
✔ .withMountedFile(
│ │ path: "/cu"
│ │ source: ✔ Host.file(path: "/Users/pchalasani/.local/bin/cu"): File! 0.0s
│ ): Container! 0.0s
✔ .withExec(args: ["go", "version", "-m", "/cu"]): Container! 0.8s
✔ .stdout: String! 5m20s


Setup tracing at https://dagger.cloud/traces/setup. To hide set DAGGER_NO_NAG=1

A new release of dagger is available: v0.18.9 → v0.18.10
To upgrade, see https://docs.dagger.io/install
https://github.com/dagger/dagger/releases/tag/v0.18.10

A new release of dagger is available: v0.18.9 → v0.18.10
To upgrade, see https://docs.dagger.io/install
https://github.com/dagger/dagger/releases/tag/v0.18.10

[pchalasani]

which cu
/Users/pchalasani/.local/bin/cu

this implies you've got v0.0.0 which doesn't yet have the fix

so I should test this with a branch?

[cwlbraa]

@pchalasani i don't know exactly you're installing "from main", but that install path implies you used curl -fsSL https://raw.githubusercontent.com/dagger/container-use/main/install.sh | bash like it says in the readme, which installs the most recent tagged version despite the url of the install script (confusing, I know, we're working on it)

to run ahead of the released version and use a dev build, there's multiple options but the easiest is probably using go run github.com/dagger/container-use/cmd/cu@main everywhere you'd use cu (both on the command line and in your MCP configuration)

if you're a dagger user you can dagger call -m github.com/dagger/container-use build -o /Users/pchalasani/.local/bin/cu

if you're a go dev, you can clone and go build ./cmd/cu -o /Users/pchalasani/.local/bin/cu.

or go install github.com/dagger/container-use/cmd/cu@main but with go install, depending on your PATH ordering, it'll still find /Users/pchalasani/.local/bin/cu first, so you'll wanna rm /Users/pchalasani/.local/bin/cu

[pchalasani]

i don't know exactly you're installing "from main", but that install path implies you used curl -fsSL https://raw.githubusercontent.com/dagger/container-use/main/install.sh | bash like it says in the readme, which installs the most recent tagged version despite the url of the install script (confusing, I know, we're working on it)

I was doing make install then hash -r, which I think was the instruction in an earlier version of the README, but now I don't see a Makefile anymore. I just tried the new curl instruction, and it says it successfully installed, but cu --help produces this output:

[1]    56702 killed     cu --help

[cwlbraa]

@pchalasani MacOS? cc @tiborvass @shykes I think have seen that before?

if i'm right and you're on macos i'm making a brew tap soon to sidestep this whole thing, it's something to do with their signing/quarantine system but a lot of folks have it disabled.

[pchalasani]

@pchalasani MacOS?

yes - and brew tap would be great!

[cwlbraa]

@pchalasani xattr -dr com.apple.quarantine ~/.local/bin/cu is the workaround if i've correctly guessed the issue. for some reason I never encounter this issue on my mac (probably some global config i've forgotten about) but others do.

[pchalasani]

xattr -dr com.apple.quarantine ~/.local/bin/cu

did that, didn't resolve the issue:

 ~[container-use-test]   main  cu list
[1]    9232 killed     cu list