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
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:
Benefits:
Thank you for considering this improvement!
Additional information
No response