asher-cli 0.0.4__tar.gz → 0.1.0__tar.gz

asher_cli-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,24 @@
+## Summary
+
+<!-- What does this PR change, and why? -->
+
+## Related issue
+
+Closes #
+
+## Changes
+
+-
+
+## Testing
+
+- [ ] `pytest` passes locally
+- [ ] Added/updated tests for new or changed behavior
+- [ ] Manually ran the CLI to verify the change (`asher ...`)
+
+## Checklist
+
+- [ ] Code is linted/formatted per project conventions
+- [ ] README / CLI help text updated if flags or commands changed
+- [ ] No secrets, tokens, or local paths committed
+- [ ] Version bump considered if this affects the published PyPI package

{asher_cli-0.0.4 → asher_cli-0.1.0}/.github/workflows/ci.yml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7
-      - uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+      - uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
       - run: uv sync --dev
       - run: uv run ruff check .
       - run: uv run ruff format --check .
@@ -29,6 +29,6 @@ jobs:
     runs-on: ${{ matrix.os }}
     steps:
       - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7
-      - uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+      - uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
       - run: uv sync --dev
       - run: uv run pytest tests/ -v --tb=short

{asher_cli-0.0.4 → asher_cli-0.1.0}/.github/workflows/claude-code-review.yml

@@ -33,7 +33,7 @@ jobs:
 
       - name: Run Claude Code Review
         id: claude-review
-        uses: anthropics/claude-code-action@428971d2ecd6e3a7cb0ee0da2a3a8b33fdb3678d # v1
+        uses: anthropics/claude-code-action@af0559ee4f514d1ef21826982bed13f7edc3c35e # v1
         with:
           claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
           plugin_marketplaces: 'https://github.com/anthropics/claude-code.git'

{asher_cli-0.0.4 → asher_cli-0.1.0}/.github/workflows/claude.yml

@@ -32,7 +32,7 @@ jobs:
 
       - name: Run Claude Code
         id: claude
-        uses: anthropics/claude-code-action@428971d2ecd6e3a7cb0ee0da2a3a8b33fdb3678d # v1
+        uses: anthropics/claude-code-action@af0559ee4f514d1ef21826982bed13f7edc3c35e # v1
         with:
           claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
 

{asher_cli-0.0.4 → asher_cli-0.1.0}/.github/workflows/coverage.yml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7
-      - uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+      - uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
       - run: uv sync --dev
       - name: Run tests with coverage
         run: uv run pytest tests/ --cov=asher --cov-report=lcov --cov-report=term-missing

{asher_cli-0.0.4 → asher_cli-0.1.0}/.github/workflows/release.yml

@@ -20,7 +20,7 @@ jobs:
       - name: Extract version from branch name
         id: version
         run: echo "version=${GITHUB_REF_NAME#release/}" >> "$GITHUB_OUTPUT"
-      - uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+      - uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
       - run: uv build
       - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7
         with:
@@ -37,7 +37,7 @@ jobs:
         with:
           name: dist
           path: dist/
-      - uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # release/v1
+      - uses: pypa/gh-action-pypi-publish@ba38be9e461d3875417946c167d0b5f3d385a247 # release/v1
 
   github-release:
     name: Create GitHub Release

{asher_cli-0.0.4 → asher_cli-0.1.0}/CLAUDE.md

@@ -41,6 +41,8 @@ asher/
   login_flow.py     LoginFlow state machine — inline email/password prompt in command bar
   robot_protocol.py RobotProtocol structural Protocol for pylitterbot robot objects
   robot_adapters.py RobotAdapter ABC + LR3/LR4/LR5 subclasses + make_adapter() factory
+  mcp_config.py     Claude Desktop config read/write for the /mcp slash command
+  mcp_bridge.py     asher-mcp-launch console script — keyring-backed pylitterbot MCP launcher
   __main__.py       main() entry point
   commands/
     base.py         Command ABC, SlashCommand, CommandRegistry
@@ -61,6 +63,9 @@ tests/
   test_connection_mixin.py ConnectionMixin structure
   test_monitoring.py      MonitoringMixin async methods
   test_ui.py              UIMixin constants, CSS, helper existence
+  test_mcp_config.py      Claude Desktop config read/write
+  test_mcp_bridge.py      mcp_bridge launcher credential/subprocess handling
+  test_mcp_command.py     /mcp slash command dispatch
 
 .github/workflows/
   ci.yml            ruff + mypy + pytest on every push/PR
@@ -83,13 +88,23 @@ LITTER_ROBOT_PASSWORD=...
 Keyring service name: `asher-cli`, keys `email` and `password`.
 Helper functions in `asher/connection/__init__.py`: `_keyring_load()`, `_keyring_save()`, `_keyring_delete()`.
 
