fix: bind-mount local --target by default to avoid slow file-by-file …

[khangpanarnd]

…import (#725)

A local directory passed via --target was handed to the SDK LocalDir manifest entry, which copies the tree into the sandbox file-by-file at session.start(). On large repositories this stalls for a very long time with no report produced (issue #725).

Default local_code targets to a read-only bind mount (applied at container-create time, effectively instant) instead of the file-by-file copy. An explicit mount: False still forces the copy. Also soften the STRIX_MAX_LOCAL_COPY_MB oversize guard from a hard error to a warning so a large --target reaches the fast path instead of being rejected at parse time.

Preserves --mount, cloned-repository, and explicit-copy behavior. Adds tests/test_fast_local_import.py (incl. a bug-condition regression test) and updates tests/test_local_sources.py for the new default.

[greptile-apps]

Greptile Summary

This PR makes local targets use read-only bind mounts by default. The main changes are:

• Default local-code targets to bind mounts instead of file copies.
• Preserve explicit copy and cloned-repository behavior.
• Replace the oversized-target error with a warning.
• Add tests for mount, copy, and repository source paths.

Confidence Score: 4/5

Oversized explicit copies and remote-Docker targets can still break the changed flow.

• Explicit copies now bypass the size limit and can stall during import.
• Remote Docker daemons cannot reliably resolve paths from the CLI host.
• The local-Docker bind-mount path has focused tests.

strix/interface/main.py and strix/interface/utils.py

Important Files Changed

Filename	Overview
strix/interface/main.py	Changes oversized local-target validation from a hard error to a warning, including for explicit copy targets.
strix/interface/utils.py	Defaults local-code targets to read-only host bind mounts while retaining explicit copy behavior.
tests/test_fast_local_import.py	Adds tests for default mounting, read-only mounts, explicit copies, and repository sources.
tests/test_local_sources.py	Updates source collection tests for the new mount default and explicit copy override.

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
strix/interface/main.py:650-656
**Explicit Copies Bypass Size Guard**

An oversized `local_code` target with `mount: False` still reaches this warning, but `collect_local_sources` preserves that flag and `build_session_entries` creates a file-by-file `LocalDir` copy. The command now proceeds into the same long import that the size guard previously blocked while incorrectly reporting that the target will be bind-mounted.

### Issue 2 of 2
strix/interface/utils.py:1237
**Remote Daemon Cannot See Target**

When Docker uses a remote daemon, this default passes the CLI machine's local path directly as a host bind source. The daemon resolves that path on its own host, so an ordinary `--target` can fail during container creation or expose the wrong directory; the previous `LocalDir` path uploaded the client-side files.

_{Reviews (1): Last reviewed commit: "fix: bind-mount local --target by defaul..." | Re-trigger Greptile}

[greptile-apps]

Explicit Copies Bypass Size Guard

An oversized local_code target with mount: False still reaches this warning, but collect_local_sources preserves that flag and build_session_entries creates a file-by-file LocalDir copy. The command now proceeds into the same long import that the size guard previously blocked while incorrectly reporting that the target will be bind-mounted.

Prompt To Fix With AI

This is a comment left during a code review.
Path: strix/interface/main.py
Line: 650-656

Comment:
**Explicit Copies Bypass Size Guard**

An oversized `local_code` target with `mount: False` still reaches this warning, but `collect_local_sources` preserves that flag and `build_session_entries` creates a file-by-file `LocalDir` copy. The command now proceeds into the same long import that the size guard previously blocked while incorrectly reporting that the target will be bind-mounted.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Remote Daemon Cannot See Target

When Docker uses a remote daemon, this default passes the CLI machine's local path directly as a host bind source. The daemon resolves that path on its own host, so an ordinary --target can fail during container creation or expose the wrong directory; the previous LocalDir path uploaded the client-side files.

Prompt To Fix With AI

This is a comment left during a code review.
Path: strix/interface/utils.py
Line: 1237

Comment:
**Remote Daemon Cannot See Target**

When Docker uses a remote daemon, this default passes the CLI machine's local path directly as a host bind source. The daemon resolves that path on its own host, so an ordinary `--target` can fail during container creation or expose the wrong directory; the previous `LocalDir` path uploaded the client-side files.

How can I resolve this? If you propose a fix, please make it concise.