Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1517GitHub issuePublicDecided· Out of scope

tdl leaves focus on the AI pane instead of nvim

Reported by kkoontz · filed Aug 24, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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

tdl leaves focus on the AI pane instead of nvimrevision 1 · captured 2026-09-28 21:24 UTC via poll

What happened

After tdl grok (or tdl <any-ai>), the cursor lands in the AI pane's prompt instead of Neovim.

What was expected

The nvim pane should have focus. The function even says so:

# Select the nvim pane for focus
tmux select-pane -t "$opencode_pane"

Cause

$opencode_pane is never set in tdl(). That variable belongs to tds(). The nvim pane in tdl is $editor_pane, and tds already focuses correctly with:

tmux select-pane -t "$editor_pane"

The last split tdl creates is the AI pane, so when select-pane gets an empty target it leaves you there.

Fix

In default/bash/fns/tmux, change the last line of tdl() from:

tmux select-pane -t "$opencode_pane"

to:

tmux select-pane -t "$editor_pane"

Steps to reproduce

  1. Super + Alt + Return to open the Work tmux session
  2. cd into a project
  3. tdl grok
  4. Cursor is in the Grok text box, not nvim

System

  • Omarchy 4.0.0-1 (quattro)
  • Confirmed in the packaged file /usr/share/omarchy/default/bash/fns/tmux and on the quattro branch of basecamp/omarchy
View raw text
## What happened

After `tdl grok` (or `tdl <any-ai>`), the cursor lands in the AI pane's prompt instead of Neovim.

## What was expected

The nvim pane should have focus. The function even says so:

```bash
# Select the nvim pane for focus
tmux select-pane -t "$opencode_pane"
```

## Cause

`$opencode_pane` is never set in `tdl()`. That variable belongs to `tds()`. The nvim pane in `tdl` is `$editor_pane`, and `tds` already focuses correctly with:

```bash
tmux select-pane -t "$editor_pane"
```

The last split `tdl` creates is the AI pane, so when `select-pane` gets an empty target it leaves you there.

## Fix

In `default/bash/fns/tmux`, change the last line of `tdl()` from:

```bash
tmux select-pane -t "$opencode_pane"
```

to:

```bash
tmux select-pane -t "$editor_pane"
```

## Steps to reproduce

1. `Super + Alt + Return` to open the Work tmux session
2. `cd` into a project
3. `tdl grok`
4. Cursor is in the Grok text box, not nvim

## System

- Omarchy 4.0.0-1 (quattro)
- Confirmed in the packaged file `/usr/share/omarchy/default/bash/fns/tmux` and on the `quattro` branch of basecamp/omarchy

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 08:35 UTC