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

[FEATURE]: Show end time after agent finishes working on a prompt #2723

New Issue
Closed
opened 2026-02-16 17:36:58 -05:00 by yindo · 8 comments
yindo commented 2026-02-16 17:36:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @erf on GitHub (Nov 9, 2025).

Originally assigned to: @val-2 on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

A few times i've fired off a prompt and let the agent do some work, whilst i go do something else, it would be useful to see the Finish time the agent finished working on the prompt.

Perhaps some other meta data would be useful too at the end of the work, like tokens used (for the specific prompt), lines of text written etc.

Originally created by @erf on GitHub (Nov 9, 2025). Originally assigned to: @val-2 on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request A few times i've fired off a prompt and let the agent do some work, whilst i go do something else, it would be useful to see the `Finish time` the agent finished working on the prompt. Perhaps some other meta data would be useful too at the end of the work, like tokens used (for the specific prompt), lines of text written etc.
yindo added the discussion label 2026-02-16 17:36:58 -05:00
yindo closed this issue 2026-02-16 17:36:58 -05:00
yindo commented 2026-02-16 17:36:58 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 9, 2025):

We have all that data but how would u want it to be surfaced?

@rekram1-node commented on GitHub (Nov 9, 2025): We have all that data but how would u want it to be surfaced?
yindo commented 2026-02-16 17:36:58 -05:00
Author
Owner
Copy Link
Copy Source

@erf commented on GitHub (Nov 9, 2025):

You could just start by adding the the finish time in parenthesis in a dimmed text like so:

Build claude-sonnet-4.5 (Finished 22:15:10)

or under, like so:

Build claude-sonnet-4.5
Completed 22:15:10

I think local 24h time is probably enough as we don't wait too long for it to process. If it is an old session (>24h), we could use a local date format type: Completed 10.11.25 22:15.

@erf commented on GitHub (Nov 9, 2025): You could just start by adding the the finish time in parenthesis in a dimmed text like so: ``` Build claude-sonnet-4.5 (Finished 22:15:10) ``` or under, like so: ``` Build claude-sonnet-4.5 Completed 22:15:10 ``` I think local 24h time is probably enough as we don't wait too long for it to process. If it is an old session (>24h), we could use a local date format type: Completed 10.11.25 22:15.
yindo commented 2026-02-16 17:36:59 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 9, 2025):

Ah okay yeah thats reasonable

@rekram1-node commented on GitHub (Nov 9, 2025): Ah okay yeah thats reasonable
yindo commented 2026-02-16 17:36:59 -05:00
Author
Owner
Copy Link
Copy Source

@val-2 commented on GitHub (Nov 18, 2025):

Hi! I’d like to work on this issue if it’s still available.
I’ve read the contributing docs and wanted to leave a comment here as suggested.
Let me know if you'd like to see it implemented as erf suggested, and whether it should go on the same line or a new one.

@val-2 commented on GitHub (Nov 18, 2025): Hi! I’d like to work on this issue if it’s still available. I’ve read the contributing docs and wanted to leave a comment here as suggested. Let me know if you'd like to see it implemented as erf suggested, and whether it should go on the same line or a new one.
yindo commented 2026-02-16 17:36:59 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 18, 2025):

@val-2 hey we would appreciate that!

I'm not really sure what would look best but maybe try a few variations maybe even some without words and then decide what you think looks good? I'm sure once u have the code setup moving to a newline vs changing a word should all be very simple

@rekram1-node commented on GitHub (Nov 18, 2025): @val-2 hey we would appreciate that! I'm not really sure what would look best but maybe try a few variations maybe even some without words and then decide what you think looks good? I'm sure once u have the code setup moving to a newline vs changing a word should all be very simple
yindo commented 2026-02-16 17:36:59 -05:00
Author
Owner
Copy Link
Copy Source

@val-2 commented on GitHub (Nov 18, 2025):

Got it, thanks!
I’ll experiment with a few variations and share the best options

@val-2 commented on GitHub (Nov 18, 2025): Got it, thanks! I’ll experiment with a few variations and share the best options
yindo commented 2026-02-16 17:36:59 -05:00
Author
Owner
Copy Link
Copy Source

@val-2 commented on GitHub (Nov 19, 2025):

I think with parentheses and no words looks better for consistency with the initial user message:

Image

For messages older than the current day, either keep showing only the time as it is now or introduce a new function in Locale that returns date.toLocaleString() when the message date doesn’t match the current day. Using that for both user and agent message looks something like this:

Image

Let me know what you would prefer

@val-2 commented on GitHub (Nov 19, 2025): I think with parentheses and no words looks better for consistency with the initial user message: <img width="687" height="650" alt="Image" src="https://github.com/user-attachments/assets/31000b72-0c56-4d97-83a8-222496a89a80" /> For messages older than the current day, either keep showing only the time as it is now or introduce a new function in Locale that returns date.toLocaleString() when the message date doesn’t match the current day. Using that for both user and agent message looks something like this: <img width="563" height="612" alt="Image" src="https://github.com/user-attachments/assets/b0b63ee3-dc85-42d9-9e6c-0eead0ac3de7" /> Let me know what you would prefer
yindo commented 2026-02-16 17:36:59 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 19, 2025):

I like this this looks good

@rekram1-node commented on GitHub (Nov 19, 2025): I like this this looks good
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 discussion
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#2723
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?