Repository navigation
0.131.23
·
224 commits
to main
since this release
Added
memo config showlists every setting with its value, its default and whether the file sets it, andmemo config migratewrites the missing ones into the file at their defaults. You then find and edit every setting in
config.json,"agent_decisions": falseincluded, without the docs. Your values, their order and keys memo does
not know stay. Every write memo already makes to the file (folders add,mail add,jobs start, mail rules) adds
the missing settings too; a plain read never rewrites the file.
Fixed
memo mail reviewnames memo's own commands in its next steps:memo messages acknowledge … --source email:<account>, so an agent runs the step as given. It offers no whole-thread read, which memo does not mount.
Changed — may break callers
- Only you decide meeting and mail findings, on every path, whatever
agent_decisionsandpermissionssay
(cli-core 0.563.0). An agent'smeetings actions confirmorreject,review confirmoractions confirmof a
batch is refused withproposal.owner-only, its own batch included. memo tasks update <task> --project <key>moves the task's subtasks with it instead of refusing; each takes a
new key there and the old keys still find them (cli-core 0.563.0). A subtask still moves alone only with
--parent none.