@odla-ai/cli 0.27.1 → 0.27.2

package/dist/index.d.cts

@@ -569,8 +569,8 @@ interface ProvisionOptions {
     token?: string;
     /** Existing odla account email used only when a fresh device handshake is required. */
     email?: string;
-    /** true forces browser launch, false disables it, undefined auto-opens whenever
-     * this machine can show a browser (skipped in CI, over SSH, or with no display). */
+    /** Browser opening is attempted by default in every real CLI environment.
+     * true records an explicit request; false is the only production suppression. */
     open?: boolean;
     /** Cap the handshake-approval wait, in seconds. When it elapses the command
      * exits with the pending handshake persisted; rerunning resumes it. Defaults
@@ -897,10 +897,10 @@ declare function initProject(options: InitOptions): void;
  *
  * The developer token comes from (in order) `options.token`, `$ODLA_DEV_TOKEN`,
  * the cached `.odla` token, or a fresh email-bound device handshake — which
- * prints a user code for the same signed-in account to review and auto-opens
- * the browser whenever this machine can show one — including scripted and
- * agent-driven runs; only CI, SSH, and display-less hosts skip it
- * (`open: true`/`false` forces/suppresses it). Network error bodies pass through
+ * prints one canonical Studio URL and attempts to open it from every real CLI
+ * environment, including CI, SSH, display-less, and agent-driven shells. Only
+ * `open: false` suppresses the attempt; opener failures remain explicit.
+ * Network error bodies pass through
  * `redactSecrets` before display.
  *
  * @param options.dryRun Print the resolved plan and return before any network call/write.

package/dist/index.d.ts

@@ -569,8 +569,8 @@ interface ProvisionOptions {
     token?: string;
     /** Existing odla account email used only when a fresh device handshake is required. */
     email?: string;
-    /** true forces browser launch, false disables it, undefined auto-opens whenever
-     * this machine can show a browser (skipped in CI, over SSH, or with no display). */
+    /** Browser opening is attempted by default in every real CLI environment.
+     * true records an explicit request; false is the only production suppression. */
     open?: boolean;
     /** Cap the handshake-approval wait, in seconds. When it elapses the command
      * exits with the pending handshake persisted; rerunning resumes it. Defaults
@@ -897,10 +897,10 @@ declare function initProject(options: InitOptions): void;
  *
  * The developer token comes from (in order) `options.token`, `$ODLA_DEV_TOKEN`,
  * the cached `.odla` token, or a fresh email-bound device handshake — which
- * prints a user code for the same signed-in account to review and auto-opens
- * the browser whenever this machine can show one — including scripted and
- * agent-driven runs; only CI, SSH, and display-less hosts skip it
- * (`open: true`/`false` forces/suppresses it). Network error bodies pass through
+ * prints one canonical Studio URL and attempts to open it from every real CLI
+ * environment, including CI, SSH, display-less, and agent-driven shells. Only
+ * `open: false` suppresses the attempt; opener failures remain explicit.
+ * Network error bodies pass through
  * `redactSecrets` before display.
  *
  * @param options.dryRun Print the resolved plan and return before any network call/write.

package/dist/index.js

@@ -57,7 +57,7 @@ import {
   startHostedSecurityJob,
   surfacePaths,
   validateInvocation
-} from "./chunk-4JWDJN3P.js";
+} from "./chunk-JWEBGIBR.js";
 export {
   AGENT_HARNESSES,
   CAPABILITIES,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@odla-ai/cli",
-  "version": "0.27.1",
+  "version": "0.27.2",
   "description": "Agent-operable CLI for odla provisioning, calendar consent and sync lifecycle, System AI administration, Worker secrets, security jobs, and smoke checks.",
   "license": "MIT",
   "homepage": "https://odla.ai/docs/packages/cli",

package/skills/odla/SKILL.md

@@ -106,9 +106,11 @@ guessing which platform/credential steps need manual work. Then:
    `npx @odla-ai/cli provision --email <existing-odla-account>
    --write-dev-vars --push-secrets`. A device code prints; that same account
    signs in, reviews the exact code, and approves it at https://odla.ai/studio.
-   Opening the link alone is inert. Relay the printed approval URL to the
-   human verbatim — the automatic browser launch is best-effort and may show
-   no tab. Outside an interactive terminal the wait is capped (90s default,
+   Opening the link alone is inert. The CLI prints exactly one `/studio?code=`
+   URL and attempts to open it in every real environment. **If you have browser
+   control, open that exact URL now.** If you do not, give it to the human
+   verbatim; never wait silently or start a substitute handshake. Outside an
+   interactive terminal the wait is capped (90s default,
    `--wait <seconds>`); exit code 75 means still pending: the handshake is
    persisted, so once the human approves, re-run the same command and it
    resumes the same code and collects the token. It creates the app,
@@ -242,11 +244,11 @@ Found a wrong step? Fix an app runbook directly. For a platform runbook,
 `runbook edit` requests an admin-approved capability — a plain handshake token is
 never admin, and `npx @odla-ai/cli whoami` tells you what you hold.
 
-⏸ That request prints an approval block with a URL on its own line. **Relay that
-URL to the human verbatim, immediately, before you wait on anything.** You cannot
-approve it yourself — the grant is issued to you, not by you — and the command
-blocks until a signed-in admin approves it. The browser launch is best-effort and
-often shows no tab, so the printed URL is the only thing the human can rely on.
+⏸ That request prints the same canonical approval block. **Use browser control
+to open its URL immediately; if unavailable, give it to the human verbatim.**
+You cannot approve it yourself — the grant is issued to you, not by you — and
+the command blocks until a signed-in admin approves it. Never wait silently or
+start a substitute handshake because the automatic opener produced no tab.
 If approval is not available, comment on the runbook instead so an admin can fix
 it later.
 

package/skills/odla-migrate/references/phase-2-db.md

@@ -7,7 +7,9 @@ schema + deny-all rules, the db key in the dev worker, and first
 Human obligation: provide the existing odla account email (not a password or
 session credential), sign in at https://odla.ai/studio, explicitly review the
 exact handshake code, and approve it. The provision run prints the code and
-opens the review page in interactive terminals; loading it alone is inert.
+attempts to open the one canonical review URL in every real CLI environment.
+Agents with browser control open that exact URL immediately; loading it alone
+is inert until the signed-in human approves.
 
 ## Steps
 

package/skills/odla-migrate/references/troubleshooting.md

@@ -40,9 +40,10 @@ password or session token.
 Cause: nobody approved within the wait cap (90s outside an interactive
 terminal; `--wait <seconds>` overrides). This is normal in agent shells and
 loses nothing — the handshake is persisted in `.odla/handshake.local.json`.
-Fix: relay the printed approval URL to the human **verbatim** (browser
-launch is best-effort — a sandboxed shell can report success with no tab
-appearing), wait for them to approve, then re-run the same command; it
+Fix: use browser control to open the one printed `/studio?code=` URL now. If
+browser control is unavailable, give that URL to the human **verbatim**. The
+CLI attempts its OS opener in every real environment, but that request can
+still produce no visible tab. Wait for approval, then re-run the same command; it
 resumes the same code and collects the token. Do not loop unattended
 retries; each handshake lives ~10 minutes.