Repository navigation
feat(protocol,sdk,nuxt): context part — what a message is about, as a plaque - #4
Open
dmitriyzhuk wants to merge 1 commit into
Open
dmitriyzhuk wants to merge 1 commit into
dmitriyzhuk wants to merge 1 commit into
Conversation
… a plaque
A message often carries what it is about beside what it says: the block of a
page the person clicked, the record they had open. Integrators had nowhere to
put that but the text, so the person later read their own message back with
notation in it — "[Block n7 · Hero: …] make it shorter".
A new part type says it instead:
{ "type": "context", "label": "Hero", "text": "Your roof fixed in a day" }
The Nuxt layer and the SDK draw it as a plaque above the words — label, then
the excerpt in quotes, one line, truncated, the full text in the tooltip — on
either side of the conversation. The hub forwards parts as-is, so it needs
nothing but the type. Which context to attach, and how to carry it to an agent
that takes plain text, stays the integrator's (PROTOCOL.md § Context Part).
First user: Bonsite's chat (BONS-157), which writes the block the owner
pointed at into the message for its agent and reads it back out of the
history as this part.
SDK typecheck reports the same three errors as main, none new; SDK build
passes. No version bump: left for the release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
A new message part type,
context: what a message is about, beside what it says — the block of a page the person clicked, the record they had open.{ "type": "context", "label": "Hero", "text": "Your roof fixed in a day" }docs/PROTOCOL.md— § Context Part.nestjs/domain/bridle.types.ts,sdk/src/types.ts,nuxt/stores/bridle.ts— the type (hub forwards parts as-is; nothing else changes there).nuxt/components/bridle/Message.vueandsdk/src/BridleChat.ce.vue— drawn as a one-line plaque above the words: label, then the excerpt in quotes, truncated, full text in the tooltip. Works on both user and assistant bubbles (border incurrentColor).Why
Integrators had nowhere to put context but the text, so the person read their own message back with notation in it (
[Block n7 · Hero: …] make it shorter). Bridle only draws the part; which context to attach and how to carry it to an agent that takes plain text stays the integrator's.First user: Bonsite's chat (BONS-157), which carries a copy of the Nuxt layer with this change.
Checks
npm run typecheck: the same three errors asmain(lines 940, 1443, 1567 → pre-existing), none new.npm run build: passes.Message.vuechange is exercised in a browser inside Bonsite's copy (BONS-157).No version bump — left for the release.
🤖 Generated with Claude Code