Skip to content

Add persistence for task pane resize positions#81

Merged
bborn merged 2 commits intomainfrom
task/165-make-the-task-pane-positions-peristence
Jan 10, 2026
Merged

Add persistence for task pane resize positions#81
bborn merged 2 commits intomainfrom
task/165-make-the-task-pane-positions-peristence

Conversation

@bborn
Copy link
Copy Markdown
Owner

@bborn bborn commented Jan 10, 2026

Summary

  • Persist task detail pane height (vertical split) and shell pane width (horizontal split) when resized
  • Settings are stored in the database and applied to all task detail views
  • Positions are saved when hiding panes, killing sessions, or leaving detail view

Test plan

  • Open a task detail with active session
  • Drag pane borders to resize
  • Press q to go back, then reopen the task
  • Verify pane positions are restored
  • Kill session with k and verify positions are still saved

🤖 Generated with Claude Code

bborn and others added 2 commits January 9, 2026 23:38
- Add task_types table with name, label, and instructions fields
- Add Task Types section in settings UI for managing types
- Support template placeholders: {{title}}, {{body}}, {{project}}, etc.
- Load task types dynamically in forms and executor
- Add 'task restart' and 'task daemon restart' commands
- Keep tmux windows after task completion for review
- Fix false positive branch merge detection for new branches

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Save the detail pane height and shell pane width when the user resizes
them by dragging the tmux pane borders. The positions are stored in the
database settings and restored when opening any task detail view.

- Add SettingShellPaneWidth config constant
- Add getShellPaneWidth() and saveShellPaneWidth() functions
- Save pane positions in breakTmuxPanes() and killTmuxSession()
- Use saved shell pane width when creating the horizontal split

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@bborn bborn merged commit 110b770 into main Jan 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant