At a glance

1 · What is claimed?

Only the report text below — no validator has restated it as checkable claims yet.

2 · What does it affect?

AreaOutside the audited area· Decided by agents · verified

3 · Is it reproducible?

No validation has been run yet.

4 · What remains unclear?

• Not validated yet: no claims, no reproducer.

5 · What happens next?

Decided by agents and verified by a second, independent agent — see the decision.

Original report

open() (
  xdg-open "$@" >/dev/null 2>&1 &
)

open() (
  xdg-open "$@" >/dev/null &
)

## Problem

Omarchy defines the interactive shell helper `open` as a detached `xdg-open` wrapper:

```bash
open() (
  xdg-open "$@" >/dev/null 2>&1 &
)
```

That keeps the terminal clean, but it also discards stderr. When `xdg-open` cannot handle a target, users running `open ...` directly in the terminal get no error output and the failure looks silent.

## Expected behavior

Keep the existing non-blocking behavior and keep stdout quiet, but allow `xdg-open` stderr to reach the terminal so actionable failures are visible.

## Suggested change

Drop only the stderr redirection:

```bash
open() (
  xdg-open "$@" >/dev/null &
)
```

This preserves the previous behavior that motivated #4366: the command remains detached and avoids job-control completion noise, while making launch failures visible to the user.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

• Out of scopeDecided by agents · verified · 2026-10-09 03:52 UTC