JoyCode

The deciding trait is that the team owns the configuration. Agents, skills, slash commands and rules belong to the group rather than to whoever set them up, so the conventions your staff engineers care about are enforced by default instead of pasted into a document nobody reads. Anyone who has watched a house style dissolve across a team will see the appeal immediately.

The cost is that this only helps if the whole team is inside it. Pick it when you can move everyone. Pick a personal tool when you cannot.

Two things happen at setup that nobody sees in a demo. The first is an access grant: the product joins your repository as an account, which is a permission conversation with whoever owns that organisation and a fact your security review will want in writing. The second is the wait, up to an hour and a half of indexing before the first useful answer.

What it does right is state the duration. A published range is a range a team can plan around, and most vendors leave the indexing cost entirely undescribed.

1. Conflicting instructions are the unglamorous failure of every configurable agent, and almost no vendor publishes the resolution order. Declaring it turns a debugging session into a lookup, because a user who sees unexpected behaviour can reason about which layer produced it.

2. Placing the organisation above the individual is the defensible default for a shared tool, though it also means a developer cannot locally override a rule that is wrong. 3. The context engine is described as deep parsing and understanding, which is a claim with no method attached.

Subsidised inference with an expiry date is a land grab, and a retail parent with this balance sheet can fund one for as long as it chooses to. The question a buyer should ask is not whether the company survives, because it will, but what the meter reads on the day the promotional window closes and the workflow is already embedded.

Moat: switching cost, built deliberately through team assets that do not travel. Likely acquirer: none. Position: use the free window, and do not let anything you cannot rebuild in a week end up inside it.

The credit allowance is what makes this budgetable: a fixed rate per seat with a stated allocation means finance sees a number and my architects see a ceiling. What sits above the line is the problem, because directory integration and on-premises models are only in the bespoke tier, which means a negotiation rather than a purchase order.

There is no Linux client, which removes part of my estate outright, and nothing runs unattended. Not yet: single sign-on and a retention policy have to be in the standard contract first.

Publishing the actual JSON, with both launchers and the per-platform differences spelled out, is the difference between a configuration surface and a screenshot. It means my own servers run here the way they run everywhere else, and adding one does not require asking anybody. Custom models can be pointed at from the client, so the bundled list is not the whole world.

What I cannot do is see any of it, run weights on my own machine, or fork the thing when a decision goes badly. Nice config file, closed box.