feat(chat): display sender identity and specific timestamps in conversation history by seoeaa · Pull Request #2432 · agentscope-ai/CoPaw

seoeaa · 2026-03-27T22:10:40Z

Summary

Display the sender name (agent name or user) above each message bubble in the chat conversation history
Display the specific timestamp of each message alongside the sender name
Fully integrated with the existing custom card system of @agentscope-ai/chat

Changes

Backend (`src/copaw/app/runner/utils.py`)

Added original_timestamp field to message metadata in agentscope_msg_to_message, exposing Msg.timestamp to the frontend via message.metadata.original_timestamp

Frontend types (`console/src/api/types/chat.ts`)

Added MessageMetadata interface with original_name, original_timestamp, original_id fields
Extended Message type with explicit name and metadata fields

Frontend `sessionApi` (`console/src/pages/Chat/sessionApi/index.ts`)

Added CoPawSenderInfoCard custom card constant
buildUserCard now prepends a CoPawSenderInfoCard before AgentScopeRuntimeRequestCard with sender name and timestamp
Added extractSenderInfo helper to extract agent name and timestamp from grouped output messages
buildResponseCard now prepends a CoPawSenderInfoCard before AgentScopeRuntimeResponseCard
Fixed patchLastUserMessage to find AgentScopeRuntimeRequestCard by code field instead of array index 0 (necessary after inserting the sender card first)

Frontend component (`console/src/pages/Chat/components/SenderInfoCard/`)

Created SenderInfoCard React component that renders sender name (bold) and formatted timestamp
Registered as CoPawSenderInfoCard in Chat/index.tsx options cards map

How it works

The CoPawSenderInfoCard card is inserted as the first card in every message (both user and assistant). The card receives { name, role, timestamp } props and renders a compact header line above the message bubble content. Timestamp is formatted using toLocaleString with year/month/day/hour/minute/second precision.

Closes #P0 — Display sender identity and specific timestamps in conversation history (Chat Experience)

…story - Add original_timestamp field to message metadata in agentscope_msg_to_message - Extend Message type to include name and metadata fields - Create CoPawSenderInfoCard component that renders sender name and timestamp - Register CoPawSenderInfoCard as custom card in chat options - Build SenderInfoCard cards before each request/response card in sessionApi - Fix patchLastUserMessage to find AgentScopeRuntimeRequestCard by code

github-actions · 2026-03-27T22:10:52Z

Welcome to CoPaw! 🐾

Hi @seoeaa, this is your 19th Pull Request.

📋 About PR Template

To help maintainers review your PR faster, please make sure to include:

✅ Description - What this PR does and why
✅ Type of Change - Bug fix / Feature / Breaking change / Documentation / Refactoring
✅ Component(s) Affected - Core / Console / Channels / Skills / CLI / Documentation / Tests / CI/CD / Scripts
✅ Checklist:
- Run and pass pre-commit run --all-files
- Run and pass relevant tests (pytest or as applicable)
- Update documentation if needed
✅ Testing - How to test these changes

✅ Local Verification Evidence:

pre-commit run --all-files
# paste summary result

pytest
# paste summary result

Complete PR information helps speed up the review process. You can edit the PR description to add these details.

🙌 Join Developer Community

Thanks so much for your contribution! We'd love to invite you to join the official CoPaw developer group! You can find the Discord and DingTalk group links under the "Developer Community" section on our docs page:
https://copaw.agentscope.io/docs/community

We truly appreciate your enthusiasm—and look forward to your future contributions! 😊

We'll review your PR soon.

gemini-code-assist

Code Review

This pull request introduces a SenderInfoCard component to display sender names and timestamps within the chat interface, along with the necessary backend and frontend changes to support message metadata. Feedback identifies a critical issue where assistant message timestamps are not displayed because metadata is stripped during message conversion. Additionally, it is recommended to remove the unused role property from the SenderInfoCard component and its associated data structures to improve code cleanliness.

gemini-code-assist · 2026-03-27T22:12:32Z

console/src/pages/Chat/sessionApi/index.ts

