Hermes can now break a big job into phases, then manage the individual tasks underneath each one. Its todo system is no longer limited to one long flat checklist. So instead of: ☐ Build homepage ☐ Add authentication Hermes can now structure the same work like this: ► Build homepage ↳ Create hero section ↳ Add navigation ↳ Build pricing section ↳ Add contact form ► Add authentication ↳ Create sign-in page ↳ Add account creation ↳ Connect auth provider ↳ Handle password reset That is the actual change. A task can now become a parent with its own nested subtasks underneath it. So when Hermes is working through something larger, it no longer has to flatten every piece of work into one list. It can keep the major phases clear, break each one into the work required underneath it, and manage those subtasks individually as the job progresses. And this is more than visual organization. Hermes keeps the parent/subtask relationships intact as work gets updated. If context is compressed during a longer session, that hierarchy is preserved too, so unfinished subtasks still retain the larger task they belong to. Even a completed parent can remain visible while work underneath it is still active. That makes the todo system much more useful for larger coding jobs, research, content production, automations, migrations, business workflows, and anything else where one task really contains several smaller ones.