3 Commits

Include renames

Author	SHA1	Message	Date
Daniele	fc226aacab	fix(view-context): a corner mark on the bubble, not a row under it ... The sent-message proof was a collapsed <details> under the user bubble: a row of height in every bubble that carried view context, for something that is evidence about the message rather than part of it. It also rendered a blank line, since the bubble is white-space: pre-wrap and the template left a newline before the element. Now a faint eye in the bubble's bottom-right corner, revealing the pairs on hover (on focus for keyboard and touch). Deliberately not expandable, so scrolling back through a conversation cannot grow a second layout, and the popover opens downwards rather than over the message it belongs to. The i18n key stays alive as the mark's aria-label; docs and changelog wording updated to match.	2026-08-23 23:36:32 +01:00
Daniele	8361a238c7	fix(view-context): tell the chat agents when not to use it ... With the eye on, the snapshot of what the user is looking at was read as part of the question: asked something unrelated to the open page, the assistant went investigating the folder with a run of tool calls. The transport was right; the prompt never said the block can be irrelevant. New fragment agents/common/view-context.md, included only by the three type: chat agents. It could have gone in harness.md — which all three already include — but harness.md is also included by the two memory-lint agents, which never receive a view. Hence the split, and hence moving the snapshot bullet there too: both halves of the rule now live in one file. The rule names the observed behaviour ("never open, list, search or otherwise investigate ... just because it is there") and keeps the deictic examples, so curing the over-use does not create the under-use. docs/ gains the same rule where the in-app assistant reads it; the CHANGELOG entry for the feature is extended, not duplicated.	2026-08-23 22:04:57 +01:00
Daniele	505f2e95c1	feat(chat): view context — tell the assistant what you're looking at ... An eye next to the paperclip shares what the user has open with their next message: the page, the folder being browsed, the file open in the viewer and any highlighted passage (line numbers where a source view exists), plus which entity a detail page is about. The bag is client-authored {label, value} pairs in English — the backend only clamps (chars, never bytes), neutralizes the harness tag and renders one <system-extra> block per message, deduped consecutively so it appears exactly when the view changed. On by default, per-device toggle, hover/tap to preview, a chip on every sent message; docs/view-context.md for users, an updated harness.md clause for the model.	2026-08-23 20:53:30 +01:00