Skip to content

NLD command execution should use current shell PATH for executable resolution #9997

@JasonLovesDoggo

Description

@JasonLovesDoggo

Summary

Feature request: have NLD-driven command execution resolve executables using the current shell PATH.

Problem

In natural-language command execution (Warp/Oz agent flow), executable lookup appears not to consistently use the user’s current shell PATH. This creates friction when commands are available in the active shell environment but are not found or selected correctly by NLD execution.

Reproduction steps or desired workflow

  1. Open Warp with a shell session where PATH includes user-installed tools.
  2. Trigger natural-language command execution through the Warp/Oz agent flow.
  3. Request a command that depends on PATH resolution.
  4. Desired: NLD resolves executables against the current shell PATH used by the active session.

Artifacts

None attached.

Warp version

v0.2026.04.27.15.32.stable_02

Operating system

macOS (version unknown)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:agentAgent workflows, conversations, prompts, cloud mode, and AI-specific UI.area:terminal-inputTerminal command-line input, cursor movement, key handling, and input editing.bugSomething isn't working.needs-infoMore issue-specific reporter detail is needed before the problem can be confidently triaged.os:macmacOS-specific behavior, regressions, or requests.repro:lowThe report points to a real problem, but reproduction details are weak or inconsistent.triagedIssue has received an initial automated triage pass.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions