Загрузка видео...

Не удалось загрузить видео

На главную

MINIMAX OPEN SOURCED A CODING AGENT THAT LIVES IN YOUR TERMINAL its called MiniMax Code CLI. i gave it one prompt, 19 minutes later i had a working interactive 3d globe. → 249 countries → 14 animated flight arcs across 16 hubs → click a country and the camera...

25,153 просмотров • 7 дней назад •via X (Twitter)

Комментарии: 23

Фото профиля neamtu
neamtu7 дней назад

Garbage

Фото профиля Israfil
Israfil7 дней назад

have you tried mcode bro?

Фото профиля Alan
Alan7 дней назад

wait open source lemme run in my pc wait sir

Фото профиля Israfil
Israfil7 дней назад

just install it in your terminal its one click process

Фото профиля Sakata
Sakata7 дней назад

I’ve been using their CLI for a while now and it’s super cool

Фото профиля Israfil
Israfil7 дней назад

Good to hear it holds up beyond a one off demo. The AGENTS.md and phased-commit flow look like the parts that make it actually usable.

Фото профиля Avid
Avid7 дней назад

Amazing! I love MiniMaX.The harness is amazing

Фото профиля Israfil
Israfil7 дней назад

yes my man its harness is so good at coding stuffs

Фото профиля K2S
K2S7 дней назад

19 mins for all that is actually insane ngl

Фото профиля Rakib
Rakib7 дней назад

Dammnnn Let me try

Фото профиля Fajar M Reza
Fajar M Reza7 дней назад

Terminal-native coding agents could turn single prompts into reproducible software workflows.

Фото профиля Peng
Peng7 дней назад

thanks for dropping the details

Фото профиля Ayyaz
Ayyaz7 дней назад

Open-sourcing MiniMax Code CLI is the useful part. A 19-minute globe from one prompt is greenfield; I'd want the same loop on a dirty worktree with broken tests.

Фото профиля D. Michel Morelli
D. Michel Morelli7 дней назад

I had tried Minimax M3 for programming, but the results weren't great.

Фото профиля Manna Code
Manna Code7 дней назад

AGENTS.md carrying the rules is the right instinct. I’d still want a live spend meter on that 19-minute globe run—phases are cute; knowing what each phase cost is how you decide to keep looping.

Фото профиля Ruuj
Ruuj7 дней назад

nice results israfil, good one

Фото профиля Farea
Farea7 дней назад

i tried mcode earlier its harness is kinda good tbh

Фото профиля Rivon
Rivon7 дней назад

Will check it out

Фото профиля painn
painn7 дней назад

would try this

Фото профиля Isoldegwow
Isoldegwow7 дней назад

the AGENTS.md doing more work than the model is the most relatable part of AI coding agents

Фото профиля J.𝙳𝚛𝚊𝚟𝚎𝚗
J.𝙳𝚛𝚊𝚟𝚎𝚗7 дней назад

Wanna try it

Фото профиля Roan
Roan7 дней назад

coding agent living in terminal sounds interesting bro

Фото профиля Isilin
Isilin7 дней назад

What was your machine config to reach 96tk/s ?

Похожие видео

Before MiniMax Code touched a single line of my website, it went and studied 3 competitor sites first. I didn't ask it to copy them. I asked it to look at how they were structured, then build something better for what I actually needed: an AI Influencer collaboration business. Here's what that actually looked like. MCode opened each competitor page inside its Built-in Browser, no separate tool, no copy-pasting URLs into a scraper. It read through their layouts, screenshotted the sections that mattered, and pulled out: → how they positioned their CTA → how pricing was laid out → what content order kept people scrolling Then it took all of that and built my site around it. Not a template. Not a copy. My services, my pricing, my client reviews, structured with what it learned from pages that already convert. While it built, I wasn't stuck at my desk. I had Remote Control running, my phone mirrored to the desktop Agent in real time. Watched it work, jumped in twice to approve changes, all from my phone while the actual build stayed local on my machine. That's the part that changed how I think about MCode. It's not a prompt-to-website tool. It's an agent that does the research step you'd normally skip because you're in a hurry, and it lets you stay in control of it remotely instead of watching a loading screen. Started with an idea. Ended with a site that's actually informed by what works. Try MiniMax Code: Using MCode? Don't skip the Daily Check-In for extra points.

Aaliya

11,919 просмотров • 22 дней назад

