@odla-ai/cli 0.13.1 → 0.14.0

package/README.md

@@ -63,6 +63,8 @@ npx odla-ai calendar connect --env dev
 npx odla-ai calendar resync --env dev
 npx odla-ai calendar disconnect --env dev --yes
 npx odla-ai capabilities --json
+npx odla-ai code connect --env dev --email owner@example.com
+npx odla-ai code connect --env prod --once # bounded enrollment + heartbeat proof
 # install SDKs, write the Worker, and create wrangler.jsonc before secret push
 npx odla-ai provision --dry-run
 npx odla-ai provision --email owner@example.com --write-dev-vars --push-secrets
@@ -88,6 +90,24 @@ npx odla-ai skill install
 npx odla-ai version
 ```
 
+`code connect` is the first-party Code host runtime. Run it from a GitHub
+checkout already connected to an app in Studio; it resolves the origin to that
+project without requiring local config. If `odla.config.mjs` exists, its app is
+used explicitly. The CLI chooses the safe installed container
+engine (Apple container or Podman by default), requests one exact
+`platform:code:host:connect` approval, atomically enrolls/offers/binds the host,
+then runs the credentialless Pi container adapter in the foreground. The Pi and
+clean-build images are digest-pinned, and build execution goes through a fixed
+CaMeL-registered recipe. Use `--engine docker` only after reviewing that daemon
+boundary. `--once` performs enrollment and one heartbeat without accepting a
+queued session.
+
+The approval and host credential records live in odla-ai/db and store hashes,
+not plaintext. The shown-once host bearer is kept only in the running CLI
+process: no Code credential file is created under `.odla/`. A subsequent
+approved `code connect` rotates the database-backed credential and invalidates
+the previous bearer.
+
 `init` writes:
 
 - `odla.config.mjs`