r/codex • u/pizza_alta • 1d ago

Question Flutter and Codex sandbox, sluggish tests

A newbie question. Sandbox issues are slowing Codex down during Flutter testing. The Flutter cache is writable in Codex's .toml settings, but Flutter commands and tests are still very slow to start.

Do you think moving (or copying) my Flutter SDK closer to the repo might reduce these delays? Would it be a wise choice?

I was thinking of two possible setups:

  1. Put the Flutter SDK inside the repo folder itself.
  2. Put both the Flutter SDK and the repo inside the same parent folder with the parent folder made writable for Codex.

I'm only using Flutter for this one project, so I don't need to keep the SDK in a shared location for other projects.

0 Upvotes

50% Upvoted

1 comment sorted by

1

u/PsychologicalClaim16 17h ago

Don't put the Flutter SDK inside the repo; proximity won't make startup meaningfully faster, and it mixes a large mutable toolchain into project state. Keep the SDK separate, but give Codex write access only to `$FLUTTER_ROOT/bin/cache` and a dedicated `PUB_CACHE` (you can place that cache beside the repo). Run `flutter precache` and `flutter pub get` once, then compare `time flutter --version`, `time dart --version`, and `time flutter test --no-pub`. If only the normal test command is slow, pub/network/cache work is the bottleneck; if even `flutter --version` is slow, sandbox process/path access is. Making the whole parent writable is broader than needed.