Replies: 2 comments
-
|
this looks closest to #21509 and #23907. Both are tracking the same Desktop/Mac app workflow you're asking about: macOS as the UI, a Linux SSH host as the real workspace, and repo files/shell/tests staying remote. #23907 is especially close because it calls out DevBox/remote repos and first-class app UX. I'd add the Rust-specific bits there, especially |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, my take with some summarization help from AI is that my use case as abvoe stipulated is fully enabled, give or take environment variables may require too much configuration, but environment variables are not required for 98% of my dev workflow. If I get to verify this I'll add my comments. The linked tickets seem to suggest requests for more extensional features for wider workflows than what my limited defintion aims at (or specifically they look at DevBox-like based workflows) . |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Can the Codex Application on Mac attach to a linux machine which already contains my Rust repo, Rust toolchain and data, and seamlessly edit and run tests (the kinds of cargo-test / cargo-check that's typically involved in rust development cycles) through that connection as seamlessly as it works when the codebase is local on the Mac?
Beta Was this translation helpful? Give feedback.
All reactions