?"Right now: this page cannot reach that program. Either it has stopped, or the machine went to sleep. The app's own bar notices and offers to reconnect it."
:"Right now: this page cannot reach that program. Either it has stopped, or the machine went to sleep. The link from the terminal will bring it back.";
?"Right now: this page is fine, but Plan2Code has not checked in for a few minutes. Have a look at the terminal panel; it may have finished its turn, hit an error, or be waiting on you there. If it is idle, press continue in the line beside Planny to wake it."
:"Right now: this page is fine, but Plan2Code has not checked in for a few minutes. Have a look at the terminal; it may have finished its turn, hit an error, or be waiting on you there. If it is idle, type continue there to wake it.";
"When a newer Plan2Code release is out, the dashboard shows ",
el("strong",null,"UPDATE AVAILABLE"),
" at the top and the app's top bar shows ",
el("strong",null,"Update available"),
". Both give you the same command, ",
el("code",null,"plan2code update"),
": run it in a terminal outside the app (not its terminal panel), then close the app and open it again. The app cannot replace itself while it runs, so a new release has no one-click update. When the app and the installed skills fall out of step, the bar offers ",
" button. It turns this page back into the cards, in the same conversation, so the next step starts right here. Plan2Code listens for it for as long as the session is open. Once the session has closed, the app's own bar notices and offers to reconnect it, no command needed."
"When the next step is another Plan2Code step, the Next step block also has a ",
el("strong",null,"Continue here"),
" button. It starts that step in this same conversation, the way a dashboard card would, with this page turning into the new step. It goes away once the session meter is red, because a long conversation is the reason to start a fresh one: press New Session at the top of the window instead."
);
}
// The Troubleshooting tab's own "getting a new link" recovery flow: classic
// only, since it ends with a command that prints a fresh browser link. Under
// the app there is no link to print or open: the bar's next-step slot and its
// Reconnect the console (app.js) already notice and bring the page back.
functionrenderStuckReconnectHelp(){
if(!page.inApp)return;
$("help-stuck-not-connected-ref").textContent="the app's own bar notices and offers to reconnect it";
$("help-stuck-table-reconnect-text").textContent="The app's own bar notices and offers Reconnect the console.";
"To get it back, press Reconnect the console in the app's own bar (it tries on its own first). Everything you typed, sent or not, is still there.";
// Not just .hidden: .handoff-command's own display:flex outranks the
// default [hidden] rule, so the element comes out of the DOM instead.
$("help-stuck-reconnect-command").remove();
}
// A handoff's "Copy for a new conversation" button is for carrying work to
// a wholly separate agent (another machine, another terminal); under the app
// that still works, but "a new conversation" is this one's own wording for
// what New Session does, so name that instead to avoid sounding like a
// second, missing feature.
functionrenderHandoffCopyHelp(){
if(!page.inApp)return;
$("help-handoff-copy-text").replaceChildren(
"A ",
el("strong",null,"Handoff"),
" is a note a step left when you stopped it with a handoff. It shows as a dashed chip after the specs. Pick one and the cards give way to a preview with its Next task and four buttons: ",
el("strong",null,"Pick it up here"),
" carries on in the same step and spec, ",
el("strong",null,"Read it all"),
" shows the whole note, ",
el("strong",null,"Copy for another session"),
" puts a ready prompt on the clipboard, for pasting into the terminal panel after a New Session or anywhere else you carry the work, and ",
el("strong",null,"Delete"),
" removes it. A picked-up handoff drops off the list, but stays in ",
el("code",null,"~/.plan2code/handoffs/"),
" until the 30-day sweep."
);
}
// The Ask tab's "carry away" prompt is meant to start a genuinely fresh,
// separate task: under the app that means pasting it into the terminal panel
// after a New Session, not into "a new conversation" that does not exist there.
functionrenderAskPromptHelp(){
if(!page.inApp)return;
$("help-ask-prompt-text").replaceChildren(
"When what you ask is really a new task, or you ask for a prompt, the answer ends with a ready-to-paste prompt in a box with a ",
el("strong",null,"Copy"),
" button. Press New Session for a clean context, then paste it into the terminal panel: it names the skill to use and the files to read, so nothing said here needs repeating."
);
}
// Matches ending.js's own renderStopping, which already says "paste into the
// terminal panel" under the app instead of "a new conversation".
// The Planny-poses catalog's own "Done" entry said the same "close the tab":
// there is no tab under the app, only the one window.
functionrenderPlannyDoneHelp(){
if(!page.inApp)return;
$("help-planny-done-text").textContent="A green star and both arms up. The session is finished. You can close the window.";
}
functionrenderFinishingStopHelp(){
if(!page.inApp)return;
$("help-finishing-stop-text").replaceChildren(
el("strong",null,"Stop session"),
", at the top, ends the session and saves your place. Any answers you have ready go with it, and Plan2Code gives you a command to pick up where you left off, to paste into the terminal panel."
);
}
// A phrase that reads differently under the app carries its app wording in
// `data-app`, and the browser wording stays in the markup as it was. Whole
// paragraphs that differ are `.for-app` / `.for-browser` siblings instead,
// switched by help.css. Plain text only: anything with markup in it is a pair.