Skip to main content
All commands support -p, --path <path> to run against a specific directory (default .), and --dev to use a local Gateway.

​
init

Initialize a Latitude project in the current directory.
  • Prompts for your API key (or uses latitude login/LATITUDE_API_KEY)
  • Lets you choose:
    • Create a new project (provide a name)
    • Use an existing project (enter projectId)
  • Creates the prompts directory (asks before clearing a non-empty folder)
  • Writes latitude-lock.json
latitude-lock.json example:

​
status

Show project and version info plus a local vs remote diff summary.
  • Prints project link, version title/description
  • Summarizes Added/Modified/Deleted prompts

​
pull

Pull remote prompts to your local filesystem with a diff preview.
  • Computes local vs remote changes
  • Choose: Accept / Cancel / View details (opens pager for full diffs)
  • -y skips confirmation and applies changes
  • Saves prompts as .promptl text files
  • Removes local files that no longer exist remotely

​
push

Push local prompt changes to the current version.
  • Reads .promptl files under rootFolder
  • Shows a diff and asks for confirmation; -y skips confirmation
  • Sends only changed files to the server

​
checkout

Checkout a specific version or create a new version and switch to it.
  • latitude checkout <versionUuid>: updates latitude-lock.json and pulls that version
  • latitude checkout -b <name>: creates a new version and switches to it
  • Validates the target version before updating the lock file

​
login

Store or override your API key in the system keychain.
  • Warns if LATITUDE_API_KEY is set (that variable takes precedence)
  • -f/--force to override without confirmation

​
help

Show CLI help.

​
Prompt file format

Prompts are stored as plain .promptl text files:
Each file contains the raw prompt content using PromptL syntax.