scriptit-cli 0.2.2__tar.gz

scriptit_cli-0.2.2/.claude-plugin/marketplace.json

@@ -0,0 +1,14 @@
+{
+  "name": "script-it",
+  "description": "Script.it for Claude Code. Better automation in a world of agents.",
+  "owner": {
+    "name": "Script.it"
+  },
+  "plugins": [
+    {
+      "name": "scriptit",
+      "source": "./agent-skills",
+      "description": "Automations your teammates and your AI agents can both run, built from readable steps a human can verify."
+    }
+  ]
+}

scriptit_cli-0.2.2/.github/workflows/ci.yml

@@ -0,0 +1,23 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.9", "3.11", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - run: ruff check scriptit_cli tests
+      - run: ruff format --check scriptit_cli tests
+      - run: pytest -q

scriptit_cli-0.2.2/.github/workflows/release.yml

@@ -0,0 +1,64 @@
+name: release
+
+# Publishes a wheel to PyPI when a version tag is pushed.
+#
+# No secrets: PyPI trusted publishing verifies this workflow's identity, and
+# the client carries no keys of its own — usage analytics ride the user's own
+# authenticated connection to their deployment.
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+    inputs:
+      dry_run:
+        description: "Build and check the wheel without publishing"
+        type: boolean
+        default: true
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Verify the tag matches the packaged version
+        if: startsWith(github.ref, 'refs/tags/v')
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          packaged=$(python -c "import scriptit_cli; print(scriptit_cli.__version__)")
+          if [ "$tag" != "$packaged" ]; then
+            echo "tag $tag != scriptit_cli.__version__ $packaged" >&2
+            exit 1
+          fi
+
+      - name: Build
+        run: |
+          python -m pip install --upgrade build twine
+          python -m build
+          python -m twine check dist/*
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      # Trusted publishing: PyPI verifies this workflow's identity, so no API
+      # token is stored anywhere.
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

scriptit_cli-0.2.2/.gitignore

@@ -0,0 +1,13 @@
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+build/
+dist/
+*.egg-info/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.DS_Store
+.coverage
+htmlcov/

scriptit_cli-0.2.2/CONTRIBUTING.md

@@ -0,0 +1,103 @@
+# Contributing
+
+Thanks for helping. Issues and pull requests are both welcome.
+
+## Setup
+
+```bash
+git clone https://github.com/script-it/cli.git
+cd cli
+python -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+```
+
+The suite is fast and needs no network or account — it covers the pure pieces
+(v2 output paging and reconnects, v1 command wrapping and exit-sentinel
+parsing, SSE framing, the credential store, session resolution). Anything that needs a live environment is exercised by
+hand against a real account before release.
+
+`tests/conftest.py` points `XDG_CONFIG_HOME` at a temp directory for every
+test. Keep it that way: without it the credential-store tests read and
+overwrite the real `~/.config/scriptit/credentials.json` on your machine.
+
+## The boundary
+
+The client forwards commands and formats what comes back; it does not execute
+automation, parse scripts, or know what a block is. Its dependencies are
+`requests`, `fire`, `filelock` and `packaging` — all small, and each earning
+its place: the last two replace hand-rolled code that was wrong on Windows and
+wrong about PEP 440.
+
+That boundary is what lets the platform ship features without a client release,
+and it is easy to erode by accident. If a change needs the runtime, it belongs
+in the platform, not here.
+
+`remote.py` supports two deployed session transports. The initial SSE frame
+selects one before dispatch: v2 uses `session_snapshot`, v1 uses
+`load_complete`. V2 sends plain commands, reads output by byte cursor and
+gets exit status from shell events or a saved shell row. V1 requires base64
+wrapping, an exit sentinel and file recovery after its SSE text cap; keep that
+compatibility code isolated.
+
+A shell POST is not safe to repeat after a lost response. Retry only a refusal
+that explicitly says it was not submitted. V2 event reconnects send
+`Last-Event-ID`, match this invocation's message/shell identity and resume
+output reads from the returned byte cursor. A saved truncated preview must
+never count as complete command output.
+
+In practice that means:
+
+- Adding a command that Script.it should answer? Add it there instead — it
+  reaches users through the client they already have.
+- Adding one this client must answer (credentials, transport, moving bytes,
+  session bookkeeping)? Add it to `CLIENT_COMMANDS` in `scriptit_cli/remote.py`,
+  to `_KNOWN_TOKENS` in `scriptit_cli/analytics.py`, and give it `--json`
+  output — or list it in `JSON_STREAMING_COMMANDS` if it streams raw bytes
+  instead of returning a result.
+- Never name a client command something the platform also uses. The client
+  answers its own names first, so a collision silently shadows the real one.
+
+## Analytics
+
+`scriptit_cli/analytics.py` reports command *names*, never their contents. The
+filter is an allowlist (`_KNOWN_TOKENS`), not a pattern — a script name, a
+workspace path and a bearer token are all shaped like a verb, so only "is this
+one of ours?" can tell them apart. A new client command belongs in that set as
+well as in `CLIENT_COMMANDS`; a test asserts the two agree, and another drives
+a real invocation with secrets in argv and asserts they reach no payload.
+
+There is no collector and no key here. Events go to the user's own deployment,
+on the credential the command already used, so `Analytics` is inert until
+something calls `bind()`. That is also why your tests collect nothing by
+default, and why `DO_NOT_TRACK=1` is the whole opt-out.
+
+## Platform support
+
+Linux and macOS are what we test; the client is written to work on Windows
+too. The store lock goes through `filelock`, which uses each platform's own
+primitive, so concurrent credential and state writes serialize everywhere
+rather than only on POSIX. Windows is not in CI, so if something there is
+broken, an issue with a reproduction would be welcome.
+
+## Pull requests
+
+- Include a test for behavior you change. Write the assertion around *why* it
+  matters, not just what the function returns — the transport has several
+  properties (no duplicated execution after a lost acknowledgement, complete
+  Unicode output across pages, `--json` keeping stdout clean) that are invisible
+  until they break.
+- Keep comments about what the code does now, not what it used to do. Change
+  history belongs in commits.
+- Run `pytest`, `ruff check` and `ruff format` before pushing. CI runs all
+  three on Python 3.9, 3.11 and 3.13.
+
+## Reporting a bug
+
+Include the client version (`scriptit version`), your Python version, the
+command you ran, and what happened. If it involves a command that ran in your
+environment, `scriptit session current` tells you which session to look at in
+the app — that transcript is usually the fastest way to see what went wrong.
+
+Please don't paste credentials, tokens, or the contents of
+`~/.config/scriptit/credentials.json` into an issue.

scriptit_cli-0.2.2/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.