lightnow-cli 1.0.3__tar.gz → 1.0.5__tar.gz

{lightnow_cli-1.0.3 → lightnow_cli-1.0.5}/.github/workflows/ci.yml

@@ -4,7 +4,6 @@ on:
   pull_request:
   push:
     branches:
-      - master
       - main
 
 permissions:

{lightnow_cli-1.0.3 → lightnow_cli-1.0.5}/.github/workflows/release.yml

@@ -57,6 +57,26 @@ jobs:
           path: dist/*
           if-no-files-found: error
 
+  github-release:
+    name: Create GitHub release
+    runs-on: ubuntu-latest
+    needs: build
+    permissions:
+      contents: write
+
+    steps:
+      - name: Download distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: python-distributions
+          path: dist
+
+      - name: Publish GitHub release notes
+        uses: softprops/action-gh-release@v2
+        with:
+          generate_release_notes: true
+          files: dist/*
+
   publish-pypi:
     name: Publish to PyPI
     runs-on: ubuntu-latest

{lightnow_cli-1.0.3 → lightnow_cli-1.0.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lightnow-cli
-Version: 1.0.3
+Version: 1.0.5
 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
@@ -46,23 +46,37 @@ Description-Content-Type: text/markdown
 
 The **LightNow CLI** connects your local MCP clients with LightNow.
 
-Use it to discover MCP servers, sync client configurations, and run
-MCP servers with LightNow-managed secrets.
+Use it to sign in, discover MCP servers, configure local AI clients such as
+Codex, Claude Desktop, Cursor, VS Code and Google Antigravity, and keep MCP
+server configuration and secrets managed by LightNow.
 
 ## Install
 
-Requirements:
+Requirements for Python-based installs:
 
 - Python 3.11 or higher
 - `pipx`
 - a [LightNow account](https://www.lightnow.ai/)
 
+Install the CLI with Homebrew:
+
+```bash
+brew tap lightnow-ai/tap
+brew install lightnow-cli
+```
+
 Install the CLI with `pipx`:
 
 ```bash
 pipx install lightnow-cli
 ```
 
+Or install it with `uv`:
+
+```bash
+uv tool install lightnow-cli
+```
+
 If you prefer installing directly from the public repository:
 
 ```bash
@@ -102,7 +116,73 @@ Show your favorites:
 lightnow favorites
 ```
 
-## Sync a Client Configuration
+## Configure an MCP Client
+
+The recommended setup is Local Proxy mode: your MCP client gets one `LightNow`
+entry and the local proxy resolves the configured MCP servers and secrets at
+runtime.
+
+Install the Local Proxy executable first with Homebrew:
+
+```bash
+brew tap lightnow-ai/tap
+brew install lightnow-proxy
+```
+
+Or install it with `pipx`:
+
+```bash
+pipx install lightnow-proxy
+```
+
+Or install it with `uv`:
+
+```bash
+uv tool install lightnow-proxy
+```
+
+The proxy package installs the `lightnow-proxy` command used in MCP client configs.
+
+For local development from a checkout:
+
+```bash
+uv tool install --from /path/to/lightnow-proxy lightnow-proxy
+```
+
+Then sync your client:
+
+```bash
+lightnow sync --client codex --local-proxy
+```
+
+Other common clients:
+
+```bash
+lightnow sync --client claude-desktop --local-proxy
+lightnow sync --client antigravity --local-proxy
+lightnow sync --client cursor --local-proxy
+lightnow sync --client vscode --local-proxy
+```
+
+Let LightNow choose the configured organization policy for a client:
+
+```bash
+lightnow sync --client codex --from-settings
+```
+
+Check whether a client is configured as expected:
+
+```bash
+lightnow config-status --client codex
+lightnow config-status --client claude-desktop --json
+lightnow config-status --client cursor --json
+lightnow config-status --client vscode --json
+```
+
+For details, examples, diagrams and troubleshooting, see
+[Connect MCP clients](https://docs.lightnow.ai/getting-started/sync-mcp-clients).
+
+### Direct Sync
 
 Sync your default LightNow runtime profile into Codex:
 
@@ -123,6 +203,13 @@ files:
 lightnow sync --client codex --runner
 ```
 
+For daemon-style local testing, `--local-proxy-transport http` writes a
+localhost Streamable HTTP entry instead of a stdio auto-start entry.
+
+Note: Google has moved individual Gemini CLI users to Antigravity. LightNow
+keeps `gemini-cli` support for Enterprise/API-key environments, but
+`antigravity` is the recommended Google local client target for individuals.
+
 ## Run One Server
 
 Run a configured MCP server through LightNow:

lightnow_cli-1.0.5/README.md

@@ -0,0 +1,190 @@
+# LightNow CLI
+
+[![PyPI](https://img.shields.io/pypi/v/lightnow-cli.svg)](https://pypi.org/project/lightnow-cli/)
+
+The **LightNow CLI** connects your local MCP clients with LightNow.
+
+Use it to sign in, discover MCP servers, configure local AI clients such as
+Codex, Claude Desktop, Cursor, VS Code and Google Antigravity, and keep MCP
+server configuration and secrets managed by LightNow.
+
+## Install
+
+Requirements for Python-based installs:
+
+- Python 3.11 or higher
+- `pipx`
+- a [LightNow account](https://www.lightnow.ai/)
+
+Install the CLI with Homebrew:
+
+```bash
+brew tap lightnow-ai/tap
+brew install lightnow-cli
+```
+
+Install the CLI with `pipx`:
+
+```bash
+pipx install lightnow-cli
+```
+
+Or install it with `uv`:
+
+```bash
+uv tool install lightnow-cli
+```
+
+If you prefer installing directly from the public repository:
+
+```bash
+pipx install git+https://github.com/lightnow-ai/lightnow-cli.git
+```
+
+## Sign In
+
+```bash
+lightnow login
+```
+
+The CLI opens a browser window for LightNow authentication. After sign-in, check
+your session with:
+
+```bash
+lightnow status
+```
+
+## Find MCP Servers
+
+Search the LightNow Registry:
+
+```bash
+lightnow search sonarqube
+```
+
+Show details for one server:
+
+```bash
+lightnow info io.github.SonarSource/sonarqube-mcp-server
+```
+
+Show your favorites:
+
+```bash
+lightnow favorites
+```
+
+## Configure an MCP Client
+
+The recommended setup is Local Proxy mode: your MCP client gets one `LightNow`
+entry and the local proxy resolves the configured MCP servers and secrets at
+runtime.
+
+Install the Local Proxy executable first with Homebrew:
+
+```bash
+brew tap lightnow-ai/tap
+brew install lightnow-proxy
+```
+
+Or install it with `pipx`:
+
+```bash
+pipx install lightnow-proxy
+```
+
+Or install it with `uv`:
+
+```bash
+uv tool install lightnow-proxy
+```
+
+The proxy package installs the `lightnow-proxy` command used in MCP client configs.
+
+For local development from a checkout:
+
+```bash
+uv tool install --from /path/to/lightnow-proxy lightnow-proxy
+```
+
+Then sync your client:
+
+```bash
+lightnow sync --client codex --local-proxy
+```
+
+Other common clients:
+
+```bash
+lightnow sync --client claude-desktop --local-proxy
+lightnow sync --client antigravity --local-proxy
+lightnow sync --client cursor --local-proxy
+lightnow sync --client vscode --local-proxy
+```
+
+Let LightNow choose the configured organization policy for a client:
+
+```bash
+lightnow sync --client codex --from-settings
+```
+
+Check whether a client is configured as expected:
+
+```bash
+lightnow config-status --client codex
+lightnow config-status --client claude-desktop --json
+lightnow config-status --client cursor --json
+lightnow config-status --client vscode --json
+```
+
+For details, examples, diagrams and troubleshooting, see
+[Connect MCP clients](https://docs.lightnow.ai/getting-started/sync-mcp-clients).
+
+### Direct Sync
+
+Sync your default LightNow runtime profile into Codex:
+
+```bash
+lightnow sync --client codex
+```
+
+Preview changes before writing:
+
+```bash
+lightnow sync --client codex --dry-run
+```
+
+Use runner mode when you do not want secrets written into client configuration
+files:
+
+```bash
+lightnow sync --client codex --runner
+```
+
+For daemon-style local testing, `--local-proxy-transport http` writes a
+localhost Streamable HTTP entry instead of a stdio auto-start entry.
+
+Note: Google has moved individual Gemini CLI users to Antigravity. LightNow
+keeps `gemini-cli` support for Enterprise/API-key environments, but
+`antigravity` is the recommended Google local client target for individuals.
+
+## Run One Server
+
+Run a configured MCP server through LightNow:
+
+```bash
+lightnow run --profile default --server sonarqube
+```
+
+## More Documentation
+
+- [CLI usage guide](https://docs.lightnow.ai/getting-started/sync-mcp-clients)
+- [CLI reference](https://docs.lightnow.ai/reference/cli)
+- [Local development](docs/development.md)
+- [Release process](docs/release.md)
+- [Security policy](SECURITY.md)
+- [Contributing](CONTRIBUTING.md)
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

lightnow_cli-1.0.5/docs/development.md

@@ -0,0 +1,77 @@
+# Local Development
+
+## Setup
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+lightnow --help
+```
+
+For local editable installs through `pipx`:
+
+```bash
+pipx install --force --editable .
+```
+
+## Checks
+
+Run all checks:
+
+```bash
+make all
+```
+
+Run targeted checks:
+
+```bash
+make lint
+make format-check
+make isort-check
+make type-check
+make test
+make cli-check
+make integration
+make package
+```
+
+The tests cover command parsing, validation logic, token refresh, registry
+queries, sync patching, local runner behavior, and secret redaction.
+
+## Local Proxy Config Posture
+
+`lightnow sync --client <client> --local-proxy` should leave the target MCP
+client with one LightNow entry and no unmanaged MCP servers unless the customer
+explicitly keeps a mixed setup.
+
+Use the redacted status command while testing client integrations:
+
+```bash
+lightnow config-status --client codex
+lightnow config-status --client claude-desktop
+lightnow config-status --client antigravity --json
+```
+
+Expected states:
+
+- `managed`: only the LightNow Local Proxy entry is configured.
+- `mixed`: LightNow Local Proxy exists, but unmanaged MCP entries are also
+  present.
+- `unmanaged`: MCP entries exist, but none point at the LightNow Local Proxy.
+- `legacy_runner`: older per-server `lightnow run` wrappers are still present.
+- `missing`, `invalid` or `unreadable`: the client config cannot be used as-is.
+
+The command must not print secrets, headers or payloads. It is the local building
+block for future UI-led enablement and enterprise posture reporting.
+
+## Local LightNow Environment
+
+Use the local profile when working against the LightNow local stack:
+
+```bash
+lightnow login --local
+```
+
+Local HTTPS verification depends on the workspace local CA. Run the LightNow
+local stack certificate setup before using `*.lightnow.local` endpoints.

{lightnow_cli-1.0.3 → lightnow_cli-1.0.5}/docs/release.md

@@ -22,7 +22,7 @@ Before publishing a release:
    ```bash
    make all
    ```
-4. Verify the GitHub Actions `CI` workflow is green on `master`.
+4. Verify the GitHub Actions `CI` workflow is green on `main`.
 5. Configure PyPI Trusted Publishing before the first PyPI release:
    - PyPI project name: `lightnow-cli`
    - Owner: `lightnow-ai`
@@ -38,7 +38,13 @@ Before publishing a release:
    - tests pass,
    - source distribution and wheel are built,
    - `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`.
 
 Do not publish with long-lived local PyPI tokens.
 

{lightnow_cli-1.0.3 → lightnow_cli-1.0.5}/lightnow_cli/__init__.py

@@ -1,3 +1,3 @@
 """LightNow CLI - A command-line tool for managing MCP servers."""
 
-__version__ = "1.0.3"
+__version__ = "1.0.5"