teams-cli 0.1.12__tar.gz → 0.2.0__tar.gz

{teams_cli-0.1.12 → teams_cli-0.2.0}/CHANGELOG.md

@@ -7,6 +7,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.0](https://github.com/rvben/teams-cli/compare/v0.1.13...v0.2.0) - 2026-10-14
+
+### Added
+
+- **desktop**: add one-command lightweight browser setup with automatic matching browser downloads, visible sign-in followed by verified hidden operation, personal-account defaults, and safe reconnect/recovery.
+- **desktop**: add managed browser clients and cached avatars ([319c494](https://github.com/rvben/teams-cli/commit/319c494b18c9dff98d26b2d069d4347a39d02e6b))
+
+### Fixed
+
+- **security**: update rustls to 0.23.46 to address the newly published TLS advisories.
+
+## [0.1.13](https://github.com/rvben/teams-cli/compare/v0.1.12...v0.1.13) - 2026-10-14
+
+### Fixed
+
+- **tui**: keep the canvas behind text so the terminal background never shows through ([596eb7b](https://github.com/rvben/teams-cli/commit/596eb7b6f79db174ba1f33e6eaf5eb345912504a))
+- **desktop**: send URLs as clickable links like Teams' compose box does ([4b46ca2](https://github.com/rvben/teams-cli/commit/4b46ca2bb2a3d466313ba2f7ce8172c6eb065dbd))
+
 ## [0.1.12](https://github.com/rvben/teams-cli/compare/v0.1.11...v0.1.12) - 2026-10-14
 
 ### Breaking Changes

{teams_cli-0.1.12 → teams_cli-0.2.0}/Cargo.lock

@@ -1776,7 +1776,7 @@ version = "1.1.8"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "c0aeb26bf5e836cc1c341c8106051b573f1766dfa05aa87f0b98be5e51b02303"
 dependencies = [
- "nix",
+ "nix 0.29.0",
  "winapi",
 ]
 
@@ -1848,6 +1848,18 @@ dependencies = [
  "memoffset",
 ]
 
+[[package]]
+name = "nix"
+version = "0.31.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "cf20d2fde8ff38632c426f1165ed7436270b44f199fc55284c38276f9db47c3d"
+dependencies = [
+ "bitflags 2.13.1",
+ "cfg-if",
+ "cfg_aliases",
+ "libc",
+]
+
 [[package]]
 name = "nom"
 version = "7.1.3"
@@ -2740,9 +2752,9 @@ dependencies = [
 
 [[package]]
 name = "rustls"
-version = "0.23.45"
+version = "0.23.46"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "0d41d731c7d2f962d1ccc364cec258de3c0e93b38c2fb3ba97ac74513048d634"
+checksum = "48e13bd8c0e9365c43cfa5c9e8f9ad49d3c8444926c9aac819e0e4dc503c8fdf"
 dependencies = [
  "aws-lc-rs",
  "once_cell",
@@ -3175,7 +3187,7 @@ dependencies = [
 
 [[package]]
 name = "teams-cli"
-version = "0.1.12"
+version = "0.2.0"
 dependencies = [
  "assert_cmd",
  "base64 0.23.1",
@@ -3188,6 +3200,7 @@ dependencies = [
  "jiff",
  "jsonschema",
  "keyring",
+ "libc",
  "open",
  "predicates",
  "rand 0.9.5",
@@ -3206,6 +3219,7 @@ dependencies = [
  "url",
  "windows-sys 0.61.2",
  "wiremock",
+ "zip",
 ]
 
 [[package]]
@@ -3215,7 +3229,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "32497e9a4c7b38532efcdebeef879707aa9f794296a4f0244f6f69e9bc8574bd"
 dependencies = [
  "fastrand",
- "getrandom 0.4.3",
+ "getrandom 0.3.4",
  "once_cell",
  "rustix",
  "windows-sys 0.61.2",
@@ -3279,7 +3293,7 @@ dependencies = [
  "libc",
  "log",
  "memmem",
- "nix",
+ "nix 0.29.0",
  "num-derive",
  "num-traits",
  "ordered-float",
@@ -3577,6 +3591,12 @@ dependencies = [
  "thiserror 2.0.20",
 ]
 
+[[package]]
+name = "typed-path"
+version = "0.12.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8e28f89b80c87b8fb0cf04ab448d5dd0dd0ade2f8891bae878de66a75a28600e"
+
 [[package]]
 name = "typenum"
 version = "1.20.1"
@@ -4263,6 +4283,20 @@ dependencies = [
  "syn 3.0.4",
 ]
 
+[[package]]
+name = "zip"
+version = "9.0.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c2d98561b612a84ae525331a7a094429ef8a5772514ed507ff6db5f54badc971"
+dependencies = [
+ "crc32fast",
+ "flate2",
+ "indexmap",
+ "memchr",
+ "nix 0.31.3",
+ "typed-path",
+]
+
 [[package]]
 name = "zmij"
 version = "1.0.23"

{teams_cli-0.1.12 → teams_cli-0.2.0}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "teams-cli"
-version = "0.1.12"
+version = "0.2.0"
 edition = "2024"
 rust-version = "1.90"
 description = "A Microsoft Teams CLI and TUI designed equally for humans and agents"
@@ -46,6 +46,7 @@ toml = "1.1"
 url = "2"
 jiff = "0.2"
 unicode-width = "0.2"
+zip = { version = "9.0.3", default-features = false, features = ["deflate-flate2"] }
 
 [target.'cfg(windows)'.dependencies]
 windows-sys = { version = "0.61", features = [
@@ -58,6 +59,9 @@ windows-sys = { version = "0.61", features = [
     "Win32_System_Threading",
 ] }
 
+[target.'cfg(target_os = "macos")'.dependencies]
+libc = "0.2"
+
 [dev-dependencies]
 assert_cmd = "2"
 jsonschema = "0.49.8"

{teams_cli-0.1.12 → teams_cli-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: teams-cli
-Version: 0.1.12
+Version: 0.2.0
 Classifier: Programming Language :: Rust
 Classifier: Programming Language :: Python :: Implementation :: CPython
 License-File: LICENSE
@@ -18,7 +18,7 @@ Project-URL: Repository, https://github.com/rvben/teams-cli
 
 Microsoft Teams from your terminal—human-first and agent-first.
 
-`teams-cli` is a Rust CLI and TUI for everyday Microsoft Teams work through supported Microsoft Graph APIs, with an optional experimental desktop backend that reads chats from, and can send chat messages through, a running Teams client on macOS, Windows or WSL. It is designed as two equally first-class experiences over one typed core: a fast, calm terminal interface for people and a deterministic, introspectable command contract for agents. The default Graph backend signs in as you with delegated OAuth and protects refresh credentials in your operating system's credential store. Output is readable text on a TTY and structured JSON when piped.
+`teams-cli` is a Rust CLI and TUI for everyday Microsoft Teams work through supported Microsoft Graph APIs, with an optional experimental desktop backend that reads chats from, and can send chat messages through, a running Teams client on macOS, Windows or WSL. A dedicated browser client also provides an experimental route on native Linux; see [browser setup](#dedicated-browser-client-experimental). It is designed as two equally first-class experiences over one typed core: a fast, calm terminal interface for people and a deterministic, introspectable command contract for agents. The default Graph backend signs in as you with delegated OAuth and protects refresh credentials in your operating system's credential store. Output is readable text on a TTY and structured JSON when piped.
 
 For humans, no arguments open guided onboarding on first use and the TUI afterward. For agents, no command ever waits for an undeclared prompt: `teams schema` works offline, collection sizes are caller-bounded, writes declare their effects, errors have stable kinds and exit codes, and stdout contains data only.
 
@@ -68,6 +68,16 @@ teams init
 teams init
 ```
 
+For a personal Microsoft account with the lightweight hidden browser:
+
+```console
+teams init --profile personal --backend desktop --desktop-client browser-core
+```
+
+This downloads its browsers automatically, opens visible sign-in once, and then
+runs hidden. See [lightweight browser setup](#low-memory-browser-client-experimental)
+for sending, reconnecting, and experimental compatibility limits.
+
 Browser PKCE is the human-friendly default. The browser talks directly to Microsoft, and the CLI never receives or stores your password. Normal sign-in requests these delegated scopes:
 
 ```text
@@ -223,6 +233,15 @@ ids returned by `chats list`; personal chats are accessed through the desktop ba
 The chat with yourself is listed too, with the id `48:notes`, so
 you can try sending there first.
 
+Desktop chat results may also include optional `avatarData` raster data URIs on
+members and one-to-one chats. Photos come only from image resources already loaded
+by that account's Teams page; the CLI never fetches a photo URL. Missing, stale,
+ambiguous, or unsupported photos leave the fields absent, so clients should show
+initials as a fallback. Reads allow at most 16 photos, 256 KiB per photo, 1 MiB of
+avatar data in total, and a one-second budget. A photo failure never fails a chat
+read. Personal photo reads have been checked on macOS; work/school and other
+platforms still need photo-specific runtime validation.
+
 Desktop profiles are read-only unless created with `init --allow-send`;
 `TEAMS_READ_ONLY=true` still blocks sending, but `TEAMS_READ_ONLY=false` cannot unlock a
 desktop profile. With the opt-in, `messages send --chat` sends one plain-text message
@@ -360,12 +379,126 @@ This backend is experimental: chat reading depends on the Teams client's interna
 cache layout and sending on its internal send interface, and an unrecognised layout
 fails with `desktop_error` rather than guessing.
 
+### Dedicated browser client (experimental)
+
+On native Linux, macOS, or WSL2, the desktop backend can use an installed Chrome,
+Chromium, or Edge browser instead of the native Teams app. WSL2 uses a Linux browser;
+visible sign-in requires WSLg or another graphical display. The existing Windows
+helper route remains the default for native desktop profiles.
+
+Create a separate read-only profile and sign in in the window that opens:
+
+```console
+teams init --profile browser --backend desktop --desktop-client browser --desktop-account work-school --yes
+# The window closes automatically after a successful chat read.
+# Teams then runs headless with the same saved sign-in:
+teams --profile browser
+# To renew sign-in or complete MFA later:
+teams --profile browser desktop login --yes
+```
+
+Login waits up to five minutes for a readable chat cache, then restarts headless
+and verifies another read before reporting success. An empty chat list is valid.
+A sign-in timeout leaves the visible window open; finish signing in and retry
+`desktop login`. Interrupting login preserves the browser and its saved profile.
+On WSL2, the visible step needs WSLg or another graphical display.
+
+Use `--desktop-account personal` for a personal Microsoft account. Sending still
+requires an explicit `init --allow-send` and the existing send confirmation.
+`init --no-login` only saves configuration. `desktop connect --visible` remains
+available for manually managed sign-in; `desktop connect` starts headless.
+
+The browser uses its own profile under the local data directory at
+`teams-cli/browser/<port>/profile`; it never copies or opens your normal browser
+profile. Different ports use different browser profiles. Disconnect closes this
+browser and keeps its sign-in data. To switch between visible and headless operation,
+disconnect first. `desktop recover` closes a verified managed browser or clears a
+stale record when no listener remains. Unverifiable processes are left untouched.
+
+The CLI checks that every listener is loopback-only and belongs to the recorded
+browser process, running as you with the expected executable, debugging port and
+dedicated profile. Only HTTPS Teams pages are used for reads or sends. While the
+port is open, other programs running as you can access that browser session.
+
+Browser discovery supports common system installations. For another installation,
+set `TEAMS_DESKTOP_BROWSER` to the absolute path of the actual browser executable,
+not a shell launcher. Snap/Flatpak installations are not automatically supported.
+The optional `TEAMS_DESKTOP_BROWSER_DATA_DIR` sets an absolute browser data directory
+(each port gets a separate subdirectory). Keep the same browser executable and data
+directory settings while managing a session. Headless mode removes the visible window; Teams still consumes browser CPU and RAM.
+
+This route is experimental. Browser lifecycle and ownership checks can be tested
+without signing in, but live Teams Web reads, sends, session persistence and MFA
+recovery still require validation on a signed-in machine. Existing native Teams
+validation does not establish browser-client compatibility.
+
+### Low-memory browser client (experimental)
+
+`--desktop-client browser-core` keeps the authenticated Teams data runtime without
+starting the main UI. It supports personal accounts only and requires the
+exact Teams Personal bootstrap build validated by this CLI. Unknown builds fail
+with `desktop_error`; the CLI does not fall back to old cache data or the full UI.
+Use `--desktop-client browser` on a separate port for the full web client.
+
+Start with one command:
+
+```console
+teams init --profile core --backend desktop --desktop-client browser-core
+```
+
+The CLI downloads a matching **Chrome for Testing / chrome-headless-shell** pair
+from Google's official Stable channel on first setup, opens a separate sign-in
+window, and hides it once chats are readable. It verifies the hidden session before
+saving your CLI profile. Core mode defaults to a personal account, port **9223**,
+and read-only access; add `--allow-send` to enable sending. Your normal browser,
+its profile, and the native Teams connection on port 9222 are left alone.
+
+Browser binaries and sign-in state live in a private `teams-cli/browser` data
+directory. The installed pair is reused offline and is not silently updated while
+sessions are running. Setup needs roughly 1 GiB of disk space for the browsers and
+extraction; the ZIP downloads are removed after installation. Linux/WSL2 need a
+desktop display (WSLg on WSL2) for initial sign-in.
+
+```console
+teams --profile core desktop login       # Sign in again; automatically hide afterward
+teams --profile core desktop disconnect  # Stop the browser; retain sign-in
+teams --profile core desktop connect     # Start hidden using the saved session
+teams --profile core desktop status      # Inspect process and recovery state
+```
+
+An interrupted sign-in retains the dedicated window and profile. Rerun `desktop
+login` to finish; an expired hidden session can use the same command. A stale
+process record is recovered automatically only when its port has no listener;
+unrelated or changed processes are refused. `desktop recover` preserves sign-in
+and can close only a verified managed browser. The status command does not prove
+that you are signed in; `chats list` or `doctor` verifies message access.
+
+Advanced setups can override both `TEAMS_DESKTOP_BROWSER` and
+`TEAMS_DESKTOP_HEADLESS_BROWSER` with absolute paths to matching executables.
+Set both or neither; a partial override is refused. `TEAMS_DESKTOP_BROWSER_DATA_DIR`
+changes the private data location. Keep these settings stable while a session is
+running. Unknown Teams builds are refused; use the full `browser` client on its
+own port if your Teams build is not yet supported.
+
+On macOS, both dedicated test browsers use mock-keychain encryption because the
+headless shell uses it. This profile contains sensitive login state and remains in
+a private directory; it never opens your ordinary browser profile.
+
+The integrated CLI measured about **307 MiB after collection and 322 MiB idle**
+of summed browser process physical footprint on macOS with a personal account.
+Signed-in reads, visible-to-headless login, sending/readback and incoming updates
+from a second verified client passed. This is approximate process accounting, not a guaranteed RAM cap or a
+Linux measurement. Startup peaks, large accounts, overnight use, reconnect/MFA and
+Linux/WSL2 signed-in operation still need validation. Size-oriented V8 settings may
+trade CPU for memory. Avatar fields may be absent because UI photos are not loaded.
+Sending still requires `init --allow-send` and the existing send confirmation.
+
 ## Graph boundaries
 
 - The Graph backend supports Microsoft 365 work or school accounts only. Use the experimental desktop backend on macOS, Windows or WSL for personal Microsoft accounts; the relevant Teams Graph endpoints do not support them.
 - A work account can authenticate successfully before Microsoft Teams is licensed or provisioned; `teams doctor` distinguishes identity access from Teams availability.
 - Calling and screen sharing are not available as a delegated user CLI; Graph calling is built around bot/application scenarios.
-- No extracted desktop tokens, browser interception, or direct calls to private Teams services; the experimental desktop backend reads the local client cache and sends only through the Teams window's own client.
+- No extracted desktop tokens or direct calls to private Teams services; the experimental desktop backend reads the local client cache and sends only through the Teams window's own client.
 - Tenant policy and admin consent can restrict delegated capabilities.
 
 ## CLI Spec

{teams_cli-0.1.12 → teams_cli-0.2.0}/README.md

@@ -2,7 +2,7 @@
 
 Microsoft Teams from your terminal—human-first and agent-first.
 
-`teams-cli` is a Rust CLI and TUI for everyday Microsoft Teams work through supported Microsoft Graph APIs, with an optional experimental desktop backend that reads chats from, and can send chat messages through, a running Teams client on macOS, Windows or WSL. It is designed as two equally first-class experiences over one typed core: a fast, calm terminal interface for people and a deterministic, introspectable command contract for agents. The default Graph backend signs in as you with delegated OAuth and protects refresh credentials in your operating system's credential store. Output is readable text on a TTY and structured JSON when piped.
+`teams-cli` is a Rust CLI and TUI for everyday Microsoft Teams work through supported Microsoft Graph APIs, with an optional experimental desktop backend that reads chats from, and can send chat messages through, a running Teams client on macOS, Windows or WSL. A dedicated browser client also provides an experimental route on native Linux; see [browser setup](#dedicated-browser-client-experimental). It is designed as two equally first-class experiences over one typed core: a fast, calm terminal interface for people and a deterministic, introspectable command contract for agents. The default Graph backend signs in as you with delegated OAuth and protects refresh credentials in your operating system's credential store. Output is readable text on a TTY and structured JSON when piped.
 
 For humans, no arguments open guided onboarding on first use and the TUI afterward. For agents, no command ever waits for an undeclared prompt: `teams schema` works offline, collection sizes are caller-bounded, writes declare their effects, errors have stable kinds and exit codes, and stdout contains data only.
 
@@ -52,6 +52,16 @@ teams init
 teams init
 ```
 
+For a personal Microsoft account with the lightweight hidden browser:
+
+```console
+teams init --profile personal --backend desktop --desktop-client browser-core
+```
+
+This downloads its browsers automatically, opens visible sign-in once, and then
+runs hidden. See [lightweight browser setup](#low-memory-browser-client-experimental)
+for sending, reconnecting, and experimental compatibility limits.
+
 Browser PKCE is the human-friendly default. The browser talks directly to Microsoft, and the CLI never receives or stores your password. Normal sign-in requests these delegated scopes:
 
 ```text
@@ -207,6 +217,15 @@ ids returned by `chats list`; personal chats are accessed through the desktop ba
 The chat with yourself is listed too, with the id `48:notes`, so
 you can try sending there first.
 
+Desktop chat results may also include optional `avatarData` raster data URIs on
+members and one-to-one chats. Photos come only from image resources already loaded
+by that account's Teams page; the CLI never fetches a photo URL. Missing, stale,
+ambiguous, or unsupported photos leave the fields absent, so clients should show
+initials as a fallback. Reads allow at most 16 photos, 256 KiB per photo, 1 MiB of
+avatar data in total, and a one-second budget. A photo failure never fails a chat
+read. Personal photo reads have been checked on macOS; work/school and other
+platforms still need photo-specific runtime validation.
+
 Desktop profiles are read-only unless created with `init --allow-send`;
 `TEAMS_READ_ONLY=true` still blocks sending, but `TEAMS_READ_ONLY=false` cannot unlock a
 desktop profile. With the opt-in, `messages send --chat` sends one plain-text message
@@ -344,12 +363,126 @@ This backend is experimental: chat reading depends on the Teams client's interna
 cache layout and sending on its internal send interface, and an unrecognised layout
 fails with `desktop_error` rather than guessing.
 
+### Dedicated browser client (experimental)
+
+On native Linux, macOS, or WSL2, the desktop backend can use an installed Chrome,
+Chromium, or Edge browser instead of the native Teams app. WSL2 uses a Linux browser;
+visible sign-in requires WSLg or another graphical display. The existing Windows
+helper route remains the default for native desktop profiles.
+
+Create a separate read-only profile and sign in in the window that opens:
+
+```console
+teams init --profile browser --backend desktop --desktop-client browser --desktop-account work-school --yes
+# The window closes automatically after a successful chat read.
+# Teams then runs headless with the same saved sign-in:
+teams --profile browser
+# To renew sign-in or complete MFA later:
+teams --profile browser desktop login --yes
+```
+
+Login waits up to five minutes for a readable chat cache, then restarts headless
+and verifies another read before reporting success. An empty chat list is valid.
+A sign-in timeout leaves the visible window open; finish signing in and retry
+`desktop login`. Interrupting login preserves the browser and its saved profile.
+On WSL2, the visible step needs WSLg or another graphical display.
+
+Use `--desktop-account personal` for a personal Microsoft account. Sending still
+requires an explicit `init --allow-send` and the existing send confirmation.
+`init --no-login` only saves configuration. `desktop connect --visible` remains
+available for manually managed sign-in; `desktop connect` starts headless.
+
+The browser uses its own profile under the local data directory at
+`teams-cli/browser/<port>/profile`; it never copies or opens your normal browser
+profile. Different ports use different browser profiles. Disconnect closes this
+browser and keeps its sign-in data. To switch between visible and headless operation,
+disconnect first. `desktop recover` closes a verified managed browser or clears a
+stale record when no listener remains. Unverifiable processes are left untouched.
+
+The CLI checks that every listener is loopback-only and belongs to the recorded
+browser process, running as you with the expected executable, debugging port and
+dedicated profile. Only HTTPS Teams pages are used for reads or sends. While the
+port is open, other programs running as you can access that browser session.
+
+Browser discovery supports common system installations. For another installation,
+set `TEAMS_DESKTOP_BROWSER` to the absolute path of the actual browser executable,
+not a shell launcher. Snap/Flatpak installations are not automatically supported.
+The optional `TEAMS_DESKTOP_BROWSER_DATA_DIR` sets an absolute browser data directory
+(each port gets a separate subdirectory). Keep the same browser executable and data
+directory settings while managing a session. Headless mode removes the visible window; Teams still consumes browser CPU and RAM.
+
+This route is experimental. Browser lifecycle and ownership checks can be tested
+without signing in, but live Teams Web reads, sends, session persistence and MFA
+recovery still require validation on a signed-in machine. Existing native Teams
+validation does not establish browser-client compatibility.
+
+### Low-memory browser client (experimental)
+
+`--desktop-client browser-core` keeps the authenticated Teams data runtime without
+starting the main UI. It supports personal accounts only and requires the
+exact Teams Personal bootstrap build validated by this CLI. Unknown builds fail
+with `desktop_error`; the CLI does not fall back to old cache data or the full UI.
+Use `--desktop-client browser` on a separate port for the full web client.
+
+Start with one command:
+
+```console
+teams init --profile core --backend desktop --desktop-client browser-core
+```
+
+The CLI downloads a matching **Chrome for Testing / chrome-headless-shell** pair
+from Google's official Stable channel on first setup, opens a separate sign-in
+window, and hides it once chats are readable. It verifies the hidden session before
+saving your CLI profile. Core mode defaults to a personal account, port **9223**,
+and read-only access; add `--allow-send` to enable sending. Your normal browser,
+its profile, and the native Teams connection on port 9222 are left alone.
+
+Browser binaries and sign-in state live in a private `teams-cli/browser` data
+directory. The installed pair is reused offline and is not silently updated while
+sessions are running. Setup needs roughly 1 GiB of disk space for the browsers and
+extraction; the ZIP downloads are removed after installation. Linux/WSL2 need a
+desktop display (WSLg on WSL2) for initial sign-in.
+
+```console
+teams --profile core desktop login       # Sign in again; automatically hide afterward
+teams --profile core desktop disconnect  # Stop the browser; retain sign-in
+teams --profile core desktop connect     # Start hidden using the saved session
+teams --profile core desktop status      # Inspect process and recovery state
+```
+
+An interrupted sign-in retains the dedicated window and profile. Rerun `desktop
+login` to finish; an expired hidden session can use the same command. A stale
+process record is recovered automatically only when its port has no listener;
+unrelated or changed processes are refused. `desktop recover` preserves sign-in
+and can close only a verified managed browser. The status command does not prove
+that you are signed in; `chats list` or `doctor` verifies message access.
+
+Advanced setups can override both `TEAMS_DESKTOP_BROWSER` and
+`TEAMS_DESKTOP_HEADLESS_BROWSER` with absolute paths to matching executables.
+Set both or neither; a partial override is refused. `TEAMS_DESKTOP_BROWSER_DATA_DIR`
+changes the private data location. Keep these settings stable while a session is
+running. Unknown Teams builds are refused; use the full `browser` client on its
+own port if your Teams build is not yet supported.
+
+On macOS, both dedicated test browsers use mock-keychain encryption because the
+headless shell uses it. This profile contains sensitive login state and remains in
+a private directory; it never opens your ordinary browser profile.
+
+The integrated CLI measured about **307 MiB after collection and 322 MiB idle**
+of summed browser process physical footprint on macOS with a personal account.
+Signed-in reads, visible-to-headless login, sending/readback and incoming updates
+from a second verified client passed. This is approximate process accounting, not a guaranteed RAM cap or a
+Linux measurement. Startup peaks, large accounts, overnight use, reconnect/MFA and
+Linux/WSL2 signed-in operation still need validation. Size-oriented V8 settings may
+trade CPU for memory. Avatar fields may be absent because UI photos are not loaded.
+Sending still requires `init --allow-send` and the existing send confirmation.
+
 ## Graph boundaries
 
 - The Graph backend supports Microsoft 365 work or school accounts only. Use the experimental desktop backend on macOS, Windows or WSL for personal Microsoft accounts; the relevant Teams Graph endpoints do not support them.
 - A work account can authenticate successfully before Microsoft Teams is licensed or provisioned; `teams doctor` distinguishes identity access from Teams availability.
 - Calling and screen sharing are not available as a delegated user CLI; Graph calling is built around bot/application scenarios.
-- No extracted desktop tokens, browser interception, or direct calls to private Teams services; the experimental desktop backend reads the local client cache and sends only through the Teams window's own client.
+- No extracted desktop tokens or direct calls to private Teams services; the experimental desktop backend reads the local client cache and sends only through the Teams window's own client.
 - Tenant policy and admin consent can restrict delegated capabilities.
 
 ## CLI Spec

{teams_cli-0.1.12 → teams_cli-0.2.0}/docs/releases.md

@@ -23,6 +23,29 @@ do not bump again. Its tag starts the release workflow.
 
 Cargo and Python package versions are kept synchronized as one release unit.
 
+## Release 0.2.0
+
+The managed lightweight browser is an experimental personal-account option on
+macOS and Linux/WSL2. `teams init --backend desktop --desktop-client browser-core`
+installs a matching Chrome for Testing pair from Google's Stable channel, uses
+port 9223, and saves the CLI profile only after both visible and hidden chat reads
+succeed. No version bump is needed: 0.2.0 is already prepared.
+
+Fresh macOS onboarding passed real downloads, automatic hiding, signed-in reads,
+one-shot sends with exact ID/content readback, incoming updates from a separate
+verified client without reloading, reuse with the download network unavailable,
+stale-process reconnection, repeated login, quiet mode, and verified shutdown.
+The managed browser measured approximately 316 MiB idle process footprint in this
+short personal-account run. macOS/Linux tests and lint, and Windows cross-compilation
+cover the installer and integration. Linux signed-in use, MFA expiry, prolonged
+operation and work/school core accounts remain outside the validated scope.
+
+After publication workflows finish, verify every intended target:
+
+```sh
+vership verify 0.2.0 --targets tag,release,crates,pypi
+```
+
 ## Release 0.1.11
 
 The `0.1.11` candidate builds on the desktop implementation validated in
@@ -128,3 +151,49 @@ uses the package version unless an explicit `version` is supplied, builds the
 real artifacts, and exercises registry validation without publishing packages,
 creating a GitHub release, generating attestations, or updating downstream
 packaging.
+
+## Browser-client validation
+
+The optional `--desktop-client browser` route runs an isolated Chrome/Chromium/Edge
+profile on macOS or Linux, including WSL2 with a Linux browser. A visible initial
+sign-in and subsequent headless operation use the same persistent profile. Native
+Teams and the WSL Windows helper retain their existing behavior.
+
+Before claiming live browser compatibility, validate signed-in personal and
+work/school cache reads, a single explicitly approved send with exact readback,
+visible-to-headless session persistence, expired-sign-in recovery, and normal
+shutdown on each intended platform. Linux process/socket tests and browser lifecycle
+smoke tests establish plumbing behavior, not signed-in Teams compatibility.
+
+Repeat the unsigned-in real-browser lifecycle test with a test installation:
+
+```sh
+TEAMS_DESKTOP_BROWSER=/absolute/path/to/test/chromium cargo test --locked --test desktop browser_lifecycle_with_disposable_profile -- --ignored
+```
+
+The test uses a disposable profile, preserves the normal browser profile, exercises
+idempotent connect and mode-change refusal, and closes the managed browser on exit.
+On macOS, use Chrome for Testing for this short-lived validation.
+
+Automatic browser login opens visibly, waits for a successful chat read, closes
+only the verified managed browser, and restarts headless with the same profile.
+The headless chat read must also succeed. Test `desktop login` and browser `init`
+with real sign-in, MFA, an empty chat list, expiry, and interrupted/timeout recovery
+before claiming this automatic flow is validated on a platform.
+
+
+## Core browser release checks
+
+`browser-core` is an opt-in, build-pinned personal-account route. It requires
+a matching Chrome for Testing / chrome-headless-shell pair (automatically
+installed from Google on first setup) and a separate private profile. A startup verifies the retained data client with a fresh chat
+query before allowing cache reads or sends. Unknown bootstrap hashes and missing
+readiness markers refuse operations; there is no automatic full-UI fallback.
+
+Release validation should cover actual CLI connect/read/login/disconnect, incoming
+updates, a separately approved send and exact readback, and footprint after those
+operations. Pure browser prototype evidence is insufficient for CLI integration.
+Run macOS and Linux checks; compile Windows native paths too. Do not claim Linux
+signed-in compatibility, work/school core support, a fixed RAM limit, or long-running
+reliability from the short personal-account macOS validation. Prototype reports,
+profiles, public bundle copies and memory snapshots remain local and uncommitted.

{teams_cli-0.1.12 → teams_cli-0.2.0}/src/backend.rs

@@ -20,9 +20,8 @@ impl TeamsBackend {
             BackendKind::Graph => Ok(Self::Graph(GraphClient::new(
                 auth::access_token(&name, &selected).await?,
             ))),
-            BackendKind::Desktop => Ok(Self::Desktop(Box::new(DesktopClient::with_account(
-                selected.desktop_port,
-                selected.desktop_account,
+            BackendKind::Desktop => Ok(Self::Desktop(Box::new(DesktopClient::from_profile(
+                &selected,
             )?))),
         }
     }

{teams_cli-0.1.12 → teams_cli-0.2.0}/src/cli.rs

@@ -9,7 +9,9 @@ use crate::output::OutputFormat;
     version,
     long_version = env!("TEAMS_LONG_VERSION"),
     about = "Microsoft Teams from your terminal, for humans and agents",
-    after_help = "Get started:\n  teams init                         Guided setup\n  teams tui --demo                   Explore without an account\n  teams doctor                       Diagnose configuration and access\n  teams schema --command 'messages send'\n                                     Inspect the automation contract"
+    after_help = "Get started:\n  teams init                         Guided setup\n  teams init --backend desktop --desktop-client browser-core
+                                     Lightweight browser, personal account
+  teams tui --demo                   Explore without an account\n  teams doctor                       Diagnose configuration and access\n  teams schema --command 'messages send'\n                                     Inspect the automation contract"
 )]
 pub struct Cli {
     /// Config profile to use
@@ -107,6 +109,9 @@ pub struct InitArgs {
     /// Select the personal or work/school Teams surface; auto refuses mixed surfaces
     #[arg(long, value_enum)]
     pub desktop_account: Option<crate::config::DesktopAccount>,
+    /// Use the native Teams app or a dedicated Chrome/Edge browser profile
+    #[arg(long, value_enum)]
+    pub desktop_client: Option<crate::config::DesktopClientKind>,
     /// Override the maintained teams-cli public-client application ID
     #[arg(long)]
     pub client_id: Option<String>,
@@ -262,16 +267,24 @@ pub struct TuiArgs {
 pub enum DesktopCommand {
     /// Inspect endpoint metadata and managed-session recovery state
     Status(DesktopArgs),
-    /// Restart Teams with debugging enabled, preserving existing settings
+    /// Open a debugging session (native Teams restart or dedicated browser launch)
     Connect(DesktopArgs),
-    /// Close this CLI's debugging session by restarting Teams normally
+    /// Sign in visibly, then automatically continue headless (browser only)
+    Login(DesktopArgs),
+    /// Close the dedicated browser, or restart native Teams normally
     Disconnect(DesktopArgs),
-    /// Restore settings after interrupted setup, without restarting Teams
+    /// Recover interrupted native settings or close a managed browser session
     Recover(DesktopArgs),
 }
 
 #[derive(Debug, Args)]
 pub struct DesktopArgs {
+    /// Override the configured desktop client
+    #[arg(long, value_enum)]
+    pub desktop_client: Option<crate::config::DesktopClientKind>,
+    /// Open the browser visibly for sign-in (browser connect only)
+    #[arg(long)]
+    pub visible: bool,
     /// Override the selected profile's desktop port
     #[arg(long, value_parser = clap::value_parser!(u16).range(1024..))]
     pub port: Option<u16>,