+function extractSenderInfo(outputMessages: OutputMessage[]): {
+  name: string;
+  timestamp: string | null;
+} {
+  // Use the first message's metadata for the sender name and timestamp
+  for (const msg of outputMessages) {
+    const metadata = (msg.metadata as
+      | {
+          original_name?: string;
+          original_timestamp?: string | null;
+        }
+      | null
+      | undefined);
+    const name =
+      metadata?.original_name ||
+      (msg.name as string | undefined) ||
+      ROLE_ASSISTANT;
+    const timestamp = metadata?.original_timestamp || null;
+    if (name !== ROLE_ASSISTANT || timestamp) {
+      return { name, timestamp };
+    }
+  }
+  return { name: ROLE_ASSISTANT, timestamp: null };
+}


There's a critical issue in this function that will prevent assistant message timestamps from being displayed. The outputMessages this function receives are of type OutputMessage[]. These are created by toOutputMessage, which explicitly sets msg.metadata to null.

Consequently, metadata?.original_timestamp will always be null, and timestamps for assistant messages will not be available.

To fix this, you'll need to ensure that the original message metadata is available when extractSenderInfo is called. One approach is to modify toOutputMessage and the OutputMessage type to not strip metadata, if that doesn't break AgentScopeRuntimeResponseCard. Another way is to refactor convertMessages and buildResponseCard to pass the original Message[] array to extractSenderInfo.

gemini-code-assist · 2026-03-27T22:12:32Z

console/src/pages/Chat/components/SenderInfoCard/index.tsx

+    name: string;
+    role: "user" | "assistant" | string;
+    timestamp: string | null;


The role property is defined in SenderInfoCardProps but it's not used within the component. To improve code clarity and maintainability, it's best to remove unused props. The corresponding role properties passed when constructing CoPawSenderInfoCard in console/src/pages/Chat/sessionApi/index.ts should also be removed.

Suggested change

name: string;

role: "user" | "assistant" | string;

timestamp: string | null;

name: string;

timestamp: string | null;

gemini-code-assist · 2026-03-27T22:12:32Z

console/src/pages/Chat/sessionApi/index.ts

+          name: senderName,
+          role: ROLE_USER,
+          timestamp,


As the role property is not used in the SenderInfoCard component, it can be removed from here.

Suggested change

name: senderName,

role: ROLE_USER,

timestamp,

name: senderName,

timestamp,

gemini-code-assist · 2026-03-27T22:12:32Z

console/src/pages/Chat/sessionApi/index.ts

+          name: senderInfo.name,
+          role: ROLE_ASSISTANT,
+          timestamp: senderInfo.timestamp,


As the role property is not used in the SenderInfoCard component, it can be removed from here.

Suggested change

name: senderInfo.name,

role: ROLE_ASSISTANT,

timestamp: senderInfo.timestamp,

name: senderInfo.name,

timestamp: senderInfo.timestamp,

seoeaa requested a deployment to maintainer-approved March 27, 2026 22:10 — with GitHub Actions Waiting

gemini-code-assist bot reviewed Mar 27, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(chat): display sender identity and specific timestamps in conversation history#2432

feat(chat): display sender identity and specific timestamps in conversation history#2432
seoeaa wants to merge 1 commit intoagentscope-ai:mainfrom
seoeaa:feat/sender-identity-timestamps

seoeaa commented Mar 27, 2026

Uh oh!

github-actions bot commented Mar 27, 2026

Welcome to CoPaw! 🐾

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Mar 27, 2026

Uh oh!

gemini-code-assist bot Mar 27, 2026

Uh oh!

gemini-code-assist bot Mar 27, 2026

Uh oh!

gemini-code-assist bot Mar 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

seoeaa commented Mar 27, 2026

Summary

Changes

Backend (src/copaw/app/runner/utils.py)

Frontend types (console/src/api/types/chat.ts)

Frontend sessionApi (console/src/pages/Chat/sessionApi/index.ts)

Frontend component (console/src/pages/Chat/components/SenderInfoCard/)

How it works

Uh oh!

github-actions bot commented Mar 27, 2026

Welcome to CoPaw! 🐾

📋 About PR Template

🙌 Join Developer Community

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Backend (`src/copaw/app/runner/utils.py`)

Frontend types (`console/src/api/types/chat.ts`)

Frontend `sessionApi` (`console/src/pages/Chat/sessionApi/index.ts`)

Frontend component (`console/src/pages/Chat/components/SenderInfoCard/`)