Repository navigation
Decide the resume chain's future (#33) after the 2026-10-22 sync #42
Description
#33, the optional revert of the fork's whole resume chain (#1, #5, #6, #9, #11, #30), is open and now conflicts with swaplabs/main.
The 2026-10-22 sync (#38) ported the chain onto upstream instead. Upstream now ships a lot of its own resume work, for example:
- fix(orcad): a restarted orcad adopts its running agents, and a windowless host resumes slept running agents stablyai/orca#29885, resuming slept running agents on windowless hosts;
- refactor(resume): build the whole recorded resume recipe in one place stablyai/orca#29830, one recorded resume recipe;
- fix(terminal): resume a relaunched workspace's sleeping agents only when shown stablyai/orca#29459, resuming only when shown;
- fix(remote): a paired client reopening a slept agent tab resumes its conversation stablyai/orca#29272 and fix(remote): opening a slept running agent on a host with no window resumes it, never a fresh launch stablyai/orca#29950, paired-client reopen;
- the dark layout-owner series (Main keeps an agent's resume record from the status it receives (dark, layout-owner build only) stablyai/orca#30455, Layout groundwork (switched off): main tells the window whether its start resumed a pane's agent, so the restored banner and reopen count come back stablyai/orca#31908).
Where they overlap, the sync gave upstream's record-based resume precedence over the fork's hook-store resume.
Decide
- Keep the chain and close LOCAL: revert the fork's agent-resume changes (optional revert) #33, or
- drop the chain: rebuild LOCAL: revert the fork's agent-resume changes (optional revert) #33 against the current
swaplabs/main. It can't be revived as it stands, because sync: upstream ec5eaf96c1 into swaplabs/main #38 moved the chain intosrc/wsl-guest,runtime/constructionand new fork modules. The cheapest moment to drop it is during a sync: take upstream for the chain's files instead of porting them.
#38's description lists, per fork PR, how each part of the chain was ported and what upstream now covers.
Activity
kiwidream commentedon Oct 27, 2026
From the 2026-10-27 sync (#60), which stopped on this: upstream stablyai#34054 now resumes a restored pane's agent from its own local hook rows (
hookRowPaneResumeRecordinresolvePaneOwnedResumeStartup). That is the case #30's no-record fallback covers, and upstream's path runs first.Three of #30's behaviours change on the merge:
The options are in #61, item 2. This is the "cheapest moment to drop" #30 that this issue mentions.
kiwidream commentedon Oct 27, 2026
From the 2026-10-27 sync (#62): on #61 the operator kept #30's behaviour and asked to combine it with upstream stablyai#34054. #30's own launcher is gone, and its rules now run on upstream's hook-row resume; fork code for that path went from 296 to 145 lines. Whether to keep or drop the chain is still this issue's decision. Dropping #30 would now mean removing
host-pane-agent-resume-start.ts, its two call sites, and the hook-store rules insrc/main/agent-hooksand the WSL relay.