Using local repos causes nonexistant path access

[viraptor]

I added a repo with a local, absolute path to the system. When running a prompt, the system tries to use that path under the usual workspace:

[dev:backend] 214 |     }
[dev:backend] 215 |
[dev:backend] 216 |     // Bun.spawn should throw this, but it incorrectly reports that the executable does not exist.
[dev:backend] 217 |     // See https://github.com/oven-sh/bun/issues/24012
[dev:backend] 218 |     if (!(await fs.stat(input.cwd).catch(() => undefined))?.isDirectory()) {
[dev:backend] 219 |       throw Object.assign(new Error(`No such file or directory: '${input.cwd}'`), {
[dev:backend]                                 ^
[dev:backend] error: No such file or directory: '/Users/viraptor/src/opencode-manager/workspace/repos/Users/viraptor/src/the_repo'
[dev:backend]  errno: -2,
[dev:backend]   path: "/Users/viraptor/src/opencode-manager/workspace/repos/Users/viraptor/src/the_repo",
[dev:backend]   code: "ENOENT"
[dev:backend]
[dev:backend]       at files (src/file/ripgrep.ts:219:27)
[dev:backend]

But the project doesn't exist there.

I don't actually know if the expectation is to clone the repo in the workspace, or should that interaction use the absolute path instead.

[chriswritescode-dev]

not sure how you got to this point ? is this still a issue? all repos should be contained inside the workspace/repos

[viraptor]

I added a new repo, selected the local option, put in an absolute path to it. That repo was but under workspace, but in a completely different location.

[namanrajpal]

@viraptor
The current "Add Local Repo" feature is designed to create new empty repositories inside the container's workspace, not to access existing repositories at absolute paths.

When you enter an absolute path like /Users/viraptor/src/the_repo, the system treats the entire path as a directory name rather than a path to traverse. It creates /workspace/repos/Users/viraptor/src/the_repo inside the container, which is why you get the "No such file or directory" error.

The feature is meant for creating brand new repos - you enter just a name like my-project, and it:

• Creates /workspace/repos/my-project inside the container
• Initializes it as an empty git repository

@chriswritescode-dev any thoughts on how to handle this ? __"Add exiting workspace repo" ?
We need to implement proper "Import Existing Local Repository" functionality, which would require:

Potential Frontend Changes:

• UI to browse/select local filesystem paths
• Distinguish between "Create New Repo" vs "Import Existing Repo"
• Path validation and permissions handling

Potential Backend Changes:

• Detect if a path already contains a valid git repository
• Support reading repos from arbitrary local paths (within security constraints)
• Handle path resolution across Docker vs local development environments
• Update the repo service to handle existing repos without re-initializing git
• Mounting a local path

This would be a new feature separate from the current "Add Local Repo" functionality.

[viraptor]

I see. But even if this was expected to create a new repo, that didn't happen either. The path was not created inside the workspace resulting in "No such file or directory" so that use case needs some error handling too.

[chriswritescode-dev]

I propose adding a option to specify a absolute path that would git clone the dir to the repos dir. so it would work but would still use a dir inside the workspace/repos. which would duplicate the codebase. I see how this might be used to bring in changes or a local dir on the same machine. I just run this in a docker container on a server in my lab. I use git as the single source of truth or create a local repo from the dialog and copy files. For example I have one for research that has a crawl4ai mcp tool that is just for looking up details or doing research on a topic.