Use try as the primary interface for Trylle platform operations. Use git for local version-control work, but do not substitute GitHub-specific tooling for Trylle resources.
Core workflow
- Confirm the CLI is available with
try --version. If it is missing, install it withbrew install trylle/trylle-cli/trywhen the user authorizes installation. - Check authentication with
try auth status --json. Never runtry auth token --showor print bot tokens unless the user explicitly requests the secret material and the environment can handle it safely. - Resolve context with
try repo context --jsoninside a checkout. Outside a checkout, pass-R OWNER/NAMEto commands that support it or passOWNER/NAMEpositionally totry repo view,clone, and similar repository commands. - Inspect the current state with a read command. Prefer
--jsonfor agent reasoning and automation. - Before a write, run
try <group> <command> --help, validate identifiers and the intended scope, then execute only the requested mutation. - Re-read the affected resource. Return a web URL with
try browse repo|pr|issuewhen it helps the user continue.
Route the task
- Repositories and daily context: use
try statusandtry repo. - Pull requests and reviews: use
try pr. - Issue triage: use
try issue. - Dependent branches and pull requests: use
try stack. - CI status and logs: use
try ci. - Repository or organization configuration: use
try actionsortry org. - Accounts and operations: use
try profile,try ssh-key,try automation, ortry bot. - Resource links and uncovered public endpoints: use
try browseortry api. - Local AI and review helpers: use
try ai,try explain,try draft, ortry diff.
Read references/command-catalog.md for the complete command map and exact argument patterns. Read references/workflows.md when creating or publishing a repository, opening or reviewing a pull request, triaging issues, handling stacks, diagnosing CI, or changing secrets and settings.
Safety and output rules
- Treat repository deletion, PR merging or closing, issue closing, label replacement, key deletion, automation toggles, token minting, and secret changes as consequential operations. Show the exact target and inspect current state first.
- Keep credentials out of command literals, logs, files, commit messages, and chat. Use pre-existing environment variables for secret values and unset temporary variables afterward.
- Prefer
--body-fileto complex inline PR, review, issue, or comment bodies. - Use
--jsonwhenever available. Human output is intended for terminal reading and may change formatting. - Do not guess unsupported flags. The installed CLI's
--helpoutput is the source of truth. - Do not use
try apiwhen a first-class command exists. For raw calls, use only the public/v1API path needed for the task.
Current CLI gotchas
- Repository inference depends on a recognizable git remote. Pass
-R OWNER/NAMEexplicitly when inference is ambiguous. try pr current --jsonexits nonzero when the current branch has no open PR instead of returning JSONnull. Usetry repo context --jsonwhen absence is an expected state.try pr reviewrequires exactly one of--approve,--request-changes, or--comment.try issue label --setreplaces the complete label set;--addand--removepreserve unrelated labels.try stack submitpushes the current branch tooriginbefore creating the pull request.- On CLI version 1.0.0,
try ci logs --followandtry ci watchreturn the current log payload rather than continuously polling. Re-run a read command when fresh state is required. - List filters such as PR author and issue labels may be applied to the returned page. Increase the page size or paginate before concluding that no matching item exists.