v2.17.0 2026-10-23
Stored secrets your API profiles use now go only to the places you allowed
- This applies on every instance, hosted or self-hosted. At the first start after the update, lynox binds each secret once to the places its profiles agree on. A secret it cannot bind is not sent by any profile until you save the profile again in the chat and allow it at the question.
- When you stop a run, the reads and requests it has under way are cut off too: web requests and web research, mail and Google reads, and on hosted instances shell commands. Each such call says it was stopped and that what it did up to then stays. Check a write before you repeat it. Sending a mail is not cut off.
- When lynox asks before a web request that writes to a service, the question in lynox now also shows the headers it sends and the values in the address, with stored secrets masked. Your yes does not carry over to later writes.
- For accounts connected through an API profile, the API page shows who connected them and, for bexio, which account was used to sign in. When a token renewal shows that the provider revoked the access, the page says so and offers to reconnect.
- When the inbox recognizes a mail as forwarded to you by a person, it no longer files it as done on its own; it puts it with the mails that need you.
- Requests to Shopify store addresses (….myshopify.com) are refused for now, with a note that Shopify is temporarily unavailable in lynox.
- If you host lynox yourself: this release contains security fixes, and we recommend updating. Repair or delete API profile files that cannot be read before you update: if one is unreadable at the first start, lynox binds no secret, also not after the repair. Read the upgrade notes in the lynox CHANGELOG on GitHub before you update or roll back; the database update has no way back.