@oxy-hq/cli 0.7.0 → 0.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oxy-hq/cli",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "oxyc — the Oxy CLI: a gh-api-style client for the Oxy HTTP API, plus the customer-account tooling that scopes a session to one customer.",
   "type": "module",
   "bin": {

package/skills/oxy-cli/SKILL.md

@@ -68,6 +68,7 @@ never sent to the server as a literal.
 
     oxyc validate                  # check the workspace YAML — no network, no token
     oxyc proxy --env dev           # local app dev against cloud data
+    oxyc login-link --next /ide    # one-time URL that signs a browser in as your token
     oxyc guide                     # this page, to paste into a context file
 
 `oxyc validate` is the one command that works entirely offline. It checks
@@ -76,6 +77,11 @@ never sent to the server as a literal.
 STRUCTURAL only — `oxy validate` also resolves `databases:` and `llm.ref`, and
 wins where the two disagree.
 
+To look at a deployed environment in a browser, navigate your browser tool to
+`$(oxyc login-link --env dev --next /ide)`. It is a one-time link that signs
+the browser in as your token — no OAuth, no inbox — and it needs a personal
+access token, which is what `oxyc login` stores.
+
 If your runtime speaks MCP, `oxyc mcp` serves the same API surface as four
 tools (`oxy_routes`, `oxy_schema`, `oxy_request`, `oxy_whoami`) instead. It
 reads its credential from `OXY_TOKEN` only — with the variable unset it exits

package/template/.github/workflows/publish.yaml

@@ -160,7 +160,7 @@ env:
   # service account are honoured from 0.7.0, which tries them first and falls
   # back to the publisher. A pin older than that still publishes, through the
   # publisher alone.
-  OXYC_VERSION: "0.7.0"
+  OXYC_VERSION: "0.8.0"
 
 jobs:
   build: