Skip to content
TyrnBeta

Troubleshooting

The backend isn’t running

The sidebar shows “Daemon is not running.” Click Start daemon. If it won’t start:

  1. Open the daemon menu in the sidebar and choose Show daemon log.
  2. Read the last lines for the error. Logs are in ~/.tyrn/logs.
  3. Try Start with debug logging for more detail, then Show daemon log again.

If the backend is running but sessions misbehave, use Restart daemon. Restarting ends running sessions.

A harness won’t install

Open Settings > Agents > Harnesses and select the harness.

  • Click Retry to try again.
  • Read Last error for what failed.
  • Check Requires. If it names a missing tool, install it and click Retry.
  • Installs download from npm, PyPI or GitHub, so check your network connection.

A session won’t start

  • Make sure the harness is installed and up to date in Settings > Agents > Harnesses.
  • If the harness uses its own sign-in (Native), sign in to it. If you chose Tyrn router, check that a provider is connected.
  • If the session form says a harness does not support Tyrn router, choose Native.
  • Use Show daemon log and look for errors from the time you clicked Start.

Model errors with Tyrn router

Tyrn router uses providers you connected. If a model errors or is missing, click Connect provider in the session form, or open Settings > Inference and check that your account or key is connected and active. See Connect models.

An update failed

Tyrn installs only updates signed by the Tyrn developer team. If a downloaded update isn’t signed correctly, you see a message like “The downloaded update has an invalid code signature, so it was not installed.” Nothing is replaced. Try Check for Updates again later, or download the latest DMG (macOS) or tarball (Linux) from the link in your access email and install it again.

Linux

A window fails to open

If Tyrn says it failed to open a window, or nothing appears, the graphics driver usually has no working Vulkan support. Tyrn needs a GPU with Vulkan support.

  1. Install your GPU’s Vulkan driver. On most distributions that is the Mesa Vulkan package for AMD and Intel (for example mesa-vulkan-drivers), or the vendor driver for NVIDIA.

  2. Install the Vulkan tools (vulkan-tools on most distributions) and check that a GPU is listed:

    Terminal window
    vulkaninfo --summary

  3. If the list is empty or the command fails, the driver is the problem. Fix it and start Tyrn again.

Try both X11 and Wayland sessions if one of them fails.

“Could not start inotify”

Tyrn watches your project folders for changes. Linux limits how many watches a user can have, and you have reached the limit. Raise the limits:

Terminal window
sudo sysctl fs.inotify.max_user_instances=1024
sudo sysctl fs.inotify.max_user_watches=524288

These last until you restart. To keep them, put the same two lines (without sudo sysctl) in a file such as /etc/sysctl.d/60-tyrn.conf:

/etc/sysctl.d/60-tyrn.conf
fs.inotify.max_user_instances = 1024
fs.inotify.max_user_watches = 524288

Then run sudo sysctl --system and restart Tyrn.

“Can’t open any files”

The file picker on Linux comes from xdg-desktop-portal and a portal backend for your desktop. If either one is missing, Tyrn can’t show the open dialog.

  1. Install xdg-desktop-portal.
  2. Install the backend that matches your desktop: xdg-desktop-portal-gnome for GNOME, xdg-desktop-portal-kde for KDE Plasma, or xdg-desktop-portal-gtk for most others. On Hyprland or Sway, use the xdg-desktop-portal-hyprland or xdg-desktop-portal-wlr backend.
  3. Log out and back in, then try again.

See Linux for the requirements.

Collect logs for a bug report

Email hi@tyrn.dev with:

  • Your Tyrn version and your macOS or Linux version.
  • What you did and what you expected.
  • ~/.tyrn/logs/daemon.log and ~/.tyrn/logs/router.log.

Logs can contain file paths and parts of your sessions. Read them before you send them.