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?

Not yet mapped to any requirement or component.

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?

Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

### System details

Omarchy 3.3.3

### What's wrong?

I keep having this situation: I start a long install (e.g. compiling PHP from source), and then 5, 10, or 20min later I find the install has failed because I walked away or switched screens and missed the password auth window.

I've had to run installs like 4 times before I managed to time it right and catch the password entry before it times out.

Suggestions:

1. ask for auth first, before the long running compile
2. don't have a timeout for auth-ing installs
3. trigger a notification, so at least if I am at my machine I can catch it.

Apologies if this is an issue with another project not omarchy - I am not sure what project the installer belongs to.

Thanks very much for everything y'all do! I'm about 4 months into using Omarchy, and I love it!

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.

No decision has been recorded yet.