From b48751f71af605c35e81a10081aa272fec927df4 Mon Sep 17 00:00:00 2001 From: leemour Date: Wed, 18 Nov 2026 08:49:07 +0100 Subject: [PATCH] docs(people): agent_merges is set in the config file, not by a command memo has no `config set` command (only show, migrate and unset), so the line that showed `memo config set agent_merges propose` sent readers to a command that fails. It now links the agent_merges section of the configuration page, which shows the setting in the config file. Co-Authored-By: Claude Opus 5.5 --- docs/people.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/people.md b/docs/people.md index adab5123..d2f76ef1 100644 --- a/docs/people.md +++ b/docs/people.md @@ -129,7 +129,7 @@ different sources, and for a phone at least one of them a messenger or a call. A records of one source share, a company's line, a role address, a name, a CRM's word or a phrase from a chat is not strong, and the link waits for you. Memo keeps which agent merged, in which run, why and on what evidence. `memo people review --kind merged` lists the agents' merges still in place, and `memo people unmerge ` undoes one. Set `agent_merges` to `propose` -(`memo config set agent_merges propose`) and every agent's link waits for you instead. +in [the config file](configuration.md#agent_merges) and every agent's link waits for you instead. ```sh memo people review