anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #1770] [MERGED] Feat: Add Agent Name in the LLM Response Footer (and re-order it) #10055

New Issue
Closed
opened 2026-02-16 18:14:37 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:14:37 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/anomalyco/opencode/pull/1770
Author: @spoons-and-mirrors
Created: 8/9/2025
Status: ✅ Merged
Merged: 8/9/2025
Merged by: @adamdotdevin

Base: dev ← Head: feat/new-llm-response-footer

📝 Commits (2)

  • 50d3335 feat(llm-footer): add agent name and color to the LLM response footer and reordered it
  • 2e29f69 refactor(color): refactor agent color handling to use GetAgentColor utility function for message and status

📊 Changes

4 files changed (+81 additions, -31 deletions)

View changed files

📝 packages/tui/internal/components/chat/message.go (+30 -2)
📝 packages/tui/internal/components/status/status.go (+7 -23)
📝 packages/tui/internal/util/color.go (+23 -1)
📝 packages/web/src/components/share/part.tsx (+21 -5)

📄 Description

Summary

Commit 1 - Add agent name and color to LLM response footer:

Display agent mode information in chat messages with consistent color coding that matches the status bar
image
image

The color on the Agent name adds some flare and is a neat visual anchor when scrolling through the conversation without being too obnoxious

Commit 2 - Refactor agent color handling:

The second commit refactors the color handling logic by extracting the agent color mapping into a centralized GetAgentColor utility function. While this refactor improves maintainability by reducing (future) code duplication, it is not necessary for the core functionality, but provides some code organization and centralized this color handling in the color utils file.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/anomalyco/opencode/pull/1770 **Author:** [@spoons-and-mirrors](https://github.com/spoons-and-mirrors) **Created:** 8/9/2025 **Status:** ✅ Merged **Merged:** 8/9/2025 **Merged by:** [@adamdotdevin](https://github.com/adamdotdevin) **Base:** `dev` ← **Head:** `feat/new-llm-response-footer` --- ### 📝 Commits (2) - [`50d3335`](https://github.com/anomalyco/opencode/commit/50d333521d8fac61586214514d33f8d62f68c091) feat(llm-footer): add agent name and color to the LLM response footer and reordered it - [`2e29f69`](https://github.com/anomalyco/opencode/commit/2e29f696ae88f0b0563aa086f3972a75672dc1ea) refactor(color): refactor agent color handling to use GetAgentColor utility function for message and status ### 📊 Changes **4 files changed** (+81 additions, -31 deletions) <details> <summary>View changed files</summary> 📝 `packages/tui/internal/components/chat/message.go` (+30 -2) 📝 `packages/tui/internal/components/status/status.go` (+7 -23) 📝 `packages/tui/internal/util/color.go` (+23 -1) 📝 `packages/web/src/components/share/part.tsx` (+21 -5) </details> ### 📄 Description ## Summary #### Commit 1 - Add agent name and color to LLM response footer: Display agent mode information in chat messages with consistent color coding that matches the status bar <img width="223" height="20" alt="image" src="https://github.com/user-attachments/assets/642091c6-3ff0-44d4-b8cc-980e4ef7fbb6" /> <img width="277" height="19" alt="image" src="https://github.com/user-attachments/assets/4eb0ae45-9ae6-4454-b241-e59d40036a1b" /> The color on the Agent name adds some flare and is a neat visual anchor when scrolling through the conversation without being too obnoxious #### Commit 2 - Refactor agent color handling: The second commit refactors the color handling logic by extracting the agent color mapping into a centralized `GetAgentColor` utility function. While this refactor improves maintainability by reducing (future) code duplication, it is not necessary for the core functionality, but provides some code organization and centralized this color handling in the color utils file. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 18:14:37 -05:00
yindo closed this issue 2026-02-16 18:14:37 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#10055
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?