Tencent CodeBuddy

The trait worth having is the terminal form. It behaves like a Unix command, so it pipes, it takes input from other tools and it fits into scripts you already wrote, which is a much better relationship with an agent than a chat panel gives you. That one property makes it useful even to people who never open the plugin.

The rest is a competent assistant rather than a distinctive one. Pick it if the cloud choice is already made. Pick Trae if you want one product instead of three.

The confusion is structural. A plugin, a standalone editor and a command-line agent all carry the brand, and the row's own notes distinguish them: shell execution belongs to the terminal form while the plugin is assistant-shaped. A team comparing notes about what it does is therefore comparing three things, and documentation that treats them as one product makes that worse.

What it does right is Rules management. Team conventions live as a managed artefact rather than as a prompt each developer retypes.

1. Naming the model families is a real transparency improvement over the undisclosed backbones that dominate this board, because a reader can reason about capability and about where inference happens. 2. What is not published is selection: nothing states which model handles which task, so the behaviour a user observes cannot be attributed.

2. Unit test generation is offered as a feature without a described execution step, so whether generated tests are run before being proposed is unstated. No benchmark accompanies any of it.

Distribution costs the vendor nothing and every install increases the odds of a cloud account. That structure makes the product durable regardless of whether this line earns anything on its own, because it is defending a much larger infrastructure business, and infrastructure businesses fund loss-leaders for a long time.

Pricing power belongs to the platform rather than to the assistant, which caps how much this can ever charge directly. Likely path: deeper bundling into the cloud's developer suite. Position: safe to use, and never the reason you choose a cloud.

The free plugin means a pilot costs nothing, which is the only easy part. Beyond that I have no comparable number: paid tiers are quoted in a currency my finance team does not hold and metered in units whose consumption rate is not published, so a sixty-developer forecast is guesswork dressed as a plan.

Nothing runs unattended, so it produces no records and touches no pipeline. Identity and retention terms are documented in a language and a jurisdiction my counsel will want time with. Not yet.

The protocol support is the only reason this is not a two. Speaking both halves means my servers are reachable from it and it is reachable from my clients, so a closed product still participates in a toolchain I control, and that is worth more than most configuration panels.

Everything upstream is sealed. The licence is proprietary, my provider key has nowhere to go, and inference happens on somebody else's machines by design. No fork, no offline mode. Grudging respect for shipping both directions of the protocol; nothing else here is mine.