occamy-1.0

Available Checkpoints

Browse the Occamy 1.0 collection or use the interactive checkpoint explorer to select a format and copy deployment commands.

Sizes are decimal GB of weight files, not peak RAM/VRAM. GGUF image input requires the separate 0.90 GB F16 vision projector. KV cache, context length, concurrency and runtime buffers need additional memory. The MLX collection groups the Apple Silicon candidates.

BF16, FP8 and NVFP4 each passed a nine-case vLLM compatibility check on a single H200, covering text, code, JSON, tool calls and follow-up, and images. NVFP4 used Marlin W4A16. These checks used ordinary decoding; the separate MTP head remains experimental. Format-specific sample checks do not establish equal benchmark quality or a general speed ranking.

1. Model Introduction

Occamy-1.0 is a compact agentic model purpose-built for real-world co-work: long-horizon, stateful tasks that require coordinated use of search, code, tools, files, structured APIs, and productivity software. Starting from the post-trained Qwen3.6-35B-A3B checkpoint, Occamy concentrates further training on reliable execution, persistent state tracking, recovery, and follow-through rather than relearning general capabilities from scratch.

Key Features

• Co-work specialization: Designed for sustained execution across multi-step professional workflows, not isolated question answering.
• Compact inference footprint: A 35B-total, 3B-active Mixture-of-Experts model that keeps long-running agent workloads practical.
• Long-horizon continuity: Designed to keep work coherent across tool calls, delegated runs, and history rewrites such as context compaction.
• Broad agentic capability: Co-work gains are accompanied by strong tool calling, terminal coding, and instruction following.
• Execution-grounded training: Supervised fine-tuning spans general agentic work, long-horizon interaction, software engineering, and tool-call grounding.
• Open training stack: The multi-harness reinforcement-learning infrastructure used to train Occamy is released as Dressage.

[!NOTE] Occamy is optimized for common co-work workloads, not as a replacement for frontier models on every task. Retrieval-heavy and simulated-user tasks still have headroom, and native browser or desktop visual interaction is not part of the current co-work training interface.

2. Model Summary

Architecture fields follow the starting checkpoint's published model card. Occamy post-trains the language backbone without changing the architecture; the vision encoder and projector are frozen during SFT. The released checkpoint configuration remains the source of truth for serving limits.

3. Evaluation Results

Full Evaluation

Within each size group, bold denotes the best result and underlining denotes the second-best result. * Official model-card or Artificial Analysis result. † Reproduced on the public task release.

Cost-Performance

Across Claw-Eval, WildClawBench, AutomationBench, and GDPval, Occamy-1.0 lies near the low-cost knee of the empirical Pareto frontier. Relative to its Qwen3.6-35B-A3B starting checkpoint, it delivers a large aggregate capability gain with only a modest change in measured per-task inference cost. Benchmark scores are equally weighted after per-benchmark min-max normalization, and costs are macro-averaged per task under the frozen pricing protocol used in the report.

4. Training Recipe

Occamy uses staged specialization and consolidation:

Qwen3.6-35B-A3B
  ├─ Marathon Expert: SFT → HDPO ┐
  └─ Sprint Expert: SFT          ├─ Uniform merge → SAO → Occamy-1.0

The Marathon Expert learns sustained execution and accuracy-conditioned efficiency, while the Sprint Expert preserves broader agentic capability. A uniform parameter-space merge combines both experts into one checkpoint with no inference-time routing or ensembling, and a final Single-Rollout Asynchronous Optimization (SAO) stage refines the merged policy on a broad co-work mixture.

The deduplicated SFT union across both experts is:

Training tasks are grounded in executable environments with observable state transitions and task-level grading. The open-source Dressage stack provides multi-harness execution, token-exact trajectory capture, sandbox integration, and multi-segment conversion for reinforcement learning.

5. Deployment

Occamy-1.0 keeps the Qwen3.6-35B-A3B architecture, so the upstream deployment recipe is the reference serving path. The examples below mirror that recipe with eight-way tensor parallelism and its full context length; adjust both to fit your hardware and confirm them against the released Occamy checkpoint configuration.

SGLang

The upstream model card recommends SGLang 0.5.10 or newer for the Qwen3.6 architecture.

python -m sglang.launch_server \
  --model-path Accio-Lab/occamy-1.0 \
  --port 8000 \
  --tp-size 8 \
  --mem-fraction-static 0.8 \
  --context-length 262144 \
  --reasoning-parser qwen3 \
  --tool-call-parser qwen3_coder

vLLM

The upstream model card recommends vLLM 0.19.0 or newer for the Qwen3.6 architecture.

vllm serve Accio-Lab/occamy-1.0 \
  --port 8000 \
  --tensor-parallel-size 8 \
  --max-model-len 262144 \
  --reasoning-parser qwen3 \
  --enable-auto-tool-choice \
  --tool-call-parser qwen3_coder

Both commands expose an OpenAI-compatible endpoint at http://localhost:8000/v1.

6. Model Usage

from openai import OpenAI

client = OpenAI(base_url="http://localhost:8000/v1", api_key="EMPTY")

response = client.chat.completions.create(
    model="Accio-Lab/occamy-1.0",
    messages=[
        {
            "role": "user",
            "content": "Inspect this repository, fix the failing test, and explain the change.",
        }
    ],
    max_tokens=32768,
    temperature=1.0,
    top_p=0.95,
    presence_penalty=1.5,
    extra_body={
        "top_k": 20,
        "chat_template_kwargs": {
            "enable_thinking": True,
            "preserve_thinking": True,
        },
    },
)

print(response.choices[0].message.content)

For multi-turn agent runs, retain the complete assistant message returned by the server, including reasoning content and tool calls, then append tool results using the standard OpenAI chat-completions schema. This preserves the execution context that Occamy relies on across long workflows.

Agent Frameworks

Occamy was trained and evaluated across multiple harnesses, including OpenClaw, Hermes Agent, and Accio Work. It can be integrated with other tool-using agent frameworks through the same OpenAI-compatible API.

7. License

This repository is released under the Apache License 2.0. See the Hugging Face model card for the terms that apply to the model weights.

8. Contact Us

For questions or feedback, please open an issue.