User Story
As an automation or AI-agent user, I want to update individual frontmatter fields through the zn CLI without replacing the complete note or using MCP.
Problem
The CLI supports reading, replacing, appending, and prepending note content, but it cannot safely update individual frontmatter fields.
Task workflows therefore require either:
- the slower MCP update operation; or
- rewriting the complete Markdown note, risking lost body content or unrelated metadata.
Solution
Add an atomic frontmatter update command:
zn meta set "inbox/Tasks/Example.md" \
--set status=in_progress \
--set assignee=author_name \
--set updated=2026-08-31T13:00:00Z \
--unset blocked-by \
--json
Optionally support conditional updates for safe concurrent claims:
zn meta set "inbox/Tasks/Example.md" \
--if status=open \
--set status=in_progress \
--set assignee=author_name
Acceptance Criteria
Contribution
I’d be happy to contribute an implementation if this feature fits the project’s direction.
User Story
As an automation or AI-agent user, I want to update individual frontmatter fields through the
znCLI without replacing the complete note or using MCP.Problem
The CLI supports reading, replacing, appending, and prepending note content, but it cannot safely update individual frontmatter fields.
Task workflows therefore require either:
Solution
Add an atomic frontmatter update command:
Optionally support conditional updates for safe concurrent claims:
Acceptance Criteria
--jsonreturns the updated path and metadataContribution
I’d be happy to contribute an implementation if this feature fits the project’s direction.