Yesterday at 02:32 AM1 day No it is a mix - usually the first few in a reply is program name with link, then some program numbers with link and in the end it is text only - it is like it runs out of links :-) Edited yesterday at 02:34 AM1 day by Panda88
22 hours ago22 hr Author Hello everyone, please upgrade to 2.4.0 ... major improvements in cache management and token usage.With kind regards,Michel
22 hours ago22 hr 12 minutes ago, Michel Kohanim said:Hello everyone, please upgrade to 2.4.0 ... major improvements in cache management and token usage.With kind regards,MichelDone. Took about 10 seconds.
18 hours ago18 hr On 11/12/2026 at 5:13 PM, Michel Kohanim said:Hello everyone,Some exciting stuff:User guide! [ link ]Migration of Python from 311 to 312Added a tool that manages 90% of github setup so that all you need to do is to a) only once: setup your github account b) create a repo and set it up with the created by eisy-ai, and c) point eisy-ai to that repo. Then just to git stuff directly from eisy-ai such as add, commit, push, fetch ...IMPORTANT WARNING - you need the latest udx and eisy-ui. Upgrading from Staging will upgrade your OS to 14.5 AND your python to 312. Please be patient. It may take up to 2 hours.With kind regards,MichelOk I finally got around to doing this today. I have to say, for such a major update, it went really well! As expected, I had to wait a bit more while it reinstalled plugins, and needed to restart some, but in the end, everything was working. I then proceeded to migrate the plugins away from PG3x, one by one. Again, smooth sailing. There is only one minor issue remaining: It won't migrate the Virtual plugin because it wasn't installed from the production store. Indeed it was installed from the beta store. Thing is, the beta version is 3.2.3 and production store version is 3.2.2, so even though I go to the production store and click on "update" in the plugin's configuration screen (and it appears to be udating), the version remains the same, probably because it sees that the production version number is lower. How do I get around that?
17 hours ago17 hr Author @Guy Lavoie thank you for the report!Regarding the issue, please submit a ticket.With kind regards,Michel
17 hours ago17 hr 10 minutes ago, Michel Kohanim said:@Guy Lavoie thank you for the report!Regarding the issue, please submit a ticket.With kind regards,MichelDone.
17 hours ago17 hr Author Hello everyone,Initial analysis of the new version showed 70% improvement in token/context usage. Added a little more housekeeping, and removes things that made processing more difficult (max_turns), and in one case we got 96% cache hit developing a plugin for Rheem Econet! So, if you have not done so yet, please upgrade to the latest to save on tokens/costs.With kind regards,Michel
17 hours ago17 hr Done. Can I assume that if I have 2 different easy's at 2 different locations, that each eisy ai plugin requires a different api for the configuration?
17 hours ago17 hr 12 minutes ago, Michel Kohanim said:Hello everyone,Initial analysis of the new version showed 70% improvement in token/context usage. Added a little more housekeeping, and removes things that made processing more difficult (max_turns), and in one case we got 96% cache hit developing a plugin for Rheem Econet!So, if you have not done so yet, please upgrade to the latest to save on tokens/costs.With kind regards,Michel@Michel Kohanim Glad to hear this!Do we need to make any adjustments to the Configuration Json? A quick check shows that there is a setting "max_turns": 20?Also, what is the current recommendation for history_token_budget? From reading your posts, it looks like <50000 - 20000?
16 hours ago16 hr Author @DennisC ,Good questions:max_turns is no longer used. It does not hurt if you keep it. My suggestions:Customer mode:max_tokens: 20000history_token_budget: 60000Developer mode:max_tokens: 64000history_token_budget: 100000You can always adjust history_token_budgets if you your conversations are compacted too frequently.With kind regards,Michel
Create an account or sign in to comment