CC GUI

The deciding trait is that it does not make you choose an engine on day one. The panel takes @file references, an image, and a conversation you can rewind when a turn goes sideways, and the diff viewer means you approve changes where you already read code. If you have been alt-tabbing to a terminal and losing your place, this is the fix.

The catch is that a wrapper inherits everything, including the rough edges of whichever tool it launched. Pick it for the JetBrains habit. Pick a terminal directly when you want fewer layers.

The structural problem is that the contract is a command line. Grok CLI, Kimi CLI, OpenCode, PI CLI, OMP CLI and the DeepSeek Harness are carried in beta, and each one ships on its own schedule with its own flags and its own output format. A rename upstream is a broken panel here, and nothing in the design pins a version or degrades gracefully when the shape changes.

What it does right is scope the promise. Claude Code and Codex are the two that are not marked beta, and those are the two the plugin was built around.

1. Publishing the data path is the rarest thing in this catalogue. Most listings describe features and leave the reader to infer where the request went; this one states the destination, states the exception, and states that the exception is shown in the interface before it takes effect. 2. Requiring an explicit dialog before reading a credential source turns an implicit capability into an observed event.

2. None of it is verified by a third party, and disclosure is not proof. It is, however, a falsifiable claim, which is more than an unfalsifiable one.

Star counts usually tell you nothing, and this one tells you something: a plugin created in November collected five thousand of them, which is demand for a shape nobody else filled. The company giving it away has other products, so this is a funnel rather than a hobby, and funnels are maintained as long as the thing they feed is worth feeding.

Moat: none in the code, real in the listing position. Likely path: a paid tier appears above the free plugin, or the engine vendors ship their own panels. Position: use it now, expect a commercial layer later.

What this costs is not what it charges. Zero per seat, installed from a marketplace my desktop policy already allows, and then every engineer authenticates a different vendor account with a different rate and a different retention policy, which is sixty procurement questions arriving one at a time.

There is no administrative console, no single sign-on and no central record of which model saw which repository. Approved with conditions: one engine chosen centrally, keys issued by us, and the permission management screen configured before rollout rather than after.

Building it from source is documented alongside the marketplace install, which tells me the author expects people to compile it, and that changes the relationship. The permission management layer is mine to configure rather than a vendor default I have to accept, and skills arrive as slash commands I can add to.

The weak spot is that model choice is not really mine here: it belongs to whichever CLI I launched, so my key lives one layer down and nothing local is reachable through this panel. Good wrapper, borrowed freedom.