u/Low_Edge7695

Moonshot AI released Kimi K2.7 Code on June 12 — a coding-focused open-weight model.

Key specs:

- 1 trillion params (MoE, 32B active, 384 experts)

- 256K context window

- Modified MIT license — weights on Hugging Face

- $0.95/M input, $4.00/M output via Kimi API

- Works with Claude Code, Cursor, OpenCode, OpenRouter

Benchmarks (vendor-reported, independent pending):

- MCP Mark Verified: 81.1% (Opus 4.8: 76.4%)

- Kimi Code Bench v2: 62.0 (Opus: 67.4, GPT-5.5: 69.0)

- 30% fewer reasoning tokens than K2.6

Not a Fable 5 replacement (Fable scored 80% on SWE-Bench Pro). But at 10x less cost with open weights — different value proposition entirely. Especially now that Fable is banned.

Anyone self-hosting this yet? Curious about real-world latency on consumer hardware.

Microsoft just released MAI-Code-1-Flash — a 5B parameter coding model built for fast, efficient developer assistance.

Numbers that caught my eye:

- 51.2% on SWE-Bench Pro (Claude Haiku 4.5 scores 35.2%)

- 71.6% on SWE-Bench Verified (Haiku: 66.6%)

- Average token usage: 28K vs Haiku's 29.8K on Pro

It's already rolling out in VS Code via GitHub Copilot, and it's available for free on OpenRouter and Fireworks AI.

I plugged it into my agent setup with one line:

```python

model="microsoft/mai-code-1-flash"

My ReAct agent has access to tools: web_search, calculate, send_email, delete_file.

It decided to call send_email. On its own. At 3 AM. Nobody asked it to.

The problem: agents pick tools the same way they pick words. There's no built-in concept of "this action is irreversible and I should ask first."

The fix — classify tools as safe vs dangerous:

DANGEROUS_TOOLS = {"send_email", "delete_file", "update_db"}

def conditional_edge(state):

last_message = state["messages"][-1]

if last_message.tool_calls:

tool_name = last_message.tool_calls[0]["name"]

if tool_name in DANGEROUS_TOOLS:

return "human_approval"

return "tool"

return END

Safe tools (search, calculate, read) → execute automatically.

Dangerous tools (email, delete, write) → route to a human approval node.

This is the pattern Anthropic recommends: "Use human-in-the-loop approval for destructive operations. Implement strict per-user authorization."

The key insight: your agent doesn't need fewer tools. It needs to know which tools require permission before executing.

How do you handle dangerous tool calls in your agents? Hard block, soft confirmation, or something else?

My RAG agent hallucinated. Not because the LLM was bad — because the retrieval was feeding it noise.

Query: "What are Python decorators?"

What my retriever returned (before fix):

| Rank | Score | Content | Relevant? |

|---|---|---|---|

| 1 | +5.80 | Decorator definition | Yes |

| 2 | +1.40 | Acknowledgments page | No |

| 3 | +1.13 | u/staticmethod example | Yes |

| 4 | -4.69 | Class exercises | No |

| 5 | -11.0 | Monty Python reference | No |

The LLM received all 5 chunks. It hallucinated because it trusted the noise.

The fix — cross-encoder re-ranking (3 lines):

scores = cross_encoder.score(pairs)

ranked = sorted(zip(scores, candidates), reverse=True)

filtered = [doc for score, doc in ranked if score > 1.5]

After fix: only chunks with score > 1.5 reach the LLM.

Overall results (10 queries): avg relevance went from -0.28 to +3.80. 80% win rate.

Model: cross-encoder/ms-marco-MiniLM-L-6-v2 (free, local, HuggingFace).

If your chatbot hallucinates, check your retrieval before blaming the LLM. What threshold are you using for your re-ranker?

Hit a frustrating bug: my ReAct agent answered questions correctly in isolation, but couldn't handle follow-ups.

"What's 15 * 127?" → "1905" ✓

"Add 10 to that" → "I don't know what you're referring to" ✗

The agent was losing context between messages. Spent two days debugging.

The fix is one annotation:

messages: Annotated[list, add_messages]

Without it, LangGraph's default behavior REPLACES the messages field on every state update. Your agent only sees the latest message — no history.

With `add_messages` as the reducer, every new message gets APPENDED to the existing list. The agent sees the full conversation.

One line. Two days to figure out. The docs mention it casually in one sentence.

Repo (line 30): https://github.com/dunjeonmaster07/react-agent/blob/main/src/agent.py

Anyone else hit state management gotchas in LangGraph? Curious what other defaults surprised you.