@agentorg/computer-sdk 0.0.38 → 0.0.40

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.
@@ -65,7 +65,7 @@ export interface paths {
65
65
  cookie?: never;
66
66
  };
67
67
  get?: never;
68
- /** Set a part's switch, which lasts across restarts. Turning it on, or on again, makes only the requests that show nothing, on the service's machine, macOS only: from macOS 26, Screen Recording's for an app hosting Cua Driver, while it is missing, which lists the app in its pane. Nothing that shows an alert or a window comes from the switch: Accessibility's alert, Cua Driver's own grant window and a browser's inspect page each come from ask with that need, on the person's click. Before macOS 26 Screen Recording's request is taken to draw an alert, so it waits for ask too; that is untested. Where a request it makes couldn't be started, it answers 409, saying why, and the switch stays on. */
68
+ /** Set a part's switch, which lasts across restarts. Turning it on asks for nothing: no request of macOS's, no alert and no window comes from the switch. What a part needs is asked for only by ask with that need, on the person's click: a screen grant's request, Cua Driver's own grant window, a browser's inspect page. */
69
69
  put: operations["setSetup"];
70
70
  post?: never;
71
71
  delete?: never;
@@ -85,7 +85,7 @@ export interface paths {
85
85
  };
86
86
  get?: never;
87
87
  put?: never;
88
- /** Ask the person, on the service's machine, macOS only, for one thing a part needs, for a button they press for it. screen-recording or accessibility, while it is missing: for a driver an app hosts, the app makes macOS's request each time, so that macOS asks again whenever it would, such as after a reset of the app's privacy entries. That grant's pane of System Settings opens as well, a second later, except at the first request the service has made, for that app's bundle identifier, of a grant whose request may draw an alert: accessibility, and screen-recording before macOS 26. macOS draws that alert until it has been answered, and the alert's own button opens the pane; after a reset, the alert and the pane both come. From macOS 26 Screen Recording's request draws nothing, so its pane opens each time. For Cua Driver's own app, while it is missing: its own grant, its app started first, which makes the system's requests in its own order, Accessibility first, in a window of its own. chrome or edge: that browser opens at its inspect page, where remote debugging is switched on. folders, for the files: each folder macOS protects that is here is read once, one after another, so that macOS asks for each in turn, now, and waits for the person's answer; their state is unknown until all are answered. With none named, it makes only what turning the part on makes. It answers once the steps have started, with each part then; what the person does next is read afresh later. A browser the service was given only the folder of, the person opens. Elsewhere it asks for nothing. */
88
+ /** Ask the person, on the service's machine, macOS only, for one thing a part needs, for a button they press for it. screen-recording or accessibility, while it is missing: for a driver an app hosts, the app makes macOS's request each time, so that macOS asks again whenever it would, such as after a reset of the app's privacy entries. That grant's pane of System Settings opens as well, a second later, except at the first request the service has made of that grant, for that app's bundle identifier: either grant's request may draw macOS's alert, which macOS draws until it has been answered, and whose own button opens the pane; after a reset, the alert and the pane both come. For Cua Driver's own app, while it is missing: its own grant, its app started first, which makes the system's requests in its own order, Accessibility first, in a window of its own. chrome or edge: that browser opens at its inspect page, where remote debugging is switched on. folders, for the files: each folder macOS protects that is here is read once, one after another, so that macOS asks for each in turn, now, and waits for the person's answer; their state is unknown until all are answered. With none named, it asks for nothing. It answers once the steps have started, with each part then; what the person does next is read afresh later. A browser the service was given only the folder of, the person opens. Elsewhere it asks for nothing. */
89
89
  post: operations["askSetup"];
90
90
  delete?: never;
91
91
  options?: never;
@@ -984,7 +984,7 @@ export interface operations {
984
984
  };
985
985
  };
986
986
  responses: {
987
- /** @description Set, and any request it makes started. */
987
+ /** @description Set. */
988
988
  200: {
989
989
  headers: {
990
990
  [name: string]: unknown;
@@ -994,15 +994,6 @@ export interface operations {
994
994
  };
995
995
  };
996
996
  401: components["responses"]["Unauthorized"];
997
- /** @description On, but a request it makes couldn't be started. */
998
- 409: {
999
- headers: {
1000
- [name: string]: unknown;
1001
- };
1002
- content: {
1003
- "application/json": components["schemas"]["Error"];
1004
- };
1005
- };
1006
997
  };
1007
998
  };
1008
999
  askSetup: {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agentorg/computer-sdk",
3
- "version": "0.0.38",
3
+ "version": "0.0.40",
4
4
  "description": "AgentComputer's TypeScript client: make, attach and use computers for agents",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {