Expand description
The command shell.
The verb is the risk class. Read verbs (get, find, list, status) can
never write, and there is no generic pass-through that would let one smuggle a
change past that rule. That is what makes a permission allowlist like
ytcli issue get:* meaningful for an agent host (docs/adr/0001-security-model.md).
Modules§
- attachment
- Attachment commands.
- auth
- Account and profile commands.
- board
- Board commands. Read-only: a board is a view of work, and moving work about
from a command line is what
issue updateis for. - cheatsheet
- One-shot compact reference.
- dict
- The values a write is allowed to take.
- entity
- Shared implementation for the entity commands.
- field
- Organisation-wide field and template listings.
- goal
- Goal commands.
- guidance
- Where to get credentials.
- help
- Long help text.
- issue
- Issue commands.
- portfolio
- Portfolio commands. A portfolio groups projects and other portfolios; the entity endpoints treat it as one more type, so only the word differs.
- project
- Project commands. Projects group issues across queues; portfolios sit above them and are out of scope for v1.
- queue
- Queue commands. Reads, and one write: creating a queue.
- sprint
- Sprints across the organisation.
- user
- People.
- wizard
- The interactive half of
auth login. - worklog
- Worklogs across issues.
- write
- The gate every writing command passes through.
Structs§
- Cli
- Token-efficient Yandex Tracker CLI for humans and AI agents.
- Global
Args - Flags every command accepts.
- Session
- Everything a command implementation needs, assembled once.
Enums§
- Command
- Top-level command groups, one per entity.
Functions§
- emit
- Write rendered output to stdout.
- not_
implemented - Placeholder for a command that is declared but not built yet.
- render_
context - Build the rendering context from flags, profile defaults and the terminal.
- report
- Print an error to stderr and hand back the exit code to return.