Add quiet/actionable visibility controls for Codex automations

Product area

Codex app automations / scheduled cron automations.

Problem

Codex app cron automations can perform useful unattended maintenance, but their chat/sidebar visibility appears to be controlled indirectly by prompt behavior, for example asking the automation to emit an archive directive when there is nothing actionable.

That makes "quiet unless actionable" automation fragile:

• routine successful runs may still clutter the user's chat/sidebar if the prompt or model output varies;
• users have to encode UI hygiene as prompt text instead of product configuration;
• automation authors cannot clearly choose between "always visible", "archive on success", "notify only on failure/action required", or "quiet unless actionable";
• this creates hesitation around using automations for legitimate nightly maintenance.

Concrete example

I created a nightly repo dirty-tree review automation. The automation:

1. Runs a script that writes a Markdown report.
2. If the report says the repo is clean, it should silently archive itself.
3. If dirty workstreams are found, it should create/update a task and notify the user.

The core automation behavior is right, but chat hygiene currently depends on prompt instructions such as:

If clean, do not leave a prose status update; end the run with exactly ::archive{reason="Nightly dirty-tree review clean"}.

This works as a workaround, but it is not a product-level guarantee.

Requested behavior

Please add explicit output/visibility controls for Codex automations, such as:

• always visible
• archive automatically on success
• quiet unless actionable
• notify only on failure/action required

Ideally this would be configured outside the prompt and enforced by the automation runner/UI.

Why this matters

Scheduled automations become much more useful when users trust they will not create chat/sidebar noise for routine success. The product should make this a stable automation setting rather than a prompt convention.

Acceptance case

A nightly maintenance automation should be able to run every day and:

• leave no visible chat/sidebar item when there is no action needed;
• create a visible notification or inbox item when action is needed;
• preserve a durable run log/report artifact;
• avoid relying on special assistant text output for routine archive behavior.