Documentation

History & Logs

Track everything Typilot does. History shows the AI outputs you care about, while Logs provide a technical record for troubleshooting.

📜 History keeps up to 1,000 entries by default • Logs update in real time • Both respect the retention rules you set in Settings

Working with History

Powerful filtering

Filter by command (gen:, exp:, fix:, img:), model, or success status. Filters apply instantly without reloading the page.

Timeline view

Each entry shows the date, time, and duration. Sorting by column lets you group similar tasks or track slow responses.

Duration insights

See how long each command took. Combine with model filters to choose the best model for quick turnarounds.

Copy & reuse

Open any entry to copy the prompt or response back to your clipboard. Great for building documentation or FAQs.

Tip: Double-click a row to open the detail drawer. You can inspect the full prompt and response, copy them, or delete just that entry.

Understanding Logs

The Logs view streams raw events from the backend. It is ideal when you contact support or need to diagnose a tricky environment issue.

info

Routine events such as “Command started” and “Model switched”.

warning

Non-blocking issues—Typilot recovered but you might want to investigate.

error

Action required. Often paired with monitoring alerts or permission problems.

Filtering tips

  • Use the search box to filter by keyword (for example, NETWORK_ or keyboard-listener).
  • Toggle log levels on or off to focus on relevant events.
  • Export logs with the download button—Typilot saves them as JSON so you can share them with support safely.

Keeping data tidy

  1. Go to Settings → Data retention to pick how many days of history and logs you keep.
  2. Click “Delete selected” in History to remove specific rows.
  3. Use “Delete all data” in Settings only when you need a complete reset (Typilot restarts automatically afterwards).
Remember: Deleting history never removes your downloaded models or settings—they have their own controls elsewhere in Typilot.

Sharing logs with support

When you contact support, attach the exported JSON and describe what you were doing when the issue occurred. Include timestamps if possible—support can line them up with server logs to help faster.