# Troubleshooting

Source: /tuil/docs/guides/troubleshooting
Locale: en

Diagnose rendering, input, stream, log, and extension failures.



Start with devtools capability, focus, event, service, and extension panels.
For visual corruption, capture terminal capabilities and a protocol recording.
For missing pointer events, inspect layout bounds and routing phases. For stream
growth, inspect retention and backpressure. For missing logs, inspect parser and
redaction outcomes.

Always verify cleanup: mouse tracking, paste, focus reporting, and alternate
screen modes must be restored after errors.