From f5dc7648bf4f6c900b9a21d71f482d2bea090ff9 Mon Sep 17 00:00:00 2001 From: Amolith Date: Thu, 23 Oct 2025 21:44:18 -0600 Subject: [PATCH] docs: mention m subcommand --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 2b6cf1d6cac86197d4e329a85c56d35c393c2174..2ec9abec9a2f12440434a958c031beb198f733ab 100644 --- a/README.md +++ b/README.md @@ -113,11 +113,12 @@ events. ### Event rendering -The interactive, human-focused sub-commands are for watching these events and -the resulting list as they change in real-time-ish. The goal and description and -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). +The interactive, human-focused sub-commands (for now, just `m` for `m`onitor), +are for watching the events and the resulting list as they change in +real-time-ish. The goal and description and 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.