Carbon-X vs NVIDIA Nemotron 3.5 Bolt E4B 4GB

Carbon-X

A DNA specialist cousin that another agent calls for variant-effect and sequence questions, with DNA kept on the machine. Hugging Face's Q4_K_M GGUF needs about 12 GB and Q8_0 about 19 GB, on llama.cpp b11742 or later. It isn't clinically validated, it isn't trained for tool calls or reasoning, and the card contradicts its own GGUF repository on llama.cpp support.

NVIDIA Nemotron 3.5 Bolt E4B 4GB

A small cousin for voice and device assistants, game characters and robot interfaces, trained for multi-turn tool calls, instruction hierarchy and short spoken replies, with thinking switchable per request. NVIDIA's Q4_K_M GGUF needs about 8 GB, and Ollama and LM Studio carry it. Context is 64K, half the Gemma 4 base, and NVIDIA publishes no safety results.

Carbon-X

1. Quickest start is llama-server -hf HuggingFaceBio/Carbon-X-GGUF:Q8_0 -ngl 99 -c 40960 --jinja --chat-template-kwargs '{"enable_thinking": false}' --temp 0.6 --top-p 0.95 --top-k 20 --min-p 0, on llama.cpp b11742 or later
2. With vLLM or Transformers pass trust_remote_code, and expect the tokenizer to fetch Qwen/Qwen3-4B-Base at a pinned revision on first load
3. Keep enable_thinking false and the card's sampling (temperature 0.6, top_p 0.95, top_k 20), the settings every reported result used
4. Keep DNA in files and pass sequences by name, compute positions and base changes in code and send them as context, the card says the model miscounts long sequences
5. Only A, C, G and T form 6-mers, so filter N and other IUPAC codes first or they become a single oov token
6. Strip the dna tags from answers if you need bare sequence, llama.cpp keeps them in the text
7. Cap max_tokens for next-base questions, long DNA generation is slow and degrades

NVIDIA Nemotron 3.5 Bolt E4B 4GB

1. Quickest start is ollama run nemotron-3.5-bolt:e4b, about 8 GB of files, and set num_ctx to 65536 or less, since NVIDIA supports 64K
2. With NVIDIA's GGUF use llama-server -m Nemotron-3.5-Bolt-E4B-Q4_K_M.gguf -c 65536 -ngl 999 --jinja, and add --reasoning on --reasoning-budget <tokens> to cap thinking
3. With vLLM 0.31.0 or later pass --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4 and the repository's chat_template.jinja
4. Pass enable_thinking explicitly in chat_template_kwargs, since the template defaults to off whatever the card says, and set skip_special_tokens false as the card's examples do
5. Use temperature=1.0 and top_p=0.95 in both modes, as the card says
6. Set conversational_mode true for spoken replies, which appends a brevity instruction to the system prompt
7. Answer a slow tool at once with a pending tool message, then send the result later as a user message starting TOOL RESULT, as the card's asynchronous pattern says
8. Keep persistent rules in the system prompt and send state updates as separate user or system messages in order, per the card's prompting guidelines