You change the number of binders from four to six. When you open it again, it says four once more. The interface responded to your click, but the application did not keep a new working state. It is exactly this gap that separates a dashboard generated once from a tool that people and agents can keep working with.
MiniMax announced Mini Apps for its Code desktop application on 22 October 2026. The vendor describes a frontend, a Node backend, a persistent data area and declared agent connections. Local execution under the user’s account is a property of this approach, not a blanket security guarantee.
Three layers, one shared working state
The frontend shows values and accepts input. The backend checks and processes a change. Storage records which state applies afterwards. If a person and an agent are to work on the same task, both need a traceable reference to this valid state.
A materials list is a good miniature example of this. The interface shows the number of binders, the server accepts only permitted quantities, and a file keeps the confirmed result. An agent’s recommendation should initially remain recognisable as a suggestion. Only the intended step of adopting it changes the valid value.
Your own local reference without an agent connection
You can investigate the storage question independently of MiniMax. The following Node example, written for this article, provides a tiny state endpoint on a loopback port. It is not a Mini App extension and does not use any MiniMax API. Save it as mini-state.mjs in an empty test folder and start it with an existing Node installation.
import { createServer } from "node:http";
import { readFile, writeFile, rename } from "node:fs/promises";
const datei = new URL("./state.json", import.meta.url);
const temp = new URL("./state.tmp", import.meta.url);
async function lesen() {
try { return JSON.parse(await readFile(datei, "utf8")); }
catch (e) { if (e.code === "ENOENT") return { anzahl: 4 }; throw e; }
}
createServer(async (req, res) => {
res.setHeader("Content-Type", "application/json");
try {
if (req.url !== "/state") { res.writeHead(404); return res.end("{}"); }
if (req.method === "PUT") {
let roh = "";
for await (const teil of req) {
roh += teil;
if (roh.length > 1024) throw Error("zu gross");
}
const { anzahl } = JSON.parse(roh);
if (!Number.isInteger(anzahl) || anzahl < 0 || anzahl > 20)
throw Error("ungueltige Menge");
await writeFile(temp, JSON.stringify({ anzahl }));
await rename(temp, datei);
} else if (req.method !== "GET") {
res.writeHead(405); return res.end("{}");
}
res.end(JSON.stringify(await lesen()));
} catch { res.writeHead(400); res.end('{"fehler":"Eingabe oder Datei pruefen"}'); }
}).listen(8765, "127.0.0.1");Read /state with an HTTP tool, then send the body {“anzahl”:6} via PUT and read it again. Then stop the process and start it again. The interesting comparison is the value after the restart. It now comes from the file and not from the memory of an open page.
What the small example deliberately leaves open
The demo is intended for individual local requests. It has no user management, no multi-user database and no robust handling of concurrent writes. These properties would be additional requirements as soon as it turns into a real application. Replacing the file via a temporary file only illustrates one limited way of saving.
An interface could now read this endpoint and send changes. An agent would be a further caller with specifically defined permissions. Both are separate extensions. A visible button does not prove that a change was saved, and a saved value does not yet prove a sensible agent decision.
From generated result to tool
So when you look at a generated Mini App, check four specific things: where does the displayed value come from? What confirms a change? Which state appears after a restart? Which action may the agent trigger itself? These questions describe actual behaviour and can be followed through with a small materials list.
The MiniMax news is interesting because it brings conversation and a workspace you can keep using closer together. The decisive mechanism, however, remains storage plus controlled action. Once you have understood it in a tiny application of your own, you can also assess a more extensive agent dashboard more precisely.
Sources and status
Sources as of 25 October 2026. Introducing MiniMax Code Mini App; official research index with announcement date; package structure and declared permissions; Node runtime and data area; security model and local execution.
