coulomb/reuse-surface
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
reuse-surface/registry/capabilities/capability.infotech.isolated-login-browser.md
tegwick 10053721bc
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
ci / validate-registry (push) Failing after 2m18s
Details
Record native Windows login proof and attended recovery discovery 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1abf1-7e95-7141-87c9-ee78332bf790
2026-11-06 20:30:43 +01:00

8.8 KiB
Raw Blame History

id name summary owner status domain tags maturity external_evidence discovery availability relations evidence consumer_guidance promotion_history
capability.infotech.isolated-login-browser Isolated Login Browser Isolated visible login window: native Windows Edge with a private disposable profile on WSL, pinned Playwright Chromium on non-WSL Linux; operator-only credentials and fixed issuer/callback guards. reuse-surface reviewed infotech
attended-login
browser
chromium
empty-profile
playwright
windows
wsl
edge
discovery availability
current target confidence rationale
D3 D4 high Real WSL input failure, Linux probes, native Windows lifecycle and actual attended login were investigated; this is bounded exploration, not systematic browser research.
current target confidence rationale
A2 A3 medium Source in railiance-platform selects a native Windows worker on WSL and retains pinned Chromium on non-WSL Linux; no separately packaged CLI.
completeness reliability
level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations
C3 high scope_vs_intent_and_consumer_expectations
Fresh owner-only native Windows profile, guarded issuer/local callback and bounded process/profile cleanup
Actual attended owner login completes, with provider readback/decryption and session revocation
Credential-free native localhost callback lifecycle and 32 platform operator tests pass
Headless screenshots, keyboard trials, or a hosted browser service.
Credential custody, password entry, or one-time-code handling by the launcher.
level confidence basis known_reliability_risks
R2 medium consumer_quality_signals
Native Windows path has focused lifecycle proof and one successful operating retry, not broad operating history.
WSLg/Chrome input stalled unpredictably even in credential-free probes; the Windows path bypasses it without proving the exact root cause.
Earlier timeout/authentication failure receipts retain unconfirmed session revocation outcomes.
A Windows desktop/Edge installation and WSL interop are required on WSL; non-WSL Linux still depends on the pinned Chromium cache.
User-close or timeout cleanup is bounded; the opener fails closed when the private profile/ACL/worker cannot be established.
intent includes excludes assumptions use_cases research_memos
Give an operator a visible browser with no saved account when a login must not reuse the workstation's default browser session.
Native Windows Edge on WSL, with a fresh owner-only profile for each invocation
Pinned headed Chromium on non-WSL Linux
Fixed Keycloak issuer and approved localhost/127.0.0.1 OpenBao callback on port 8250
Owned browser/profile lifecycle cleanup
Shared/default browser profiles and remote headless services
Credential entry/storage by the agent or launcher
Changing issuer, MFA, callback registration, grants or output allowlists
Existing attended platform owner lane and allowed issuer/callback
Windows Edge and PowerShell/WSL interop on WSL; pinned Chromium and a display on non-WSL Linux
Open the platform-root OpenBao login without an existing disposable-account session.
current_level target_level current_artifacts target_artifacts consumption_modes
A2 A3
../railiance-platform/scripts/operator-browser/cmd.exe
../railiance-platform/scripts/operator-browser/xdg-open
../railiance-platform/scripts/openbao-attended-exec.py
../coulomb-social/scripts/node_modules/playwright-core/browsers.json
../railiance-platform/scripts/operator-browser/windows_browser.py
A small installable command whose only job is the empty-profile login window.
informational
source adaptation
cli
depends_on supports related_to
capability.infotech.headless-browser
documentation tests consumer_feedback bug_reports incidents
../railiance-platform/docs/backup-credential-recovery.md
../railiance-platform/docs/evidence/2026-11-06-operator-browser-native-windows.json
../railiance-apps/docs/evidence/2026-11-06-vergabe-browser-window-repair.json
../railiance-platform/tests/test_operator_browser.py
../railiance-platform/tests/test_operator_windows_browser.py
2026-11-02: the attended OpenBao window was Firefox, the Windows default. A later login also opened a Firefox tab because OpenBao calls `cmd.exe /c start` on WSL and never reaches xdg-open. The empty profile was not used. The login still completed after the old session expired.
2026-11-06: founder confirms native Windows controls respond normally; actual contained owner login worked like a charm.
../railiance-apps/docs/evidence/2026-11-06-vergabe-attended-provider-success-return.json
../railiance-apps/docs/evidence/2026-11-06-vergabe-attended-backup-complete-return.json
../railiance-apps/docs/evidence/2026-11-06-vergabe-browser-window-repair.json
recommended_for not_recommended_for known_limitations
One attended login that must show the one-time-code page and return to localhost.
Screenshot or keyboard trials. Use capability.infotech.headless-browser.
Any flow that should reuse the operator's normal signed-in browser.
Only fixed issuer/callback paths are allowed; no shared/default-profile fallback.
The authorization URL is passed to the PowerShell worker via stdin, then appears in the owned browser startup argument; no claim of zero URL visibility in all process arguments.
Agent never handles passwords, OTPs, cookies or token-helper values.
Fixture callback navigation is credential-free; actual founder login success is recorded separately.
date dimension from to rationale author
2026-11-06 discovery D2 D3 Platform 8519459 plus native private-profile/callback/cleanup proof and founder-reported actual contained login in Apps 6947673. Earlier failures retained; narrow scope and limited history. codex
date dimension from to rationale author
2026-11-06 completeness C1 C3 Platform 8519459 plus native private-profile/callback/cleanup proof and founder-reported actual contained login in Apps 6947673. Earlier failures retained; narrow scope and limited history. codex
date dimension from to rationale author
2026-11-06 reliability R1 R2 Platform 8519459 plus native private-profile/callback/cleanup proof and founder-reported actual contained login in Apps 6947673. Earlier failures retained; narrow scope and limited history. codex

Isolated Login Browser

The runtime implementation is owned by railiance-platform; reuse-surface provides discovery and the bounded consumption assessment. Platform commit 8519459e6fedd1bfb25dc2cdee6372d7252f5d0a selects native Windows Edge on WSL through its existing operator-browser entry. Non-WSL Linux retains the pinned Playwright Chromium path. Both use disposable profiles; neither reuses the operator's shared browser session.

Current acceptance — 2026-11-06

The founder observed wrong/unresponsive controls, stalled tabs and titlebar X in WSLg/Chrome, including credential-free probes. Native Windows Edge responded normally. The corrected worker uses the current user's numeric SID for a private protected profile ACL, guards owned process identity and cleans its own profile. It receives the URL through stdin; the browser subsequently receives it as a startup argument. Existing issuer/callback, factor, token-helper and output controls remain in effect.

The founder's real login then succeeds. The provider receipt records Warden exit 0 and session revocation/storage cleanup; the final backup receipt records the completed recovery sequence. Thirty-two platform operator tests and a credential-free native callback/process/profile lifecycle fixture are separate quality evidence. Older failed attempts retain their unknown outcomes.

Consumption boundary

Use the reviewed railiance-platform/scripts/openbao-attended-exec.py lane and its operator-browser directory. Do not repurpose the launcher for arbitrary URLs, widen callback/issuer guards or run it with a shared profile. Existing operation authorization still governs the owner command.

This local attended window is separate from capability.infotech.headless-browser, the remote screenshot/trial service. D3/A2/C3/R2 describes the bounded visible-login core with its documented Windows workaround and limited history. It grants no credential or deployment authority.