gravity-cli 0.4.2__tar.gz → 0.4.3__tar.gz

gravity_cli-0.4.2/README.md → gravity_cli-0.4.3/PKG-INFO

@@ -1,3 +1,20 @@
+Metadata-Version: 2.5
+Name: gravity-cli
+Version: 0.4.3
+Summary: gravity cli — init, run, and push python agents to the Gravity marketplace
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.12
+Requires-Dist: gravity-schema==0.4.3
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: keyring>=25.0.0
+Requires-Dist: python-dotenv>=1.0.0
+Requires-Dist: rich>=13.9.0
+Requires-Dist: typer>=0.15.0
+Requires-Dist: uv>=0.8.0
+Description-Content-Type: text/markdown
+
 <h1 align="center">Gravity CLI</h1>
 
 <p align="center">
@@ -625,7 +642,7 @@ outputs:                          # extra formats the platform renders and deliv
 | `runtime.timeout_seconds` | no | `300` | 10 to 28800. |
 | `dependencies.lockfile` | no | `requirements.lock` | Compiled by `gravity validate`; ships with the agent. |
 | `inputs[]` | no | none | Up to 50. Each has `name` (a lowercase identifier, the key in `state["inputs"]`), `type`, `label`, and optionally `required`, `default`, `options`, `accept`. |
-| `inputs[].type` | **yes** | | `text`, `textarea`, `number`, `boolean`, `static-dropdown` (needs `options`), `email`, `url`, `date`, `secret` (an API key or password: masked, sealed with KMS, never shown back; no `default`) or `file` (no `default`; `accept` lists extensions such as `[pdf, csv]`). |
+| `inputs[].type` | **yes** | | `text`, `textarea`, `number`, `boolean`, `static-dropdown` (needs `options`), `email`, `url`, `date`, `secret` (an API key, password or other confidential value) or `file` (no `default`; `accept` lists extensions such as `[pdf, csv]`). |
 | `permissions.tools` | no | none | Up to 50 catalog names, such as `gmail.read`. Run `gravity tools` for the list. |
 | `permissions.models.tier` | no | `standard` | `standard` or `premium`. |
 | `approvals.required_for` | no | none | Tools that pause until a person approves. Each must also be declared under `permissions.tools` or a slot adapter. |
@@ -639,27 +656,6 @@ outputs:                          # extra formats the platform renders and deliv
 
 Unknown fields are rejected rather than ignored, so a typo is reported instead of silently dropped.
 
-### Secret inputs
-
-**API keys and passwords: use `type: secret`**, never `text`. The user types it into a masked box;
-the platform seals it with AWS KMS the moment it is submitted, keeps it out of every API response,
-log and stored checkpoint, and decrypts it only to hand it to your running agent as
-`state["inputs"]["<name>"]`, exactly like any other input. A secret input cannot have a `default`,
-holds at most 4096 bytes, and is meant for the user's own credential for a service your agent
-calls (their Supadata or Notion key), not for a key of yours: yours never goes in the agent or its
-manifest. Two rules for your code: don't put the key in `result` or `corpus` (they are shown
-to the user and stored in clear), and don't copy it into your own objects or logs: the platform
-can hide it in the state it checkpoints, not wherever your code sends it. When the user schedules
-the agent, they re-enter the key to change it; it is never shown back.
-
-```yaml
-inputs:
-  - name: supadata_api_key
-    type: secret
-    label: "Your Supadata API key"
-    required: true
-```
-
 ## An agent project
 
 ```
@@ -735,8 +731,8 @@ Real tools act on a connected account. Connect one with `gravity-gateway connect
 
 ## What's new
 
-- **0.4.2** Documents `type: secret` (below) and the `supadata.get_transcript` tool.
-- **0.4.1** `type: secret` inputs: API keys and passwords the user enters are sealed with AWS KMS on the platform, never shown back, and handed only to the running agent. New built-in tool `supadata.get_transcript` (`gravity tools supadata`).
+- **0.4.3** Documents the `secret` input type and the `supadata.get_transcript` tool.
+- **0.4.1** New input type `secret` for an API key, password or other confidential value. New built-in tool `supadata.get_transcript` (`gravity tools supadata`).
 
 ## Limitations
 

gravity_cli-0.4.2/PKG-INFO → gravity_cli-0.4.3/README.md

@@ -1,20 +1,3 @@
-Metadata-Version: 2.5
-Name: gravity-cli
-Version: 0.4.2
-Summary: gravity cli — init, run, and push python agents to the Gravity marketplace
-License-Expression: Apache-2.0
-License-File: LICENSE
-License-File: NOTICE
-Requires-Python: >=3.12
-Requires-Dist: gravity-schema==0.4.2
-Requires-Dist: httpx>=0.27.0
-Requires-Dist: keyring>=25.0.0
-Requires-Dist: python-dotenv>=1.0.0
-Requires-Dist: rich>=13.9.0
-Requires-Dist: typer>=0.15.0
-Requires-Dist: uv>=0.8.0
-Description-Content-Type: text/markdown
-
 <h1 align="center">Gravity CLI</h1>
 
 <p align="center">
@@ -642,7 +625,7 @@ outputs:                          # extra formats the platform renders and deliv
 | `runtime.timeout_seconds` | no | `300` | 10 to 28800. |
 | `dependencies.lockfile` | no | `requirements.lock` | Compiled by `gravity validate`; ships with the agent. |
 | `inputs[]` | no | none | Up to 50. Each has `name` (a lowercase identifier, the key in `state["inputs"]`), `type`, `label`, and optionally `required`, `default`, `options`, `accept`. |
