Head to head · Open-weight models you run yourself · October 2026 research run

Hy-Memory-30B-A3B vs North Mini Code 1.0

Hy-Memory-30B-A3B and North Mini Code 1.0 score within a point of each other on agent readiness, 61 (C) and 61 (C). North Mini Code 1.0 leads on agent interface. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons

Which one, for what

Hy-Memory-30B-A3B C

Best for Agents with an external memory framework that want a local model for the write path on a 24 GB card

Ahead on

  • Documentation and upkeep, 68 against 36

Watch for

Not a general assistant or a tool caller

North Mini Code 1.0 C

Best for Developers who want a coding agent on their own GPU with a permissive licence

Ahead on

  • Agent interface, 85 against 65

Watch for

No limitations, safety results, languages or data description on the card

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep Hy-Memory-30B-A3B +32

Hy-Memory-30B-A3B 68

Model card 8, Intended use (the write path of Mem0, MemOS and Hy-Memory), parameters (30B, about 3B active) and languages (English and Chinese, in the metadata) are there. Training data 5, A general description of the two training stages inside the harnesses, with no datasets, sizes or cut-off. Last change 20, the last commit, on 16 October 2026, added the licence and the card, 25 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (16 to 30 October 2026), 3 have a reply from a tencent organisation member. Version policy 5, A first release, with nothing replaced. File health 10, Config, tokenizer and template agree on the architecture, the context and the thinking levels. 8 + 5 + 20 + 20 + 5 + 10 = 68.

North Mini Code 1.0 36

Model card 11, Intended use, the architecture, the parameters and the context are on the card. Training data 0, the card gives the training method and nothing about the data. Last change 10, the main repository last changed on 15 June 2026 (outdated chat templates removed), 148 days before this check, and the draft model's repository on 29 July, 104 days. Responsiveness 0, none of the 11 most recent discussions that aren't pull requests (7 June to 6 November 2026) has a reply from a CohereLabs member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, A first release, with each build in its own repository. File health 10, Config, template and card agree on the architecture, and the June commit that removed broken templates says so. 11 + 0 + 10 + 0 + 5 + 10 = 36.

Agent interface North Mini Code 1.0 +20

Hy-Memory-30B-A3B 65

Chat template 20, chat_template.jinja in the repository. Tool-calling format 10, the card doesn't mention tools. Trained tool calling 10, the template can render tool calls, but the card presents the model as a memory writer that returns memories as text or JSON and says nothing of calling tools. Structured output 5, the card's quickstart asks for a JSON object with a memories list in the system prompt and shows nothing else, no response_format and no schema, so JSON output is shown by example without a documented way to constrain it. Reasoning control 10, the card passes reasoning_effort as no_think per request through chat_template_kwargs, and the template takes high, low or no_think. Context 10, 262,144 tokens native (max_position_embeddings in config.json). 20 + 10 + 10 + 5 + 10 + 10 = 65.

North Mini Code 1.0 85

Chat template 20, chat_template.jinja in the repository (12,397 characters). Tool-calling format 25, the card documents how tools are declared (JSON schema through the chat template), how the call and its thinking go back into the history and how results are appended, and names the cohere_command4 tool-call parser for vLLM, which released vLLM has. Trained tool calling 20, the card says the model was specifically trained with tool-use capabilities for agentic coding, with reinforcement learning on verifiable tasks, and the template renders every call in a turn with thinking between them. Structured output 0, JSON schema is for describing tools. Reasoning control 10, the template has a reasoning_effort setting, and the card names the cohere_command4 reasoning parser, which returns thinking apart from the answer. Context 10, 256K tokens per the card, with 64K of output, and 500,000 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Score by category

CategoryWeight this runHy-Memory-30B-A3BNorth Mini Code 1.0Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258585even
Risk20%206060even
Agent interface10%106585North Mini Code 1.0 +20
Documentation and upkeep10%106836Hy-Memory-30B-A3B +32
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactHy-Memory-30B-A3BNorth Mini Code 1.0
KindOpen-weight modelOpen-weight model
VendorTencent (Hy team)Cohere
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-162026-07-29
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked

Verdicts

Hy-Memory-30B-A3B

A specialist that writes an agent's long-term memory, built to slot into Mem0, MemOS or Tencent's own framework in place of a general model. It fits a 24 GB card from Tencent's own GGUF, under plain Apache 2.0, and Tencent answers on the repository. Its results are Tencent's own and nobody has rerun them.

North Mini Code 1.0

A coding agent model that fits one 24 GB GPU at 4 bits, trained for tool use, with a 256K context, Apache 2.0 and four released runtimes. It's a research release and reads like one: nothing on limitations, safety or data, the card's run instructions are out of date, and Cohere hasn't answered a question on the repository.

Before you call either

Hy-Memory-30B-A3B

  1. Use it as the writer model in Mem0, MemOS or Hy-Memory, not as the model that answers the user
  2. Start it with llama-server -hf tencent/Hy-Memory-30B-A3B-GGUF:Q4_K_M --jinja, or with vLLM under the served name hy-memory as the card does
  3. Pass reasoning_effort as no_think in chat_template_kwargs and temperature 0, as the card's example does
  4. Ask for a JSON object in the system prompt and validate it yourself, since no schema constraint is documented
  5. Treat what it stores as unverified. It keeps what a conversation says, true or not

North Mini Code 1.0

  1. Serve it with vLLM 0.33.0 or later and --tool-call-parser cohere_command4 --reasoning-parser cohere_command4 --enable-auto-tool-choice, with cohere_melody installed
  2. Pass the model's thinking back with its tool calls on every turn. The card says results drop without it
  3. Describe tools in JSON schema and append tool results as a dictionary with the tool role
  4. Use temperature 1.0 and top_p 0.95
  5. For llama.cpp the GGUF files are Unsloth's or bartowski's conversions, not Cohere's
  6. It's text only. Don't send images

Questions

Which is better for AI agents, Hy-Memory-30B-A3B or North Mini Code 1.0?

Hy-Memory-30B-A3B and North Mini Code 1.0 score within a point of each other on agent readiness, 61 (C) and 61 (C). North Mini Code 1.0 leads on agent interface.

Other comparisons with Hy-Memory-30B-A3B or North Mini Code 1.0

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.