ytr

Install

brew install slavkluev/tap/ytr

This is third-party code. Review the repository files before installing.

What it does

ytr works with Yandex Tracker from the command line. It creates, searches, views and updates issues, moves them through statuses and shows their changelog. Comments, links, worklogs and checklists are subcommands, and bulk move, update and transition run asynchronously with polling. It covers statuses, priorities, resolutions and issue types, queue field discovery, components and users. Output is predictable: JSON with field selection, jq filtering and meaningful exit codes, and the bundled SKILL.md teaches the agent every command.

Who it is for. For developers and managers who track work in Yandex Tracker and want an agent to handle it.

Example request

Find my open issues in queue PROJ, move PROJ-123 to In Progress and log two hours on it

Limitations

Requires an OAuth token, organization ID and organization type, 360 or cloud. Delete and bulk commands apply immediately and there is no read-only mode. Unofficial project.

How to disable. Run ytr auth logout, remove the binary with brew uninstall ytr and delete the ytr skill folder from the agent's skills directory.

Security check

• Creates, edits and deletes issues, comments and worklogs in a live Tracker
• Bulk operations affect many issues at once
• Stores an OAuth token in a config file

README in short

The README briefly lists CLI features and three install options: Homebrew, go install and release binaries. The quick start shows auth via environment variables and typical commands for issues, comments, worklogs, bulk operations and reference data. It explains auth precedence and links to SKILL.md for agents. MIT licensed.

SKILL.md

---
name: ytr
description: >-
  Yandex Tracker CLI for managing issues, comments, worklogs, and more.
  Use when the user needs to interact with Yandex Tracker: search/filter
  issues, create or update tasks, manage worklogs, bulk operations, etc.
license: MIT
compatibility: Requires ytr binary in PATH
metadata:
  author: slavkluev
  version: "4.0"
---

# ytr -- Yandex Tracker CLI

## Auth

```bash
# Environment variables (recommended for agents)
export YTR_TOKEN="your-oauth-token"
export YTR_ORG_ID="your-org-id"
export YTR_ORG_TYPE="360"   # or "cloud"

# Or interactive login (humans)
ytr auth login

# Or explicit login flags
ytr auth login --token TOKEN --org-id ORG --org-type 360

# Verify authentication
ytr auth status
```

Authentication precedence:

1. Flags: `--token`, `--org-id`, `--org-type`
2. Environment variables: `YTR_TOKEN`, `YTR_ORG_ID`, `YTR_ORG_TYPE`
3. Config file saved by `ytr auth login`

Notes:

- For regular commands, flag-based and env-based auth require all three values together.
- `ytr auth login` is the exception: it can detect the organization type when `--org-type` is omitted.
- Config is stored in `~/.config/ytr/config.yaml`.

Related