Compatibility and known limits
The precise scope of the current review build and remaining acceptance work.
On this page
Conflux native harness preview
Conflux now has its own Rust coding harness: project creation, file tools, per-command approval, Plan/Build modes, effort controls and encrypted opt-in resume. Terminal and Projects console use one core. Linux and complete-response Chat Completions are the current boundary; browser tools, MCP, desktop packaging and long live coding acceptance are not included.
What is ready
Version 0.3.0 includes ordered failover, multiple encrypted keys, a quota ledger, accounts, receipts, route inspection, forecasts, reference savings, degradation controls and Harness Profiles. JSON/SSE Chat Completions and practical Responses/Messages translators are implemented.
The current regression suite, production build and browser checks are recorded in the review report. Genuine installed Codex and Claude Code ran coding tasks. Demo Groq, OpenRouter and LLM7 generation passed. Docker packaging and isolated browser checks passed.
Protocol boundary
- Committed mid-stream output cannot be safely replayed.
- Hosted tools, encrypted reasoning and remote compaction are unsupported.
- Provider capability differences can exclude a model from a route.
- Conversation continuity does not preserve hidden reasoning.
- LLM7 current tool declarations and one live tool call are verified; full coding-task fidelity still needs acceptance.
Remaining acceptance and implementation
- A single coding task naturally exhausting all three free accounts has not been demonstrated.
- Older Gemini model IDs returned 404; the tested Gemini 3.5 Flash-Lite route passed. ZenMux 403 and restricted or missing account access remain unresolved.
- PostgreSQL and embeddings are not implemented.
- Measured 20–40% tokenizer savings remain unverified; byte reduction is measured.
- Paid API connections are opt-in and must be explicitly enabled at both provider and pool level. No public registry package or image is claimed.