Indiana CLI

Downloads are publicly hosted by Indiana. On macOS/Linux, use curl: dependencies are included, and installation invokes no npm and needs no npm account or sudo. Install Node.js 22 or newer first; the archive does not include a Node.js runtime.

curl supports macOS arm64/x64 and Linux arm64/x64 with glibc/musl. The script detects your platform, verifies SHA-256, and installs to ~/.local/bin/indiana with releases in ~/.local/share/indiana/releases. Add ~/.local/bin to PATH as shown above. Customize locations with absolute INDIANA_BIN_DIR and INDIANA_INSTALL_ROOT paths. Rerun curl to upgrade; unrelated executables are never overwritten. Archives and checksums are listed at https://tinker.cash/downloads/cli/portable.json.

npm is also available; use this option on Windows. It downloads the CLI from our website and dependencies from the public npm registry. No repository access or npm account is required.

From 0.3.3, use update --check to check releases and indiana update to upgrade. Successful interactive commands check the public version at most daily and show an upgrade notice. Checks have a 1.5-second deadline; offline failures leave command results intact. JSON, CI, non-interactive, help and version runs stay silent. Set INDIANA_NO_UPDATE_CHECK=1 to disable automatic checks, or use update --check --json explicitly. Updates verify downloads and the installed version, preserving custom curl directories or the global npm prefix, configuration and credentials. Releases always come from the official website, independently of --server.

If you have 0.3.2 or earlier, run this page's curl or npm install command once to bootstrap 0.3.3. Subsequent releases can be discovered automatically and installed with indiana update. Source or unrecognized installations receive installation guidance.

To uninstall the default curl installation, remove ~/.local/bin/indiana and ~/.local/share/indiana; saved configuration and credentials remain. Uninstall npm installations with npm uninstall -g @indiana/cli. Rerunning the current installation command also upgrades the CLI. npm archive metadata is at https://tinker.cash/downloads/cli/latest.json. Public installation does not expand account permissions: management operations still require login and explicit approval.

Set the target service URL and existing Organization/App IDs, then run doctor to check connectivity and login configuration. Select the required Account, Organization, App or Environment grants during login. context use saves your selection; account permissions and approval determine access.

config init creates indiana.config.json without overwriting files. Scope priority is explicit flags, project configuration, then the selected profile. context use updates existing project configuration or otherwise the profile. Configuration may be committed; exclude tokens and SDK keys. Use INDIANA_CLI_CONFIG_DIR to change the user configuration directory.

• The CLI opens your system browser. Sign in with your console account and approve the OAuth identity request.
• A second page shows the device request, App, environment and permissions. Check the device label and requested scope before approval.
• The CLI waits for approval, then saves credentials. Pending requests expire after 10 minutes and management grants after 30 days. Token refresh does not extend the grant.

Login requests only project.read by default. For resource reads, explicitly add --permissions project.read,coupons.read,rewards.read to the login command. Writes require their matching resource grant, such as customers.write, features.write, plans.write or platform.write. Request only what the task needs; an existing grant is never expanded automatically.

Login requires a browser and temporarily listens at http://127.0.0.1:43187/callback. Free this port before retrying if it is occupied.

Sign in with your Console account; the CLI refreshes saved login credentials automatically. Sign in again after account, membership or device access is revoked. Browser cookies, SDK keys and CI service accounts cannot be used to log in.

Credentials default to the operating system credential store, bound to the management origin, profile, issuer, client, user and session. An unavailable credential store fails explicitly, without automatic file fallback. POSIX users may explicitly choose --credential-store file with 0700 directories and 0600 files. Windows does not support this file mode.

whoami returns the server-verified identity and scope without tokens. With no saved credential, logout succeeds immediately. Otherwise, it verifies revocation of this device's exact server grant before deleting local credentials. Network failure retains credentials and reports incomplete revocation. logout --local only removes local credentials; the server grant may remain valid. Use /cli/sessions on the selected management server to review and revoke individual devices. Revoking one device leaves other devices unchanged.

requiredPermissions in operations describe lists the complete grant dependencies. Customer creation also needs plans.read and features.read; Feature changes need plans.write and balances.read; Product writes also need features.read, customers.read, balances.read and rewards.read. Missing dependencies fail before mutation so defaults and existing references cannot be silently omitted.

customer-create.json contains { "input": { "externalUserId": "user-42", "name": "Alex" } }. An update file contains { "requestId": "<new UUID>", "patch": { "name": "Alex Updated" } }. App/environment come from the approved selection; conflicting values are rejected. Design actions use the current Console DTOs and retain revision, requestId and publication validation.

Use repeatable --query key=value fields, such as features list --query id=<feature-uuid>. --file - reads stdin. call <operationId> --input envelope.json accepts {params,query,body} for a catalogued operation; arbitrary URLs and RPCs are rejected. --input cannot be mixed with the individual input flags.

To change scope, logout and login --permissions with the required resource grants; existing device grants never expand automatically. --out <new-file> saves JSON with 0600 permissions without overwriting files; failure removes this operation’s incomplete output. Failed writes are never retried automatically.

Use current editable Funnel/Paywall documents and canonical Offering fields (lookupKey/displayName/items/metadata). Input must be valid UTF-8 and JSON, at most 1,000,000 bytes. draft allows incomplete drafts; publish checks publication structure. validate accepts --file - for stdin. Obsolete formats are rejected.

Validation reports validation=local and serverChecks=not_run. Structural validity does not authorize publication: tenant access, fixed references, providers and current state still require server checks. diff emits JSON Pointers, change kinds and stable SHA-256 hashes without document values. It shows up to 100 changes with total / truncated fields.

Pull into a new directory. screen.json holds structure, copy and actions; edit localized HTML and shared CSS under html/<node-id>/. indiana.source.json retains the target, App/environment and pull baseline. Use a local editor or AI agent, check and review the changes, then submit a draft or import them into the Web code editor for review.

Pull uses platform.read; push uses platform.write and the original native authoring checks. Check/diff run offline. Push enforces the original revision and preserves files on conflict; library targets create a private template copy. Commands do not publish, watch files or start a local preview server.