@@ -109,6 +109,9 @@ tasks and their descriptions are rendered at the top of the UI and updated based
on database events using some Charm libraries. Change events are underneath the
rendered state, sorted most recent (top) to least recent (bottom).
+This will probably be implemented later, once the LLM-oriented planning commands
+are solid and I see regular success with them.
+
### The format the model sees
It uses individual unicode symbols to represent task statuses. This costs one