Memory vs. Graphs, clearly explained! memory is great, and the ceiling arrives quietly: it stores what happened. it does not store what to do about it. six runs later your file has fifty lines, and the model reloads all of them before it does anything. Graph engineering fixes this by changing what memory is: not a place things are kept, but an edge that runs backwards. you need both, and here is the sentence that resolves the whole confusion: a store keeps what happened. an edge keeps what to do about it. ↳ a store grows with every run, and every line is reloaded before the next one ↳ an edge carries one derived rule, and the rule replaces the run that produced it Prompts → Context → Harness → Loops → Graphs the transcript goes away, the constraint stays. and the constraint is smaller, because "adapters preserve keyword args exactly" is four hundred tokens shorter than the run that proved it. the same four blocks work on anything you can cut into lanes. i pointed them at token launches on Robinhood Chain, open source, nothing leaves your terminal the trick is knowing what deserves to survive. an output is not memory. "ported the utils slice, green on first pass" tells the next run nothing it can act on. the rule you derived from it does. one thing to know before you scale it. what you write down is not what comes back. ↳ the root rules file and auto memory are re-injected from disk. they come back intact, every time ↳ path-scoped rules live in message history. they get summarized away and do not return until a matching file is read again so a rule that must persist cannot be path-scoped. move it to the root and pay the always-loaded cost, or accept that it is advisory in any long session. and the one that eats whole nights: a memory file that has never had a line deleted is not memory. it is a tax on every run you will ever make, and nobody reads it back. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this, and the repo that runs it is below ↓

Hanako

47,766 просмотров • 22 дней назад

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.

Akshay 🚀

51,540 просмотров • 3 месяцев назад

run agent harnesses 100% private & offline. (no token costs, no API keys, 100% open-source) your agent runs locally. the model doesn't. every prompt, every file, and every secret still leaves your machine before the agent does anything with it. Magnitude fixes that. it's an open source inference server that runs models on your own hardware and plugs into the coding agent you already use. setup is one command. it profiles your machine, measures the memory bandwidth that sets your token rate, and hands back complete configurations instead of a list of models. each one names a model, a compression level, a context size, and a speed range you can expect. pick one and start working. it doesn't replace your harness. setup asks which one you want and writes that config for you. Pi, OpenCode, Claude Code, Codex, and Cline all work, and there's a built-in one tuned for local models if you don't have a harness yet. that one uses your shell, edits files, and runs scripts out of the box. add skills and it handles Excel, PowerPoint, PDFs, or Chrome. everyday work it covers: → analyze sensitive data → manage private notes → review code and logs → search and organize files → build docs or slides Apache 2.0. no rate limits, and nothing leaves the machine. 𝗻𝗽𝗺 𝗶 -𝗴 @𝗺𝗮𝗴𝗻𝗶𝘁𝘂𝗱𝗲𝗱𝗲𝘃/𝗰𝗹𝗶 the repo is here: (don't forget to star 🌟) i wrote the full breakdown of why picking the configuration is the hard part. the article is quoted below.

Akshay 🚀

55,693 просмотров • 27 дней назад

HERMES AGENT VS OPENCLAW. a local ai onboarding flow test. a 3.9gb bonsai served on localhost, both agents upstream and latest, i point each one at the endpoint and watch which one even finds it. > hermes opens a provider menu, thirty plus options, local servers sitting right there next to the cloud ones, i hand it 127.0.0.1:8899, it verifies the endpoint, one model visible, auto-detects the model by name, bonsai-27b-q1_0, reads the context length straight off the server, saves it, and starts reasoning and firing real tool calls on my local model. no key. no friction. > openclaw has no menu. it goes hunting for a codex login, an openai key, finds none because there are none, prints no models available three times, defaults to openai/gpt-5.5, a cloud model it cannot reach, and dead ends on run auth login --provider openai. read that back. it asked me for an openai key. to run a model already running on my own machine. it never once looked at localhost. to be fair, openclaw can run local if you hand wire endpoint yourself. what it will not do is find the model already sitting on your box. hermes agent found it in one line. now the part i owe you. the auto-detect that just won, the model name read, the .gguf strip, the context length probe off the server, that is my code, it is in hermes agent main right now, authorship preserved, #2051 and #4218. the wizard fix that stops an agent from silently routing you to someone else's creds, the exact trap openclaw still falls into, mine too, #4210. i contribute to hermes agent, i told you that going in. one agent is built to talk to whatever you are running, the other is built to talk to a cloud api, so one found my model and ran it and the other asked me to log into openai. onboarding flow of both, mapped, below.

Sudo su

23,816 просмотров • 2 месяцев назад

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,591 просмотров • 3 месяцев назад