@ora-ai/cli 0.7.3 → 0.7.4

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.
Files changed (2) hide show
  1. package/README.md +6 -2
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -96,8 +96,12 @@ whose CLI isn't currently connected answers 502 `TUNNEL_NOT_CONNECTED`.
96
96
  - **Journey**: create the tunnel `--access public`, then use the hostname as
97
97
  the journey's `targetDomain` — e.g. `924649e0-….t.agentfront.sh`. The
98
98
  agent browses it like any site.
99
- - **Scan**: `{ "url": "tunnel://<tunnelId>/", "url_kind": "tunnel" }` — works
100
- for any access mode, including `private`.
99
+ - **Audit** (the agent-readiness audit at ora.ai): create the tunnel
100
+ `--access public` and let `ax` run it end to end —
101
+ `ax audit localhost:<port> --tunnel-cmd 'ora tunnel <port> --access public'`
102
+ (npm `ax`; `ax audit localhost:<port> --tunnel ora` does the same with just
103
+ `ORA_API_KEY`). `tunnel://<id>/` targets are for ora's in-cluster scanners
104
+ only, not a public API.
101
105
 
102
106
  ### Manage tunnels
103
107
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ora-ai/cli",
3
- "version": "0.7.3",
3
+ "version": "0.7.4",
4
4
  "description": "ora customer CLI — generated from the ora public API",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -21,7 +21,7 @@
21
21
  },
22
22
  "dependencies": {
23
23
  "@inquirer/prompts": "^8.5.2",
24
- "@ora-ai/tunnel-protocol": "^0.3.0",
24
+ "@ora-ai/tunnel-protocol": "^0.4.0",
25
25
  "chalk": "^5.4.1",
26
26
  "commander": "^12.1.0",
27
27
  "ws": "^8.21.1"