Feat/tag agent version user - #309
Merged
Merged
Conversation
When a source write carries `x-da-initiator: mcp`, flag daCtx.users (after the permission check) so the recorded version/audit user reads "email (agent)". getUsersForMetadata appends the marker; collab sync is unaffected since 'mcp' != 'collab'. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
|
||
| return users.map((user) => ({ email: user.email })); | ||
| return users.map((user) => ({ | ||
| email: user.isAgentic ? `${user.email} (agent)` : user.email, |
There was a problem hiding this comment.
@hannessolo Adapting the email string to include agent feels a bit counterintuitive to me. Could we instead just update the metadata to include the info that it is done by an agent similar to the isAgentic above, and then leave it up to the UI to interpret and display as needed? If we adapt the email like this, it would also complicate any UI scenarios that would require email as-is. Wdyt?
anfibiacreativa
approved these changes
Aug 4, 2026
Keep the recorded author email clean and add a structured `isAgentic` flag to the users JSON; the UI appends "(agent)" when present. Collapse logic is unchanged, so agent and human edit sessions still group together. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
sharanyavinod
approved these changes
Aug 4, 2026
hannessolo
added a commit
that referenced
this pull request
Aug 4, 2026
Re-triggers the release that was skipped when #309 squash-merged without a conventional `feat:` prefix (it landed as "Feat/tag agent version user"). No code change — the feature is already on main; this cuts the release. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Collaborator
|
🎉 This PR is included in version 1.14.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
4 participants
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.
Tag requests from MCP as agentic in history entry