Still seems you aren't cleanup any of those timeouts in `providers/codex/appServer.js` on disable/destroy.

Hey, I think there's a misunderstanding. There is cleanup: In `providers/codex/appServer.js`, `destroy()` starts at line 256. The two paths are: - Request timeouts: `destroy()` → `_rejectPending()` → `_rejectRequest()` → `_takePending()`. The actual `GLib.Source.remove(entry.timeoutId)` is at line 434. - Stderr-drain timeout: `destroy()` → `_failConnection()` → `finishStderrDrain()`. That callback removes `connection.stderrDrainId` at line 574. Having said that, there are way too many indirections, so I think I'll refactor this in the future version to make it much simpler.

It should be clear for the reviewers that the timeouts getting removed on destroy and before creating a new one. Trace back 4 steps to find the timeout removal isn't really a good approach. When one of them get removed in the future update, you can break the chain and we can miss it in the diff.