Problem when working with devcontainer

[rulrok]

Version

0.8.1

Platform

Linux (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

ui

What happened, and what did you expect?

When using the MCP server from a VS Code Dev Container, tool calls fail because the agent passes the repository path from inside the container (for example, /workspace/project), while the MCP server runs on the host and expects the corresponding host path (for example, /path/to/project). I expected the MCP server to either resolve the container path automatically, support configurable container-to-host path mappings, or otherwise handle Dev Container environments without requiring the agent to be manually provided with the host repository path.

Reproduction

1. Create a VS Code Dev Container for any local Git repository where the repository is mounted at a different path inside the container than on the host (for example, host: /path/to/project, container: /workspace/project).

2. Start an MCP server on the host machine.

3. From an agent running inside the Dev Container, invoke any codebase-memory-mcp tool that accepts a project/repository path, passing the container workspace path (either explicitly or by allowing the agent to infer its current workspace).

   Example:

   {
     "project": "/workspace/project",
     ...
   }

4. Observe that the MCP server attempts to resolve /workspace/project on the host filesystem and fails because that path only exists inside the container.

Actual result

The MCP tool fails because it receives the container path instead of the corresponding host path.

Expected result

The MCP server should either:

• resolve the container path to the host path automatically,
• support configurable container-to-host path mappings,
• or clearly indicate that a host filesystem path is required when running from a Dev Container.

Workaround

If the agent is explicitly provided with the host repository path (for example, /path/to/project) instead of the container path, the same MCP tool call succeeds.

Logs

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

No response

Confirmations

• I searched existing issues and this is not a duplicate.
• My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

[DeusData]

Thanks for the Dev Container report. Triage: editor/container integration and path-mapping UX.

The host/server path versus container/workspace path split is real, but we need to be careful not to guess mappings incorrectly. A useful design would likely be explicit container-to-host path mapping in config or client setup docs, with clear errors when a path only exists inside the container.