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

[Feature] Mirror parent session name to child sessions #3564

New Issue
Open
opened 2026-02-16 17:40:40 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:40:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @fglogan on GitHub (Dec 15, 2025).

Originally assigned to: @thdxr on GitHub.

Summary

When a session is renamed, child sessions should reflect the parent session name with a suffix (e.g., genesis-analyzer parent spawns genesis-analyzer|cs-1, genesis-analyzer|cs-2, etc.).

Problem

Currently, child sessions spawned by the Task tool have generic or auto-generated names that don't indicate which parent session they belong to. This makes it difficult to:

  1. Identify which child sessions relate to which work context
  2. Navigate between related sessions
  3. Understand session hierarchy at a glance

Proposed Solution

Naming Convention

When a parent session is named <session-name>, child sessions should be named:

  • <session-name>|cs-1
  • <session-name>|cs-2
  • etc.

Or alternatively:

  • <session-name> [1]
  • <session-name> [2]

Behavior

  1. On parent rename: All existing child sessions update their names to reflect the new parent name
  2. On child spawn: New child session automatically inherits parent name with incremented suffix
  3. Session list display: Show hierarchy clearly, perhaps with indentation: 
    genesis-analyzer
  ├─ genesis-analyzer|cs-1 (completed)
  ├─ genesis-analyzer|cs-2 (running)
  └─ genesis-analyzer|cs-3 (pending)

Use Case

When working on multiple projects simultaneously, users may have:

  • genesis-analyzer session with 3 child tasks
  • opencode-plugin session with 2 child tasks

Without name mirroring, it's unclear which child sessions belong to which context.

Additional Context

This improves the UX when using agents heavily, as the Task tool spawns many child sessions that currently lack clear association with their parent context.

Originally created by @fglogan on GitHub (Dec 15, 2025). Originally assigned to: @thdxr on GitHub. ## Summary When a session is renamed, child sessions should reflect the parent session name with a suffix (e.g., `genesis-analyzer` parent spawns `genesis-analyzer|cs-1`, `genesis-analyzer|cs-2`, etc.). ## Problem Currently, child sessions spawned by the Task tool have generic or auto-generated names that don't indicate which parent session they belong to. This makes it difficult to: 1. Identify which child sessions relate to which work context 2. Navigate between related sessions 3. Understand session hierarchy at a glance ## Proposed Solution ### Naming Convention When a parent session is named `<session-name>`, child sessions should be named: - `<session-name>|cs-1` - `<session-name>|cs-2` - etc. Or alternatively: - `<session-name> [1]` - `<session-name> [2]` ### Behavior 1. **On parent rename**: All existing child sessions update their names to reflect the new parent name 2. **On child spawn**: New child session automatically inherits parent name with incremented suffix 3. **Session list display**: Show hierarchy clearly, perhaps with indentation: ``` genesis-analyzer ├─ genesis-analyzer|cs-1 (completed) ├─ genesis-analyzer|cs-2 (running) └─ genesis-analyzer|cs-3 (pending) ``` ## Use Case When working on multiple projects simultaneously, users may have: - `genesis-analyzer` session with 3 child tasks - `opencode-plugin` session with 2 child tasks Without name mirroring, it's unclear which child sessions belong to which context. ## Additional Context This improves the UX when using agents heavily, as the Task tool spawns many child sessions that currently lack clear association with their parent context.
yindo commented 2026-02-16 17:40:40 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 15, 2025):

This issue is related to existing discussions about session management and naming. Please check:

  • #4040: Session auto naming - discusses automatic session naming functionality
  • #5578: Custom command to cycle between child sessions - proposes alternatives for navigating child sessions
  • #3291: Navigation to parent session from child/subagent sessions - discusses parent-child navigation keybinds
  • #4133: Use a cheap model to name sessions - discusses session naming efficiency

These issues cover related aspects of session hierarchy and naming conventions. Feel free to cross-reference for context on how child sessions are managed.

@github-actions[bot] commented on GitHub (Dec 15, 2025): This issue is related to existing discussions about session management and naming. Please check: - #4040: Session auto naming - discusses automatic session naming functionality - #5578: Custom command to cycle between child sessions - proposes alternatives for navigating child sessions - #3291: Navigation to parent session from child/subagent sessions - discusses parent-child navigation keybinds - #4133: Use a cheap model to name sessions - discusses session naming efficiency These issues cover related aspects of session hierarchy and naming conventions. Feel free to cross-reference for context on how child sessions are managed.
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
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#3564
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?