Note: Codex Micro (input.app v0.17.0 and v0.17.2) unstable behavior 2026-07-25

codex-micro-input-app-unstable-behavior.md

Input.app modifies a sealed resource after first launch on macOS

Summary

Immediately after a clean installation, Input.app passes macOS code-signature verification.

After launching the app once, verification fails because the app bundle's sealed AppleScript resource has been modified:

/Applications/input.app/Contents/Resources/scripts/window-info-retriever.scpt

Environment

• OS: macOS
• Architecture: Apple Silicon (arm64)
• Application: Input (it.focusense.input-app)
• Verification command:

codesign --verify --deep --strict --verbose=4 /Applications/input.app

Reproduction steps

1. Quit Input completely.
2. Remove the existing /Applications/input.app.
3. Install a fresh copy of Input.
4. Before launching Input, run the verification command.
5. Launch Input once, then quit it.
6. Run the same verification command again.

Result immediately after installation, before first launch

The nested frameworks and helper applications are prepared and validated successfully. The final result is:

/Applications/input.app: valid on disk
/Applications/input.app: satisfies its Designated Requirement

Result after launching Input once

The nested frameworks and helper applications are still prepared and validated, but verification of the main application bundle fails:

/Applications/input.app: a sealed resource is missing or invalid
file modified: /Applications/input.app/Contents/Resources/scripts/window-info-retriever.scpt

Difference

- /Applications/input.app: valid on disk
- /Applications/input.app: satisfies its Designated Requirement
+ /Applications/input.app: a sealed resource is missing or invalid
+ file modified: /Applications/input.app/Contents/Resources/scripts/window-info-retriever.scpt

Observed behavior

window-info-retriever.scpt is part of the signed application bundle. It retrieves information about the current foreground application and window through System Events, including values such as:

• Application name
• Process ID
• Bundle identifier
• Application path
• Focused-window title

Running the script should not normally change the compiled .scpt file. However, the file differs from its sealed version after Input has been launched once, invalidating the signature of the whole application bundle.

Expected behavior

Launching Input should not modify files inside the signed application bundle. If the script must be generated or modified at runtime, a working copy should be stored in a writable user-data location, for example:

~/Library/Application Support/Input/

The following command should continue to succeed after launching and quitting the application:

codesign --verify --deep --strict --verbose=4 /Applications/input.app

Additional observation

Once the signature becomes invalid, macOS logs repeated provenance-sandbox messages associated with Input:

ASP: Unable to apply provenance sandbox

This report does not claim that all observed runtime warnings are caused by the modified script, but the before/after verification confirms that the signed application bundle is modified during or immediately after its first launch.