Recover a shortcut or note save

The opening key does nothing

1. Confirm Ouros X is running.
2. Choose Open Ouros from its app menu.
3. If the menu opens the bar but the key does not, check the assigned shortcut and System Settings → Privacy & Security → Input Monitoring.
4. Test with a non-sensitive application query such as Safari in Files.

Grant only the access relevant to the failing action. An expanded view can consume Escape before the whole bar closes; focus and the current layer matter.

A note did not save

Keep the editor open. Retain the text and exact error before retrying. In the editor, Command K → Copy text lets you preserve text in another editor. Do not erase the draft or reset settings to diagnose a save failure.

After an explicit successful save, choose Reveal saved note and inspect the actual Markdown file. An empty editor alone is not enough to confirm success. Follow the complete save-and-check procedure.

A key behaves differently in another view

Check which field, editor, result list or terminal has focus. Return can execute a shell command in Commands. Hiding a terminal view is not proof that its process stopped. See essential shortcuts before retrying.

A terminal session is unavailable

These checks apply to the unreleased, local-only Ouros X 2.1.6 terminal update, not the public stable release.

1. Keep a working local terminal open. A problem reaching one session service does not mean every local session has failed.
2. Read the unavailable message. An empty history with a service error is not confirmation that no sessions exist. Previously known sessions can remain visible but unavailable.
3. Check the device and the session service you selected. If an explicitly selected service cannot be reached, Ouros does not quietly create the session somewhere else.
4. Reconnect to the original service and inspect the existing session and its output. Recovery should clear the unavailable message even when the session list has not changed.

If starting a session returned an unclear result, do not immediately submit it again. The service may already have started the work. Ouros does not automatically repeat creation or switch services after that uncertainty. Check the original device and session before deciding whether a fresh start is needed.

Closing a window does not stop device-owned managed work. An unavailable row does not prove the work stopped either. This does not automatically adopt an agent running outside Ouros; see terminal and session ownership.

Screen reading cannot capture

1. Open System Settings → Privacy & Security → Screen Recording.
2. Enable Ouros X.
3. Open eyes1te again and retry the capture.

The app uses the Screen Recording already granted to Ouros X when the bundled helper cannot capture on its own. Follow Find and change a setting for the plugin itself.

For unresolved errors, use the shared help checklist.