@tarout/cli 0.2.0 → 0.2.2

package/README.md

@@ -3,17 +3,20 @@
 [![npm version](https://img.shields.io/npm/v/@tarout/cli.svg)](https://www.npmjs.com/package/@tarout/cli)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
-The official command-line interface for [Tarout](https://tarout.sa) - a Platform-as-a-Service for deploying applications, databases, and more.
+The official command-line interface for [Tarout](https://tarout.sa) — the Saudi cloud platform built for coding agents. Your agent writes code and defines infrastructure; Tarout provisions it instantly.
 
 ## Installation
 
 ```bash
-npm install -g @tarout/cli
+curl -fsSL https://tarout.sa/install.sh | sh
 ```
 
 Or with other package managers:
 
 ```bash
+# Using npm
+npm install -g @tarout/cli
+
 # Using yarn
 yarn global add @tarout/cli
 
@@ -30,14 +33,10 @@ bun add -g @tarout/cli
 # 1. Login via browser (opens authentication page)
 tarout login
 
-# 2. List your applications
-tarout apps list
+# 2. Inspect and deploy from your project root
+tarout deploy --wait --source upload
 
-# 3. Deploy an application
-tarout deploy my-app
-
-# 4. View logs
-tarout logs my-app --follow
+# The first deploy prompts to create or link an app, and to create detected resources.
 ```
 
 ## Commands
@@ -51,8 +50,8 @@ tarout logs my-app --follow
 | `tarout whoami` | Show current user, organization, and environment |
 
 ```bash
-# Login with custom API URL (for self-hosted)
-tarout login --api-url https://your-tarout-instance.com
+# Login with a custom API URL (e.g. staging)
+tarout login --api-url https://staging.tarout.sa
 ```
 
 ### Applications
@@ -80,14 +79,14 @@ tarout apps delete my-api --yes
 
 | Command | Description |
 |---------|-------------|
-| `tarout deploy <app>` | Deploy an application |
+| `tarout deploy [app]` | Deploy an application |
 | `tarout deploy:status <app>` | Check deployment status |
 | `tarout deploy:cancel <app>` | Cancel running deployment |
 | `tarout deploy:list <app>` | List recent deployments |
 
 ```bash
-# Deploy specific branch
-tarout deploy my-app --branch feature/new-feature
+# Inspect and deploy the current folder
+tarout deploy --wait --source upload
 
 # Deploy and wait for completion
 tarout deploy my-app --wait
@@ -96,6 +95,8 @@ tarout deploy my-app --wait
 tarout deploy:status my-app
 ```
 
+`tarout deploy` inspects the current folder for database, file storage, and Git signals before it asks questions. If Git exists, local upload remains available, so users without GitHub can still deploy. If the user chooses GitHub, run `tarout providers github connect` to open Tarout's Git provider setup page, then connect the repository to the app and deploy with `--source configured`.
+
 ### Logs
 
 | Command | Description |
@@ -157,9 +158,6 @@ tarout db create mydb --type postgres
 # Create MySQL database
 tarout db create mydb --type mysql
 
-# Create Redis instance
-tarout db create cache --type redis
-
 # Get connection string
 tarout db info mydb
 
@@ -241,6 +239,7 @@ APP_ID=$(tarout apps list --json | jq -r '.[0].id')
 | 3 | Authentication error (not logged in) |
 | 4 | Resource not found |
 | 5 | Permission denied |
+| 6 | Needs input — see `needs_input` event below |
 
 ### JSON Output Format
 
@@ -257,6 +256,51 @@ All `--json` output follows a consistent structure:
 { "success": true, "data": [...], "meta": { "total": 10 } }
 ```
 
+### Agent Input Relay (`needs_input`)
+
+When `tarout up --json` hits a choice point and the value wasn't passed as a
+flag, it emits a single `needs_input` line on stdout and exits with code `6`
+instead of crashing or silently defaulting. The external agent reads that
+event, asks the human user in its chat UI, then re-invokes `tarout up` with
+the same arguments plus the new flag.
+
+```json
+{
+  "type": "needs_input",
+  "field": "name",
+  "kind": "input",
+  "question": "Application name:",
+  "default": "my-project",
+  "flag": "--name",
+  "sensitive": false,
+  "context": { "step": "app_name", "defaultName": "my-project" }
+}
+```
+
+Fields:
+- `field` — stable id (e.g. `name`, `region`, `token`, `source`).
+- `kind` — `"input" | "select" | "confirm" | "password"`.
+- `question` — show verbatim to the user.
+- `choices` — present when `kind: "select"`.
+- `default` — pre-fill suggestion.
+- `flag` — the CLI flag to pass on the next invocation.
+- `sensitive` — `true` for tokens / passwords (mask in UI, omit from logs).
+- `context` — free-form metadata the agent can use to phrase a richer prompt.
+
+Loop pattern for an agent:
+
+```text
+1. invoke `tarout up --json [flags]`
+2. read stdout line-by-line
+3. if line.type === "needs_input":
+     - ask the user for `question`
+     - re-invoke with the same flags + `${flag} ${answer}`
+4. otherwise treat the final JSON envelope as success / error
+```
+
+Flags currently supported by `tarout up` for skipping the relay:
+`--token`, `--name`, `--plan`, `--source`, `--repo`, `--branch`, `--region`, `--yes`.
+
 ## Configuration
 
 Configuration is stored at `~/.tarout/config.json`:
@@ -286,7 +330,7 @@ Configuration is stored at `~/.tarout/config.json`:
 
 ## Support
 
-- Documentation: [docs.tarout.sa](https://docs.tarout.sa)
+- Documentation: [tarout.sa/docs](https://tarout.sa/docs)
 - Issues: [GitHub Issues](https://github.com/tarout/platform/issues)
 - Discord: [Join our community](https://discord.gg/2tBnJ3jDJc)
 

package/dist/api-735LN7BA.js

@@ -0,0 +1,11 @@
+import {
+  createApiClient,
+  getApiClient,
+  resetApiClient
+} from "./chunk-7YS2WBLB.js";
+import "./chunk-KL3JNPAY.js";
+export {
+  createApiClient,
+  getApiClient,
+  resetApiClient
+};

package/dist/billing-WOKNOS4N.js

@@ -0,0 +1,11 @@
+import {
+  pollCheckoutUntilTerminal,
+  registerBillingCommands
+} from "./chunk-5XBVQICT.js";
+import "./chunk-7YS2WBLB.js";
+import "./chunk-CJMIX35A.js";
+import "./chunk-KL3JNPAY.js";
+export {
+  pollCheckoutUntilTerminal,
+  registerBillingCommands
+};