mirror of
https://github.com/stablyai/orca.git
synced 2026-11-01 17:47:40 +00:00
Brennan Benson
5ffc8d7972
* Keep Chat UI users who opened new tabs in the terminal on the terminal Before the chat upgrade, Experimental Chat UI had a separate Default view choice, and it defaulted to Terminal. The upgrade retired that choice so Chat UI on now means new agent tabs open as chat, which moved people who had kept the terminal default into chat with no obvious way back. On load, a profile saved by a pre-upgrade build with Chat UI on and Default view not set to Chat now gets Chat UI turned off, and is left out of the one-time native chat upgrade tip. The old key is stripped on the first save, so the migration runs once and a later opt-in sticks. * Update the saved-settings test for Chat UI on with Default view Terminal * Show the upgrade tip to terminal-default users, with a switch to turn on chat mode People who had Chat UI on with new tabs opening in the terminal now keep the terminal on upgrade, but they still need the tip's directions for moving between chat and CLI. They now get the same upgrade tip, plus a note that new agent tabs still open in the terminal and a "Turn on chat mode" switch. The switch shows when Chat UI is off as the tip opens and stays put while it is flipped. The tip is taller in that case so nothing scrolls. * Decide the chat mode switch from the saved tip audience, not the live setting The upgrade tip's 'Turn on chat mode' switch showed whenever Chat UI was off when the tip opened, so a chat-view member who had turned Chat UI off also got it. Main now answers with one tip variant (none, standard, keep-terminal) from the saved audience, and only keep-terminal shows the note and switch. Also moves the feature tip panel styling into a DialogContent surface variant and drops the Label restyle, and tests that the switch stays put after flipping. * Let the upgrade tip decide the chat mode switch from its variant The modal now passes the saved tip variant to the dialog, which decides the switch itself, so the dialog tests cover that decision.
32 lines
1.2 KiB
TypeScript
32 lines
1.2 KiB
TypeScript
import type { NativeChatUpgradeTipVariant } from '../../shared/native-chat-upgrade-tip-audience'
|
|
import type { OnboardingState } from '../../shared/onboarding-state-types'
|
|
|
|
export type OnboardingApi = {
|
|
get: () => Promise<OnboardingState>
|
|
// Why: main merges the checklist field-by-field, so a partial checklist is fine.
|
|
update: (
|
|
updates: Partial<Omit<OnboardingState, 'checklist'>> & {
|
|
checklist?: Partial<OnboardingState['checklist']>
|
|
}
|
|
) => Promise<OnboardingState>
|
|
/** Read-only: main decides the audience once, from the profile as saved before the chat upgrade. */
|
|
getNativeChatUpgradeTipVariant: () => Promise<NativeChatUpgradeTipVariant>
|
|
}
|
|
|
|
export type StarNagApi = {
|
|
onShow: (
|
|
callback: (payload?: { mode?: 'gh' | 'web'; surface?: 'card' | 'toast' }) => void
|
|
) => () => void
|
|
onHide: (callback: () => void) => () => void
|
|
dismiss: () => Promise<void>
|
|
later: () => Promise<void>
|
|
complete: () => Promise<void>
|
|
disable: () => Promise<void>
|
|
openWeb: () => Promise<void>
|
|
starOrca: () => Promise<boolean>
|
|
forceShow: () => Promise<void>
|
|
agentValueMoment: () => Promise<{ status: 'ready'; mode: 'gh' | 'web' } | { status: 'skipped' }>
|
|
showAgentValueMoment: () => Promise<void>
|
|
onboardingCompleted: () => Promise<void>
|
|
}
|