@tapi-dev/sdk 0.1.36 → 0.1.39

package/README.md

@@ -13,20 +13,32 @@ This package is ESM-first and works in runtimes with `fetch`, including modern N
 The CLI command is `tapi`. If your package manager only installed the SDK
 locally and `tapi` is not on `PATH`, use `npx tapi` as a fallback.
 
-## Developer Flow
-
-Tapi Studio is launched from the developer app repo. The repo's `.tapi/project.json`
-is the project binding, so one developer can work on multiple Tapi projects from
-different directories without a global Studio project picker.
-
-```bash
-npm install @tapi-dev/sdk
-tapi init --project brokerage
-tapi studio
-```
-
-`tapi studio` checks the required local `tapi-service`, installs it when needed,
-downloads the portable Studio server release when the channel manifest uses
+## Developer Flow
+
+Tapi Studio is launched from the signed-in developer account. Running
+`tapi studio` lists the Tapps available to that account, asks which one to open,
+then starts Studio in that Tapp context. The current directory can still provide
+a default via `.tapi/project.json`, but it is no longer required for Studio to
+know which Tapp to show.
+
+```bash
+npm install @tapi-dev/sdk
+tapi login
+tapi tapp create brokerage
+tapi studio
+```
+
+Useful Studio launch forms:
+
+```bash
+tapi studio                    # ask which Tapp to open
+tapi studio --tapp brokerage   # open one Tapp directly
+tapi studio --select           # force the picker
+tapi studio --last             # reuse the last selected Tapp
+```
+
+`tapi studio` checks the required local `tapi-service`, installs it when needed,
+downloads the portable Studio server release when the channel manifest uses
 `installerKind: portable-server`, starts Studio locally, and opens the browser.
 If the channel still publishes a legacy NSIS desktop Studio manifest and no
 Studio executable is installed yet, `tapi studio` runs the installer first, then
@@ -52,10 +64,12 @@ The current artifact and current release are kept.
 
 Useful commands:
 
-```bash
-tapi init --project brokerage
-tapi link --project brokerage
+```bash
+tapi login
+tapi init --project brokerage
+tapi link --project brokerage
 tapi studio
+tapi studio --tapp brokerage
 tapi service install --channel pilot
 tapi service status
 tapi services describe schwab.place_order
@@ -80,8 +94,8 @@ ServiceMaps and service-run contracts are saved in the bound Tapi server
 project. Runtime SDK calls read the service catalog from that project.
 
 ```bash
-TAPI_API_KEY=tapi_project_key tapi tapp create brokerage --name "Brokerage"
-TAPI_API_KEY=tapi_project_key tapi tapp service add brokerage schwab.place_order \
+tapi tapp create brokerage --name "Brokerage"
+tapi tapp service add brokerage schwab.place_order \
   --service-map sm_123 \
   --entry place_order
 ```
@@ -102,23 +116,23 @@ page that can create or accept a queue id, attach that queue to the Tapp, and
 assign one or more slots on the runner:
 
 ```bash
-TAPI_API_KEY=tapi_project_key tapi runner setup \
+tapi runner setup \
   --runner-id john-laptop \
   --project brokerage
 ```
 
 ## Quick Start
 
