Audited GhostCLI: the gateway does not behave like the Anthropic API
I ran a technical audit of GhostCLI on October 12, 2026: about 200 API responses across 10 test batteries. Here is what I found, backed by the raw files:
Invented tool results: on a stock-price test, the models never called the tool but still answered with prices for AAPL and MSFT. For a coding agent, this is dangerous.
Advertised 256k context: at 220k tokens, 380,935 characters were silently cut from the middle of my prompt.
Fake token counts: input_tokens follows a simple length ÷ 4 formula, not a real tokenizer.
Prefabricated replies: “hello” returns a fixed answer in 0.4 s with 0 tokens, even for a model whose backend was down.
Ignored parameters: max_tokens, stop_sequences, forced tool use and thinking are ignored, and streaming arrives in a single block.
Hidden instructions: requests sent with no system prompt receive injected instructions, and questions in French get answers in Portuguese.
On the models: the “Fable 5.1” and “Opus 5.5” endpoints use formatting typical of Gemini, not Claude. This is a strong indication, not proof. When I raised it, support did not name the upstream provider and only offered a screenshot.
Whatever the underlying model, the service does not deliver what it sells. I would not use it for professional work or send any confidential code through it.








