Skip to content

Add cwd (Current Working Directory) to Notify Input #5387

Closed

Description

@BobbyWang0120

What feature would you like to see?

Problem:
When customizing notification scripts for Codex, the current input does not include the current working directory (cwd). For Codex CLI, it is possible to manually extract the working directory path. However, for the Codex VS Code extension, the cwd is always reported as "~/", making it impossible to accurately determine the project or directory context using notifications.

Request:
Please include the cwd information directly in the notify input payload for both Codex CLI and Codex VS Code extension. This would allow users to write smarter notification scripts that react or organize based on the real project context, without requiring manual path extraction.

Proposed Solution:

  • Modify the notify mechanism to inject the actual cwd value into the notification payload sent to scripts and extensions.
  • Ensure the cwd reflects the correct working directory in both CLI and extension environments, not just defaulting to "~/".

Benefits:

  • Enables more dynamic and context-aware notification scripts
  • Reduces manual overhead for users managing multiple projects
  • Unifies behavior between CLI and VS Code extension

Thank you for considering this improvement!

Additional information

No response

Activity

  1. added a commit that references this issue on Oct 20, 2025
    7fc01c6
  2. added a commit that references this issue on Oct 24, 2025
    4a8cdf2
  3. added a commit that references this issue on Nov 10, 2025
    6202e44
  4. added a commit that references this issue on Nov 14, 2025
    a1b8a4e
  5. added a commit that references this issue on Dec 2, 2025
    b089ca7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions