feat(ui): launch session from locked composer #156
No reviewers
Labels
No labels
backend
bug
chore
duplication
effort:complex
effort:medium
effort:trivial
enhancement
frontend
fullstack
priority:high
ready-for-agent
refactor
security
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
dries/ocman!156
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/launch-session-from-locked-composer"
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?
When no live OpenCode instance is available, the composer is locked and previously only showed a passive "No live connection" hint. The only ways to launch were the sidebar/header button, clicking the locked area (undiscoverable), or the disconnected toast.
This adds a green Launch session button directly in the locked composer bar. It calls the existing
handleLaunchOpencode(spawnsopencode --port 0in tmux) directly, shows "Launching…" while in flight, and skips the intermediate disconnected toast. Clicking the disabled area still works as a fallback.Changes
Composer.tsx— newlaunchingprop; the disabled-state hint becomes a real Launch button whenonLaunchRequestis wired.SessionDetail.tsx—onLaunchRequestnow calls the real launcher directly; removed the now-deadhandleLaunchHintClick.Composer.css—.oc-bar-launchstyling.Coverage ratchet: ✅ pass
Tolerance: -0.1%. Baseline stored on
gh-pages.