-| `inputs[].type` | **yes** | | `text`, `textarea`, `number`, `boolean`, `static-dropdown` (needs `options`), `email`, `url`, `date`, `secret` (an API key or password: masked, sealed with KMS, never shown back; no `default`) or `file` (no `default`; `accept` lists extensions such as `[pdf, csv]`). |
+| `inputs[].type` | **yes** | | `text`, `textarea`, `number`, `boolean`, `static-dropdown` (needs `options`), `email`, `url`, `date`, `secret` (an API key, password or other confidential value) or `file` (no `default`; `accept` lists extensions such as `[pdf, csv]`). |
 | `permissions.tools` | no | none | Up to 50 catalog names, such as `gmail.read`. Run `gravity tools` for the list. |
 | `permissions.models.tier` | no | `standard` | `standard` or `premium`. |
 | `approvals.required_for` | no | none | Tools that pause until a person approves. Each must also be declared under `permissions.tools` or a slot adapter. |
@@ -656,27 +639,6 @@ outputs:                          # extra formats the platform renders and deliv
 
 Unknown fields are rejected rather than ignored, so a typo is reported instead of silently dropped.
 
-### Secret inputs
-
-**API keys and passwords: use `type: secret`**, never `text`. The user types it into a masked box;
-the platform seals it with AWS KMS the moment it is submitted, keeps it out of every API response,
-log and stored checkpoint, and decrypts it only to hand it to your running agent as
-`state["inputs"]["<name>"]`, exactly like any other input. A secret input cannot have a `default`,
-holds at most 4096 bytes, and is meant for the user's own credential for a service your agent
-calls (their Supadata or Notion key), not for a key of yours: yours never goes in the agent or its
-manifest. Two rules for your code: don't put the key in `result` or `corpus` (they are shown
-to the user and stored in clear), and don't copy it into your own objects or logs: the platform
-can hide it in the state it checkpoints, not wherever your code sends it. When the user schedules
-the agent, they re-enter the key to change it; it is never shown back.
-
-```yaml
-inputs:
-  - name: supadata_api_key
-    type: secret
-    label: "Your Supadata API key"
-    required: true
-```
-
 ## An agent project
 
 ```
@@ -752,8 +714,8 @@ Real tools act on a connected account. Connect one with `gravity-gateway connect
 
 ## What's new
 
-- **0.4.2** Documents `type: secret` (below) and the `supadata.get_transcript` tool.
-- **0.4.1** `type: secret` inputs: API keys and passwords the user enters are sealed with AWS KMS on the platform, never shown back, and handed only to the running agent. New built-in tool `supadata.get_transcript` (`gravity tools supadata`).
+- **0.4.3** Documents the `secret` input type and the `supadata.get_transcript` tool.
+- **0.4.1** New input type `secret` for an API key, password or other confidential value. New built-in tool `supadata.get_transcript` (`gravity tools supadata`).
 
 ## Limitations
 

{gravity_cli-0.4.2 → gravity_cli-0.4.3}/packages/gravity-schema/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "gravity-schema"
-version = "0.4.2"
+version = "0.4.3"
 description = "Gravity agent manifest contract — models, validation, and JSON Schema export"
 readme = "README.md"
 license = "Apache-2.0"

{gravity_cli-0.4.2 → gravity_cli-0.4.3}/pyproject.toml

@@ -1,13 +1,13 @@
 [project]
 name = "gravity-cli"
-version = "0.4.2"
+version = "0.4.3"
 description = "gravity cli — init, run, and push python agents to the Gravity marketplace"
 readme = "README.md"
 license = "Apache-2.0"
 license-files = ["LICENSE", "NOTICE"]
 requires-python = ">=3.12"
 dependencies = [
-    "gravity-schema==0.4.2",  # released in lockstep: always the same version as this package
+    "gravity-schema==0.4.3",  # released in lockstep: always the same version as this package
     "typer>=0.15.0",
     "httpx>=0.27.0",
     "rich>=13.9.0",

{gravity_cli-0.4.2 → gravity_cli-0.4.3}/src/gravity_cli/BUILDER_GUIDE.md

@@ -127,16 +127,8 @@ keeps the digest as a draft for the user to send. That's why the fallback in §3
 Other input fields you can use: `default:` (a value if the user leaves it blank; not for `file`),
 `options: [a, b]` (for `static-dropdown`), `accept: [pdf, csv]` (for `file`).
 
-**API keys and passwords: use `type: secret`**, never `text`. The user types it into a masked box;
-the platform seals it with AWS KMS the moment it is submitted, keeps it out of every API response,
-log and stored checkpoint, and decrypts it only to hand it to your running agent as
-`state["inputs"]["<name>"]`, exactly like any other input. A secret input cannot have a `default`,
-holds at most 4096 bytes, and is meant for the user's own credential for a service your agent
-calls (their Supadata or Notion key), not for a key of yours: yours never goes in the agent or its
-manifest. Two rules for your code: don't put the key in `result` or `corpus` (they are shown
-to the user and stored in clear), and don't copy it into your own objects or logs: the platform
-can hide it in the state it checkpoints, not wherever your code sends it. When the user schedules
-the agent, they re-enter the key to change it; it is never shown back.
+**API keys, passwords and other confidential values: use `type: secret`**, never `text`. A secret
+input cannot have a `default`.
 
 ### 3.2 `requirements.txt`
 

{gravity_cli-0.4.2 → gravity_cli-0.4.3}/uv.lock

@@ -164,7 +164,7 @@ wheels = [
 
 [[package]]
 name = "gravity-cli"
-version = "0.4.2"
+version = "0.4.3"
 source = { editable = "." }
 dependencies = [
     { name = "gravity-schema" },
@@ -201,7 +201,7 @@ dev = [
 
 [[package]]
 name = "gravity-schema"
-version = "0.4.2"
+version = "0.4.3"
 source = { editable = "packages/gravity-schema" }
 dependencies = [
     { name = "pydantic" },