@ariobarin/glossa 0.1.0-beta.10 → 0.1.0-beta.12

package/README.md

@@ -24,29 +24,36 @@ macOS or Linux:
 curl -fsSL https://glossa.sh/install.sh | sh
 ```
 
-Then choose a recognizable name during this computer's first enrollment:
+Open a terminal in the directory you want to expose, then run:
 
 ```shell
-cd path/to/a/project
-glossa --device-name "my-workstation" .
+glossa
 ```
 
 The hosted commands run the tracked scripts in `site`. They verify native
-release checksums before installing. Use `glossa update` or its
-`glossa upgrade` alias to update later with the original installation method.
+release checksums before installing. Stop every running Glossa session, then
+rerun the original installation method to update Glossa.
 
 Glossa opens Google sign-in automatically when needed using OAuth Device Authorization Flow. Public client and resource identifiers are built in, so testers do not configure OAuth values. Use the same Google account when authorizing Glossa in ChatGPT.
 
 OAuth and device credentials use the operating-system credential store. If it is unavailable, Glossa warns before using a restricted credential file.
 
-`--device-name` is used only during initial enrollment. Later starts reuse the enrolled name; use `glossa devices rename <id> <name>` to change it. Without the option, the first managed session enrolls the computer under its hostname. `glossa start .` selects the current directory explicitly. Each process registers an independent workspace, so the same computer may expose several workspaces at once. The process prints the canonical root, connection state, shell authority warning, and write or command activity. Press Ctrl+C to disconnect.
+Glossa signs in automatically and exposes the current directory. Pass a directory
+to expose a different workspace. The responsive terminal interface shows the
+workspace, device, and current connection or tool status.
 
-The experimental `glossa ui .` command opens a compact live session HUD and immediately exposes the selected workspace. Press `d` for recent activity, `?` for help, and `q` to disconnect. The screen keeps the worker-account authority warning visible.
+Press `d` for compact tool history, `s` for account and device status, or `?`
+for help. The activity view shows each local tool name and a compact form of its
+input. Press `q` or Ctrl+C to disconnect.
 
-Glossa signs in automatically whenever an authenticated command needs an account. `glossa login` is an optional preflight. `glossa status` validates the session and relay, then reports enrolled devices and active workers. `glossa doctor` performs a read-only readiness check, including the local device credential, and supports `--json`. Use `glossa devices list`, `glossa devices rename <id> <name>`, and `glossa devices revoke <id>` to manage enrolled computers.
+Connected clients can modify files inside the exposed workspace and run commands
+with the full environment and permissions of the operating-system account that
+launched Glossa.
 
-Generate shell completion with `glossa completions <powershell|bash|zsh|fish>` and source the output from your shell profile. For example, use `glossa completions powershell | Out-String | Invoke-Expression` in PowerShell, `source <(glossa completions bash)` in Bash, `source <(glossa completions zsh)` after `compinit` in Zsh, or `glossa completions fish | source` in Fish.
+Use `glossa status` to show the signed-in account, relay, devices, and active
+workspaces. Use `glossa devices revoke <id>` to revoke a device. Use
+`glossa logout` to remove local OAuth credentials and open browser sign-out.
 
 The managed endpoint defaults to `https://mcp.glossa.sh`. Development deployments may override `GLOSSA_RELAY_ORIGIN` and `GLOSSA_WORKER_ORIGIN`. Plain HTTP is accepted only for loopback relay origins and loopback or private IPv4 worker origins.
 
-Run `glossa logout` to remove the CLI's local OAuth credentials. Running workers remain connected until stopped or revoked. Run `glossa logout --browser` before switching Google accounts so the next Glossa authorization does not silently reuse the previous browser session.
+Other running Glossa sessions remain connected until stopped or revoked.