Loading chapter

03 - SYSTEM

Permissionsetup.

Typilot listens for a global shortcut, reads selected text, and types responses back. Every OS protects these capabilities - each platform needs an explicit grant. Five minutes per platform.

macOSAccessibility

WindowsKeyboard access

Linux · Waylandinput + uinput

Linux · X11input + XTest

macOS

Required

Grant Accessibility access so Typilot can watch shortcuts and type into any macOS app.

When Typilot prompts you automatically.

Install from the DMG and launch.
On the Accessibility alert, click Open System Settings.
In the Accessibility list, switch Typilot on. Unlock the padlock with your password if needed.
Quit and reopen Typilot so the permission applies.

Enable manually if you missed the popup.

Open System Settings → Privacy & Security → Accessibility.
Unlock the padlock, then enable the checkbox beside Typilot.
If Typilot doesn't appear, launch it once - it will add itself to the list.
Close System Settings, restart Typilot.

Confirm it worked.

The toggle next to Typilot stays on after restart.
In Typilot → Monitoring, "Keyboard Listener" shows Online.
Press Cmd + Space in another app - the prompt appears.

Windows

Required

Windows protects apps from reading global keyboard input. Toggle keyboard access on and let Typilot through SmartScreen.

First launch checklist.

Install Typilot, double-click the shortcut.
If SmartScreen appears: click More info → Run anyway.
Allow Typilot to run in background and show notifications.
Right-click the tray icon, confirm Launch on startup is enabled so permissions persist after reboot.

Allow desktop apps to use your keyboard.

Open Settings → Privacy & security → Keyboard.
Toggle Let desktop apps access your keyboard to On.
Launch Typilot - Windows lists it under the toggle with a recent access timestamp.

Verify.

Settings → Monitoring → Keyboard Listener is Online.
Press Ctrl + Space in Notepad - Typilot appears.
Type gen: hello world, press send - Typilot types the response.

Linux · Wayland

Required

Wayland blocks global keyboard capture by default. Join the right groups (or install the .deb) so Typilot can read /dev/input and write to /dev/uinput.

Fastest path - the .deb installer.

sudo dpkg -i Typilot_*.deb
sudo apt-get install -f

The installer creates the input and uinput groups, writes udev rules, and sets permissions. Reboot so group membership applies.

Manual setup - AppImage / Flatpak / source.

Add yourself to the groups:

sudo groupadd -f uinput
sudo usermod -aG input $USER
sudo usermod -aG uinput $USER

Create persistent udev rules:

echo 'KERNEL=="event*", GROUP="input", MODE="0660"' | sudo tee /etc/udev/rules.d/99-input.rules
echo 'KERNEL=="uinput", GROUP="uinput", MODE="0660"' | sudo tee /etc/udev/rules.d/99-uinput.rules
sudo udevadm control --reload-rules
sudo udevadm trigger

Reboot - group membership only refreshes on a full restart.

Verify after reboot.

echo $XDG_SESSION_TYPE   # → wayland
groups | grep -E 'input|uinput'
ls -l /dev/input/event*
ls -l /dev/uinput

Permissions should look like crw-rw---- with group input or uinput. Then Typilot → Monitoring → Keyboard Listener should be Online.

Linux · X11

Recommended

X11 is more permissive than Wayland, but the same groups + udev rules prevent "permission denied" after a reboot.

Before you start.

echo $XDG_SESSION_TYPE   # → x11

Install Typilot (AppImage / .deb / package manager), launch once.

Grant device access.

sudo groupadd -f uinput
sudo usermod -aG input $USER
sudo usermod -aG uinput $USER

echo 'KERNEL=="event*", GROUP="input", MODE="0660"' | sudo tee /etc/udev/rules.d/99-input.rules
echo 'KERNEL=="uinput", GROUP="uinput", MODE="0660"' | sudo tee /etc/udev/rules.d/99-uinput.rules

sudo udevadm control --reload-rules
sudo udevadm trigger
sudo reboot

Enable XTest (usually already on).

xdpyinfo | grep XTst

If empty, install libxtst6 on Ubuntu/Debian (or the equivalent for your distro).

FINAL CHECKLIST

Typilot launches with no warning dialogs.
Keyboard Listener shows Online.
Activation shortcut opens Typilot in another app.
Typilot can type a short response back into the active window.
You rebooted (Linux) or relaunched (macOS / Windows).

NEXT → 04 LICENSES & ACCOUNTS

