About the working directory and memory directory

[padixa]

I found few issues when I use VSCode connect to it and try to coding.

1. Current working directory, it will show the current directory is : /app, which is in the docker. not current real one.

The /app directory is read-only. Let me ask the user where they want to create the project directory.

2. It will show some messages like:

The memory directory doesn't exist. Let me try to write to the memory file directly - the system said the directory already exists. Let me check if there's another path.

Actually, the error says ENOTSUP: operation not supported on socket - this means the /home/claude path doesn't exist or isn't accessible. Let me just skip the memory write and inform the user.

[rynfar]

I havnt used this through vscode yet. I'll need to research this and figure out how to handle that. Let me see what I can find!

[padixa]

It always misunderstand the current working directory. Actually I don't have '/app' folder in current folder

[rynfar]

Since you're using OpenCode in VSCode, the proxy should be picking up the working directory from the system prompt — OpenCode embeds it in an <env> block that the proxy parses. The fact that it's falling through to /app (the Docker container's internal path) means that extraction is failing, but we need to see what's actually being sent to know why.

Could you help us narrow this down?

1. Start the proxy with CLAUDE_PROXY_DEBUG=1 and share the log output for one request. We're looking for whether hasSystemPrompt shows true or false.

2. What version of OpenCode are you running, and which VSCode extension? (e.g., the OpenCode VSCode extension, or OpenCode CLI connected through a terminal inside VSCode?)

As a workaround until we sort this out, you can set CLAUDE_PROXY_WORKDIR to a path inside the container that's volume-mounted to your project:

docker run \
  -v ~/.claude:/home/claude/.claude \
  -v /path/to/your/project:/workspace \
  -e CLAUDE_PROXY_WORKDIR=/workspace \
  -p 3456:3456 meridian

That should fix both the working directory and the memory directory errors. But we'd still like to understand why the automatic extraction isn't working for your setup so we can fix it properly.

[padixa]

I'm using Claude code extension for VSCode, newest version.
I don't think that's a good idea, I have multiple projects, we can't use a fixed workspace path when deploy to docker in other machine.

[padixa]

seems like the issue is not related to vscode, when open Claude CLI then ask to execute git commit, it will also output:

The /app directory is read-only. Let me ask the user where they want to create the project directory.

[rynfar]

Let me explore this some more.