Objective
Expose enough session-origin metadata for clients to distinguish issue-triggered Every Code sessions from ordinary human-started sessions.
Finish Line
Every Code sessions advertise structured automation metadata to clients
Current Status
State: Planned, with live-test evidence. Every Code issue-label launches can create local sessions, and PR feedback now routes into the existing tmux session rather than creating a new process/thread. DUI visibility still needs structured session origin/activity metadata instead of relying on title text or a new thread.
Next action: Identify the session registration/remote inbox payload and add a minimal metadata field or environment-derived origin contract for automated sessions and feedback activity.
Blocked by: None for the Code metadata contract; Launchplane can already pass request/repo/issue context when starting Code.
Last verified: 2026-05-06 during cbusillo/sellyouroutboard#67 / PR just-every#75 live feedback test.
Scope
- Define a small session origin schema, e.g. human vs every-code.
- Allow Launchplane worker to pass origin metadata through environment, CLI arg, or startup config.
- Include origin metadata in the session registration/control payload used by DUI.
- Keep ordinary sessions unchanged.
Acceptance Criteria
- Human-started Code sessions still appear normally.
- Every Code sessions expose stable structured metadata, not just title text.
- Metadata includes enough information to link back to the GitHub issue/work request.
- Tests or a local smoke test verify the metadata reaches the client payload.
Relationships
Related to cbusillo/launchplane#327 and blocks the DUI rendering issue.
Validation
Targeted Code tests or a live remote-inbox/DUI payload smoke test.
Objective
Expose enough session-origin metadata for clients to distinguish issue-triggered Every Code sessions from ordinary human-started sessions.
Finish Line
Every Code sessions advertise structured automation metadata to clients
Current Status
State: Planned, with live-test evidence. Every Code issue-label launches can create local sessions, and PR feedback now routes into the existing tmux session rather than creating a new process/thread. DUI visibility still needs structured session origin/activity metadata instead of relying on title text or a new thread.
Next action: Identify the session registration/remote inbox payload and add a minimal metadata field or environment-derived origin contract for automated sessions and feedback activity.
Blocked by: None for the Code metadata contract; Launchplane can already pass request/repo/issue context when starting Code.
Last verified: 2026-05-06 during cbusillo/sellyouroutboard#67 / PR just-every#75 live feedback test.
Scope
Acceptance Criteria
Relationships
Related to cbusillo/launchplane#327 and blocks the DUI rendering issue.
Validation
Targeted Code tests or a live remote-inbox/DUI payload smoke test.