Repository navigation
v0.55.3
AnythingMCP 0.55.3: learning topics with their own folders
A small feature release for learning projects, plus everything merged since 0.55.2. It includes one additive database migration.
Learning projects (#1770, #1771)
- Topics set by an admin. You can list a project's topics when you create it, or add one later on the project's Topics tab. You can also rename a topic and give it a folder of its own. The member's assistant files lessons under these topics first, and only starts a new topic when none fits. A member who covers two areas can now have each area in its own folder, limited to its own roles.
- Renaming a topic renames its skills; the published skill gets a new version.
- Moving a topic moves its draft and published skills.
- Reminder after read-only tools. The reminder to call
learning_recordwas only added after tools that change something. It is now also added after read-only tools, at most every ten minutes. A member who mostly looks things up (reports, price lists, read-only SQL) is reminded too. - Members always see their own drafts. Before, a member couldn't see their own drafts in a folder limited to roles they lack. Published skills still follow the folder's role limit.
- API:
POST /api/learning/projectsacceptstopics.POST /api/learning/projects/{id}/topicsadds a topic.PATCH /api/learning/topics/{id}renames, rewords or moves one.- All three need a workspace admin.
Also in this release
- Tools card: after an import, it shows what was imported. A blocked OpenAPI spec download now explains why (#1768).
- Cloud: follow-up of the running trial and onboarding tests (#1769). Self-hosted is unchanged.
- CLI 0.1.8: knows the two new topic routes.
Upgrading
docker compose pull, thendocker compose up -d.- Migration
20261117120000_learning_topic_folderruns at start. It adds a nullablefolder_idcolumn, an index and a foreign key tolearning_topics. Existing topics keep using their project's folder.