latere

latere is the command line of the Latere platform. You sign in once, and one binary reaches every capability with your identity: workloads in Environments, apps you deploy with a git push, models through the Latere API, the Latere agent on your machine and an adversarial review of a Claude Code session, and repositories on Latere Code (code.latere.ai). There is no API key to allocate and no second credential to manage.

latere login
latere environments apply -f workload.yaml
latere apps create hello && git push latere main && latere apps logs -f
latere models invoke --model openai/gpt-4.1-mini "Say hi"
latere agents run
git clone https://code.latere.ai/<owner>/<repo>.git

Install

curl -fsSL https://platform.latere.ai | sh

platform.latere.ai answers curl and wget with the installer, and a browser with the platform's site.

The installer supports Linux and macOS on amd64 and arm64. It writes to $HOME/.local/bin, so it needs no sudo, and prints the line to add to your shell profile when that directory is not on your PATH.

# Pin a version
curl -fsSL https://platform.latere.ai | sh -s -- vX.Y.Z

# Install system-wide
curl -fsSL https://platform.latere.ai | PREFIX=/usr/local sh

# Build from source
go install github.com/latere-ai/latere-cli/cmd/latere@latest

The installer finds the newest release through the GitHub releases redirect rather than the rate-limited GitHub API, so it also works behind shared NAT. If it still cannot resolve a version, for example behind a restrictive proxy, pin one with the sh -s -- vX.Y.Z form. It checks the archive against the release's checksums.txt when shasum is available.

Every release carries archives for Linux, macOS, and Windows on amd64 and arm64, and a checksums.txt. On Windows, download the .zip from the releases page.

Stay up to date

Auto-upgrade is on by default. latere checks for a new release at most once a day, and the next time you run a command after one appears, it replaces itself and then runs your command.

latere upgrade            # install the latest release now
latere upgrade v0.2.29    # install a specific release; this is how you roll back
latere upgrade --check    # report whether a newer release exists, without installing
latere upgrade --auto off # turn auto-upgrade off
latere upgrade --auto on  # turn it back on

If a release is broken, roll back with latere upgrade <previous-version> and add latere upgrade --auto off to stay there. Every upgrade verifies the archive against the release's checksum and its gzip integrity before it replaces the binary. An empty binary, an archive or a binary over 200 MiB, and an archive that expands past 400 MiB are refused, and the installed executable is left as it was.

The daily check and auto-upgrade are skipped for go install and development builds, when CI is set, when stderr is not a terminal, and when latere lives in a directory you cannot write, such as a PREFIX=/usr/local install; there latere upgrade tells you to run the installer again. LATERE_NO_UPDATE_CHECK=1 turns the check off entirely. Self-upgrade is not available on Windows, where a running binary is locked; download the release you want from the releases page instead.

Sign in

latere login

latere login runs the OAuth 2.0 device-code flow against auth.latere.ai: it prints a URL and a code, you approve in a browser and choose your personal account or an organization, and the CLI saves one login token to ~/.config/latere/auth-token.json. Every product command mints a short-lived token for that one product from it. docs/login-and-tokens.md explains what is stored and how each product gets its credential.

latere whoami                 # the principal the saved login names
latere org                    # the active context
latere org <org-uuid>         # switch to an organization, without signing in again
latere org --personal         # switch to your personal account
latere logout                 # revoke the session and the model keys it created, then clear the login

latere login --token <token>  # save a token issued elsewhere, for CI
latere print-token            # print the login token, for scripts that call auth

Git with Latere Code

Latere Code (code.latere.ai) hosts git repositories. latere login also configures git's credential helper for that host, so a plain clone authenticates with your saved login and no token goes in the URL:

latere login
git clone https://code.latere.ai/<owner>/<repo>.git

latere repos create <owner>/<name> creates a repository to push to, and latere repos list shows the ones you can reach (docs/repos.md). latere apps create creates an app, whose repository you push to deploy it. The app is private: latere apps visibility unlisted opens it to anyone with the link, latere apps password to anyone with a password, and latere apps share invites people to it by email. latere apps rename <new-slug> changes its address (docs/apps.md).

The helper answers for that host only; every other host keeps the helpers you already have. Fetch and clone need read access, push needs write access, and a public repository clones with no credential at all.

latere login --no-git                  # sign in without touching git config
latere git-credential setup            # configure the helper yourself
latere git-credential setup --remove   # remove it

In CI, sign the job in with a token and let the same helper answer:

latere login --token "$LATERE_TOKEN"
git clone https://code.latere.ai/<owner>/<repo>.git

Capabilities

Command	What it does	Guide
latere environments	Workloads in Latere Environments: create one from a manifest, run commands, open a shell, read logs, and move files in and out.	docs/environments.md
latere apps	Apps on the platform: create one and add its git remote, decide who can open it, give it a password and invite people by email, change its address, list your apps, show one, list its deploys, follow a build to its outcome, and delete one. A new app is private, and a git push deploys.	docs/apps.md
latere repos	Git repositories on Latere Code: create one under your handle or your organization, list your context's repositories and the ones shared with you, and look one up by name.	docs/repos.md
latere models	Call language models through the Latere API with a model key the CLI creates and keeps: list the models your key reaches, point a stock SDK at the API, and check a model with one call.	docs/models.md
latere agents	Latere Agents on this machine: run runs the agent in your directory against your files, interactively or on one prompt; provider chooses its model; review runs an adversarial review of your latest Claude Code session, whose unresolved attacks set the exit code.	docs/agents.md

docs/configuration.md lists every environment variable the CLI reads and every file it keeps.

Shell completion comes from the binary: latere completion <shell> prints the script for bash, zsh, fish, or PowerShell.

For operators

latere eval manages model-evaluation suites on eval.latere.ai: a manifest declares tasks crossed with a model and harness matrix, and latere eval apply -f suite.yaml reconciles it, with --dry-run to see the change first. latere eval suites and latere eval cells --suite <id> list what exists. It is an administration tool and does not use your login: it presents the token in EVAL_ADMIN_TOKEN or --token, which is a token the issuer minted for the eval audience, held by a platform administrator or a service account. A manifest is one YAML document of at most 256 KiB after prompt files are inlined; a file:// prompt is read relative to the manifest, and a nonempty prompt_text takes precedence over prompt. Apply never deletes a cell and does not retry: when the response does not confirm the suite, its status, and the dry-run mode, the command reports that the outcome is unknown. latere eval --help has the rest.

Compatibility

latere is released from git tags and is before 1.0. A command that moves keeps its old spelling as a hidden alias, so latere auth login still works after the session commands moved to the top level. Output formats are not frozen: if a script parses the output, pin a version with latere upgrade vX.Y.Z and latere upgrade --auto off, and prefer --json where a command offers it.

Contributing

CONTRIBUTING.md covers building, the test suites, the quality gate, and how the code is organized. The design records behind each command group are in specs/, and CHANGELOG.md says what each release changed.

License

MIT. See LICENSE.