[feature]: TRAE #643

Activity

1. jonasfroeller

   added

   enhancementNew feature or requestNew feature or request

   on Sep 17, 2026
2. linear commented on Sep 17, 2026

   

   linearBot

   on Sep 17, 2026 – with Linear

   More actions

   001-318
3. xiufengsun commented on Sep 20, 2026

   

   xiufengsun

   on Sep 20, 2026

   Owner

   More actions

   Happy to take a PR. Two constraints worth knowing before you spend time on it, both learned from the TRAE CN attempt in #474:

   A hardcoded decryption key is fine to post. It is in the shipped binary, so it is not a secret — extracting it is the normal way anyone reads a SQLCipher store. What I will not merge is anything that sends a user credential off the machine; if the integration needs a token for a vendor API, that path has to be opt-in behind an explicit flag, defaulting off.

   Verify what input_tokens actually means before you trust it. This is the single thing most provider PRs get wrong here. Codex and every-code fold cached reads into their input count, and copying that naively inflated cost 6-7x. Check the parsed numbers against TRAE's own billing or cost field on a few hundred records rather than assuming the field names mean what they say. The repo's normalization is:

   input_tokens                = non-cached input only
   cached_input_tokens         = cache reads
   cache_creation_input_tokens = cache writes
   reasoning_output_tokens     = reasoning
   

   Also: if this is international TRAE and the CN build writes a different store, they should be separate sources rather than one bucket — same call I made for WorkBuddy in #632.

   No rush on timing. If you want, open it as a draft early and I will review the parser shape before you polish it.
4. jonasfroeller commented on Sep 20, 2026

   

   jonasfroeller

   on Sep 20, 2026

   Author

   More actions

   "A hardcoded decryption key is fine to post." - I wasn't sure if it was device-bound and therefore unique. I got the idea from the CN version, but I didn't know if it was universal for the English one too. (I didn't even check until now, but yeah, it matches exactly ^^)

   Noted. Thank you for the recommendations! I have to do a few other things first tho, so it might take a few more days.
5. jonasfroeller

   added 2 commits that reference this issue on Sep 26, 2026

   feat: track TRAE (xiufengsun#643)

   ed9cbb6

   feat: track TRAE (xiufengsun#643)

   d914959
6. jonasfroeller

   closed this as completedon Sep 30, 2026
7. xiufengsun commented on Sep 30, 2026

   

   xiufengsun

   on Sep 30, 2026

   Owner

   More actions

   Released in v1.1.4. The published release includes the CLI and macOS, Windows, and Linux builds. TRAE costs can be partial for multi-request turns, and the Linux TRAE data path remains unverified.