Loading chapter

03 - SYSTEM

Permissionsetup.

Typilot listens for a global shortcut, reads selected text, and types responses back. Every OS protects these capabilities - each platform needs an explicit grant. Five minutes per platform.

macOSAccessibility

WindowsKeyboard access

Linux · Waylandinput + uinput

Linux · X11input + XTest

macOS

Required

Grant Accessibility access so Typilot can watch shortcuts and type into any macOS app.

When Typilot prompts you automatically.

Install from the DMG and launch.
On the Accessibility alert, click Open System Settings.
In the Accessibility list, switch Typilot on. Unlock the padlock with your password if needed.
Quit and reopen Typilot so the permission applies.

Enable manually if you missed the popup.

Open System Settings → Privacy & Security → Accessibility.
Unlock the padlock, then enable the checkbox beside Typilot.
If Typilot doesn't appear, launch it once - it will add itself to the list.
Close System Settings, restart Typilot.

Confirm it worked.

The toggle next to Typilot stays on after restart.
In Typilot → Monitoring, "Keyboard Listener" shows Online.
Press Cmd + Space in another app - the prompt appears.

Windows

Required

Windows protects apps from reading global keyboard input. Toggle keyboard access on and let Typilot through SmartScreen.

First launch checklist.

Install Typilot, double-click the shortcut.
If SmartScreen appears: click More info → Run anyway.
Allow Typilot to run in background and show notifications.
Right-click the tray icon, confirm Launch on startup is enabled so permissions persist after reboot.

Allow desktop apps to use your keyboard.

Open Settings → Privacy & security → Keyboard.
Toggle Let desktop apps access your keyboard to On.
Launch Typilot - Windows lists it under the toggle with a recent access timestamp.

Verify.

Settings → Monitoring → Keyboard Listener is Online.
Press Ctrl + Space in Notepad - Typilot appears.
Type gen: hello world, press send - Typilot types the response.

Linux · Wayland

Required

Wayland blocks global keyboard capture by default. Join the right groups (or install the .deb) so Typilot can read /dev/input and write to /dev/uinput.

Fastest path - the .deb installer.

sudo dpkg -i Typilot_*.deb
sudo apt-get install -f

The installer creates the input and uinput groups, writes udev rules, and sets permissions. Reboot so group membership applies.

Manual setup - AppImage / Flatpak / source.

Add yourself to the groups:

sudo groupadd -f uinput
sudo usermod -aG input $USER
sudo usermod -aG uinput $USER

Create persistent udev rules:

echo 'KERNEL=="event*", GROUP="input", MODE="0660"' | sudo tee /etc/udev/rules.d/99-input.rules
echo 'KERNEL=="uinput", GROUP="uinput", MODE="0660"' | sudo tee /etc/udev/rules.d/99-uinput.rules
sudo udevadm control --reload-rules
sudo udevadm trigger

Reboot - group membership only refreshes on a full restart.

Verify after reboot.

echo $XDG_SESSION_TYPE   # → wayland
groups | grep -E 'input|uinput'
ls -l /dev/input/event*
ls -l /dev/uinput

Permissions should look like crw-rw---- with group input or uinput. Then Typilot → Monitoring → Keyboard Listener should be Online.

Linux · X11

Recommended

X11 is more permissive than Wayland, but the same groups + udev rules prevent "permission denied" after a reboot.

Before you start.

echo $XDG_SESSION_TYPE   # → x11

Install Typilot (AppImage / .deb / package manager), launch once.

Grant device access.

sudo groupadd -f uinput
sudo usermod -aG input $USER
sudo usermod -aG uinput $USER

echo 'KERNEL=="event*", GROUP="input", MODE="0660"' | sudo tee /etc/udev/rules.d/99-input.rules
echo 'KERNEL=="uinput", GROUP="uinput", MODE="0660"' | sudo tee /etc/udev/rules.d/99-uinput.rules

sudo udevadm control --reload-rules
sudo udevadm trigger
sudo reboot

Enable XTest (usually already on).

xdpyinfo | grep XTst

If empty, install libxtst6 on Ubuntu/Debian (or the equivalent for your distro).

FINAL CHECKLIST

Typilot launches with no warning dialogs.
Keyboard Listener shows Online.
Activation shortcut opens Typilot in another app.
Typilot can type a short response back into the active window.
You rebooted (Linux) or relaunched (macOS / Windows).

NEXT → 04 LICENSES & ACCOUNTS