Repository navigation
Stamp source=opencode on recorded messages - #47
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe change standardizes Honcho metadata across assistant, user, and tool activity records. Each record now uses ChangesMetadata normalization
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Feature Suggested reviewers: Merge Risk: ⚪ Minimal · up to The change standardizes message metadata while retaining lifecycle event details across assistant, user, and tool records. No current production impact or merge-blocking risk is evident. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
A rabbit sees the records align Comment |
Cover user prompt, tool activity and assistant flush, which now go through shared core functions on main, and keep the hook name under `event`. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Merged main into this branch (a merge rather than a rebase, to avoid force-pushing the fork) and resolved the conflicts: the 1.x hook bodies now delegate to shared core functions, so the stamp moved there. Also stamped the sites added since this PR was opened: user prompt capture, tool activity capture, and assistant flush. The import path still stamps |
Live message paths currently store the triggering event name (chat.message, tool.execute.after, event.message.updated) in metadata
source, while the import path stampsopencode-sdk— so no single key identifies this integration as the writer, and operators sharing one Honcho workspace across integrations cannot census writers. This setssource: "opencode"on all three live paths and preserves the event name under a neweventkey (no information lost). Suite: 25 pass.Part of a four-repo batch proposing the same
source: <integration>convention in codex-honcho, claude-honcho, and cursor-honcho so a singlemetadata->>'source'census separates writers.Summary by CodeRabbit