Roadmap · non-binding

Safe first. Then broader.

These are possible next areas of work, not a commitment or schedule. Every extension needs its own privacy and security review.

In focus

Interactive checks of the existing Accessibility, clipboard, shortcut, undo, Services menu and keyboard flows in real apps. This is open quality assurance, not an available feature.

Windows: A desktop version (Tauri) is in development (alpha). There is only a manually started, unsigned test build for known testers, no public download and no commitment on scope.

Next

  • Fill the compatibility table with real, manually recorded results.
  • Replace the screenshot placeholders with real screenshots after manual checks.
  • Run the prepared Developer ID signing and notarization once a certificate is available.

Under review

  • Real code execution stays blocked; Apple’s Containerization framework was evaluated only.
  • Cursor scope without a selection: only with reliable public Accessibility data and tight limits.
  • Hunk selection with performance, Unicode and stale-selection tests.

Long term

  • Custom actions and import/export of app profiles, versioned and credential-free.
  • Custom text shortcuts (snippet expansion), designed without permanent keystroke monitoring.

There are no binding dates. Status changes only once code and verification exist.