Il s’agit d’une ancienne version. La dernière version est la 1.2.12. QoderWake 1.2.12 · Date de sortie:
Fichiers d’installation 1.2.10
| Architecture | Type | Portée | Taille du fichier | Télécharger | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE (Inno Setup) | Tous les utilisateurs | 250,3 Mo | download.qoder.com | VirusTotal |
Le lien et l’empreinte SHA256 proviennent du manifeste communautaire du Gestionnaire de paquets Windows. Comparez l’empreinte du fichier téléchargé avant de l’exécuter.
Notes de version
@Waker Experience and Group Stability Improvements
Improvements
- @Waker and Automation Setup: Improved account details, authorization confirmations, and delivery destination displays, with clearer guidance when no IM connection is configured.
- Feishu Authorization: Reduced repeated QR-code scans when complete, valid authorization is already available, and unified permission requests for bot search.
- Personal Avatar Memory: Improved reading and recall for large memory collections, reducing memory usage and failures when loading extensive memories.
- Update Guidance: Clarified that restarting and reconnecting after an update may take 3–5 minutes, with clearer retry and repair instructions when something goes wrong.
Bug Fixes
- Fixed shared group files disappearing after list refreshes and errors when uploading group attachments.
- Fixed background processing of historical group tasks with many files causing other tasks to stall or time out.
- Fixed stale task progress being sent after a task became invalid, and DingTalk Personal Avatars continuing to reply after the user had already responded.
- Fixed consecutive WeCom messages being incorrectly treated as busy, and subsequent messages failing to proceed after a conversation failed to start.
- Fixed recovery issues with remote Feishu pairing approvals and configurations with multiple responding Wakers.
- Fixed repeated requests and incorrect “result not found” errors in @Waker responsibility conflict detection.
- Fixed some DingTalk @Waker tasks failing to prepare their working directory on Windows, and document queries being incorrectly blocked with some older DingTalk sign-in configurations.
- Fixed recovery or reinstallation failures after some unsuccessful updates, and conversation startup failures caused by automatic Connector token renewal.
