RonnyHe

Head of R&D at MiniMax Code. Co-creator of DeerFlow. Building the next generation of AI agent systems.

[RonnyHe @Ronny_MiniMax]

hello, world! i'm daniel! currently i'm the head of r&d of MiniMax code @MiniMax_AI, which is a frontier ai lab in china.

i enjoy working on our ai-native product @MiniMaxAgent . i'm really obsessed with this question: what does an ai-native organization look like? how can our organization co-evolve together with llms?

besides that, i'm passionate about open source. i'm the co-author of the deerflow project, which is a representative work in harness engineering and has 78k 🌟 on github.

if you're passionate about open source, foundation models, or agents- or if you enjoy playing basketball or riding a road bike - let's chat and be friends! :)

[Asteri @Asteri_eth]

I put Anthropic's whole harness playbook for long-running coding agents on one page

honestly the most useful thing I've read on agents all year

two Anthropic engineering posts + the Opus 5.5 launch, squeezed into one sheet:

> a planner grows a one-line idea into a 16-feature spec
> a generator builds it, an evaluator opens the app in Playwright and fails any sprint below the bar
> session one writes https://t.co/K47G5WnxJt, a progress log and 200+ failing features. every session after closes one and commits
> the 4 ways agents wreck long tasks, and the fix for each
> 3 prompts to copy: coding agent, QA agent, planner

solo run: 20 minutes, $9, the game didn't even respond to input

full harness: 6 hours, $200, playable

QA was about 8% of the bill on their DAW run

and Opus 5.5 runs about 40% cheaper than Opus 5

bookmark this before you wire up your next agent

[RonnyHe @Ronny_MiniMax]

@yujiachen_y But you are using Dia, man. Lol

[RonnyHe @Ronny_MiniMax]

M3.1 Flash Weight is public now:

Hugging Face:
https://t.co/AwZeYPTvmd
ModelScope:
https://t.co/LDEGbV9seN

[Leanna Ren @RenLeanna]

"control, we have touchdown"🥕🐰
landing confirmed!

M3.1 Flash by H3

[RonnyHe @Ronny_MiniMax]

@Cyrbuzz123 That's exactly why it's a published standard, not internal glue. The contract is what apps build against, and we'll treat breaking changes to it carefully.

[RonnyHe @Ronny_MiniMax]

Mini Apps are now an open standard in MiniMax Code: a port, an Agent, a data directory. You describe the tool, the Agent builds it.
https://t.co/u1ZJdNbg32

Built something useful? Contribute it 👇
https://t.co/X1XuP404GY https://t.co/CejbIMn4xk

[RonnyHe @Ronny_MiniMax]

@AlgoritmaTurk @MiniMax_AI @MiniMaxAgent Thanks for digging in and confirming the fix! The MCP transport timeout with no reconnect is a great catch. Mind opening a separate issue for it so we can track it on its own? 🙏

[RonnyHe @Ronny_MiniMax]

@madmanstudioio Exactly. It's a tool you keep, not an artifact you export. Data persists, and the Agent can pick up where you left off.

[RonnyHe @Ronny_MiniMax]

@_wickyjohn Thanks for noticing! The page can suggest, but you decide what the Agent actually sees.

[RonnyHe @Ronny_MiniMax]

@aiclawdius You do, with the Agent. That's the point: the person who uses the tool can change it in a sentence, instead of waiting on someone who owns it. And if it's useful to others, PR it to the community repo and it gets maintained there.

[RonnyHe @Ronny_MiniMax]

@swordBluesy Agreed, static declaration is step one. Runtime checks on child processes and permission changes are on our list. Thanks for pushing on this.

[RonnyHe @Ronny_MiniMax]

@djekyll Partly enforced: when a page hands something to the Agent, it lands in your input box first, and tool calls go through approvals. The rest is how you design your app.

[RonnyHe @Ronny_MiniMax]

@11Shixi Fair point, and you read the docs closely 🙏 Before the old process stops, the host can roll back. After that, a failed swap should say so clearly. Noted for the UI.

[RonnyHe @Ronny_MiniMax]

@Rosasynthesiz It's an open standard on top of the MiniMax Plugin protocol, and the community repo is MIT. Today it runs in MiniMax Code. If other harnesses want to host it, we'd love that.

[RonnyHe @Ronny_MiniMax]

@farukguney_ai 100%, that's the whole point. It's a real page: drag, edit, fix numbers yourself, and the Agent sees the same state when you need it.

[RonnyHe @Ronny_MiniMax]

@Charles__Kira @MiniMaxAgent Exactly. Fork one, ask the Agent to tune it to how you work, and PR it back if others would want it.

[RonnyHe @Ronny_MiniMax]

@jurlycat Thanks! Would love to see what you build with it.

[RonnyHe @Ronny_MiniMax]

@ClaraOnAI Thanks! Would love to see what you build with it.

[RonnyHe @Ronny_MiniMax]

@Charles__Kira Thanks! Can't wait to see what you vibe.

[RonnyHe @Ronny_MiniMax]

@PinakCorp Tool approvals show up right inside the page, so you see what the app is about to do before it happens. And /miniapp-creator starts with read-only queries against each data source before it writes anything.

[RonnyHe @Ronny_MiniMax]

@guannanjiayou The app's backend gets its own persistent data directory, and the Agent keeps the same tool approvals as your normal session.