Skip to content

feat: the approval page and the API learn the OS and environment the CLI runs in - #168

Closed
bitpshr wants to merge 1 commit into
paul/windows-loopback-fixfrom
paul/cli-platform-user-agent
Closed

bitpshr wants to merge 1 commit into
paul/windows-loopback-fixfrom
paul/cli-platform-user-agent

Conversation

@bitpshr

@bitpshr bitpshr commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Summary

From the API's side today, a CLI request is just elevenlabs-cli/<version> cmd/<command>, so a problem like the Windows sign-in misses in #167 can't be told apart from WSL, containers or SSH. The hand-written commands now append os/<windows|macos|linux|other>, plus env/<ssh|container|wsl> when one applies, after their cmd/ tag. Only whether the relevant environment variables are set is checked, and their values are never sent.

onboard also passes cli_os and cli_env on the approval-page link. A sign-in whose callback never reaches the CLI makes no API call, so the page's events are the only place those misses can be counted per platform. Container detection moves from onboard/browser.rs to a small workflow/platform.rs, and the browser check behaves exactly as before.

Stacked on #167, which changes the same sign-in code. The xi side, which reads the tags on the backend and the link parameters on the approval page, is a separate PR. With no version bump, this ships with the next release.

Testing

  • cargo test: the platform detection tests and the command_scope tests pass, and so do the onboard integration tests. The Windows code type-checks for x86_64-pc-windows-msvc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant