opensandbox-cli 0.1.1__tar.gz → 1.1.1__tar.gz

{opensandbox_cli-0.1.1 → opensandbox_cli-1.1.1}/.gitignore

@@ -269,6 +269,19 @@ nbdist/
 generated/
 **/generated/**
 
+# Fast Sandbox FastPath gRPC stubs are committed intentionally (deterministic protoc
+# output; the server package needs them at install time, so they are checked
+# in rather than regenerated).
+!server/opensandbox_server/services/fast_sandbox/generated/
+!server/opensandbox_server/services/fast_sandbox/generated/**
+server/opensandbox_server/services/fast_sandbox/generated/__pycache__/
+
+# execd eBPF kernel BTF dumps (bpf2go build-time only, never committed —
+# see components/execd/pkg/ebpf/prog/audit.bpf.c; regenerate with:
+#   bpftool btf dump file /sys/kernel/btf/vmlinux format c > .../vmlinux.h)
+components/execd/pkg/ebpf/prog/vmlinux.h
+components/execd/pkg/ebpf/prog/vmlinux_*.h
+
 # gVisor runtime binaries (downloaded dynamically)
 kubernetes/test/kind/gvisor/runsc
 kubernetes/test/kind/gvisor/containerd-shim-runsc-v1
@@ -276,3 +289,8 @@ bin/
 obj/
 
 .qoder/
+/.vs
+
+# fast-sandbox pinned source checkout (materialized by
+# manifests/release/build-fast-sandbox.sh from manifests/third-party/fast-sandbox.commit)
+.fast-sandbox/

{opensandbox_cli-0.1.1 → opensandbox_cli-1.1.1}/PKG-INFO

@@ -1,11 +1,11 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: opensandbox-cli
-Version: 0.1.1
+Version: 1.1.1
 Summary: OpenSandbox CLI - Command-line interface for managing sandboxes
 Project-URL: Homepage, https://open-sandbox.ai
-Project-URL: Repository, https://github.com/alibaba/OpenSandbox
+Project-URL: Repository, https://github.com/opensandbox-group/OpenSandbox
 Project-URL: Documentation, https://open-sandbox.ai
-Project-URL: Issues, https://github.com/alibaba/OpenSandbox/issues
+Project-URL: Issues, https://github.com/opensandbox-group/OpenSandbox/issues
 Author-email: OpenSandbox Team <ninan.nn@alibaba-inc.com>
 License:                                  Apache License
                                    Version 2.0, January 2004
@@ -224,10 +224,11 @@ Classifier: Topic :: Software Development :: Libraries
 Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Requires-Dist: click<9.0,>=8.1.0
-Requires-Dist: opensandbox<0.2.0,>=0.1.9
+Requires-Dist: opensandbox<2.0.0,>=1.1.1
 Requires-Dist: pyyaml<7.0,>=6.0
 Requires-Dist: rich<14.0,>=13.0.0
 Requires-Dist: tomli>=2.0.0; python_version < '3.11'
+Requires-Dist: tomlkit<1.0,>=0.13.0
 Description-Content-Type: text/markdown
 
 # OpenSandbox CLI
@@ -235,9 +236,11 @@ Description-Content-Type: text/markdown
 `osb` is the command-line interface for OpenSandbox. It is built for the common day-to-day flows:
 
 - create and manage sandboxes
+- build golden-image templates and create sandboxes from templates or snapshots
 - run commands inside a sandbox
 - read and modify sandbox files
 - inspect runtime egress policy
+- manage sandbox-local Credential Vault state
 - collect low-level diagnostics
 - install OpenSandbox-specific skills for coding agents
 
@@ -282,6 +285,7 @@ opensandbox-server
 osb config init
 osb config set connection.domain localhost:8080
 osb config set connection.protocol http
+osb config set connection.api_key <your-api-key>
 osb config show -o json
 ```
 
@@ -379,6 +383,109 @@ osb sandbox create \
   --volumes-file volumes.json
 ```
 
+Create with Credential Vault proxy enabled:
+
+```bash
+osb sandbox create --image python:3.12 --network-policy-file network-policy.json --credential-proxy -o json
+```
+
+Create from a template (golden image):
+
+```bash
+osb sandbox create --template <template-id> --timeout 30m -o json
+```
+
+Template mode fixes the workload shape on the server: `--image`, `--env`,
+`--resource`, `--entrypoint`, `--volumes-file`, and `--credential-proxy` cannot
+be combined with `--template`. Only `--timeout` (required), `--metadata`,
+`--extension`, and `--network-policy-file` may accompany it. Only templates in
+the `Succeeded` phase can be used. See [Manage templates](#manage-templates).
+
+Create from a snapshot:
+
+```bash
+osb sandbox create --snapshot-id <snapshot-id> --timeout 30m -o json
+```
+
+`--image`, `--template`, and `--snapshot-id` are mutually exclusive.
+
+Create from a request file (`-f`, like `kubectl apply -f`):
+
+```bash
+osb sandbox create -f sandbox-request.json -o json
+```
+
+`sandbox-request.json` uses the public `CreateSandboxRequest` JSON format
+(camelCase keys):
+
+```json
+{
+  "image": "python:3.12",
+  "timeout": 1800,
+  "resourceLimits": { "cpu": "1", "memory": "2Gi" },
+  "entrypoint": ["python", "-m", "http.server"],
+  "networkPolicy": {
+    "defaultAction": "deny",
+    "egress": [{ "action": "allow", "target": "pypi.org" }]
+  }
+}
+```
+
+- Exactly one of `image` (string or `{ "uri": ..., "auth": { "username": ..., "password": ... } }`),
+  `templateId`, or `snapshotId` is required; `timeout` is integer seconds, or
+  `null` for manual cleanup.
+- Supported fields: `image`, `templateId`, `snapshotId`, `platform`, `timeout`,
+  `resourceLimits`, `resourceRequests`, `env`, `metadata`, `extensions`,
+  `entrypoint`, `networkPolicy`, `credentialProxy`, `secureAccess`, `volumes`,
+  `lifecycle`.
+- `-f` cannot be combined with request-building flags; `--skip-health-check`,
+  `--ready-timeout`, and `-o` still apply. In template mode the file may only
+  set `timeout`, `metadata`, `extensions`, and `networkPolicy` alongside
+  `templateId` (a finite `timeout` is required).
+
+### Manage templates
+
+Templates are golden-image builds; the build runs asynchronously, so poll
+`template get` until the status phase is `Succeeded`. Template management
+requires a Kubernetes-backed runtime.
+
+```bash
+osb template create --image python:3.12 --publish s3://bucket/publish -o json
+osb template get <template-id> -o json
+osb template list -o json
+osb template delete <template-id> -o json
+```
+
+`template create` also accepts `--resource cpu=1 memory=512Mi disk=2Gi`,
+`--entrypoint` (repeat per argv item), `--env KEY=VALUE`, `--metadata
+KEY=VALUE`, `--format native|overlaybd`, `--readiness-probe`, and
+`--warmup-seconds`. Or pass a request file in the public `CreateTemplateRequest`
+JSON format:
+
+```bash
+osb template create -f template-request.json -o json
+```
+
+```json
+{
+  "image": "python:3.12",
+  "publish": "s3://bucket/publish",
+  "resourceLimits": { "cpu": "1", "memory": "512Mi" },
+  "readiness": { "probe": "tcp://127.0.0.1:44772", "warmupSeconds": 60 }
+}
+```
+
+### Manage snapshots
+
+Snapshots capture a sandbox's state and can back new sandboxes.
+
+```bash
+osb snapshot create <sandbox-id> --name golden -o json
+osb snapshot get <snapshot-id> -o json
+osb snapshot list --sandbox-id <sandbox-id> -o json
+osb snapshot delete <snapshot-id> -o json
+```
+
 ### List and inspect sandboxes
 
 ```bash
@@ -390,6 +497,17 @@ osb sandbox metrics <sandbox-id>
 osb sandbox metrics <sandbox-id> --watch -o raw
 ```
 
+### Pause a sandbox
+
+Pause is asynchronous. `Pause request accepted` confirms that the server accepted
+the request, not that the sandbox has reached the `Paused` state. Poll the sandbox
+until the transition finishes:
+
+```bash
+osb sandbox pause <sandbox-id>
+osb sandbox get <sandbox-id> -o json
+```
+
 ### Expose a service
 
 ```bash
@@ -412,6 +530,21 @@ osb command status <sandbox-id> <execution-id> -o json
 osb command logs <sandbox-id> <execution-id> -o json
 ```
 
+Background start errors or a stream ending before startup confirmation make the
+CLI exit non-zero without success metadata. After a successful start, use
+`command status` and `command logs` to check the process's eventual result.
+
+By default the payload after `--` is joined into one shell command string, so
+pipelines, redirection, and `$VAR` expansion work as in a terminal. Add `--argv`
+to pass the arguments to the executable as a literal argv list (no shell) when
+values such as `$HOME`, quotes, embedded spaces, or empty strings must reach the
+process unchanged. `--argv` needs a sandbox image whose execd accepts argv
+requests:
+
+```bash
+osb command run <sandbox-id> -o raw --argv -- python3 -c "import sys; print(sys.argv[1:])" "a b" '$HOME' "x'y" ""
+```
+
 Persistent shell session:
 
 ```bash
@@ -433,6 +566,11 @@ osb file replace <sandbox-id> /workspace/app.py --old old --new new -o json
 osb file chmod <sandbox-id> /workspace/script.sh --mode 755 -o json
 ```
 
+Downloads replace regular files only on success; a failed or interrupted
+download preserves any existing regular file. Existing devices and named pipes
+receive data directly. Stdout aliases (such as `/dev/stdout`) stream only the file
+bytes, without a success message. See the [CLI guide](../docs/cli/index.md#work-with-files).
+
 ### Manage runtime egress policy
 
 Inspect current policy:
@@ -453,26 +591,46 @@ If you are debugging connectivity, verify behavior with an actual command:
 osb command run <sandbox-id> -o raw -- curl -I https://pypi.org
 ```
 
+### Manage Credential Vault
+
+Credential Vault operations call the sandbox egress sidecar through the Python SDK.
+Create the sandbox with `--credential-proxy` and an explicit network policy before
+writing vault state.
+
+```bash
+osb credential-vault create <sandbox-id> --file vault.yaml -o json
+osb credential-vault get <sandbox-id> -o json
+osb credential-vault patch <sandbox-id> --file mutation.yaml -o json
+osb credential-vault credential list <sandbox-id> -o json
+osb credential-vault binding list <sandbox-id> -o json
+osb credential-vault delete <sandbox-id> -o json
+```
+
+Use `--file -` to read a JSON/YAML payload from stdin. Do not pass plaintext
+credential values as command-line flags; keep them in the payload stream or file.
+
 ### Collect diagnostics
 
 Use the stable diagnostics commands for API-backed log and event descriptors.
 
 ```bash
-osb diagnostics events <sandbox-id> --scope lifecycle -o raw
 osb diagnostics events <sandbox-id> --scope runtime -o raw
+osb diagnostics events <sandbox-id> --scope all -o raw
 osb diagnostics logs <sandbox-id> --scope container -o raw
-osb diagnostics logs <sandbox-id> --scope lifecycle -o json
+osb diagnostics logs <sandbox-id> --scope all -o json
 osb diagnostics events <sandbox-id> --scope runtime -o json
 osb diagnostics logs <sandbox-id> --scope container -o yaml
 ```
 
-`--scope` is required for stable diagnostics. Common scopes are `lifecycle` and
-`container` for logs, and `lifecycle` and `runtime` for events. Raw output
-prints inline diagnostic text, or the content URL when diagnostics are
-delivered as a temporary URL. Structured CLI output follows the SDK/Python field
-style, for example `content_url`, `content_length`, and `expires_at`.
-Some server builds may return `DIAGNOSTICS_NOT_IMPLEMENTED` for scoped
-diagnostics until the stable backend implementation is enabled.
+`--scope` is required for stable diagnostics. The built-in server supports
+`container` and `all` for logs, and `runtime` and `all` for events. It returns
+`DIAGNOSTICS_SCOPE_UNSUPPORTED` for unavailable scopes, including lifecycle events.
+Best-effort scopes may include a `warnings` field when the backend can only
+provide a subset. Raw output prints inline
+diagnostic text, or the content URL when diagnostics are delivered as a
+temporary URL. Structured CLI output follows the SDK/Python field style, for
+example `content_url`, `content_length`, and `expires_at`. Older server builds
+may still return `DIAGNOSTICS_NOT_IMPLEMENTED` for scoped diagnostics.
 
 Legacy DevOps diagnostics remain experimental. Prefer `osb diagnostics logs/events`
 for stable API-backed log and event collection.
@@ -506,6 +664,8 @@ Not every command supports every format. Use `--help` on the specific command wh
 The main command groups are:
 
 - `osb sandbox`: lifecycle management
+- `osb template`: golden-image template builds
+- `osb snapshot`: snapshot management
 - `osb command`: command execution and persistent sessions
 - `osb file`: file and directory operations
 - `osb egress`: runtime egress policy
@@ -518,6 +678,8 @@ Explore them directly:
 
 ```bash
 osb sandbox --help
+osb template --help
+osb snapshot --help
 osb command --help
 osb file --help
 osb skills --help

{opensandbox_cli-0.1.1 → opensandbox_cli-1.1.1}/README.md

@@ -3,9 +3,11 @@
 `osb` is the command-line interface for OpenSandbox. It is built for the common day-to-day flows:
 
 - create and manage sandboxes
+- build golden-image templates and create sandboxes from templates or snapshots
 - run commands inside a sandbox
 - read and modify sandbox files
 - inspect runtime egress policy
+- manage sandbox-local Credential Vault state
 - collect low-level diagnostics
 - install OpenSandbox-specific skills for coding agents
 
@@ -50,6 +52,7 @@ opensandbox-server
 osb config init
 osb config set connection.domain localhost:8080
 osb config set connection.protocol http
+osb config set connection.api_key <your-api-key>
 osb config show -o json
 ```
 
@@ -147,6 +150,109 @@ osb sandbox create \
   --volumes-file volumes.json
 ```
 
+Create with Credential Vault proxy enabled:
+
+```bash
+osb sandbox create --image python:3.12 --network-policy-file network-policy.json --credential-proxy -o json
+```
+
+Create from a template (golden image):
+
+```bash
+osb sandbox create --template <template-id> --timeout 30m -o json
+```
+
+Template mode fixes the workload shape on the server: `--image`, `--env`,
+`--resource`, `--entrypoint`, `--volumes-file`, and `--credential-proxy` cannot
+be combined with `--template`. Only `--timeout` (required), `--metadata`,
+`--extension`, and `--network-policy-file` may accompany it. Only templates in
+the `Succeeded` phase can be used. See [Manage templates](#manage-templates).
+
+Create from a snapshot:
+
+```bash
+osb sandbox create --snapshot-id <snapshot-id> --timeout 30m -o json
+```
+
+`--image`, `--template`, and `--snapshot-id` are mutually exclusive.
+
+Create from a request file (`-f`, like `kubectl apply -f`):
+
+```bash
+osb sandbox create -f sandbox-request.json -o json
+```
+
+`sandbox-request.json` uses the public `CreateSandboxRequest` JSON format
+(camelCase keys):
+
+```json
+{
+  "image": "python:3.12",
+  "timeout": 1800,
+  "resourceLimits": { "cpu": "1", "memory": "2Gi" },
+  "entrypoint": ["python", "-m", "http.server"],
+  "networkPolicy": {
+    "defaultAction": "deny",
+    "egress": [{ "action": "allow", "target": "pypi.org" }]
+  }
+}
+```
+
+- Exactly one of `image` (string or `{ "uri": ..., "auth": { "username": ..., "password": ... } }`),
+  `templateId`, or `snapshotId` is required; `timeout` is integer seconds, or
+  `null` for manual cleanup.
+- Supported fields: `image`, `templateId`, `snapshotId`, `platform`, `timeout`,
+  `resourceLimits`, `resourceRequests`, `env`, `metadata`, `extensions`,
+  `entrypoint`, `networkPolicy`, `credentialProxy`, `secureAccess`, `volumes`,
+  `lifecycle`.
+- `-f` cannot be combined with request-building flags; `--skip-health-check`,
+  `--ready-timeout`, and `-o` still apply. In template mode the file may only
+  set `timeout`, `metadata`, `extensions`, and `networkPolicy` alongside
+  `templateId` (a finite `timeout` is required).
+
+### Manage templates
+
+Templates are golden-image builds; the build runs asynchronously, so poll
+`template get` until the status phase is `Succeeded`. Template management
+requires a Kubernetes-backed runtime.
+
+```bash
+osb template create --image python:3.12 --publish s3://bucket/publish -o json
+osb template get <template-id> -o json
+osb template list -o json
+osb template delete <template-id> -o json
+```
+
+`template create` also accepts `--resource cpu=1 memory=512Mi disk=2Gi`,
+`--entrypoint` (repeat per argv item), `--env KEY=VALUE`, `--metadata
+KEY=VALUE`, `--format native|overlaybd`, `--readiness-probe`, and
+`--warmup-seconds`. Or pass a request file in the public `CreateTemplateRequest`
+JSON format:
+
+```bash
+osb template create -f template-request.json -o json
+```
+
+```json
+{
+  "image": "python:3.12",
+  "publish": "s3://bucket/publish",
+  "resourceLimits": { "cpu": "1", "memory": "512Mi" },
+  "readiness": { "probe": "tcp://127.0.0.1:44772", "warmupSeconds": 60 }
+}
+```
+
+### Manage snapshots
+
+Snapshots capture a sandbox's state and can back new sandboxes.
+
+```bash
+osb snapshot create <sandbox-id> --name golden -o json
+osb snapshot get <snapshot-id> -o json
+osb snapshot list --sandbox-id <sandbox-id> -o json
+osb snapshot delete <snapshot-id> -o json
+```
+
 ### List and inspect sandboxes
 
 ```bash
@@ -158,6 +264,17 @@ osb sandbox metrics <sandbox-id>
 osb sandbox metrics <sandbox-id> --watch -o raw
 ```
 
+### Pause a sandbox
+
+Pause is asynchronous. `Pause request accepted` confirms that the server accepted
+the request, not that the sandbox has reached the `Paused` state. Poll the sandbox
+until the transition finishes:
+
+```bash
+osb sandbox pause <sandbox-id>
+osb sandbox get <sandbox-id> -o json
+```
+
 ### Expose a service
 
 ```bash
@@ -180,6 +297,21 @@ osb command status <sandbox-id> <execution-id> -o json
 osb command logs <sandbox-id> <execution-id> -o json
 ```
 
+Background start errors or a stream ending before startup confirmation make the
+CLI exit non-zero without success metadata. After a successful start, use
+`command status` and `command logs` to check the process's eventual result.
+
+By default the payload after `--` is joined into one shell command string, so
+pipelines, redirection, and `$VAR` expansion work as in a terminal. Add `--argv`
+to pass the arguments to the executable as a literal argv list (no shell) when
+values such as `$HOME`, quotes, embedded spaces, or empty strings must reach the
+process unchanged. `--argv` needs a sandbox image whose execd accepts argv
+requests:
+
+```bash
+osb command run <sandbox-id> -o raw --argv -- python3 -c "import sys; print(sys.argv[1:])" "a b" '$HOME' "x'y" ""
+```
+
 Persistent shell session:
 
 ```bash
@@ -201,6 +333,11 @@ osb file replace <sandbox-id> /workspace/app.py --old old --new new -o json
 osb file chmod <sandbox-id> /workspace/script.sh --mode 755 -o json
 ```
 
+Downloads replace regular files only on success; a failed or interrupted
+download preserves any existing regular file. Existing devices and named pipes
+receive data directly. Stdout aliases (such as `/dev/stdout`) stream only the file
+bytes, without a success message. See the [CLI guide](../docs/cli/index.md#work-with-files).
+
 ### Manage runtime egress policy
 
 Inspect current policy:
@@ -221,26 +358,46 @@ If you are debugging connectivity, verify behavior with an actual command:
 osb command run <sandbox-id> -o raw -- curl -I https://pypi.org
 ```
 
+### Manage Credential Vault
+
+Credential Vault operations call the sandbox egress sidecar through the Python SDK.
+Create the sandbox with `--credential-proxy` and an explicit network policy before
+writing vault state.
+
+```bash
+osb credential-vault create <sandbox-id> --file vault.yaml -o json
+osb credential-vault get <sandbox-id> -o json
+osb credential-vault patch <sandbox-id> --file mutation.yaml -o json
+osb credential-vault credential list <sandbox-id> -o json
+osb credential-vault binding list <sandbox-id> -o json
+osb credential-vault delete <sandbox-id> -o json
+```
+
+Use `--file -` to read a JSON/YAML payload from stdin. Do not pass plaintext
+credential values as command-line flags; keep them in the payload stream or file.
+
 ### Collect diagnostics
 
 Use the stable diagnostics commands for API-backed log and event descriptors.
 
 ```bash
-osb diagnostics events <sandbox-id> --scope lifecycle -o raw
 osb diagnostics events <sandbox-id> --scope runtime -o raw
+osb diagnostics events <sandbox-id> --scope all -o raw
 osb diagnostics logs <sandbox-id> --scope container -o raw
-osb diagnostics logs <sandbox-id> --scope lifecycle -o json
+osb diagnostics logs <sandbox-id> --scope all -o json
 osb diagnostics events <sandbox-id> --scope runtime -o json
 osb diagnostics logs <sandbox-id> --scope container -o yaml
 ```
 
-`--scope` is required for stable diagnostics. Common scopes are `lifecycle` and
-`container` for logs, and `lifecycle` and `runtime` for events. Raw output
-prints inline diagnostic text, or the content URL when diagnostics are
-delivered as a temporary URL. Structured CLI output follows the SDK/Python field
-style, for example `content_url`, `content_length`, and `expires_at`.
-Some server builds may return `DIAGNOSTICS_NOT_IMPLEMENTED` for scoped
-diagnostics until the stable backend implementation is enabled.
+`--scope` is required for stable diagnostics. The built-in server supports
+`container` and `all` for logs, and `runtime` and `all` for events. It returns
+`DIAGNOSTICS_SCOPE_UNSUPPORTED` for unavailable scopes, including lifecycle events.
+Best-effort scopes may include a `warnings` field when the backend can only
+provide a subset. Raw output prints inline
+diagnostic text, or the content URL when diagnostics are delivered as a
+temporary URL. Structured CLI output follows the SDK/Python field style, for
+example `content_url`, `content_length`, and `expires_at`. Older server builds
+may still return `DIAGNOSTICS_NOT_IMPLEMENTED` for scoped diagnostics.
 
 Legacy DevOps diagnostics remain experimental. Prefer `osb diagnostics logs/events`
 for stable API-backed log and event collection.
@@ -274,6 +431,8 @@ Not every command supports every format. Use `--help` on the specific command wh
 The main command groups are:
 
 - `osb sandbox`: lifecycle management
+- `osb template`: golden-image template builds
+- `osb snapshot`: snapshot management
 - `osb command`: command execution and persistent sessions
 - `osb file`: file and directory operations
 - `osb egress`: runtime egress policy
@@ -286,6 +445,8 @@ Explore them directly:
 
 ```bash
 osb sandbox --help
+osb template --help
+osb snapshot --help
 osb command --help
 osb file --help
 osb skills --help

{opensandbox_cli-0.1.1 → opensandbox_cli-1.1.1}/pyproject.toml

@@ -1,4 +1,4 @@
-# Copyright 2026 Alibaba Group Holding Ltd.
+# Copyright 2026 The OpenSandbox Authors.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -42,18 +42,21 @@ classifiers = [
     "Typing :: Typed",
 ]
 dependencies = [
-    "opensandbox>=0.1.9,<0.2.0",
+    # `command run --argv` passes a list to commands.run; the SDK accepts a
+    # list there from 0.1.17. Release the CLI only after that SDK is published.
+    "opensandbox>=1.1.1,<2.0.0",
     "click>=8.1.0,<9.0",
     "rich>=13.0.0,<14.0",
     "pyyaml>=6.0,<7.0",
+    "tomlkit>=0.13.0,<1.0",
     "tomli>=2.0.0; python_version < '3.11'",
 ]
 
 [project.urls]
 Homepage = "https://open-sandbox.ai"
-Repository = "https://github.com/alibaba/OpenSandbox"
+Repository = "https://github.com/opensandbox-group/OpenSandbox"
 Documentation = "https://open-sandbox.ai"
-Issues = "https://github.com/alibaba/OpenSandbox/issues"
+Issues = "https://github.com/opensandbox-group/OpenSandbox/issues"
 
 [project.scripts]
 opensandbox = "opensandbox_cli.main:cli"
@@ -64,8 +67,8 @@ source = "vcs"
 
 [tool.hatch.version.raw-options]
 root = ".."
-tag_regex = "^cli/v(?P<version>\\d+\\.\\d+\\.\\d+(?:[\\.\\w\\+\\-]*)?)$"
-git_describe_command = 'git describe --dirty --tags --long --match "cli/v*"'
+tag_regex = "^release-(?P<version>\\d+\\.\\d+\\.\\d+(?:[\\.\\w\\+\\-]*)?)$"
+git_describe_command = 'git describe --dirty --tags --long --match "release-*"'
 fallback_version = "0.1.1"
 
 [tool.hatch.build]

{opensandbox_cli-0.1.1 → opensandbox_cli-1.1.1}/src/opensandbox_cli/__init__.py

@@ -1,4 +1,4 @@
-# Copyright 2026 Alibaba Group Holding Ltd.
+# Copyright 2026 The OpenSandbox Authors.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.

{opensandbox_cli-0.1.1 → opensandbox_cli-1.1.1}/src/opensandbox_cli/__main__.py

@@ -1,4 +1,4 @@
-# Copyright 2026 Alibaba Group Holding Ltd.
+# Copyright 2026 The OpenSandbox Authors.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.

{opensandbox_cli-0.1.1 → opensandbox_cli-1.1.1}/src/opensandbox_cli/client.py

@@ -1,4 +1,4 @@
-# Copyright 2026 Alibaba Group Holding Ltd.
+# Copyright 2026 The OpenSandbox Authors.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -90,15 +90,10 @@ class ClientContext:
             self._manager = SandboxManagerSync.create(self.connection_config)
         return self._manager
 
-    def resolve_sandbox_id(self, sandbox_id: str) -> str:
-        """Return the sandbox ID exactly as provided by the user."""
-        return sandbox_id
-
     def connect_sandbox(
         self, sandbox_id: str, *, skip_health_check: bool = True
     ) -> SandboxSync:
         """Connect to an existing sandbox by ID."""
-        sandbox_id = self.resolve_sandbox_id(sandbox_id)
         return SandboxSync.connect(
             sandbox_id,
             connection_config=self.connection_config,

{opensandbox_cli-0.1.1 → opensandbox_cli-1.1.1}/src/opensandbox_cli/commands/__init__.py

@@ -1,4 +1,4 @@
-# Copyright 2026 Alibaba Group Holding Ltd.
+# Copyright 2026 The OpenSandbox Authors.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.