lightnow-cli 1.2.0__tar.gz → 1.3.1__tar.gz

{lightnow_cli-1.2.0 → lightnow_cli-1.3.1}/.github/workflows/release.yml

@@ -96,3 +96,27 @@ jobs:
 
       - name: Publish distributions to PyPI
         uses: pypa/gh-action-pypi-publish@release/v1
+
+  update-homebrew:
+    name: Update Homebrew formula
+    runs-on: ubuntu-latest
+    needs: publish-pypi
+
+    steps:
+      - name: Dispatch published version to Homebrew tap
+        env:
+          GH_TOKEN: ${{ secrets.HOMEBREW_TAP_TOKEN }}
+          TAG_NAME: ${{ github.ref_name }}
+        run: |
+          version="${TAG_NAME#v}"
+          payload="$(jq -n \
+            --arg formula "lightnow-cli" \
+            --arg version "$version" \
+            '{event_type: "python-release-published", client_payload: {formula: $formula, version: $version}}')"
+          curl --fail-with-body --silent --show-error \
+            --request POST \
+            --header "Accept: application/vnd.github+json" \
+            --header "Authorization: Bearer ${GH_TOKEN}" \
+            --header "X-GitHub-Api-Version: 2022-11-28" \
+            https://api.github.com/repos/lightnow-ai/homebrew-tap/dispatches \
+            --data "$payload"

lightnow_cli-1.3.1/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "1.3.1"
+}

{lightnow_cli-1.2.0 → lightnow_cli-1.3.1}/CHANGELOG.md

@@ -4,6 +4,33 @@ All notable changes to the LightNow CLI are documented here.
 
 This project follows semantic versioning.
 
