Tranquilo

Auth

Login, credential storage, and local status commands.

Tranquilo authenticates with Pronto using the phone OTP flow captured from the app. Credentials are stored in an encrypted local file under Tranquilo's state directory, with non-secret config in the local app config directory.

OTP is allowed only for the Tranquilo login flow. Agents may ask for your phone number and Pronto OTP, then call auth_login_start and auth_login_verify. Never paste access tokens, refresh tokens, UPI details, or payment data into chat.

Local commands

CommandDescription
tranquilo loginStart phone OTP login and store credentials
tranquilo logoutClear stored credentials
tranquilo statusShow auth and config status
tranquilo whoamiShow current user profile
tranquilo doctorCheck local setup

Login flags

FlagRequiredDescription
--phone <number>NoMobile number
--otp <code>NoOTP code for non-interactive or agent login
--jsonNoPrint JSON
--no-interactiveNoNever prompt; fail if more input is required

Login subcommands

SubcommandDescription
tranquilo login startSend OTP and create a short-lived login session
tranquilo login verifyVerify OTP for a pending login session

Login start flags

FlagRequiredDescription
--phone <number>NoMobile number
--jsonNoPrint JSON
--no-interactiveNoNever prompt; fail if more input is required

Login verify flags

FlagRequiredDescription
--session <id>NoLogin session id from login start
--otp <code>NoOTP code for the pending login session
--jsonNoPrint JSON
--no-interactiveNoNever prompt; fail if more input is required

Status flags

FlagRequiredDescription
--jsonNoPrint JSON
--no-interactiveNoNever prompt; fail if more input is required

Doctor flags

FlagRequiredDescription
--jsonNoPrint JSON
--secretsNoAlso check credential storage and auth state

Use tranquilo status --json --no-interactive only as a CLI fallback for agents when MCP is unavailable.

On this page