hermes-agent/apps/desktop/electron/primary-profile-pin.ts
hermes-seaeye[bot] aae6c2044e
fmt(js): npm run fix on merge (#123390)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2026-09-26 03:39:27 +00:00

71 lines
2.6 KiB
TypeScript

/**
* Which profile the PRIMARY (window) backend answers for.
*
* Two signals exist and they legitimately disagree mid-session:
*
* - the stored preference (active-profile.json) — the profile Desktop should
* boot into on the NEXT launch. The rail's live workspace switch rewrites
* it via `hermes:profile:remember` without re-homing the primary.
* - the profile the live primary child was actually spawned with.
*
* Routing (`resolveProfileBackendRoute`, `ensureBackend`, the pool) must use
* the second while a primary is up. Reading the preference instead made a
* request for the booted profile (e.g. "default") stop matching
* `primaryProfile`, fall through to the pool, and spawn a second backend for
* the same HERMES_HOME. That duplicate held a pool slot and starved every other
* profile into "timed out while waiting for a free slot".
*
* Pure: main.ts owns the file read and the start/teardown call sites.
*/
export class PrimaryProfilePin {
#booted: null | string = null
/** Called by startHermes() with the profile the primary is launching as. */
pin(profile: null | string | undefined): string {
const value = String(profile ?? '').trim() || 'default'
this.#booted = value
return value
}
/** Called when the primary is torn down; the next start re-reads the preference. */
clear(): void {
this.#booted = null
}
get booted(): null | string {
return this.#booted
}
/**
* The key routing should treat as "primary": the live primary's profile when
* one is pinned, else the stored preference, else 'default'.
*/
resolve(readPreference: () => null | string | undefined): string {
if (this.#booted) {
return this.#booted
}
return String(readPreference() ?? '').trim() || 'default'
}
}
/**
* One authoritative launch-profile decision for a startup attempt (#108417).
*
* `routingProfile` is what the pin and the routing table should answer for
* (the preference at decision time, 'default' when unset); `argvProfile` is
* what the local launch argument and child env carry (the same preference,
* `null` when unset so the legacy flag-less launch is preserved). Both come
* from the SAME read so a preference change landing mid-startup becomes the
* next boot's decision instead of splitting routing identity from
* `--profile`.
*/
export function resolveLaunchProfile(readPreference: () => null | string | undefined): {
argvProfile: null | string
routingProfile: string
} {
const argvProfile = String(readPreference() ?? '').trim() || null
return { argvProfile, routingProfile: argvProfile ?? 'default' }
}