[Question/Suggestion] Regarding API Call Notebook Optimization and Other Issues

  1. For questions about the transit API, please refer to: 【建议/求助】关于gcli2API配置填写问题求助,以及几点优化建议 - #3 by gbye134340_89335 2. From the error screenshot, the AI-generated fields are not fields of our built-in tools, which may be due to AI malfunction or some inferior reverse-engineered interfaces. The [Tool Test] page in the menu at the top right of the chat page can be used for convenient testing. 3. We currently use the Android standard interface to obtain the calendar ID and have tested it on our test machines. Some manufacturers may have different interfaces, but we do not have testing equipment. Since there are not many users, we do not plan to purchase equipment for optimization in the short term. 4. The memory you understand is storage, not the actual runtime memory used. One area that can be optimized is to disable permanent memory. Other areas cannot be optimized, which is the main reason we were reluctant to add regex and HTML rendering before. 5. b212 upgraded the underlying implementation of full-text search (fts5), and for upgraded users, errors may occur due to the presence of old format data tables. This issue will be fixed in b213 later. 6. The issue with the knowledge base logs has been fixed, but errors will still occur for old role cards. 7. Voice reading does not use a filtering mechanism but instead has special marker symbols set. Set it in the role - [Read Text Content] section.