-Create one TAPI client in server-side app code. Use a developer API key, the
-Tapp id that owns the service call, and optionally the same project id from
-`.tapi/project.json`.
+Create one TAPI client in server-side app code. Use a Firebase ID token for the
+developer identity that owns and pays for the Tapp, the Tapp id that owns the
+service call, and optionally the same project id from `.tapi/project.json`.
 
 ```ts
 import { TapiClient } from "@tapi-dev/sdk";
 
 export const tapi = new TapiClient({
   baseUrl: process.env.TAPI_BASE_URL!,
-  apiKey: process.env.TAPI_API_KEY!,
+  authToken: process.env.TAPI_FIREBASE_ID_TOKEN!,
   tappId: process.env.TAPI_TAPP_ID!,
   projectId: process.env.TAPI_PROJECT_ID!,
 });
@@ -130,7 +144,7 @@ holding a browser open:
 ```ts
 const tapi = new TapiClient({
   baseUrl: process.env.TAPI_BASE_URL!,
-  apiKey: process.env.TAPI_API_KEY!,
+  authToken: process.env.TAPI_FIREBASE_ID_TOKEN!,
   tappId: process.env.TAPI_TAPP_ID!,
   projectId: process.env.TAPI_PROJECT_ID!,
   dev: false,
@@ -144,7 +158,7 @@ production failure:
 ```ts
 const tapi = new TapiClient({
   baseUrl: process.env.TAPI_BASE_URL!,
-  apiKey: process.env.TAPI_API_KEY!,
+  authToken: process.env.TAPI_FIREBASE_ID_TOKEN!,
   tappId: process.env.TAPI_TAPP_ID!,
   projectId: process.env.TAPI_PROJECT_ID!,
   dev: true,
@@ -269,8 +283,8 @@ export default {
 };
 ```
 
-```bash
-TAPI_API_KEY=tapi_project_key tapi triggers sync
+```bash
+tapi triggers sync
 ```
 
 `triggers sync` upserts by trigger name for the current `.tapi/project.json`
@@ -295,14 +309,13 @@ await tapi.triggers.disable("act_123");
 You can inspect the same input/output contract from the CLI:
 
 ```bash
-tapi services describe schwab.place_order \
-  --api-base-url "$TAPI_BASE_URL" \
-  --api-key "$TAPI_API_KEY" \
-  --project "$TAPI_PROJECT_ID"
-```
-
-Do not expose `TAPI_API_KEY` in public browser bundles. Put the SDK behind your
-own backend route, server action, or job worker when using secret API keys.
+tapi services describe schwab.place_order \
+  --api-base-url "$TAPI_BASE_URL" \
+  --project "$TAPI_PROJECT_ID"
+```
+
+Do not expose developer Firebase ID tokens in public browser bundles. Put the
+SDK behind your own backend route, server action, or job worker.
 
 ## Runtime Profiles and Proxies
 
@@ -370,7 +383,7 @@ If your JavaScript runtime does not provide `WebSocket`, pass one:
 ```ts
 const tapi = new TapiClient({
   baseUrl: process.env.TAPI_BASE_URL!,
-  apiKey: process.env.TAPI_API_KEY!,
+  authToken: process.env.TAPI_FIREBASE_ID_TOKEN!,
   tappId: process.env.TAPI_TAPP_ID!,
   webSocket: MyWebSocketImplementation,
 });
@@ -378,17 +391,16 @@ const tapi = new TapiClient({
 
 ## Configuration
 
-```env
+```env
 TAPI_BASE_URL=https://your-tapi-api-host
-TAPI_API_KEY=tapi_project_key
+TAPI_FIREBASE_ID_TOKEN=firebase_id_token_for_the_tapp_owner
 TAPI_TAPP_ID=brokerage
 TAPI_PROJECT_ID=brokerage
 ```
 
 `tappId` is required. Service calls are made for that Tapp, and the developer
-who owns the Tapp pays for the service delivery. `projectId` is optional when
-the API key is already project-scoped. If provided, the SDK sends it as the
-`X-Tapi-Project` header and the server rejects mismatches.
+who owns the Tapp pays for the service delivery. If provided, `projectId` is
+sent as the `X-Tapi-Project` header and the server rejects mismatches.
 
 ## Common Project Setup
 
@@ -406,7 +418,7 @@ import { TapiClient } from "@tapi-dev/sdk";
 
 export const tapi = new TapiClient({
   baseUrl: process.env.TAPI_BASE_URL!,
-  apiKey: process.env.TAPI_API_KEY!,
+  authToken: process.env.TAPI_FIREBASE_ID_TOKEN!,
   tappId: process.env.TAPI_TAPP_ID!,
   projectId: process.env.TAPI_PROJECT_ID!,
 });
@@ -446,10 +458,10 @@ Cloud runs are requested from the SDK, but VM provisioning, service
 installation, worker leases, browser internals, and AWS cleanup stay on the
 Tapi server. The SDK is only the front door.
 
-Keep this code server-side. Do not put `TAPI_API_KEY` in a browser bundle and
-do not wire AWS or Stripe from the developer's app. The app sends its own user
-identity to Tapi, and Tapi handles prepaid Stripe checkout, credit accounting,
-AWS worker provisioning, and cleanup.
+Keep this code server-side. Do not put developer Firebase ID tokens in a
+browser bundle and do not wire AWS or Stripe from the developer's app. The app
+sends its own user identity to Tapi, and Tapi handles prepaid Stripe checkout,
+credit accounting, AWS worker provisioning, and cleanup.
 
 The minimum developer flow is:
 
@@ -523,7 +535,7 @@ low, `runCloudBatch` converts the server's HTTP `402` into a normal
 `availableBalanceCents`, and `requiredBalanceCents`. That keeps the button
 handler simple.
 
-Credits are scoped under the Tapi API key owner, Tapp id, and
+Credits are scoped under the authenticated Firebase owner, Tapp id, and
 `user.externalUserId`. Use the same `externalUserId` for quote, balance,
 checkout, and run calls. If you omit `externalUserId` but provide `email`, Tapi
 uses the normalized email as the external user id.

package/dist/cli.d.ts

@@ -66,12 +66,14 @@ export interface StudioCliOptions {
     workspaceRoot?: string;
     projectId?: string;
     projectSlug?: string;
+    projectIdSource?: "option" | "env" | "workspace" | "selection";
     workspaceMode: boolean;
     launchUrlQuery?: string;
+    tappSelectionMode: "auto" | "select" | "last" | "none";
 }
 export interface RunnerSetupCliOptions {
     apiBaseUrl: string;
-    apiKey: string;
+    authToken?: string;
     projectId: string;
     runnerId: string;
     port: number;