wisent-app command
export
Export the authenticated account’s canonical Wisent account-data JSON to a new local file.
Usage
wisent-app export <destination.json> [--session-file <file> | --token-stdin] [--api-base <url>]
The command downloads the canonical account-data document, verifies that the response is JSON, and writes it to the destination with owner-only mode 0600. It refuses to overwrite an existing path.
Authentication and options
Credential input
By default the command reads ~/.config/wisent/session.json, which must contain a Supabase access_token. On macOS and Linux the file must have mode 0600. Use --token-stdin to pipe a bearer token instead. Tokens are never accepted in arguments or environment variables.
Shared options
--session-file <file>- Read a session from this path instead of the default. Also configurable with
WISENT_SESSION_FILE. --token-stdin- Read the bearer token from standard input. It cannot be combined with
--session-file. --api-base <url>- Use a different API base instead of
https://bobloo.com/api. Also configurable withWISENT_API_BASE. HTTPS is required except for localhost.
Result and exit status
Success prints the resolved destination path. An argument, credential, file, transport, non-successful HTTP, or invalid-JSON response failure uses exit status 1. The command never prints the bearer token or exported account contents.
Graphical import and document contract
The web, iOS, and Android import flows use the same document and server operation. Read the account-data guide for the graphical workflow, accepted records, duplicate handling, atomic validation, and explicit refusals.
Related command: wisent-app import.