Command Code

The deciding trait is the taste profile. It builds a picture of how you write code and lets you push and pull that picture across a team, which means the correction you made in January is not one you make again in March. Every other agent asks you to encode the same preferences in a markdown file and hope it gets read.

The cost is that the profile is another thing that can be wrong about you, quietly, for weeks. Pick it if you want the tool to converge on your habits. Pick Aider if you would rather write the rules down and know exactly what they say.

Combine two documented features and you get the failure mode. Git operations are built in, up to commits and pull requests, and the flag that skips confirmation is shipped and named. A run that goes wrong therefore ends with unreviewed work on a branch and a request for someone to merge it, which is worse than a mess on disk because it looks finished.

What it does right is the opposite feature. Plan mode investigates without editing anything, which is the correct separation and one most terminal agents leave to a system prompt.

1. A superlative over more than sixty models is a comparative claim and therefore requires a comparison: which task set, which scaffold, how many attempts. None is offered, so the statement is marketing rather than a finding. 2. Tool-call repair is the more interesting design choice, since it treats malformed calls as a recoverable class rather than a failed turn.

2. That repair mechanism is exactly what a weaker model needs, which makes the positioning coherent even while the claim behind it is unevidenced. The engineering and the sentence are not the same thing.

A price ladder running from one dollar to two hundred is not segmentation, it is an experiment still in progress, and the tiers that carry credits are reselling inference at a margin somebody is guessing at. Shipping since August 2025 shows persistence; it does not show an entity you could sign a contract with.

Moat: none visible, since the differentiator is a profile file and a model roster anyone can copy. Likely path: acquisition of the founders by a model vendor wanting a terminal surface, or a quiet end. Position: pay monthly, never annually.

Twelve hundred dollars a month is not the problem; the tiers above it and the credits underneath them are, because a heavy quarter moves engineers up the ladder without anyone deciding to. That is an unbudgeted meter and I have seen where it ends.

The genuinely useful part is that it runs headless, so it can sit in delivery tooling and be measured rather than only felt. Against that: no identity integration, no provisioning, nothing to hand a security questionnaire, and a vendor I cannot describe in a supplier record. Not yet.

The extension surface is genuinely good. MCP servers attach, skills are editable, slash commands and plugins are mine to write, and there is a provider plan so my own account pays for the tokens rather than a credit balance somebody else meters. On paper that is most of what I ask for.

Then I look for the source and there is none, and the package metadata says UNLICENSED, which is not a licence but its absence. Every prompt, every tool definition and every default stays the vendor's. No local weights either. I can decorate this thing; I cannot own it.