Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Bash Prompt Erasing Output
Reported by alaeddin14 · filed Feb 27, 2026Closed upstream on 2026-02-27 by commit 8ac7cd9e23cc (closed by dhh). GitHub close reason: completed.
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 v3.4.0
What's wrong?
Description
Since the v3.4.0 update, commands that output text without a trailing newline (e.g., curl without -w "\n" or printf) have their output erased by the prompt rendering process.
Steps to Reproduce
- Use the default Omarchy Bash configuration.
- Run a command that does not end in a newline:
printf "This text should be visible"- Actual Behavior: The line is erased and the prompt appears on an empty line.
- Expected Behavior: The prompt should appear immediately following the text (or the text should remain visible).
Root Cause
A new __sanitize_prompt function was introduced in ~/.local/share/omarchy/default/bash/init (Commit 49a2941e):
# clear stale readline state before rendering prompt (prevents artifacts in prompt after abnormal exits like SIGQUIT)
__sanitize_prompt() { printf '\r\033[K'; }
PROMPT_COMMAND="__sanitize_prompt${PROMPT_COMMAND:+;$PROMPT_COMMAND}"This function runs via PROMPT_COMMAND before every prompt. The \r (carriage return) moves the cursor to the start of the current line, and \033[K (clear to end of line) erases everything on that line. If a command didn't move the cursor to a new line, this "sanitization" wipes the output.
Temporary Workaround
Add the following to ~/.bashrc after sourcing the Omarchy defaults:
# Fix Omarchy v3.4.0 issue where output without newline is erased
__sanitize_prompt() { :; }View raw text
### System details
Omarchy v3.4.0
### What's wrong?
### Description
Since the v3.4.0 update, commands that output text **without a trailing newline** (e.g., `curl` without `-w "\n"` or `printf`) have their output erased by the prompt rendering process.
### Steps to Reproduce
1. Use the default Omarchy Bash configuration.
2. Run a command that does not end in a newline:
```bash
printf "This text should be visible"
```
3. **Actual Behavior:** The line is erased and the prompt appears on an empty line.
4. **Expected Behavior:** The prompt should appear immediately following the text (or the text should remain visible).
### Root Cause
A new `__sanitize_prompt` function was introduced in `~/.local/share/omarchy/default/bash/init` (Commit `49a2941e`):
```bash
# clear stale readline state before rendering prompt (prevents artifacts in prompt after abnormal exits like SIGQUIT)
__sanitize_prompt() { printf '\r\033[K'; }
PROMPT_COMMAND="__sanitize_prompt${PROMPT_COMMAND:+;$PROMPT_COMMAND}"
```
This function runs via `PROMPT_COMMAND` before every prompt. The `\r` (carriage return) moves the cursor to the start of the current line, and `\033[K` (clear to end of line) erases everything on that line. If a command didn't move the cursor to a new line, this "sanitization" wipes the output.
### Temporary Workaround
Add the following to `~/.bashrc` after sourcing the Omarchy defaults:
```bash
# Fix Omarchy v3.4.0 issue where output without newline is erased
__sanitize_prompt() { :; }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.