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

[PR #10321] feat: Sequential numbering for forked session titles (Issue #10105) #13401

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

Original Pull Request: https://github.com/anomalyco/opencode/pull/10321

State: closed
Merged: Yes

What does this PR do?

Instead of four sessions receiving generic session titles, such as New session - 2026-01-22T14:30:00.000Z, sequential numbering will be applied: #2 will be suffixed onto the title the first time it is forked, #3 the second time, and so on.

Before forking

Screenshot 2026-01-23 at 9 51 37 PM

After forking once

Screenshot 2026-01-23 at 9 52 30 PM

After forking twice

Screenshot 2026-01-23 at 9 53 02 PM

Resolves #10105.

How did you verify your code works?

Manual testing: the feature works, but unfortunately, as shown in the screenshots, GLM 4.6's sense of humour does not appear to have improved.

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/10321 **State:** closed **Merged:** Yes --- ### What does this PR do? Instead of four sessions receiving generic session titles, such as `New session - 2026-01-22T14:30:00.000Z`, sequential numbering will be applied: ` #2` will be suffixed onto the title the first time it is forked, ` #3` the second time, and so on. #### Before forking <img width="894" height="777" alt="Screenshot 2026-01-23 at 9 51 37 PM" src="https://github.com/user-attachments/assets/2cda066c-058f-4495-8cdc-6cdcad7629a1" /> #### After forking once <img width="893" height="777" alt="Screenshot 2026-01-23 at 9 52 30 PM" src="https://github.com/user-attachments/assets/a92248cb-a701-4c04-9789-d138a139f253" /> #### After forking twice <img width="897" height="786" alt="Screenshot 2026-01-23 at 9 53 02 PM" src="https://github.com/user-attachments/assets/983c5318-be95-400a-b266-103209d63dc7" /> Resolves #10105. ### How did you verify your code works? Manual testing: the feature works, but unfortunately, as shown in the screenshots, GLM 4.6's sense of humour does not appear to have improved.
yindo added the pull-request label 2026-02-16 18:18:15 -05:00
yindo closed this issue 2026-02-16 18:18:15 -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#13401
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?