CHANGELOG

A changelog command containing version history and release notes for a desktop application and its related packages.

In plain words
What is it for?
Use it as a reference when checking which versions were released and what changes or fixes were recorded.
Why use it?
It provides a record of past releases, fixes, and dependency updates, but the input does not describe an interactive coding-agent capability.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/bytedance/ui-tars-desktop/changelog
Clone the repo
git clone --depth 1 https://github.com/bytedance/UI-TARS-desktop
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,418 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01418
Opus 5 $0.00000 $0.00709
Sonnet 5 $0.00000 $0.00284
Haiku 4.5 $0.00000 $0.00142

Measured yesterday against content hash 1011cb61b246, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

CHANGELOG scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/agent-infra/mcp-servers/commands/CHANGELOG.md · 292 lines

How it starts

The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.

0.4.0 2024-12-10 - add logging

1.2.29

1.2.28

1.2.26

1.2.25

1.2.24

1.2.23

Patch Changes

  • chore: rename mcpName

1.2.22

Patch Changes

  • 910105e: feat(mcp-servers): support mcp offical registry

1.2.21

Patch Changes

  • 9e1a390: fix(browser): server declares logging capability but doesn't implement method logging/setLevel

1.2.20

1.2.19

1.2.18

Patch Changes

  • feat: add cwd for default

1.2.17

1.2.16

1.2.16-beta.0

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

Patch Changes

1.2.10

Patch Changes

1.2.9

1.2.8

1.2.7

1.2.6

Patch Changes

1.2.5

1.2.5-beta.0

1.2.4

1.2.3

Patch Changes

  • Updated dependencies [9a5a933]
  • Updated dependencies [20aabee]
  • Updated dependencies
  • Updated dependencies [0eb2630]

1.2.3-beta.2

Patch Changes

1.2.3-beta.1

Patch Changes

1.2.3-beta.0

Patch Changes

1.2.2

1.2.1

1.2.0

Minor Changes

  • 7bbc77b: feat: upgrade mcp version to ~1.13

Patch Changes

1.2.0-beta.0

Minor Changes

  • feat: upgrade mcp version to ~1.13

Patch Changes

1.1.10

1.1.9

1.1.8

1.1.7

1.1.6

Patch Changes

  • a85ef50: chore: publish

1.1.6-beta.10

1.1.6-beta.9

1.1.6-beta.8

1.1.6-beta.7

1.1.6-beta.6

1.1.6-beta.5

1.1.6-beta.4

1.1.6-beta.3

1.1.6-beta.2

Patch Changes

  • chore: publish

1.1.6-beta.1

1.1.6-beta.0

Read the full file on GitHub · 292 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 292 lines · 0 tokens per session scan A 1011cb61b246

Subscribe to this mod's changes

CHANGELOG is a command published in the GitHub repository bytedance/UI-TARS-desktop (38,753 stars, last pushed 27d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,418 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.