Repository navigation
feat(vault): allow editing intent body via intent update - #89
Merged
Merged
Conversation
geekgonecrazy
approved these changes
Jun 23, 2026
`atomic vault intent update` previously only updated frontmatter (status, assignee, priority, title); the Markdown body was always preserved unchanged. Filling in an intent's Problem / Acceptance Criteria / Scope / TODOs required editing the materialized file on disk and running `vault sync`. Add a `content` field to `IntentUpdateOptions` and two CLI flags so the body can be set directly: - `--body <STRING>` to replace the body inline - `--body-stdin` to pipe the body from a file (e.g. `cat plan.md | ...`) The flags are mutually exclusive. When neither is given, the body is left unchanged (existing behavior). Updating with no fields at all now returns a clear "nothing to update" error instead of a no-op. Mirrors the stdin pattern of `vault memory write`. No immutability gate is added — vault intents are editable work documents, consistent with the existing edit-on-disk + `vault sync` path.
vinceblock99
force-pushed
the
chore/intent-update-body
branch
from
June 23, 2026 13:49
87473b1 to
efa4015
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
--bodyand--body-stdintoatomic vault intent update.Why
Intent bodies previously required editing the materialized Markdown file and running vault sync.
Safety
Body edits are allowed directly while an intent is backlog and unlinked. Once it has started or is linked to a goal, rewriting the body requires
--force. Metadata updates remain unaffected.Test
cargo test -p atomic-repository intent_update --libcargo check -p atomic-clicargo clippy -p atomic-repository -p atomic-cli -- -D warnings