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?

AreaIn the audited areamenu· 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?

Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. So far: in the audited area (menu) — decided by agents · verified; matches no known issue — decided by agents · verified; not a duplicate of another report — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

omarchy default agent cursor

"setup.default.agent.cursor": {"icon":"...","label":"Cursor","when":"omarchy-cmd-present agent","checked":"[[ \"cursor\" == \"cursor\" ]]","action":"omarchy-default-agent cursor"},

## Problem
Cursor CLI is supported by `omarchy-default-agent` (line 36) but is not included in the agent selection menu at `omarchy-menu.jsonc`.

Currently the menu offers: claude, codex, copilot, crush, gemini, grok, omp, opencode, pi.

Users who want Cursor as their default agent must use the CLI:
```bash
omarchy default agent cursor
```

But there's no way to select it from the menu (Setup → Defaults → Agent).

## Solution
Add `setup.default.agent.cursor` to the default menu entries in `omarchy-menu.jsonc`:

```jsonc
"setup.default.agent.cursor": {"icon":"...","label":"Cursor","when":"omarchy-cmd-present agent","checked":"[[ \"cursor\" == \"cursor\" ]]","action":"omarchy-default-agent cursor"},
```

## Context
- Cursor CLI is installed via `curl https://cursor.com/install -fsS | bash`
- The `agent` command is the entry point
- The `omarchy-default-agent` script already handles cursor (skips mise, uses `agent --yolo`)
- Cursor is not currently in the default agent list — this would be a new addition

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

• Related PRpr/10171· confirmed
• Fixed bypr/8450· confirmed

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.