ytr CLI
A Yandex Tracker CLI built for LLM agents: issues, comments, worklogs, checklists and bulk operations, with an agent skill
- 11 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- 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
Install
- Works in
- Services
Manual install
brew install slavkluev/tap/ytrFor macOS. On other systems use go install or a release binary.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- 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
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.
Good fit when
- You want the agent to create an issue and log time after work
- You need to bulk transition or move issues between queues
- You need issues as JSON for a script or report
Not a fit when
- You need an MCP server and the agent may not run shell commands
- The agent must not change anything in Tracker
Example request
Find my open issues in queue PROJ, move PROJ-123 to In Progress and log two hours on itLimitations
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.
FAQ
Which organization type do I set?
360 for Yandex 360 organizations and cloud for Yandex Cloud ones. ytr auth login can detect it.
Where are credentials stored?
After ytr auth login, in ~/.config/ytr/config.yaml. Flags and environment variables override the file.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsYandex Tracker CLI
tracker
The tracker command-line tool for Yandex Tracker with JSON output and a ready SKILL.md workflow for agents
Yandex Tracker skill on the official Python client
Yandex Tracker Skill
A skill for Claude Code, Codex and Gemini CLI on top of the official yandex_tracker_client package: search, issues, statuses, sprints, bulk edits
A Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
A CLI and skill for Yandex Tracker and Wiki: short output readable by people and agents alike, instead of raw MCP payloads costing thousands of tokens
A Yandex 360 toolkit: Tracker, Wiki and Forms via a CLI, an MCP server, a Python SDK and a Claude Code plugin
A Claude Code plugin for Yandex Tracker and Wiki backed by the yandex-cli binary: 16 commands with output tuned for agent reading
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.
README badge
Original 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`.