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

Save session as custom tree #17

New Issue
Closed
opened 2026-02-03 04:41:37 +00:00 by chihlasm · 1 comment
chihlasm commented 2026-02-03 04:41:37 +00:00 (Migrated from github.com)
Copy Link

After completing a session with custom steps, offer to save as tree:

  • POST /api/v1/sessions/{id}/save-as-tree endpoint
  • Prompt user after session completion (if custom steps were added)
  • Create user_tree from session path + custom steps
  • Allow user to name and edit before saving

Reference: PHASE-2.5-PERSONAL-BRANCHING.md

After completing a session with custom steps, offer to save as tree: - [ ] POST /api/v1/sessions/{id}/save-as-tree endpoint - [ ] Prompt user after session completion (if custom steps were added) - [ ] Create user_tree from session path + custom steps - [ ] Allow user to name and edit before saving Reference: PHASE-2.5-PERSONAL-BRANCHING.md
chihlasm commented 2026-02-08 04:07:31 +00:00 (Migrated from github.com)
Copy Link

✅ Implemented save session as custom tree feature. Backend converts session path and custom steps into linear tree structure with fork tracking. Frontend includes SaveSessionAsTreeModal with smart default naming and draft/published choice. Sessions can be saved directly to tree editor for customization. 14 tests passing. Completed in commits c7b2c59 and 996b664.

✅ Implemented save session as custom tree feature. Backend converts session path and custom steps into linear tree structure with fork tracking. Frontend includes SaveSessionAsTreeModal with smart default naming and draft/published choice. Sessions can be saved directly to tree editor for customization. 14 tests passing. Completed in commits c7b2c59 and 996b664.
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 backend feature frontend priority: low
Milestone
No items
No Milestone Phase 2.5
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#17
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?