Enter a keyword to search published documentation.
nano-use
Permissions and Troubleshooting
Map nano-use observation and input failures to macOS permissions, coordinates, and local process errors.
Screen Recording
The screenshot path uses ScreenCaptureKit. Grant Screen Recording permission to the actual terminal or agent host process that launches nano-use. An empty or unavailable capture should be treated as an observation failure, not as evidence that the desktop is blank.
Accessibility
click, right_click, double_click, drag, type, keypress, and scroll post local input events. Grant Accessibility permission to the launching process before relying on those actions.
Coordinates and displays
Pointer and scroll commands check coordinates against one axis-aligned bounding rectangle enclosing all active display rectangles. A point outside that rectangle fails before the input event is posted, but the code does not test each display separately, so points in gaps between displays can pass validation. Multi-display layouts can include non-zero or negative origins; derive coordinates from the current observation and confirm the intended display rather than assuming one screen starts at zero.
Command errors
type and keypress reject empty values. keypress rejects an unknown main key or a combination with more than one main key. Screenshot encoding, event construction, output writing, and display discovery can also return local errors.
Recovery sequence
- Re-run
nano-use --helpto confirm the binary being called. - Confirm Screen Recording or Accessibility for the launching process.
- Capture a fresh observation before deriving coordinates.
- Retry only the smallest intended action and inspect its result.