@reminix/cli 0.0.0-stage → 1.0.0-rc.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md ADDED
@@ -0,0 +1,265 @@
1
+ # Changelog
2
+
3
+ What changed in the Reminix CLI (`@reminix/cli`). Generated from the source on each release; newest first.
4
+
5
+ ## 1.0.0-rc.10 (2026-11-12)
6
+
7
+ ### Added
8
+
9
+ - Members and pending invitations now carry `seat`: the seat type a person
10
+ holds or will hold (`GET /v1/workspace/members`,
11
+ `GET /v1/workspace/invitations`). It is null for a guest, or where the
12
+ product has no seat types.
13
+
14
+ ### Changed
15
+
16
+ - An approval request for a run now has a plain `summary`, such as "Run
17
+ refund-customer (version 2) in production", without the run's inputs.
18
+ The inputs are in the request's `input` (`GET /v1/approvals/{id}`). Its
19
+ `reason` is empty, because Reminix writes none of its own for a run;
20
+ the `summary` says what will happen.
21
+ - In Reminix a `seat` is `"publishers"` or `"runners"`. An invitation can
22
+ choose either.
23
+
24
+ Only publishers create scripts, upload versions and publish them. A
25
+ runner gets `403 forbidden` for those, and so does anyone uploading a
26
+ version of a script they can't publish.
27
+
28
+ `GET /v1/workspace/usage` no longer has the `authors` count. Seats
29
+ replace it.
30
+
31
+ A workspace keeps up to 1 GB of files on Free, 10 GB on Pro and 100 GB
32
+ on Business. An upload past that gets `402 plan_limit_reached`.
33
+
34
+ ## 1.0.0-rc.9 (2026-11-07)
35
+
36
+ ### Added
37
+
38
+ - Lists can start from a date. `GET /v1/workspace/audit-events` and
39
+ `GET /v1/workspace/webhook-endpoints/{endpointId}/deliveries` take
40
+ `before`, an ISO time, and return the items older than it, newest first.
41
+
42
+ Audit events take two filters. `action` keeps one kind of event.
43
+ `actor` keeps what one person, key or token did: pass `user:` and an
44
+ item's `actor.id`, or `credential:` and its `credential.id`. Each audit
45
+ event now carries those ids.
46
+
47
+ Webhook deliveries take `status`: `pending`, `delivered` or `failed`.
48
+ - Listing runs takes `status`, which keeps only runs in one state, such as
49
+ `failed`. Listing runs and listing files both take `before`, which starts
50
+ the list from a moment instead of from now. For example,
51
+ `before=2026-11-01T00:00:00Z` lists what came before November.
52
+
53
+ ### Changed
54
+
55
+ - The usage count `authors` is now described as "People who published or
56
+ uploaded this month". Its id and numbers haven't changed.
57
+ - Listing files filters by file name with `name`, which replaces `q`. Every
58
+ filter is now named after the field it narrows.
59
+
60
+ ## 1.0.0-rc.8 (2026-11-07)
61
+
62
+ ### Added
63
+
64
+ - `reminix files download <file-id> --json` prints the file's details and
65
+ where it was saved, like every other command's `--json`.
66
+ - A `run.cancelled` webhook event, sent when a run is cancelled: by
67
+ someone (`runs.cancel`), or because its approval was denied, expired or
68
+ couldn't start. Its `data` is the same as `run.failed`'s, with `error`
69
+ saying why. Triggers can start a script on it.
70
+ - Each plan now limits how many runs a workspace has going at once: 1 on
71
+ Free, 5 on Pro and 15 on Business, short and long runs together. Of
72
+ those, at most 2 can be long runs on Pro and 5 on Business. Starting
73
+ one more answers `429 rate_limited` with a `Retry-After` header (a few
74
+ seconds for a short run, 30 for a long one) instead of running; the
75
+ SDKs and the CLI wait and try again on their own.
76
+ - You can now change a webhook endpoint's URL, description or event types
77
+ without deleting it: `client.workspace.webhookEndpoints.update()`
78
+ (`PATCH /v1/workspace/webhook-endpoints/{endpointId}`). The endpoint
79
+ keeps its signing secret, so your verification code keeps working.
80
+
81
+ ### Changed
82
+
83
+ - An AI agent connected through the MCP server can no longer change who
84
+ may run a script or which of its runs need approval:
85
+ `PATCH /v1/scripts/{slug}` (`scripts.update`) answers `403 forbidden`
86
+ when an agent's token sends `access`, `teamIds` or `approvalPolicy`.
87
+ People's own tokens and API keys change them as before. And with
88
+ `approvalPolicy: "always"`, an agent's run now always waits for
89
+ approval, even when an owner or admin connected the agent.
90
+ - An approval request (`POST /v1/workspace/approval-requests`) now runs in
91
+ the environment it was filed in once a person approves it, such as live
92
+ when you asked from live. Before, it ran in the default environment
93
+ unless its input named one. Requests filed before this change still
94
+ run in the default.
95
+ - The descriptions of every method and command are rewritten to be easier
96
+ to read: one rule per sentence, with nothing about how calls behave
97
+ changed. They now also say that only workspace owners can manage webhook
98
+ endpoints with a personal access token.
99
+ Every response in the API reference now comes with an example of what
100
+ it returns.
101
+ - Error messages and CLI output read as whole sentences: what went wrong,
102
+ then what to do. For example, an unknown environment now says
103
+ `Unknown environment "staging". This product's environments are test, live.`
104
+ Error codes are unchanged, so code that checks `error.code` keeps
105
+ working. Code that matches the exact text of a message may need
106
+ updating.
107
+ - One name per idea, across the API, the SDKs, the CLI and MCP (breaking,
108
+ before 1.0):
109
+
110
+ - Upload a version is `scriptVersions.upload` (`script_versions.upload`
111
+ in Python), and takes `source` (was `archive`), `install` (was
112
+ `build`), `timeoutSeconds` (was `timeout`) and `envVars` (was `env`).
113
+ A version answers with `version` (was `number`), `install`,
114
+ `installLog`, `buildBytes`, `buildSha256`, `envVars` and `via` (was
115
+ `createdVia`); version paths are `/versions/{version}`.
116
+ - Test-run a version is `scriptVersions.testRun` (`test_run`).
117
+ - A run has `via` (was `interface`; an agent's runs are `agent`, was
118
+ `mcp`) and `startedBy: { userId, name, credential: { type, name } }`.
119
+ Its log is `runs.log` at `GET /v1/runs/{runId}/log` (was `runs.logs`,
120
+ `/logs`). The 202 schema is `RunAwaitingApproval` (was `HeldRun`).
121
+ - A file has `origin` (`input` or `saved`, was `direction` `in`/`out`),
122
+ `input` (was `field`) and `mediaType` (was `type`); list files with
123
+ `?origin=`. `files.upload` and `files.download` (at
124
+ `GET /v1/files/{fileId}/download`) replace `files.create` and
125
+ `files.content`. The SDKs' `FileUpload` takes `mediaType`
126
+ (`media_type` in Python). A script saves files to `/saved`
127
+ (`$REMINIX_SAVED`, was `/outputs`), and reads its inputs file at
128
+ `$REMINIX_INPUTS_FILE` (was `$REMINIX_INPUTS`).
129
+ - Secrets: `allowEnvVar` (was `allowEnv`; the CLI's `--allow-env-var`),
130
+ a secret use's `format` (was `value`), and `secretValues.delete`
131
+ (`reminix secret-values delete`, was `secrets.unset`).
132
+ - Triggers have `lastRunAt` (was `lastFiredAt`); a script's
133
+ `usedBy.startsScripts` was `followedBy`; an environment's `usedBy` was
134
+ `usage`. The event `run.succeeded` was `run.completed`. Script ids
135
+ start `scr_`.
136
+ - The CLI: `reminix upload [dir...]` uploads a draft (`publish --draft`
137
+ is gone), and `--dry-run` replaces `--plan`.
138
+ - Path parameters such as `endpointId` and `deliveryId` now come with a
139
+ description ("The endpoint's ID.") in the SDKs' type hints, the
140
+ command line's help and the API reference.
141
+ - `login` and `logout` now point to **Account → Personal access tokens**,
142
+ the page's new name in the app (it was "API tokens").
143
+ - The API reference's "Too many requests" answer now gives the limit: 100
144
+ requests a minute for each credential, whether an API key, a personal
145
+ access token or an agent's sign-in. Wait the number of seconds in the
146
+ `Retry-After` header before trying again.
147
+ - Method and command descriptions are clearer, and say who can call each
148
+ one. A workspace API key's access to updating, archiving, restoring and
149
+ test-running scripts is now stated. The CLI's `reminix publish`,
150
+ `reminix upload` and `reminix run` shortcuts describe themselves the
151
+ same way as the full commands.
152
+ - Error messages are easier to read. Each one states the problem in one
153
+ sentence, then what to do in the next:
154
+
155
+ ```text
156
+ SHOP_KEY has no value in staging. Add it in Settings → Scripts.
157
+ ```
158
+
159
+ If your code matches the text of an error, match its `code` instead.
160
+ The codes haven't changed.
161
+ - Environments and secrets now live under **Settings → Scripts** in the
162
+ app. A run error that sends you to the app to fix a secret or an
163
+ environment now names that tab.
164
+ - A run's `output`, `error` and log (`GET /v1/runs/{id}`,
165
+ `GET /v1/runs/{id}/log`) never show a secret value the run had access
166
+ to: printed as it is, or base64- or URL-encoded, it reads `[secret]`.
167
+ - API keys and webhooks now live together under **Settings → Developers**
168
+ in the app, and the descriptions of the API key and webhook endpoint
169
+ operations point there.
170
+ - `POST /v1/scripts/{slug}/runs` no longer fails a run because no machine
171
+ was free at once: the run waits up to 2 minutes for one, and its
172
+ `timeoutSeconds` counts from when its code starts. A short run still
173
+ answers `200` when it ends within 60 seconds; one still going then
174
+ answers `202` with status `running`, like a long run, and you follow it
175
+ with `GET /v1/runs/{id}`.
176
+ - `GET /v1/workspace/usage` returns its list as `counts` instead of `meters`.
177
+ Update anything that reads `meters` from `client.workspace.usage.get()`, the
178
+ Python client or the CLI's output.
179
+
180
+ ### Fixed
181
+
182
+ - `files.upload` refuses a file over the plan's size with `402
183
+ plan_limit_reached`, naming the plan's limit, on every plan. On Pro and
184
+ Business a file just over 100 MB used to get a generic `413` instead.
185
+ - Clearer, corrected descriptions for Reminix's operations in the API
186
+ reference, the SDKs' type hints, the command line's help and the MCP
187
+ tools:
188
+
189
+ - `runs.create` (and `scriptVersions.testRun`) documents its 429: 100
190
+ requests a minute per key or token, or the plan's runs at once all
191
+ going. Its 402 now also names used-up long-run minutes and a file
192
+ input larger than the plan takes, and its 400 an archived script. A
193
+ run takes at most its version's `timeoutSeconds`, not always 30.
194
+ - `runs.cancel` says a cancelled run sends a `run.cancelled` event, and
195
+ that a workspace API key may cancel too.
196
+ - `files.upload` documents its 413: uploads over 1,000 MB are refused.
197
+ An upload can be given to one run.
198
+ - `files.get`: an upload not yet used is also readable by owners,
199
+ admins and workspace API keys.
200
+ - `scripts.update`: its 402 is about every-run approval (Business), and
201
+ it changes tags too. `scriptSettings.update`: its 402 is about
202
+ second-person publishing (Business).
203
+ - `schedules.update` and `triggers.update`: `enabled` no longer claims a
204
+ default; leaving it out keeps it as it is.
205
+ - Name rules are given where they are checked: a script's `slug`, its
206
+ tags, an environment's `name`, a secret's `name`, and a secret's
207
+ `value` (at most 16,384 bytes).
208
+ - A run that waited for approval now reports when it actually started:
209
+ its `startedAt` (`GET /v1/runs/{id}`, and a run wherever the SDKs and
210
+ the CLI show one) is when it was approved, not when it was requested, and a cancelled long run's
211
+ `durationMs` counts only the time it ran, never the wait.
212
+
213
+ ## 1.0.0-rc.7 (2026-10-19)
214
+
215
+ ### Changed
216
+
217
+ - - `reminix run` waits through a person's approval, as the SDKs' `run`
218
+ does: it prints where to approve the run, then follows it to the end.
219
+ `--no-wait` answers at once instead.
220
+ - A cancelled run says why, in every client: "Run run_… was cancelled:
221
+ The approval was denied" (the run's `error`). The CLI no longer prints
222
+ "failed: null".
223
+ - Files are uploaded without a guessed type; the API takes it from the
224
+ file's name, the same way for every client. `reminix run --file` no
225
+ longer reads the script first: one file is sent as one id, and the API
226
+ takes it for an input that is a list of files.
227
+ - Publishing is one call. `scriptVersions.create` (Upload a version)
228
+ takes `create`, `name`, `description` and `publish`: it can make a new
229
+ script, rename one, and publish the upload, answering with an
230
+ `approval` link when a person must approve. Without `readme`, the
231
+ folder's `README.md` is used. `reminix publish` uses it, so a name or
232
+ description changed in `reminix.json` now reaches the script.
233
+ - `reminix init` works out the command the same way `publish` does, so
234
+ the two agree on every folder (an entry like `main.py` beside other
235
+ scripts, `pyproject.toml`, `package.json`).
236
+
237
+ ## 1.0.0-rc.6 (2026-10-19)
238
+
239
+ ### Fixed
240
+
241
+ - `login` in the browser no longer shows Safari's "This is a non-secure
242
+ form" warning after **Allow**. The page now hands the new token back to
243
+ the waiting CLI encrypted to a key only that CLI holds, by a redirect
244
+ instead of a form. A CLI from before this change is asked to update.
245
+ - `reminix run <slug> --number <n>` test-runs version n (a draft).
246
+ `--version <n>` printed the CLI's own version instead of running, so it
247
+ is gone. A run whose output is text prints it as it is, without quotes.
248
+
249
+ ## 1.0.0-rc.5 (2026-10-16)
250
+
251
+ No user-facing changes.
252
+
253
+ ## 1.0.0-rc.4 (2026-10-16)
254
+
255
+ ### Added
256
+
257
+ - Each release comes with a `CHANGELOG.md` listing what changed, newest first.
258
+
259
+ ### Changed
260
+
261
+ - The package page (README, on GitHub, npm and PyPI) shows what the product does with a first real example, and links the guide, the API reference, the changelog and support.
262
+
263
+ ## 1.0.0-rc.3 (2026-10-16)
264
+
265
+ No user-facing changes.
package/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
package/NOTICE ADDED
@@ -0,0 +1,2 @@
1
+ Reminix CLI
2
+ Copyright 2026 Omsome L.L.C-FZ
package/README.md CHANGED
@@ -1,3 +1,65 @@
1
- # Temporary Holding Version
1
+ # @reminix/cli
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ The Reminix CLI turns a script in a folder into a Reminix script, publishes it for your team and runs it, from a terminal, CI or another script.
4
+
5
+ Reminix turns your scripts into internal tools. Upload a Python, shell or Node script, and Reminix runs it from a form, the API, the CLI or your AI agents, on a schedule or from a webhook. Keys stay out of the code, and every run is on record.
6
+
7
+ ## Install
8
+
9
+ ```bash
10
+ npm install -g @reminix/cli
11
+ ```
12
+
13
+ Or run it without installing: `npx @reminix/cli --help`.
14
+
15
+ ## Sign in
16
+
17
+ ```bash
18
+ reminix login
19
+ ```
20
+
21
+ Your browser opens: sign in, choose the workspaces the CLI may use, and
22
+ click **Allow**. On a server or in CI, set `REMINIX_TOKEN` to a personal
23
+ access token instead.
24
+
25
+ ## Publish a script and run it
26
+
27
+ In the script's folder, here `monthly-report`, publish it for your
28
+ team. Reminix works out how it runs from the folder. Each `{name}` in
29
+ the command becomes an input, optional inside `[ … ]`:
30
+
31
+ ```bash
32
+ reminix publish --command "python report.py [--month {month}]"
33
+ ```
34
+
35
+ Then anyone on the team can run it from the app's form, through the
36
+ API, as an agent tool, or here:
37
+
38
+ ```bash
39
+ reminix run monthly-report --input '{"month":"2026-09"}' --out ./reports
40
+ ```
41
+
42
+ ## Everything else
43
+
44
+ Every API operation is a command: `reminix --help` lists them, and any
45
+ command takes `--json` for the API's exact answer, for scripts and
46
+ agents.
47
+
48
+ ## Links
49
+
50
+ - [Website](https://reminix.com)
51
+ - [CLI guide](https://reminix.com/docs/cli/)
52
+ - [API reference](https://reminix.com/docs/reference/)
53
+ - [Changelog](https://github.com/reminixhq/reminix-cli/blob/main/CHANGELOG.md)
54
+ - [Discord](https://reminix.com/discord)
55
+ - [Report a security issue](https://reminix.com/security/)
56
+
57
+ ## Contributing
58
+
59
+ This repository is generated from Reminix's source on each
60
+ release, so pull requests are ported there and credited (see
61
+ [CONTRIBUTING.md](https://github.com/reminixhq/reminix-cli/blob/main/CONTRIBUTING.md)).
62
+
63
+ ## License
64
+
65
+ Licensed under the Apache License 2.0.