Skip to content
OmniJevPublic

Latest commit

ย 

History

21 Commits

Folders and files

NameName
Last commit message
Last commit date
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Flide: Accelerating Decision Inference with Exact State Forking

English ยท ็ฎ€ไฝ“ไธญๆ–‡ ยท ๆ—ฅๆœฌ่ชž

arXiv PyPI Website Docs License Python PyTorch

News ยท Speed ยท Exact answers ยท Quick start ยท Models ยท Options

Flide is fast inference infrastructure for Jev-style decision models. With exact state forking it is up to 9.4 times faster than vLLM and SGLang, and every answer is the one the model gives the question alone. It serves the Jev /v1/systemone API.

๐Ÿ”ฅ News

Fork the state into every question: a generation engine runs every question as a sequence and computes part of the state again, multi-item scoring adds delimiters that change the answers, and Flide forks the state at its last token

With three questions, a generation engine runs three sequences and computes 4 cells of the state again, and multi-item scoring adds 3 delimiters that change the answers. Flide runs one sequence, computes nothing twice, adds no tokens, and gives each question the answer it gets when asked alone.

Speed

Speed of Flide, vLLM and SGLang on one H200 with Qwen3.5-0.8B

On one H200 with Qwen3.5-0.8B, Flide is up to 9.4 times faster than both vLLM and SGLang (QuALITY, where it is 14 times faster than vLLM), 3.6 to 4 times faster on RACE and the Decision Index, and serves 2.4 times the throughput with 64 clients. The more questions a state carries, the bigger the gap.

Exact answers

Shared work, exact answers: Flide stays within 1.1 points of a float32 reference, multi-item scoring moves 0.9 to 14.8 points; with --batch-invariant a request gets the same bits however it is batched

Flide stays within 1.1 points of a float32 reference, the closest of any engine, and flips at most 2.3% of decisions at 0.5. Multi-item scoring moves answers by up to 14.8 points and flips up to 28.9%. With --batch-invariant, a request gets the same bits however it is batched.

Quick start

See the docs for every model, the API and all options.

1. Install

uv venv -p 3.12 && source .venv/bin/activate
uv pip install flide torchvision

2. Start a server

Any chat model on Qwen3.5 or Gemma 4 serves as it is and answers through its next token.

flide serve --model Qwen/Qwen3.5-4B

OneJev models read their answers their own way, and Flide serves them as they are too.

flide serve --model OmniJev/OneJev1.6-0.8B

An Open-Jev release is an adapter on a Qwen3.5 base. Merge it into a checkpoint once, then serve that.

python -m flide_open_jev.prepare ZefanCai/Open-Jev-2B open-jev-2b
flide serve --model open-jev-2b

flide serve listens on all interfaces at port 8000; pass --host 127.0.0.1 to keep it local.

3. Send a request

curl http://localhost:8000/v1/systemone -H "Content-Type: application/json" -d '{
  "state": "Order #1182 arrived with a cracked screen. The customer asks for a refund and attached two photos.",
  "questions": {
    "action": {"type": "choice", "instructions": "What should support do next?",
               "criteria": {"refund": "refund the order", "replace": "send a replacement", "escalate": "ask a human"}},
    "urgent": {"type": "noul", "instructions": "Does this need a reply within the hour?"}
  }
}'

OneJev models also read images. Put <image:1> where the photo belongs in the state and send the photo in media.

IMG=$(base64 -w0 photo.jpg)
curl http://localhost:8000/v1/systemone -H "Content-Type: application/json" -d @- <<EOF
{
  "state": {"ticket": "Order #1182 arrived with a cracked screen. The customer asks for a refund.", "photo": "<image:1>"},
  "media": [{"type": "image", "data": "data:image/jpeg;base64,$IMG"}],
  "questions": {
    "cracked": {"type": "noul", "instructions": "The photo shows a cracked screen"},
    "action": {"type": "choice", "instructions": "What should support do next?",
               "criteria": {"refund": "refund the order", "replace": "send a replacement", "escalate": "ask a human"}}
  }
}
EOF

Every answer carries the probability of each option, ready for a threshold.

Models

The last three columns say how much faster Flide answers one request than the engine its release ships, as the median latency over the requests of each workload on one H200, where DI is the Decision Index. The chat models run against the faster of vLLM and SGLang, and OneJev against qev, the engine it used before Flide. KnowLine 35B runs with --quantize fp8, as its release serves it in FP8. A value marked ~ is the average over the sizes tested.

Model Inputs DI MultiRC QuALITY
AJev text 3.7ร— 9.3ร— 2.6ร—
Bespoke-Nimble text 2.6ร— 2.1ร— 1.6ร—
cerno text ~4.1ร— ~8.6ร— 1.1ร—
Darwin text 1.6ร— 7.0ร— 1.2ร—
Drex text ~3.4ร— ~7.9ร— ~1.7ร—
Gemma 4 text, images ~1.3ร— ~1.7ร— ~1.0ร—
Intern-Decision text, images 4.4ร— 1.1ร— 1.5ร—
JADE text 2.0ร— 9.2ร— 1.7ร—
Jeffan text 3.1ร— 2.6ร— 1.9ร—
JevAny text, images 1.5ร— 5.8ร— 1.2ร—
jiwo text ~1.9ร— ~5.9ร— 1.8ร—
Kev text ~7.9ร— ~1.5ร— ~1.7ร—
KnowLine text ~1.4ร— ~5.6ร— ~1.5ร—
Linne text 2.3ร— 8.6ร— 1.2ร—
Lumma text, images 1.7ร— 7.1ร— 1.2ร—
Lychee text 1.4ร— 1.5ร— 1.4ร—
mammoth text, images ~4.3ร— ~2.8ร— ~1.8ร—
mogan text 1.6ร— 8.5ร— 1.8ร—
OneJev text, images, video ~6.8ร— 7.3ร— 4.7ร—
Open-Jev text 4.2ร— 5.0ร— ~1.5ร—
pplx-decider text, images 3.1ร— 1.4ร— 1.2ร—
Quyet text ~3.9ร— ~7.1ร— ~1.6ร—
Qwen3.5 text, images ~2.1ร— ~4.8ร— ~1.3ร—
Senova text 3.1ร— 28.1ร— 1.2ร—
Sieve text 3.0ร— 14.3ร— 2.6ร—
StartLux text 2.6ร— 1.1ร— 1.2ร—
SynACK Decide text 3.3ร— 11.9ร— 3.0ร—
torchcast text, images 1.6ร— 8.4ร— 1.4ร—
Wald text 1.6ร— 12.7ร— 1.5ร—
Xor text, images, video 2.5ร— 6.2ร— 2.8ร—

Options

Option What it does
--session-cache-gb 40 keeps the states of earlier requests, so an agent's next step reads only what is new
--batch-invariant the same bits for a request whatever it is batched with, at some cost in speed
--quantize fp8 Qwen3.5 in FP8 on Ada, Hopper and Blackwell GPUs
--frontends 2 HTTP, rendering and tokenizing in two processes of their own, for many clients

License

Apache-2.0. flide/kernels/gdn.py holds a kernel derived from two kernels of flash-linear-attention (MIT); THIRD_PARTY_NOTICES lists it with the other code Flide builds on.

Citation

If you use Flide in your research, please cite our paper.

@article{li2026flide,
  title   = {Flide: Accelerating Decision Inference with Exact State Forking},
  author  = {Li, Bobo and Song, Jiajia and Fei, Hao and Hsu, Wynne and Lee, Mong Li},
  journal = {arXiv preprint arXiv:2610.42148},
  year    = {2026}
}