CHIM

Dwemer Dynamics Home Overview Installation Plugins Configuration Roleplay Settings Skyrim Settings Large Language Models Text-to-Speech Speech-to-Text Image-to-Text Modders Guide FAQ Remote Hosting Guide Linux Setup Guide Log Files

⬇️Download 🎥Video Guide DiscordDiscord YouTubeYouTube PatreonPatreon

CHIM Log Files

When CHIM is failing, the fastest fix is usually finding the right log first instead of guessing. This page keeps the useful log locations, but uses the actual current HerikaServer and DwemerDistro launcher UI labels from the codebase.

Log Files

AIAgent Log

This is the main first-stop log for the Skyrim plugin side.

AIAgent.log is commonly found in:

C:\Users\YOURUSER\Documents\My Games\Skyrim Special Edition\SKSE

C:\Users\YOURUSER\Documents\My Games\Skyrim.INI\SKSE

If CHIM is not connecting, not sending requests, or not responding correctly in-game, this is usually the first log to read.

Papyrus Log

Use the Papyrus log when the issue feels like a Skyrim scripting problem instead of a server or provider problem.

C:\Users\YOURUSER\Documents\My Games\Skyrim Special Edition\Logs\Script\Papyrus.0.log

This is useful for tracking script errors, missing functions, and plugin-side events that never reach the CHIM server cleanly.

CHIM Server Logs

The current codebase exposes the main CHIM server logs through two real entry points:

  1. HerikaServer: Control Panel then the Server Logs tab.
  2. Distro Launcher: Debugging then Create Diagnostic File.

The HerikaServer side is embedding the CHIM distro debugger from the dashboard, and the launcher diagnostic export writes a summary file to:

Desktop\DwemerDistro-Diagnostics\diagnostics-YYYYMMDD-HHMMSS.txt

The CHIM log viewer code is currently reading from the HerikaServer log folder and surfaces these files:

  1. apache_error.log
  2. chim.log
  3. output_from_llm.log
  4. context_sent_to_llm.log
  5. output_to_plugin.log
  6. stt.log
  7. vision.log
  8. debugStream.log
  9. context_sent_to_llm_fast.log
  10. monitor.log
  11. service.log

In the launcher code, there are also direct live tail commands for Apache, XTTS, Chatterbox, PocketTTS, MeloTTS, Piper, localWhisper, and Parakeet logs. So if the launcher or server log views are not enough, the debugging tools are already wired to those service-specific logs too.