chihlasm/resolutionflow
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[Feature] Multi-Tree Sessions #68

New Issue
Closed
opened 2026-02-10 16:01:25 +00:00 by chihlasm · 1 comment
chihlasm commented 2026-02-10 16:01:25 +00:00 (Migrated from github.com)
Copy Link

Summary

When troubleshooting reveals the problem is in a different domain, branch into another tree mid-session without losing context. The export captures the entire journey as a unified narrative.

Workflow

  1. Engineer is in "VPN Issues" tree, 5 steps deep
  2. Discovers the actual problem is DNS, not VPN
  3. Clicks "Open Related Tree" → selects "DNS Resolution Issues"
  4. Current tree bookmarked, linked session starts in DNS tree
  5. DNS session completes → returns to VPN tree where they left off
  6. Export shows unified narrative with both trees

Export Example

```

VPN Connection Issues

  1. Verified VPN client version: OK
  2. Checked tunnel status: UP
  3. Tested connectivity through tunnel: FAIL
    → Branched to: DNS Resolution Issues

DNS Resolution Issues (linked)

  1. Ran nslookup: timeout

  2. Checked DNS config: wrong DC

  3. Resolution: Updated DNS to 10.0.0.5

  4. Returned to VPN - retested: PASS

  5. Resolution: DNS misconfiguration causing apparent VPN failure
    ```

Implementation Notes

  • Session model: add `parent_session_id`, `branched_at_node_id`
  • "Open Related Tree" action on any node (tree selector modal)
  • Breadcrumb shows tree chain: VPN > DNS
  • Export renderer handles nested/linked sessions
  • Back button returns to parent session at bookmark point

Sources

  • `docs/plans/2026-02-04-feature-ideas-brainstorm.md` — Idea 7

Priority

Backlog — complex UX, large refactor, high value when ready

## Summary When troubleshooting reveals the problem is in a different domain, branch into another tree mid-session without losing context. The export captures the entire journey as a unified narrative. ## Workflow 1. Engineer is in "VPN Issues" tree, 5 steps deep 2. Discovers the actual problem is DNS, not VPN 3. Clicks "Open Related Tree" → selects "DNS Resolution Issues" 4. Current tree bookmarked, linked session starts in DNS tree 5. DNS session completes → returns to VPN tree where they left off 6. Export shows unified narrative with both trees ## Export Example \`\`\` ## VPN Connection Issues 1. Verified VPN client version: OK 2. Checked tunnel status: UP 3. Tested connectivity through tunnel: FAIL → Branched to: DNS Resolution Issues ## DNS Resolution Issues (linked) 1. Ran nslookup: timeout 2. Checked DNS config: wrong DC 3. Resolution: Updated DNS to 10.0.0.5 4. Returned to VPN - retested: PASS 5. Resolution: DNS misconfiguration causing apparent VPN failure \`\`\` ## Implementation Notes - Session model: add \`parent_session_id\`, \`branched_at_node_id\` - "Open Related Tree" action on any node (tree selector modal) - Breadcrumb shows tree chain: VPN > DNS - Export renderer handles nested/linked sessions - Back button returns to parent session at bookmark point ## Sources - \`docs/plans/2026-02-04-feature-ideas-brainstorm.md\` — Idea 7 ## Priority **Backlog** — complex UX, large refactor, high value when ready
chihlasm commented 2026-03-21 15:26:31 +00:00 (Migrated from github.com)
Copy Link

Deferred — multi-tree sessions add complexity before the single-flow experience is validated with real users. Can revisit post-PMF.

Deferred — multi-tree sessions add complexity before the single-flow experience is validated with real users. Can revisit post-PMF.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
10x-analysis
From 10x product analysis
 backend
FastAPI/Python work
 bug
Something isn't working
 collaboration
Team sharing, escalation, notifications
 database
PostgreSQL/schema changes
 documentation
Documentation updates
 duplicate
This issue or pull request already exists
 enhancement
Improvement to existing feature
 feature
New functionality
 frontend
React work
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 integration
PSA, external service integrations
 intelligence
Analytics, AI, data-driven features
 invalid
This doesn't seem right
 priority: high
Do this soon
 priority: low
Nice to have
 priority: medium
Important but not urgent
 question
Further information is requested
 quick-win
Low effort, high value
 strategic
Long-term strategic bet
 ux
User experience improvements
 wontfix
This will not be worked on
No Label 10x-analysis backend feature frontend priority: low
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
chihlasm
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#68
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?