Objective
Make Launchplane-backed Every Code sessions robust enough for regular use: isolated worktrees, readable session identity, preview automation, PR feedback, and clean lifecycle handling.
Finish Line
Every Code runs isolated, visible, preview-aware local sessions with clean close and PR feedback
Current Status
State: Done. Launchplane-side Every Code automation lifecycle is implemented and all sub-issues are closed. The remaining DUI visibility problem is a Code-side detached TUI registration bug tracked as cbusillo/code#29.
Next action: Work cbusillo/code#29 to make detached tmux Code sessions register with remote inbox/DUI before attach.
Blocked by: cbusillo/code#29 for the DUI visibility improvement; Launchplane workstream itself is complete.
Last verified: 2026-05-06 with all seven sub-issues closed, live webhook sync completed, local worker running from the main Launchplane checkout, and failed DUI smoke routed to cbusillo/code#29.
Scope
- Launchplane worker lifecycle and GitHub webhook behavior.
- Every Code prompt/context and worktree setup.
- PR preview label automation using Launchplane's existing preview lifecycle.
- PR feedback ingestion and worker resume/injection.
- Session origin metadata so UIs can distinguish automated sessions.
Acceptance Criteria
- Every Code runs from a dedicated per-request worktree and never clobbers an active checkout.
- The first prompt instructs Code to read the issue body and all comments before acting.
- Automated sessions are identifiable to Code/DUI users without relying on title text alone.
- PRs created by Every Code can request Launchplane previews when the repo supports previews.
- PR comments/reviews can guide follow-up work on the same request.
- Closing/merging the relevant issue/PR causes the local worker to close the local Code session cleanly.
Relationships
Parent plan for the focused implementation issues in this workstream.
Validation
Use unit tests for worker state, webhook classification, and API behavior. Use at least one live tagged issue/PR smoke test for worktree launch, preview labeling, and terminal cleanup.
Decisions
- Do not route session cleanup through Discord/DUI; Launchplane records intent and the local worker shuts down local sessions.
- Do not rely on prompts for worktree isolation; the worker creates the worktree.
- Use Launchplane's existing
launchplane-preview PR label as the first preview trigger.
Open Questions
- Exact session metadata contract between Code, Launchplane, and Discord UI.
- Whether PR feedback injection should target a live session first, with resume as fallback, or always start a fresh turn.
Objective
Make Launchplane-backed Every Code sessions robust enough for regular use: isolated worktrees, readable session identity, preview automation, PR feedback, and clean lifecycle handling.
Finish Line
Every Code runs isolated, visible, preview-aware local sessions with clean close and PR feedback
Current Status
State: Done. Launchplane-side Every Code automation lifecycle is implemented and all sub-issues are closed. The remaining DUI visibility problem is a Code-side detached TUI registration bug tracked as cbusillo/code#29.
Next action: Work cbusillo/code#29 to make detached tmux Code sessions register with remote inbox/DUI before attach.
Blocked by: cbusillo/code#29 for the DUI visibility improvement; Launchplane workstream itself is complete.
Last verified: 2026-05-06 with all seven sub-issues closed, live webhook sync completed, local worker running from the main Launchplane checkout, and failed DUI smoke routed to cbusillo/code#29.
Scope
Acceptance Criteria
Relationships
Parent plan for the focused implementation issues in this workstream.
Validation
Use unit tests for worker state, webhook classification, and API behavior. Use at least one live tagged issue/PR smoke test for worktree launch, preview labeling, and terminal cleanup.
Decisions
launchplane-previewPR label as the first preview trigger.Open Questions