+## [1.3.1](https://github.com/lightnow-ai/lightnow-cli/compare/v1.3.0...v1.3.1) (2026-07-17)
+
+
+### Bug Fixes
+
+* **sync:** replace existing codex proxy connection ([c09b7f7](https://github.com/lightnow-ai/lightnow-cli/commit/c09b7f75f9d78c943ed7556b10b10ff99dbb2008))
+
+## [1.3.0](https://github.com/lightnow-ai/lightnow-cli/compare/v1.2.0...v1.3.0) (2026-07-15)
+
+
+### Features
+
+* **#7:** support account-bound proxy connections ([11b2f5a](https://github.com/lightnow-ai/lightnow-cli/commit/11b2f5a3806e2b9f67637e231783692aacdb78de))
+* **#9:** device control plane ([0d1db03](https://github.com/lightnow-ai/lightnow-cli/commit/0d1db033be28b23e45d9ae38bc0c4754a0cd7380))
+* **devices:** register local proxy client inventory ([ebcbe95](https://github.com/lightnow-ai/lightnow-cli/commit/ebcbe95a099d7b203a89c5886a5d90b300a47e38))
+* support account-bound proxy connections ([6d9f3ad](https://github.com/lightnow-ai/lightnow-cli/commit/6d9f3ad8f633182e57ca8291a9eb297a6330fd72))
+
+
+### Bug Fixes
+
+* address account-bound session review ([6e41fd8](https://github.com/lightnow-ai/lightnow-cli/commit/6e41fd881789a0f4ac287fd4abece0c69a964093))
+
+
+### Documentation
+
+* **devices:** explain control plane registration ([f4329f5](https://github.com/lightnow-ai/lightnow-cli/commit/f4329f559ff43f4b501b500b19c3b40f57ad94bf))
+
 ## [1.2.0](https://github.com/lightnow-ai/lightnow-cli/compare/v1.1.0...v1.2.0) (2026-07-12)
 
 

{lightnow_cli-1.2.0 → lightnow_cli-1.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lightnow-cli
-Version: 1.2.0
+Version: 1.3.1
 Summary: Official LightNow CLI for MCP registry discovery, client config sync, and local MCP runner workflows
 Project-URL: Homepage, https://github.com/lightnow-ai/lightnow-cli
 Project-URL: Repository, https://github.com/lightnow-ai/lightnow-cli
@@ -18,6 +18,7 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Topic :: Software Development :: Build Tools
 Classifier: Topic :: Utilities
 Requires-Python: >=3.11
+Requires-Dist: filelock>=3.16.1
 Requires-Dist: httpx>=0.24.0
 Requires-Dist: jsonschema>=4.17.0
 Requires-Dist: pydantic>=2.0.0
@@ -159,6 +160,40 @@ Then sync your client:
 lightnow sync --client codex --local-proxy
 ```
 
+### Multiple accounts and organizations
+
+Each Local Proxy connection can have its own client alias, LightNow login,
+profile and personal or tenant scope. The sync command binds the connection to
+the account that is signed in at that moment; signing in with another account
+later does not silently move an existing connection.
+Connection aliases are either `lightnow` or start with `lightnow-` or
+`lightnow_`, so they remain TOML-safe and distinguishable from unmanaged local
+MCP servers.
+
+For example, configure personal and organization connections side by side:
+
+```bash
+lightnow login
+lightnow sync --client codex --local-proxy \
+  --connection lightnow-personal --profile default
+
+# Sign in with the organization account before creating this connection.
+lightnow login
+lightnow sync --client codex --local-proxy \
+  --connection lightnow-acme --tenant <tenant-id> --profile engineering
+```
+
+Codex then exposes both `lightnow-personal` and `lightnow-acme`. Re-run sync
+with the same `--connection` value to update that connection. Account-bound
+sessions are stored separately under `~/.lightnow/sessions/`; proxy YAML files
+contain only their path and expected identity, never access or refresh tokens.
+
+Use `lightnow config-status --client codex --json` to inspect all connections,
+including their non-secret account, scope, profile and session-binding status.
+Signing in to another account preserves existing bound sessions. An explicit
+`lightnow logout` removes the active account's named session, so proxies bound
+to that account stop authenticating until it is signed in and synced again.
+
 Other common clients:
 
 ```bash
@@ -187,6 +222,12 @@ lightnow config-status --client cursor --json
 lightnow config-status --client vscode --json
 ```
 
+With metadata telemetry enabled, each Local Proxy sync also registers the
+machine and its client-specific Runtime Profile in the LightNow Control Plane.
+The CLI stores a stable installation UUID in its protected configuration and a
+separate stable client-instance UUID in each generated proxy configuration. It
+does not report IP or MAC addresses, serial numbers, local paths, or secrets.
+
 For details, examples, diagrams and troubleshooting, see
 [Connect MCP clients](https://docs.lightnow.ai/getting-started/sync-mcp-clients).
 

{lightnow_cli-1.2.0 → lightnow_cli-1.3.1}/README.md

@@ -113,6 +113,40 @@ Then sync your client:
 lightnow sync --client codex --local-proxy
 ```
 
+### Multiple accounts and organizations
+
+Each Local Proxy connection can have its own client alias, LightNow login,
+profile and personal or tenant scope. The sync command binds the connection to
+the account that is signed in at that moment; signing in with another account
+later does not silently move an existing connection.
+Connection aliases are either `lightnow` or start with `lightnow-` or
+`lightnow_`, so they remain TOML-safe and distinguishable from unmanaged local
+MCP servers.
+
+For example, configure personal and organization connections side by side:
+
+```bash
+lightnow login
+lightnow sync --client codex --local-proxy \
+  --connection lightnow-personal --profile default
+
+# Sign in with the organization account before creating this connection.
+lightnow login
+lightnow sync --client codex --local-proxy \
+  --connection lightnow-acme --tenant <tenant-id> --profile engineering
+```
+
+Codex then exposes both `lightnow-personal` and `lightnow-acme`. Re-run sync
+with the same `--connection` value to update that connection. Account-bound
+sessions are stored separately under `~/.lightnow/sessions/`; proxy YAML files
+contain only their path and expected identity, never access or refresh tokens.
+
+Use `lightnow config-status --client codex --json` to inspect all connections,
+including their non-secret account, scope, profile and session-binding status.
+Signing in to another account preserves existing bound sessions. An explicit
+`lightnow logout` removes the active account's named session, so proxies bound
+to that account stop authenticating until it is signed in and synced again.
+
 Other common clients:
 
 ```bash
@@ -141,6 +175,12 @@ lightnow config-status --client cursor --json
 lightnow config-status --client vscode --json
 ```
 
+With metadata telemetry enabled, each Local Proxy sync also registers the
+machine and its client-specific Runtime Profile in the LightNow Control Plane.
+The CLI stores a stable installation UUID in its protected configuration and a
+separate stable client-instance UUID in each generated proxy configuration. It
+does not report IP or MAC addresses, serial numbers, local paths, or secrets.
+
 For details, examples, diagrams and troubleshooting, see
 [Connect MCP clients](https://docs.lightnow.ai/getting-started/sync-mcp-clients).
 

{lightnow_cli-1.2.0 → lightnow_cli-1.3.1}/docs/release.md

@@ -19,6 +19,9 @@ Required GitHub setup:
 - Repository secret: `RELEASE_PLEASE_TOKEN`
 - Token permissions: contents, pull requests, and issues read/write for this
   repository
+- Repository secret: `HOMEBREW_TAP_TOKEN`
+- Token permissions: contents read/write for `lightnow-ai/homebrew-tap`; the
+  token is used only to send the post-PyPI repository dispatch
 - Repository Actions setting: allow GitHub Actions to create pull requests
 
 Use a real PAT or GitHub App token for `RELEASE_PLEASE_TOKEN`, not the default
@@ -33,7 +36,9 @@ Normal release flow:
 4. Release Please creates the `vX.Y.Z` tag and GitHub Release.
 5. The existing tag-based `Release` workflow builds and publishes PyPI
    distributions through Trusted Publishing.
-6. Update the Homebrew tap after the release artifact is available.
+6. After PyPI succeeds, the release workflow dispatches the exact published
+   version to `lightnow-ai/homebrew-tap`. The tap regenerates, audits, installs,
+   and tests the formula before committing it.
 
 Manual release checklist for fallback or first-time setup:
 
@@ -64,11 +69,10 @@ Manual release checklist for fallback or first-time setup:
    - `twine check` passes,
    - a GitHub Release is created with generated release notes and distribution artifacts,
    - PyPI publish succeeds through Trusted Publishing.
-8. Update the Homebrew tap after the release artifact is available:
-   - repository: `lightnow-ai/homebrew-tap`
-   - formula: `Formula/lightnow-cli.rb`
-   - replace the formula template URL, version and SHA256 with the released artifact,
-   - run `brew audit`, `brew install --build-from-source`, and `brew test`.
+8. Verify the `Update formula` workflow in `lightnow-ai/homebrew-tap`. For a
+   recovery run, dispatch it manually with formula `lightnow-cli` and the exact
+   already-published version; it uses the same generation and verification path
+   as the automatic release dispatch.
 
 Do not publish with long-lived local PyPI tokens.
 

{lightnow_cli-1.2.0 → lightnow_cli-1.3.1}/lightnow_cli/__init__.py

@@ -1,3 +1,3 @@
 """LightNow CLI - A command-line tool for managing MCP servers."""
 
-__version__ = "1.2.0"  # x-release-please-version
+__version__ = "1.3.1"  # x-release-please-version

{lightnow_cli-1.2.0 → lightnow_cli-1.3.1}/lightnow_cli/commands/auth.py

@@ -412,8 +412,10 @@ def login(
         config_manager.set_token(
             token,
             refresh_token if isinstance(refresh_token, str) else None,
-            None,
+            user_info,
+            update_active_session=False,
         )
+        config_manager.persist_current_session(user_info)
 
         console.print("[bold green]✓ Authentication successful![/bold green]")
         if user_info: