Trylle Documentation

Use the try command for repositories, pull requests, issues, CI, AI helpers, and agent workflows.

The Trylle CLI is the terminal interface to the Trylle platform. Use try for platform resources and git or jj for local version-control operations.

npm install -g @trylle/trylle-cli
try auth login
try whoami

Two executable names

The npm and PyPI packages install both try and trylle-cli. This documentation uses the shorter try name. A Cargo install provides only trylle-cli.

Choose a guide

Install the CLI

Choose npm, uv, or Cargo and keep the binary current.

Authenticate

Create a CLI Key, save it safely, and verify the active identity.

Everyday workflows

Work with repositories, pull requests, issues, stacks, CI, and settings.

AI commands

Configure a direct provider or run a local coding agent.

Diff reviews

Review Git, jj, and Trylle pull request diffs in the terminal.

Agent skill

Teach Codex, Claude, OpenCode, or Cursor how to operate Trylle safely.

Understand the execution boundary

The CLI combines several kinds of commands. Their credentials and side effects are deliberately separate.

Surface	Examples	Where it runs	Credential
Trylle platform	`repo`, `pr`, `issue`, `ci`	Public Trylle API	Trylle CLI Key or bot token
Local VCS	`clone`, parts of `stack`, local `diff`	System Git or local jj repository	Git transport credential when needed
Direct AI	`ask`, `explain`, `draft`	Configured AI provider	Provider API key, or none for local Ollama
Local agent	`agent`	Installed Codex, Claude, or OpenCode CLI	The local agent's own authentication
Diff TUI	`diff`	Local terminal; Trylle API for PR input	None for local diffs; Trylle credential for PRs

Direct AI calls are bring-your-own-key requests to the selected provider. They do not use a Trylle CLI Key and are not charged against Trylle-hosted AI usage.

Resolve repository context

Inside a checkout, commands that accept -R/--repo infer OWNER/NAME from a recognized Git remote. Inspect what the CLI resolved before a write:

try repo context

Outside a checkout, or when multiple remotes make the target ambiguous, pass the repository explicitly:

try pr list -R OWNER/NAME
try issue view 42 -R OWNER/NAME

Commands such as try repo view, try clone, and try repo clone accept OWNER/NAME positionally instead.

Human and structured output

Most platform commands default to formatted terminal output:

try status

Scripts and agents can request structured output where the leaf command supports it. try explain, try draft, and try diff also offer structured output. try ask and try agent do not because they are interactive or streaming workflows.

A reliable operating pattern

Inspect authentication with try auth status and try whoami.
Resolve the target with try repo context or pass -R OWNER/NAME.
Run try <group> <command> --help before a consequential write.
Execute the narrow command and inspect its result.
Re-read the changed resource, then use try browse ... --no-open to return its URL.

The command reference lists every top-level group and the caveats that matter in automation.

Trylle CLI