feature(client): summary-first SCT events in CLI and web UI#5
Open
CodeLieutenant wants to merge 4 commits into
Open
feature(client): summary-first SCT events in CLI and web UI#5CodeLieutenant wants to merge 4 commits into
CodeLieutenant wants to merge 4 commits into
Conversation
Dispatch a bounded, best-effort summarization pass from the event-similarity worker: sanitize and BGE-embed through a shared EventEmbedder, then hand ERROR/CRITICAL events to an OpenAI-backed Summarizer whose result is written to the new sct_event.summary column. Summarization runs on a capped thread pool with a backlog gate and can never break embedding. Summary prompts are externalized to versioned files.
Add an offline harness that sweeps prompts and models over real SCT events, scores each summary with an LLM judge (coverage/faithfulness/conciseness), tracks token-based cost, compression and latency, and renders an HTML report. Optionally collapses near-duplicate events through the worker's embedder so the sweep sees the canonical set production would summarize. Regenerates uv.lock for the new openai/tiktoken/chromadb dependencies.
Add a Summary field to the SCT event model and render it in `argus run events` where present, falling back to the original message so output is never blank. A --raw flag forces the original; JSON output is additive and carries both message and summary. Marks the CLI plan phase done.
Add an optional AI-summary view to SctEvent: when an event carries a summary, a labelled toggle switches the body between the original message and the summary, defaulting to original-first. The chosen default is a per-user preference in localStorage. Events without a summary render exactly as before, and copy-to-clipboard always copies the original.
CodeLieutenant
force-pushed
the
feat/event-summarization-eval
branch
from
July 23, 2026 15:45
976bee8 to
4f4b18a
Compare
CodeLieutenant
force-pushed
the
feat/sct-event-summary-ui
branch
from
July 23, 2026 15:45
ffb94e5 to
3764708
Compare
CodeLieutenant
force-pushed
the
feat/event-summarization-eval
branch
5 times, most recently
from
July 24, 2026 12:46
6f8150f to
5447b55
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
1 participant
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.
Extracted from scylladb#1048 to keep the summarization backend (worker + eval harness) separate from the user-facing surfaces.
What
argus run events): renders the AIsummaryfield summary-first, with--rawto force the original message. JSON output is additive (summaryalongsidemessage).SctEvent.svelte): per-event toggle between original and AI summary, an "AI summary" badge, and a per-user default persisted in localStorage (original-first). No summary → renders exactly as before; the copy button still copies the original message.Stacking
Based on
feat/event-summarization-eval(the scylladb#1048 backend branch) so summaries render end-to-end here. Retarget the base tomasteronce scylladb#1048 merges. Both surfaces are additive and inert without the backend — the CLI falls back tomessageand the toggle only appears whenevent.summaryexists.