zibloh 0.1.0__tar.gz

zibloh-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+*.zip

zibloh-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

zibloh-0.1.0/PKG-INFO

@@ -0,0 +1,153 @@
+Metadata-Version: 2.5
+Name: zibloh
+Version: 0.1.0
+Summary: Zibloh CLI and MCP server: build, deploy and run Zibloh robots from the terminal or Claude Code
+Project-URL: Homepage, https://zibloh.com
+Project-URL: Repository, https://github.com/Milmoh/zibloh-mcp
+Author: Milmoh
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: automation,claude-code,mcp,robots,rpa,zibloh
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.11
+Requires-Dist: httpx<1,>=0.27
+Requires-Dist: mcp<3,>=2.2
+Requires-Dist: typer<1,>=0.12
+Description-Content-Type: text/markdown
+
+# Zibloh CLI and Claude Code plugin
+
+Write, deploy, configure, run and debug [Zibloh](https://zibloh.com) robots from the terminal or
+from Claude Code. The same package is:
+
+- the `zibloh` CLI (`zibloh <module> <action>`, every command takes `--json`);
+- an MCP server (`zibloh mcp`, stdio) with the same operations as `<module>_<action>` tools;
+- a Claude Code plugin: the MCP server, three skills (`zibloh-setup`, `zibloh-workflow`,
+  `zibloh-robot-authoring`) and a hook that keeps API keys out of prompts.
+
+## Before you start
+
+1. **Features.** Your company needs the **Autoservicio** (`self_serve`) and **API Keys**
+   features enabled, plus **Secrets de robot** if your robots need credentials. Ask your Zibloh
+   contact.
+2. **A company admin to approve the login.** Logging in opens the web app and a company admin
+   clicks *Autorizar* (see [Log in](#log-in)). Nobody creates or copies an API key by hand.
+3. **Network access to `app.zibloh.com`.** Everything the CLI and the MCP server do, including
+   uploading robot code, goes to `https://app.zibloh.com` (`https://devapp.zibloh.com` for
+   Milmoh's dev platform). If Claude runs with a network allowlist, that domain must be on it:
+
+   - **Claude Desktop / claude.ai** (code execution): an organization Owner adds
+     `app.zibloh.com` in *Organization settings → Capabilities → Code execution*, under the
+     additional allowed domains. Members of a Team/Enterprise organization cannot change it
+     themselves. Without it the session fails with `403` and `blocked-by-allowlist` from
+     Claude's proxy, before the request reaches Zibloh.
+   - **Claude Code with the sandbox enabled**: add it to `sandbox.network.allowedDomains` in
+     `~/.claude/settings.json` (or the project's `.claude/settings.json`):
+
+     ```json
+     { "sandbox": { "network": { "allowedDomains": ["app.zibloh.com"] } } }
+     ```
+
+   - **Company firewall / proxy**: allow outbound HTTPS to `app.zibloh.com`.
+
+   Nothing else is needed: no `amazonaws.com` domains.
+
+## Install
+
+Claude Code plugin:
+
+```
+/plugin marketplace add Milmoh/zibloh-mcp
+/plugin install zibloh@zibloh
+```
+
+CLI only (Python 3.11+; with [uv](https://docs.astral.sh/uv/) or pipx):
+
+```bash
+uv tool install zibloh      # or: pipx install zibloh
+zibloh version
+```
+
+Upgrade with `uv tool upgrade zibloh`.
+
+## Log in
+
+From Claude Code, just ask ("log me in to Zibloh"): Claude calls the `auth_login` tool. From a
+terminal:
+
+```bash
+zibloh login            # --env dev for Milmoh's dev platform
+zibloh whoami
+```
+
+Either way your browser opens at `app.zibloh.com/cli-login?code=XXXX-XXXX` (if it does not, open
+the URL shown). Log in, check that the code matches the one in your terminal or in Claude Code,
+choose what it may do (*Completo*, *Ejecución* or *Lectura*, and *MCP* for Claude Code) and
+click **Autorizar**. The CLI then receives an API key for this computer, named
+`Claude Code · <computer>` or `CLI · <computer>`, and stores it in
+`~/.config/zibloh/credentials.json` (mode 0600). The key never appears on screen or in the chat;
+to cut access, revoke it in *Configuración de empresa → API Keys*. Approving needs a company
+admin.
+
+For CI and scripts that already have a key: `zibloh login --with-key < keyfile` (or the hidden
+prompt). `ZIBLOH_API_KEY`, `ZIBLOH_BASE_URL`, `ZIBLOH_ENV` and `ZIBLOH_PROFILE` override the
+stored login; `--profile` switches between saved logins.
+
+The plugin also stops any prompt that contains a Zibloh API key (`zbl_…`) before Claude reads
+it. If that happens, revoke the key.
+
+## The loop
+
+```bash
+zibloh launchers list                                  # where can it run
+zibloh robots init ./my-robot                          # scaffold from the template
+# ... write main.py ...
+zibloh robots validate ./my-robot --target cloud
+zibloh robots create --name "Facturas proveedor"       # once; note the robot_id
+zibloh robots target <robot_id> --cloud                # or --launcher <launcher_id>
+zibloh secrets create ERP_PASSWORD                     # hidden prompt
+zibloh robots secrets bind <robot_id> ERP_PASSWORD
+zibloh robots deploy <robot_id> ./my-robot
+zibloh robots options define <robot_id> --from-config ./my-robot/config.json
+zibloh robots options set <robot_id> test_mode=true
+zibloh robots run <robot_id> --wait
+zibloh robots executions logs <execution_id>
+```
+
+Schedules (`cron`, `auto_execute`) are set in the web app for now.
+
+## What it will not do
+
+- Show secret values: there is no reveal command, and the MCP tools only take secrets from an
+  environment variable or a file, never as text.
+- Create companies, enable features, create launcher licences or manage users: those stay in
+  the web app.
+
+## Audit
+
+Every call carries `X-Zibloh-Client` (`cli`/`mcp`), `X-Zibloh-Tool` (the command or tool),
+`X-Zibloh-Session` (one per process, or `ZIBLOH_SESSION`) and `X-Request-Id`. Zibloh stores one
+audit row per call made with an API key.
+
+## Development
+
+```bash
+uv venv && uv pip install -e . pytest respx
+.venv/bin/pytest
+```
+
+Releases: bump the version in `pyproject.toml`, `src/zibloh/__init__.py` and
+`.claude-plugin/plugin.json`, merge, then push a `vX.Y.Z` tag; `.github/workflows/publish.yml`
+publishes to PyPI with trusted publishing (environment `pypi`, no stored token).
+
+`src/zibloh/templates/` is a copy of `main.py`, `main_browser_template.py`, `config.json` and
+`requirements.txt` from the `zibloh-robot-template` repo; keep them in sync.
+
+## License
+
+Apache-2.0. See [LICENSE](https://github.com/Milmoh/zibloh-mcp/blob/main/LICENSE).

zibloh-0.1.0/README.md

@@ -0,0 +1,131 @@
+# Zibloh CLI and Claude Code plugin
+
+Write, deploy, configure, run and debug [Zibloh](https://zibloh.com) robots from the terminal or
+from Claude Code. The same package is:
+
+- the `zibloh` CLI (`zibloh <module> <action>`, every command takes `--json`);
+- an MCP server (`zibloh mcp`, stdio) with the same operations as `<module>_<action>` tools;
+- a Claude Code plugin: the MCP server, three skills (`zibloh-setup`, `zibloh-workflow`,
+  `zibloh-robot-authoring`) and a hook that keeps API keys out of prompts.
+
+## Before you start
+
+1. **Features.** Your company needs the **Autoservicio** (`self_serve`) and **API Keys**
+   features enabled, plus **Secrets de robot** if your robots need credentials. Ask your Zibloh
+   contact.
+2. **A company admin to approve the login.** Logging in opens the web app and a company admin
+   clicks *Autorizar* (see [Log in](#log-in)). Nobody creates or copies an API key by hand.
+3. **Network access to `app.zibloh.com`.** Everything the CLI and the MCP server do, including
+   uploading robot code, goes to `https://app.zibloh.com` (`https://devapp.zibloh.com` for
+   Milmoh's dev platform). If Claude runs with a network allowlist, that domain must be on it:
+
+   - **Claude Desktop / claude.ai** (code execution): an organization Owner adds
+     `app.zibloh.com` in *Organization settings → Capabilities → Code execution*, under the
+     additional allowed domains. Members of a Team/Enterprise organization cannot change it
+     themselves. Without it the session fails with `403` and `blocked-by-allowlist` from
+     Claude's proxy, before the request reaches Zibloh.
+   - **Claude Code with the sandbox enabled**: add it to `sandbox.network.allowedDomains` in
+     `~/.claude/settings.json` (or the project's `.claude/settings.json`):
+
+     ```json
+     { "sandbox": { "network": { "allowedDomains": ["app.zibloh.com"] } } }
+     ```
+
+   - **Company firewall / proxy**: allow outbound HTTPS to `app.zibloh.com`.
+
+   Nothing else is needed: no `amazonaws.com` domains.
+
+## Install
+
+Claude Code plugin:
+
+```
+/plugin marketplace add Milmoh/zibloh-mcp
+/plugin install zibloh@zibloh
+```
+
+CLI only (Python 3.11+; with [uv](https://docs.astral.sh/uv/) or pipx):
+
+```bash
+uv tool install zibloh      # or: pipx install zibloh
+zibloh version
+```
+
+Upgrade with `uv tool upgrade zibloh`.
+
+## Log in
+
+From Claude Code, just ask ("log me in to Zibloh"): Claude calls the `auth_login` tool. From a
+terminal:
+
+```bash
+zibloh login            # --env dev for Milmoh's dev platform
+zibloh whoami
+```
+
+Either way your browser opens at `app.zibloh.com/cli-login?code=XXXX-XXXX` (if it does not, open
+the URL shown). Log in, check that the code matches the one in your terminal or in Claude Code,
+choose what it may do (*Completo*, *Ejecución* or *Lectura*, and *MCP* for Claude Code) and
+click **Autorizar**. The CLI then receives an API key for this computer, named
+`Claude Code · <computer>` or `CLI · <computer>`, and stores it in
+`~/.config/zibloh/credentials.json` (mode 0600). The key never appears on screen or in the chat;
+to cut access, revoke it in *Configuración de empresa → API Keys*. Approving needs a company
+admin.
+
+For CI and scripts that already have a key: `zibloh login --with-key < keyfile` (or the hidden
+prompt). `ZIBLOH_API_KEY`, `ZIBLOH_BASE_URL`, `ZIBLOH_ENV` and `ZIBLOH_PROFILE` override the
+stored login; `--profile` switches between saved logins.
+
+The plugin also stops any prompt that contains a Zibloh API key (`zbl_…`) before Claude reads
+it. If that happens, revoke the key.
+
+## The loop
+
+```bash
+zibloh launchers list                                  # where can it run
+zibloh robots init ./my-robot                          # scaffold from the template
+# ... write main.py ...
+zibloh robots validate ./my-robot --target cloud
+zibloh robots create --name "Facturas proveedor"       # once; note the robot_id
+zibloh robots target <robot_id> --cloud                # or --launcher <launcher_id>
+zibloh secrets create ERP_PASSWORD                     # hidden prompt
+zibloh robots secrets bind <robot_id> ERP_PASSWORD
+zibloh robots deploy <robot_id> ./my-robot
+zibloh robots options define <robot_id> --from-config ./my-robot/config.json
+zibloh robots options set <robot_id> test_mode=true
+zibloh robots run <robot_id> --wait
+zibloh robots executions logs <execution_id>
+```
+
+Schedules (`cron`, `auto_execute`) are set in the web app for now.
+
+## What it will not do
+
+- Show secret values: there is no reveal command, and the MCP tools only take secrets from an
+  environment variable or a file, never as text.
+- Create companies, enable features, create launcher licences or manage users: those stay in
+  the web app.
+
+## Audit
+
+Every call carries `X-Zibloh-Client` (`cli`/`mcp`), `X-Zibloh-Tool` (the command or tool),
+`X-Zibloh-Session` (one per process, or `ZIBLOH_SESSION`) and `X-Request-Id`. Zibloh stores one
+audit row per call made with an API key.
+
+## Development
+
+```bash
+uv venv && uv pip install -e . pytest respx
+.venv/bin/pytest
+```
+
+Releases: bump the version in `pyproject.toml`, `src/zibloh/__init__.py` and
+`.claude-plugin/plugin.json`, merge, then push a `vX.Y.Z` tag; `.github/workflows/publish.yml`
+publishes to PyPI with trusted publishing (environment `pypi`, no stored token).
+
+`src/zibloh/templates/` is a copy of `main.py`, `main_browser_template.py`, `config.json` and
+`requirements.txt` from the `zibloh-robot-template` repo; keep them in sync.
+
+## License
+
+Apache-2.0. See [LICENSE](https://github.com/Milmoh/zibloh-mcp/blob/main/LICENSE).

zibloh-0.1.0/pyproject.toml

@@ -0,0 +1,48 @@
+[project]
+name = "zibloh"
+version = "0.1.0"
+description = "Zibloh CLI and MCP server: build, deploy and run Zibloh robots from the terminal or Claude Code"
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Milmoh" }]
+keywords = ["zibloh", "rpa", "robots", "automation", "mcp", "claude-code"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Topic :: Software Development :: Build Tools",
+]
+dependencies = [
+    "httpx>=0.27,<1",
+    "typer>=0.12,<1",
+    "mcp>=2.2,<3",
+]
+
+[project.urls]
+Homepage = "https://zibloh.com"
+Repository = "https://github.com/Milmoh/zibloh-mcp"
+
+[project.scripts]
+zibloh = "zibloh.cli:main"
+
+[dependency-groups]
+dev = ["pytest>=8", "respx>=0.21"]
+
+[build-system]
+requires = ["hatchling>=1.27"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/zibloh"]
+
+# The sdist is the CLI source only: no tests, skills or plugin files.
+[tool.hatch.build.targets.sdist]
+include = ["src/zibloh", "README.md", "LICENSE", "pyproject.toml"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+pythonpath = ["tests"]

zibloh-0.1.0/src/zibloh/__init__.py

@@ -0,0 +1,3 @@
+"""Zibloh CLI and MCP server."""
+
+__version__ = "0.1.0"

zibloh-0.1.0/src/zibloh/__main__.py

@@ -0,0 +1,3 @@
+from zibloh.cli import main
+
+main()