Permission Setup Guide

When Typilot prompts you automatically

1. Install Typilot from the DMG and launch it for the first time.
2. macOS shows an “Accessibility Access” alert. Click Open System Settings.
3. In the Accessibility list, find Typilot and switch it on. Unlock the padlock with your password if needed.
4. Quit and re-open Typilot so the permission is applied.

How to confirm it worked

• Return to Accessibility settings—the toggle next to Typilot should stay on.
• In Typilot, open Settings → Monitoring; “Keyboard Listener” should show Running.
• Press Cmd + Space in another app—the Typilot prompt should appear.

First launch checklist

1. Install Typilot, then double-click the shortcut to open it.
2. If Windows Defender SmartScreen appears, click More info → Run anyway.
3. When asked, allow Typilot to run in the background and show notifications.
4. Look for the Typilot icon in the system tray (bottom-right). Right-click and confirm Launch on startup is enabled so permissions persist after a reboot.

Optional but recommended

• Controlled Folder Access: If Windows Security blocks Typilot, go to Windows Security → Virus & threat protection → Ransomware protection and add Typilot as an allowed app.
• Run as administrator (only if needed): Right-click the Typilot shortcut → Properties → Compatibility → check Run this program as administrator if other automation tools block simulation. Most users do not need this.
• Firewall: Typilot communicates with Ollama locally. Ensure ollama.exe is allowed in Windows Defender Firewall so Typilot can reach it.

Verify everything works

• Open Typilot and visit Settings → Monitoring; the Keyboard Listener should show Online.
• Press Ctrl + Space in Notepad—Typilot should appear.
• Type gen: hello world and press the send key (period). Typilot should type the response for you.

Fastest option: use the official .deb installer

1. Download the Ubuntu package from the Typilot Download page.
2. Open a terminal and run:

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

3. The installer creates the input and uinput groups, configures udev rules, and sets permissions automatically.
4. Reboot your computer so the new group memberships apply.

Verify access after reboot

• Confirm your session type: run echo $XDG_SESSION_TYPE — it should show wayland.
• Check your groups:

  groups | grep -E 'input|uinput'

• Ensure the devices are accessible:

  ls -l /dev/input/event*
  ls -l /dev/uinput

  You should see permissions like crw-rw---- with the group set to input or uinput.

• Open Typilot → Settings → Monitoring and confirm the Keyboard Listener status is Online.

Before you start

• Confirm you’re on X11: echo $XDG_SESSION_TYPE should return x11.
• Install Typilot (AppImage, .deb, or package manager) and launch it once.
• Keep a terminal handy—you’ll run a few quick commands.

Grant device access

1. Add your user to the necessary groups (same as Wayland):

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

2. Create udev rules in case your distribution resets permissions:

   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

3. Reload udev rules and reboot:

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

Test and verify

• After rebooting, run:

  groups | grep -E 'input|uinput'

  to confirm membership.
• Launch Typilot from a terminal and watch for any “permission denied” messages.
• Press your activation shortcut in a text editor. If Typilot does not appear, reopen Typilot from the terminal to view logs.
• If simulation fails, run sudo dmesg | grep uinput to check for kernel messages.