+## MCP bridge (`/mcp`)
+
+pylitterbot ships an optional MCP server (`pip install pylitterbot[mcp]`, run via `python -m pylitterbot.mcp`) that lets an MCP client like Claude Desktop monitor/control the robot directly. Its own docs configure it with plaintext credentials in the client's JSON config — asher-cli avoids that:
+
+- `/mcp on|off|status` (in `asher/commands/__init__.py`, logic in `asher/mcp_config.py`) adds/removes an entry (named by `mcp_config._SERVER_NAME`) in every `claude_desktop_config.json` this OS's Claude Desktop might read (`mcp_config.config_paths()` — on Windows this includes both the standard installer path and any MSIX/Microsoft Store virtualized path). The entry's `command` is `sys.executable -m asher.mcp_bridge` — never the credentials themselves.
+- `/mcp on` also auto-installs pylitterbot's `mcp` extra via `sys.executable -m pip install "pylitterbot[mcp]==<installed version>"` if the `mcp` package isn't importable yet.
+- `asher/mcp_bridge.py` (console script `asher-mcp-launch`) is what Claude Desktop actually spawns. It reads email/password from the OS keyring at process start, sets them as `LITTER_ROBOT_USERNAME`/`LITTER_ROBOT_PASSWORD` (pylitterbot's expected names — note these differ from asher-cli's own `.env` var `LITTER_ROBOT_USER`) in that process's environment only, then execs `python -m pylitterbot.mcp`. No credentials ever touch the on-disk MCP config.
+- `/mcp on` requires keyring credentials. If none are found but `.env` fallback credentials are set, it copies them into the keyring automatically (since the bridge process can't reliably discover a project-relative `.env` — Claude Desktop controls its working directory, not asher-cli).
+- Requires the `mcp` extra: `uv sync --extra mcp` / `pip install asher-cli[mcp]`. Restart Claude Desktop after toggling for the change to take effect.
+
 ## Command convention
 
 **Normal commands** (no prefix) — robot actions only:
 `clean`, `status`, `lock`, `unlock`, `sleep`, `wake`, `night-light on|off|auto`, `night-light-brightness <level>`, `history`, `clear`, `help`
 
 **Slash commands** (`/` prefix) — app management only:
-`/login`, `/logout`, `/exit`, `/robots`, `/robot <index|name>`
+`/login`, `/logout`, `/exit`, `/robots`, `/robot <index|name>`, `/pets`, `/pet <index|name>`, `/cat on|off|color <hex>`, `/refresh <seconds|off>`, `/config`, `/mcp on|off|status`
 
 **Special cases** (accepted both with and without `/`):
 `exit`, `quit`, `q` — exit the app
@@ -144,6 +159,10 @@ pylitterbot auto-detects robot type. Commands that differ per model are handled
 - `robot.set_night_light_brightness(int)` or `robot.set_night_light_mode(NightLightMode)`
 - `robot.get_activity_history(limit=int)` → list of `Activity` objects with `.timestamp` and `.action` (`LitterBoxStatus` enum)
 
+## Code comments
+
+Don't add comments above functions or inline unless the WHY is genuinely non-obvious (a hidden constraint, a subtle invariant, a workaround for a specific bug). Well-named identifiers should make the WHAT self-evident. Before reaching for a comment, check whether the explanation can instead be expressed through abstraction or encapsulation — e.g. domain logic buried in a mixin or command handler should move to a self-commenting, domain-named method rather than being explained in a comment. Favor human-readable, domain-driven names and logical flow over prose explanations, while keeping code legible to agents working in this repo.
+
 ## Development notes
 
 - Textual and pylitterbot are both asyncio-native — compose cleanly with `@work` tasks

asher_cli-0.1.0/CODEOWNERS

@@ -0,0 +1 @@
+* @karanshukla

{asher_cli-0.0.4 → asher_cli-0.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: asher-cli
-Version: 0.0.4
+Version: 0.1.0
 Summary: Terminal dashboard for Litter Robot (LR3/LR4/LR5) via the Whisker cloud API
 License: MIT License
         
@@ -35,11 +35,13 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Topic :: Home Automation
 Requires-Python: >=3.10
 Requires-Dist: keyring>=24.0.0
-Requires-Dist: pylitterbot==2025.5.0
+Requires-Dist: pylitterbot==2025.6.2
 Requires-Dist: python-dotenv>=1.0.0
 Requires-Dist: rich>=13.0.0
 Requires-Dist: textual>=0.47.0
 Requires-Dist: tzlocal>=5.4
+Provides-Extra: mcp
+Requires-Dist: pylitterbot[mcp]==2025.6.2; extra == 'mcp'
 Description-Content-Type: text/markdown
 
 # Asher CLI
@@ -154,12 +156,14 @@ LITTER_ROBOT_PASSWORD=yourpassword
 ## Releasing
 
 ```bash
-# bump version, commit, and tag in one step
+# bump version, commit, and tag in one step, then push with tags
 uv run bump-my-version bump patch    # 0.0.1 → 0.0.2
 uv run bump-my-version bump minor    # 0.0.2 → 0.1.0
 uv run bump-my-version bump major    # 0.1.0 → 1.0.0
 
-# then push the release branch to trigger PyPI publish
+git push && git push --tags
+
+# then push the release branch to trigger PyPI publish with the new semver
 git checkout -b release/0.0.2
 git push origin release/0.0.2
 ```

{asher_cli-0.0.4 → asher_cli-0.1.0}/README.md

@@ -110,12 +110,14 @@ LITTER_ROBOT_PASSWORD=yourpassword
 ## Releasing
 
 ```bash
-# bump version, commit, and tag in one step
+# bump version, commit, and tag in one step, then push with tags
 uv run bump-my-version bump patch    # 0.0.1 → 0.0.2
 uv run bump-my-version bump minor    # 0.0.2 → 0.1.0
 uv run bump-my-version bump major    # 0.1.0 → 1.0.0
 
-# then push the release branch to trigger PyPI publish
+git push && git push --tags
+
+# then push the release branch to trigger PyPI publish with the new semver
 git checkout -b release/0.0.2
 git push origin release/0.0.2
 ```