Skip to content

Open Home briefs with sources and contextual follow-up chat - #2005

Merged
asim merged 1 commit into
mainfrom
codex/brief-details-chat
Oct 3, 2026
Merged

asim merged 1 commit into
mainfrom
codex/brief-details-chat

Conversation

@asim

@asim asim commented Oct 3, 2026

Copy link
Copy Markdown
Member

Home briefs currently discard their source material, so readers must find the headlines again before asking follow-up questions.

Adds More → /brief for the exact edition, grouped story details and supporting source links. The existing hourly generation creates these details in the same call. Opening a page performs no model work. Ask about this brief opens or resumes an account-scoped private conversation with the original source material attached; consulted editions persist beyond rotation. Existing editions remain readable, but their discarded sources cannot be recovered. New source-backed details appear after the next successful generation.

Validation: agent/brief, agent, home and internal/server short tests passed; full Go build passed. Regression coverage includes edition identity across serialization, retained context after cache rotation, source URL filtering, CSRF-protected handoff and account isolation.

Draft: AGENTS.md requires browser layout verification before merge. No browser binary is installed; Playwright Chromium installation failed repeatedly with invalid/truncated download archives. Desktop/mobile screenshots and layout checks remain outstanding. No live model-generation or production deployment verification performed.

@asim
asim marked this pull request as ready for review October 3, 2026 10:24
@asim
asim merged commit 5915750 into main Oct 3, 2026
2 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 3, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-03T10:28:48.627171Z dfd5ecc Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dfd5eccd2c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread agent/console.go
Comment on lines +198 to +202
attached := ""
if ref := thread.Attachment(owner, session); strings.HasPrefix(ref, "brief:") {
if entry, ok := brief.Get(strings.TrimPrefix(ref, "brief:")); ok {
attached = `<section class="record-card"><h2>Brief</h2><p>` + html.EscapeString(entry.Text) + `</p><a href="/brief?id=` + entry.ID() + `">Sources and details</a></section>`
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Refresh the brief card during in-place navigation

When a user opens a brief conversation and then clicks “New conversation,” that link is intercepted by the in-place navigator in internal/app/html/mu.js:492-496, which replaces the transcript, title, and welcome content but never removes or replaces this new brief section. The old card therefore remains visible even though the new conversation has no brief attachment, misleading the user into believing their next question includes that source material; the attachment card needs to participate in the same DOM swap.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant