41 Commits

• [codex] Add environment shell info (#26480)

  ## Why
  
  Shell detection needs to be available through the `Environment`
  abstraction so callers can ask the selected local or remote environment
  for shell metadata without adding a separate HTTP endpoint or parallel
  info-source path. This keeps shell metadata shaped like the existing
  environment-owned filesystem capability and lets remote environments
  answer through exec-server JSON-RPC.
  
  ## What changed
  
  - Added `environment/info` to the exec-server protocol/client/server and
  exposed `Environment::info()`.
  - Added local and remote environment info providers on `Environment`,
  following the existing capability-provider pattern used for filesystem
  access.
  - Moved the shared shell detection logic into `codex-shell-command` and
  kept core shell APIs as wrappers around that implementation.
  - Returned shell metadata as `EnvironmentInfo { shell: ShellInfo }`
  using the existing shell detection path.
  - Added a remote environment test that calls `Environment::info()`
  through an exec-server-backed environment.
  
  ## Validation
  
  - `git diff --check`
  - `just test -p codex-shell-command`
  - `just test -p codex-core -E 'test(/shell::tests::/)'`\n- `just test -p
  codex-exec-server environment`

  pakrym-oai · 2026-06-04 22:36:25 -07:00
  6a6a5f925e
• fix: add shell fallback paths for pwsh/powershell that work on GitHub Actions Windows runners (#16617)

  Recently, I merged a number of PRs to increase startup timeouts for
  scripts that ran under PowerShell, but in the failure for
  `suite::codex_tool::test_shell_command_approval_triggers_elicitation`, I
  found this in the error logs when running on Bazel with BuildBuddy:
  
  ```
  [mcp stderr] 2026-04-02T19:54:10.758951Z ERROR codex_core::tools::router: error=Exit code: 1
  [mcp stderr] Wall time: 0.2 seconds
  [mcp stderr] Output:
  [mcp stderr] 'New-Item' is not recognized as an internal or external command,
  [mcp stderr] operable program or batch file.
  [mcp stderr] 
  ```
  
  This error implies that the command was run under `cmd.exe` instead of
  `pwsh.exe`. Under GitHub Actions, I suspect that the `%PATH%` that is
  passed to our Bazel builder is scrubbed such that our tests cannot find
  PowerShell where GitHub installs it. Having these explicit fallback
  paths should help.
  
  While we could enable these only for tests, I don't see any harm in
  keeping them in production, as well.

  Michael Bolin · 2026-04-02 13:47:10 -07:00
  93380a6fac
• Apply argument comment lint across codex-rs (#14652)

  ## Why
  
  Once the repo-local lint exists, `codex-rs` needs to follow the
  checked-in convention and CI needs to keep it from drifting. This commit
  applies the fallback `/*param*/` style consistently across existing
  positional literal call sites without changing those APIs.
  
  The longer-term preference is still to avoid APIs that require comments
  by choosing clearer parameter types and call shapes. This PR is
  intentionally the mechanical follow-through for the places where the
  existing signatures stay in place.
  
  After rebasing onto newer `main`, the rollout also had to cover newly
  introduced `tui_app_server` call sites. That made it clear the first cut
  of the CI job was too expensive for the common path: it was spending
  almost as much time installing `cargo-dylint` and re-testing the lint
  crate as a representative test job spends running product tests. The CI
  update keeps the full workspace enforcement but trims that extra
  overhead from ordinary `codex-rs` PRs.
  
  ## What changed
  
  - keep a dedicated `argument_comment_lint` job in `rust-ci`
  - mechanically annotate remaining opaque positional literals across
  `codex-rs` with exact `/*param*/` comments, including the rebased
  `tui_app_server` call sites that now fall under the lint
  - keep the checked-in style aligned with the lint policy by using
  `/*param*/` and leaving string and char literals uncommented
  - cache `cargo-dylint`, `dylint-link`, and the relevant Cargo
  registry/git metadata in the lint job
  - split changed-path detection so the lint crate's own `cargo test` step
  runs only when `tools/argument-comment-lint/*` or `rust-ci.yml` changes
  - continue to run the repo wrapper over the `codex-rs` workspace, so
  product-code enforcement is unchanged
  
  Most of the code changes in this commit are intentionally mechanical
  comment rewrites or insertions driven by the lint itself.
  
  ## Verification
  
  - `./tools/argument-comment-lint/run.sh --workspace`
  - `cargo test -p codex-tui-app-server -p codex-tui`
  - parsed `.github/workflows/rust-ci.yml` locally with PyYAML
  
  ---
  
  * -> #14652
  * #14651

  Michael Bolin · 2026-03-16 16:48:15 -07:00
  b77fe8fefe
• fix: move inline codex-rs/core unit tests into sibling files (#14444)

  ## Why
  PR #13783 moved the `codex.rs` unit tests into `codex_tests.rs`. This
  applies the same extraction pattern across the rest of `codex-rs/core`
  so the production modules stay focused on runtime code instead of large
  inline test blocks.
  
  Keeping the tests in sibling files also makes follow-up edits easier to
  review because product changes no longer have to share a file with
  hundreds or thousands of lines of test scaffolding.
  
  ## What changed
  - replaced each inline `mod tests { ... }` in `codex-rs/core/src/**`
  with a path-based module declaration
  - moved each extracted unit test module into a sibling `*_tests.rs`
  file, using `mod_tests.rs` for `mod.rs` modules
  - preserved the existing `cfg(...)` guards and module-local structure so
  the refactor remains structural rather than behavioral
  
  ## Testing
  - `cargo test -p codex-core --lib` (`1653 passed; 0 failed; 5 ignored`)
  - `just fix -p codex-core`
  - `cargo fmt --check`
  - `cargo shear`

  Michael Bolin · 2026-03-12 08:16:36 -07:00
  0c8a36676a
• Fix Linux tmux segfault in user shell lookup (#13900)

  Replace the Unix shell lookup path in `codex-rs/core/src/shell.rs` to
  use
  `libc::getpwuid_r()` instead of `libc::getpwuid()` when resolving the
  current
  user's shell.
  
  Why:
  - `getpwuid()` can return pointers into libc-managed shared storage
  - on the musl static Linux build, concurrent callers can race on that
  storage
  - this matches the crash pattern reported in tmux/Linux sessions with
  parallel
    shell activity
  
  Refs:
  - Fixes #13842

  Eric Traut · 2026-03-11 12:33:07 -07:00
  026cfde023
• Make shell detection tests

  robust to Nix shell paths (#12476)
  
  ## Summary
  - Updated `codex-rs/core/src/shell.rs` tests for shell detection to stop
  asserting hardcoded shell paths.
  - `detects_bash` and `detects_sh` now assert executable basenames
  (`bash`, `sh`) rather than `/bin/*`/`/usr/bin/*` absolute paths.
  - This keeps behavior the same while avoiding failures in Nix
  environments where shells are resolved from `/nix/store/.../bin`.
  
  ## Testing
  - `nix develop .#default --command sh -lc 'export
  PKG_CONFIG_PATH=/nix/store/6az1q591wwlgazzskngr6rl7gmhpyvnc-libcap-2.77-dev/lib/pkgconfig:/nix/store/fgm3pz8486ksh3f94629lpb7xjr2wjp7-openssl-3.6.0-dev/lib/pkgconfig:$PKG_CONFIG_PATH;
  export PKG_CONFIG_PATH_FOR_TARGET=$PKG_CONFIG_PATH; cd
  /home/alex/workspace/openai/codex/codex-rs && cargo test -p codex-core
  --lib detects_bash && cargo test -p codex-core --lib detects_sh'`
  
  ## Why
  The two failing tests previously hardcoded fixed paths and failed under
  the Nix shell due to Nix-provided shell binary locations.
  
  ## Links
  - Bug report / enhancement request: not publicly filed yet; this was
  reproduced in the local Nix environment.

  Alex Kwiatkowski · 2026-02-21 20:08:02 -08:00
  1dad0a7f4a
• chore: rename codex-command to codex-shell-command (#11378)

  This addresses some post-merge feedback on
  https://github.com/openai/codex/pull/11361:
  
  - crate rename
  - reuse `detect_shell_type()` utility

  Michael Bolin · 2026-02-10 17:03:46 -08:00
  d44f4205fb
• fix: make sure the shell exists (#10222)
  jif-oai · 2026-01-30 14:18:31 +01:00
  09d25e91e9
• feat: async shell snapshot (#9600)
  jif-oai · 2026-01-21 10:41:13 +00:00
  b75024c465
• chore: upgrade to Rust 1.92.0 (#8860)

  **Summary**
  - Upgrade Rust toolchain used by CI to 1.92.0.
  - Address new clippy `derivable_impls` warnings by deriving `Default`
  for enums across protocol, core, backend openapi models, and
  windows-sandbox setup.
  - Tidy up related test/config behavior (originator header handling, env
  override cleanup) and remove a now-unused assignment in TUI/TUI2 render
  layout.
  
  **Testing**
  - `just fmt`
  - `just fix -p codex-tui`
  - `just fix -p codex-tui2`
  - `just fix -p codex-windows-sandbox`
  - `cargo test -p codex-tui`
  - `cargo test -p codex-tui2`
  - `cargo test -p codex-windows-sandbox`
  - `cargo test -p codex-core --test all`
  - `cargo test -p codex-app-server --test all`
  - `cargo test -p codex-mcp-server --test all`
  - `cargo test --all-features`

  viyatb-oai · 2026-01-16 11:12:52 -08:00
  f89a40a849
• feat: add shell snapshot for shell command (#7786)
  jif-oai · 2025-12-11 13:46:43 +00:00
  29381ba5c2
• feat: shell snapshotting (#7641)
  jif-oai · 2025-12-09 18:36:58 +00:00
  7836aeddae
• feat(core) Add login to shell_command tool (#6846)

  ## Summary
  Adds the `login` parameter to the `shell_command` tool - optional,
  defaults to true.
  
  ## Testing
  - [x] Tested locally

  Dylan Hurd · 2025-12-05 11:03:25 -08:00
  a8cbbdbc6e
• core: make shell behavior portable on FreeBSD (#7039)

  - Use /bin/sh instead of /bin/bash on FreeBSD/OpenBSD in the process
  group timeout test to avoid command-not-found failures.
  
  - Accept /usr/local/bin/bash as a valid SHELL path to match common
  FreeBSD installations.
  
  - Switch the shell serialization duration test to /bin/sh for improved
  portability across Unix platforms.
  
  With this change, `cargo test -p codex-core --lib` runs and passes on
  FreeBSD.

  Xiao-Yong Jin · 2025-11-20 16:01:35 -08:00
  0fbcdd77c8
• Always fallback to real shell (#6953)

  Either cmd.exe or `/bin/sh`.

  pakrym-oai · 2025-11-20 10:58:46 -08:00
  30ca89424c
• fix(shell) fallback shells (#6948)

  ## Summary
  Add fallbacks when user_shell_path does not resolve to a known shell
  type
  
  ## Testing
  - [x] Tests still pass

  Dylan Hurd · 2025-11-19 16:41:38 -08:00
  b00a7cf40d
• fix(windows) shell_command on windows, minor parsing (#6811)

  ## Summary
  Enables shell_command for windows users, and starts adding some basic
  command parsing here, to at least remove powershell prefixes. We'll
  follow this up with command parsing but I wanted to land this change
  separately with some basic UX.
  
  **NOTE**: This implementation parses bash and powershell on both
  platforms. In theory this is possible, since you can use git bash on
  windows or powershell on linux. In practice, this may not be worth the
  complexity of supporting, so I don't feel strongly about the current
  approach vs. platform-specific branching.
  
  ## Testing
  - [x] Added a bunch of tests 
  - [x] Ran on both windows and os x

  Dylan Hurd · 2025-11-17 22:23:53 -08:00
  28ebe1c97a
• Revert "Revert "Overhaul shell detection and centralize command generation for unified exec"" (#6607)

  Reverts openai/codex#6606

  pakrym-oai · 2025-11-13 16:45:17 -08:00
  7b027e7536
• Revert "Overhaul shell detection and centralize command generation for unified exec" (#6606)

  Reverts openai/codex#6577

  pakrym-oai · 2025-11-13 08:43:00 -08:00
  e6995174c1
• Overhaul shell detection and centralize command generation for unified exec (#6577)

  This fixes command display for unified exec. All `cd`s and `ls`es are
  now parsed.
  
  <img width="452" height="237" alt="image"
  src="https://github.com/user-attachments/assets/ce92d81f-f74c-485a-9b34-1eaa29290ec6"
  />
  
  Deletes a ton of tests that were doing nothing from shell.rs.
  
  ---------
  
  Co-authored-by: Pavel Krymets <pavel@krymets.com>

  pakrym-oai · 2025-11-13 08:28:09 -08:00
  d28e912214
• feat: shell_command tool (#6510)

  This adds support for a new variant of the shell tool behind a flag. To
  test, run `codex` with `--enable shell_command_tool`, which will
  register the tool with Codex under the name `shell_command` that accepts
  the following shape:
  
  ```python
  {
    command: str
    workdir: str | None,
    timeout_ms: int | None,
    with_escalated_permissions: bool | None,
    justification: str | None,
  }
  ```
  
  This is comparable to the existing tool registered under
  `shell`/`container.exec`. The primary difference is that it accepts
  `command` as a `str` instead of a `str[]`. The `shell_command` tool
  executes by running `execvp(["bash", "-lc", command])`, though the exact
  arguments to `execvp(3)` depend on the user's default shell.
  
  The hypothesis is that this will simplify things for the model. For
  example, on Windows, instead of generating:
  
  ```json
  {"command": ["pwsh.exe", "-NoLogo", "-Command", "ls -Name"]}
  ```
  
  The model could simply generate:
  
  ```json
  {"command": "ls -Name"}
  ```
  
  As part of this change, I extracted some logic out of `user_shell.rs` as
  `Shell::derive_exec_args()` so that it can be reused in
  `codex-rs/core/src/tools/handlers/shell.rs`. Note the original code
  generated exec arg lists like:
  
  ```javascript
  ["bash", "-lc", command]
  ["zsh", "-lc", command]
  ["pwsh.exe", "-NoProfile", "-Command", command]
  ```
  
  Using `-l` for Bash and Zsh, but then specifying `-NoProfile` for
  PowerShell seemed inconsistent to me, so I changed this in the new
  implementation while also adding a `use_login_shell: bool` option to
  make this explicit. If we decide to add a `login: bool` to
  `ShellCommandToolCallParams` like we have for unified exec:
  
  
  https://github.com/openai/codex/blob/807e2c27f0a9f2e85c50e7e6df5533f0d9b853c7/codex-rs/core/src/tools/handlers/unified_exec.rs#L33-L34
  
  Then this should make it straightforward to support.

  Michael Bolin · 2025-11-12 08:18:57 -08:00
  29364f3a9b
• Fix bash detection failure in VS Code Codex extension on Windows under certain conditions (#3421)

  Found that the VS Code Codex extension throws “Error starting
  conversation” when initializing a conversation with Git for Windows’
  bash on PATH.
  Debugging showed the bash-detection logic did not return as expected;
  this change makes it reliable in that scenario.
  Possibly related to issue #2841.

  Axojhf · 2025-10-28 21:29:16 -07:00
  802d2440b4
• chore: drop useless shell stuff (#5848)
  jif-oai · 2025-10-28 14:52:52 +00:00
  be4bdfec93
• chore: rework tools execution workflow (#5278)

  Re-work the tool execution flow. Read `orchestrator.rs` to understand
  the structure

  jif-oai · 2025-10-20 20:57:37 +01:00
  5e4f3bbb0b
• chore: clippy on redundant closure (#4058)

  Add redundant closure clippy rules and let Codex fix it by minimising
  FQP

  jif-oai · 2025-09-22 19:30:16 +00:00
  be366a31ab
• fix: ensure cwd for conversation and sandbox are separate concerns (#3874)

  Previous to this PR, both of these functions take a single `cwd`:
  
  
  https://github.com/openai/codex/blob/71038381aa0f51aa62e1a2bcc7cbf26a05b141f3/codex-rs/core/src/seatbelt.rs#L19-L25
  
  
  https://github.com/openai/codex/blob/71038381aa0f51aa62e1a2bcc7cbf26a05b141f3/codex-rs/core/src/landlock.rs#L16-L23
  
  whereas `cwd` and `sandbox_cwd` should be set independently (fixed in
  this PR).
  
  Added `sandbox_distinguishes_command_and_policy_cwds()` to
  `codex-rs/exec/tests/suite/sandbox.rs` to verify this.

  Michael Bolin · 2025-09-18 14:37:06 -07:00
  8595237505
• fix: some nit Rust reference issues (#3849)

  Fix some small references issue. No behavioural change. Just making the
  code cleaner

  jif-oai · 2025-09-18 18:18:06 +01:00
  992b531180
• fix: Record EnvironmentContext in SendUserTurn (#3678)

  ## Summary
  SendUserTurn has not been correctly handling updates to policies. While
  the tui protocol handles this in `Op::OverrideTurnContext`, the
  SendUserTurn should be appending `EnvironmentContext` messages when the
  sandbox settings change. MCP client behavior should match the cli
  behavior, so we update `SendUserTurn` message to match.
  
  ## Testing
  - [x] Added prompt caching tests

  Dylan · 2025-09-16 11:32:20 -07:00
  11285655c4
• chore: enable clippy::redundant_clone (#3489)

  Created this PR by:
  
  - adding `redundant_clone` to `[workspace.lints.clippy]` in
  `cargo-rs/Cargol.toml`
  - running `cargo clippy --tests --fix`
  - running `just fmt`
  
  Though I had to clean up one instance of the following that resulted:
  
  ```rust
  let codex = codex;
  ```

  Michael Bolin · 2025-09-11 11:59:37 -07:00
  bec51f6c05
• Back out "feat: POSIX unification and snapshot sessions (#3179)" (#3430)

  This reverts https://github.com/openai/codex/pull/3179.
  
  #3179 appears to introduce a regression where sourcing dotfiles causes a
  bunch of activity in the title bar (and potentially slows things down?)
  
  
  https://github.com/user-attachments/assets/a68f7fb3-0749-4e0e-a321-2aa6993e01da
  
  Verified this no longer happens after backing out #3179.
  
  Original commit changeset: 62bd0e3d9d

  Michael Bolin · 2025-09-10 12:40:24 -07:00
  51d9e05de7
• feat: POSIX unification and snapshot sessions (#3179)

  ## Session snapshot
  For POSIX shell, the goal is to take a snapshot of the interactive shell
  environment, store it in a session file located in `.codex/` and only
  source this file for every command that is run.
  As a result, if a snapshot files exist, `bash -lc <CALL>` get replaced
  by `bash -c <CALL>`.
  
  This also fixes the issue that `bash -lc` does not source `.bashrc`,
  resulting in missing env variables and aliases in the codex session.
  ## POSIX unification
  Unify `bash` and `zsh` shell into a POSIX shell. The rational is that
  the tool will not use any `zsh` specific capabilities.
  
  ---------
  
  Co-authored-by: Michael Bolin <mbolin@openai.com>

  jif-oai · 2025-09-08 18:09:45 -07:00
  62bd0e3d9d
• ZSH on UNIX system and better detection (#3187)
  jif-oai · 2025-09-05 09:51:01 -07:00
  ba631e7928
• Bridge command generation to powershell when on Windows (#2319)

  ## What? Why? How?
  - When running on Windows, codex often tries to invoke bash commands,
  which commonly fail (unless WSL is installed)
  - Fix: Detect if powershell is available and, if so, route commands to
  it
  - Also add a shell_name property to environmental context for codex to
  default to powershell commands when running in that environment
  
  ## Testing
  - Tested within WSL and powershell (e.g. get top 5 largest files within
  a folder and validated that commands generated were powershell commands)
  - Tested within Zsh
  - Updated unit tests
  
  ---------
  
  Co-authored-by: Eddy Escardo <eddy@openai.com>

  eddy-win · 2025-08-20 16:30:34 -07:00
  050b9baeb6
• chore: upgrade to Rust 1.89 (#2465)

  Codex created this PR from the following prompt:
  
  > upgrade this entire repo to Rust 1.89. Note that this requires
  updating codex-rs/rust-toolchain.toml as well as the workflows in
  .github/. Make sure that things are "clippy clean" as this change will
  likely uncover new Clippy errors. `just fmt` and `cargo clippy --tests`
  are sufficient to check for correctness
  
  Note this modifies a lot of lines because it folds nested `if`
  statements using `&&`.
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/2465).
  * #2467
  * __->__ #2465

  Michael Bolin · 2025-08-19 13:22:02 -07:00
  50c48e88f5
• Added allow-expect-in-tests / allow-unwrap-in-tests (#2328)

  This PR:
  * Added the clippy.toml to configure allowable expect / unwrap usage in
  tests
  * Removed as many expect/allow lines as possible from tests
  * moved a bunch of allows to expects where possible
  
  Note: in integration tests, non `#[test]` helper functions are not
  covered by this so we had to leave a few lingering `expect(expect_used`
  checks around

  Parker Thompson · 2025-08-14 17:59:01 -07:00
  a075424437
• chore: introduce ConversationManager as a clearinghouse for all conversations (#2240)

  This PR does two things because after I got deep into the first one I
  started pulling on the thread to the second:
  
  - Makes `ConversationManager` the place where all in-memory
  conversations are created and stored. Previously, `MessageProcessor` in
  the `codex-mcp-server` crate was doing this via its `session_map`, but
  this is something that should be done in `codex-core`.
  - It unwinds the `ctrl_c: tokio::sync::Notify` that was threaded
  throughout our code. I think this made sense at one time, but now that
  we handle Ctrl-C within the TUI and have a proper `Op::Interrupt` event,
  I don't think this was quite right, so I removed it. For `codex exec`
  and `codex proto`, we now use `tokio::signal::ctrl_c()` directly, but we
  no longer make `Notify` a field of `Codex` or `CodexConversation`.
  
  Changes of note:
  
  - Adds the files `conversation_manager.rs` and `codex_conversation.rs`
  to `codex-core`.
  - `Codex` and `CodexSpawnOk` are no longer exported from `codex-core`:
  other crates must use `CodexConversation` instead (which is created via
  `ConversationManager`).
  - `core/src/codex_wrapper.rs` has been deleted in favor of
  `ConversationManager`.
  - `ConversationManager::new_conversation()` returns `NewConversation`,
  which is in line with the `new_conversation` tool we want to add to the
  MCP server. Note `NewConversation` includes `SessionConfiguredEvent`, so
  we eliminate checks in cases like `codex-rs/core/tests/client.rs` to
  verify `SessionConfiguredEvent` is the first event because that is now
  internal to `ConversationManager`.
  - Quite a bit of code was deleted from
  `codex-rs/mcp-server/src/message_processor.rs` since it no longer has to
  manage multiple conversations itself: it goes through
  `ConversationManager` instead.
  - `core/tests/live_agent.rs` has been deleted because I had to update a
  bunch of tests and all the tests in here were ignored, and I don't think
  anyone ever ran them, so this was just technical debt, at this point.
  - Removed `notify_on_sigint()` from `util.rs` (and in a follow-up, I
  hope to refactor the blandly-named `util.rs` into more descriptive
  files).
  - In general, I started replacing local variables named `codex` as
  `conversation`, where appropriate, though admittedly I didn't do it
  through all the integration tests because that would have added a lot of
  noise to this PR.
  
  
  
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/2240).
  * #2264
  * #2263
  * __->__ #2240

  Michael Bolin · 2025-08-13 13:38:18 -07:00
  08ed618f72
• Include output truncation message in tool call results (#2183)

  To avoid model being confused about incomplete output.

  pakrym-oai · 2025-08-11 11:52:05 -07:00
  0cf57e1f42
• [approval_policy] Add OnRequest approval_policy (#1865)

  ## Summary
  A split-up PR of #1763 , stacked on top of a tools refactor #1858 to
  make the change clearer. From the previous summary:
  
  > Let's try something new: tell the model about the sandbox, and let it
  decide when it will need to break the sandbox. Some local testing
  suggests that it works pretty well with zero iteration on the prompt!
  
  ## Testing
  - [x] Added unit tests
  - [x] Tested locally and it appears to work smoothly!

  Dylan · 2025-08-05 20:44:20 -07:00
  725dd6be6a
• feat: stream exec stdout events (#1786)

  ## Summary
  - stream command stdout as `ExecCommandStdout` events
  - forward streamed stdout to clients and ignore in human output
  processor
  - adjust call sites for new streaming API

  aibrahim-oai · 2025-08-01 13:04:34 -07:00
  bc7beddaa2
• Trim bash lc and run with login shell (#1725)

  include .zshenv, .zprofile by running with the `-l` flag and don't start
  a shell inside a shell when we see the typical `bash -lc` invocation.

  pakrym-oai · 2025-07-29 16:49:02 -07:00
  6b10e22eb3
• Optionally run using user profile (#1678)
  pakrym-oai · 2025-07-25 11:45:23 -07:00
  7ee87123a6