Esacode

Changelog

What shipped, and what is next

Every release of the EsaSim platform and workers. Planned items are marked as such.

  1. v0.12Planned

    More data tools

    • ChangedVersion 0.12.88. Project cards under My projects and Shared with you have the same cover proportion as Demos and Public (16:9).
    • ChangedVersion 0.12.87. The page scrolls under the top bar, which is no longer part of it (its scroll bar starts below the bar). Projects, Public and Demos: the search is centred, with the categories of the cards next to it to show only one. Each category has its colour on the cards. Demo and public cards have a bigger picture, and demos carry the esacode mark in a corner of it.
    • ChangedVersion 0.12.86. The dashboard's top bar stays in view while the page scrolls; at the bottom of the menu, the EsaSim version comes first, then the plan, then your profile; cards have a soft shadow in light mode and a faint glow in dark mode.
    • ChangedMaking a project public goes through review: its admins ask (Settings › Visibility shows In review, and can withdraw), a platform admin checks its readme, blueprints, the code of its blocks and its files under Admin › Public projects (with signals worth a look: outside addresses, risky calls, secrets, executables), then approves it (it shows under Projects › Public) or rejects it with a reason. Its people get an email either way; a rejected project can ask again. Projects already public stay public.
    • AddedAI assistants of platform admins review public projects (review_public_projects: list, read, file, approve, reject).
    • AddedClone into my workspace on a demo or public project of another workspace: in its header, on its readme page, and as a small button on its card under Projects › Demos and Public. Your own projects do not show it: they are in your workspace already.
    • FixedThe dot of an open project in the menu blinked while someone in another workspace ran it (a demo or a public project of yours): it now blinks only for the runs of your workspace, the ones its Runs tab shows.
    • AddedAI assistants can delete a flow that is no longer useful (delete_flow, with the flow's exact name to confirm): its draft and versions go, its runs and results stay. Project admins and whoever created the flow; not while a run of it is going on. In the agent panel it is one of the changes put in place together.
    • ChangedDemos and public projects: Clone into my workspace (in the header of every tab) makes the whole project yours: its blueprints, the code of its blocks, its readme and cover, and now its files too (assets/ and data/: models, policies, pictures), so the clone runs as it is; the results of its runs stay with it. The clone remembers where it came from.
    • ChangedHome page: the motto is now Where we build Physical AI, on two lines; while the robot loads, a loader stands where it will appear (its download in percent), then the robot and the cards fade in; the dark Works with band below the hero is narrower, its line and logos centred in it.
    • AddedWorker repair scripts: on Windows (administrator PowerShell) & ([scriptblock]::Create((irm https://esacode.com/install/fix-worker.ps1))), on Linux curl -fsSL https://esacode.com/install/fix-worker.sh | sudo bash. They put the newest worker in place of every worker service on the computer, checked against its SHA-256, keep its pairing, settings and data, and let it update itself from then on.
    • ImprovedWorker 0.13.2: Linux has a ready-made program too (x86-64), and a ready-made worker always updates by downloading the new program, never by building it on the machine.
    • AddedComputing › Your workers: a Version column (with where it stands: latest, offered, updating, failed, by hand), and every row opens to the worker's hardware, what it holds of each project (Wipe cache), its whole configuration and its update status with what to do.
    • FixedWindows workers could not update themselves: the service may now change its own folder (installs before 0.13 made it read-only, so every update stopped with "access denied"). Workers installed before need it once, by an administrator on that computer: the install command again, or the icacls line the worker's page shows.
    • ImprovedWorker 0.13.1: checks it can write its folder and, if not, says so in the dashboard with the command that fixes it (instead of failing when an update comes); a failed update is tried again an hour later, not only after a restart.
    • ChangedThe readme is edited on the Readme page: Edit opens the text with a preview, and the cover, picked from the project's pictures or uploaded from your computer into assets/covers/ (so it travels with the project on GitHub). Settings keeps the name, description and type. Readme pictures can point at the project's files (![…](assets/covers/name.png)).
    • AddedSettings › Results and cache: results stay on the worker that made them and EsaSim keeps their list (worker 0.13); Move results to GitHub puts each run's results in results/run-<number>/ of the project's repository; Ask to download shows a window when a run you started ends (a zip straight from the worker, only with your yes); the project's files are cleared from the workers after each run, when the project is closed, or by hand (Clear now).
    • AddedSettings › Hardware needed: RAM, free disk, how many GPUs and their type (a vendor or a model such as RTX 4090). Workers without it are not picked for the project's runs, the Compute tab says why, and a run whose workers all lack it does not start.
    • AddedCompute: open a worker to see its processor, memory, disk, accelerators (memory, driver), system, Python, Docker and worker version, and what it holds of each project; Wipe cache deletes every project's files on it (its software and dataset folders stay).
    • ImprovedWorker 0.13.0: keeps results on the machine (EsaSim gets their list), clears the folders of the runs a project asks for, wipes its cache on request, and reports what it holds per run.
    • Added3D view: a robot model's links can have parts with their own finish ("parts": [{v, f, color, roughness, metalness, clearcoat, clearcoat_roughness}]), such as a glossy white shell and satin metal rings; a tool on the flange is drawn as a marker pen (holder, barrel, coloured band, felt tip).
    • FixedPages with the agent panel showed a script error from the file viewer (it took the panel for a dataset upload box).
    • FixedWindows workers fetch what a block needs before it runs: on a computer without Microsoft's Visual C++ runtime (a fresh Windows), PyTorch, OpenCV and onnxruntime could not load ("c10.dll or one of its dependencies"). The worker now adds Microsoft's runtime files to its own data folder the first time a block needs them, and the Windows installer installs the runtime for the whole computer.
    • AddedAI assistants can take a folder of a worker into a project's assets (project_assets, from_folder): the worker lists the folder, then its files come into the assets by themselves and are saved with the project on GitHub. list_assets says which repository the project is saved to, and list_datasets the machine and path of each connection.
    • AddedWindows workers install with one line, on a computer that has nothing installed: in an administrator PowerShell, the line the dashboard shows downloads the ready-made worker program (checked against its SHA-256), gives it its own Python with PyTorch (the CUDA build with an NVIDIA GPU) and the usual packages, installs the service, pairs it and starts it. No Git, CMake or Visual Studio any more. Installed workers update themselves by downloading the new program.
    • AddedProject assets block (Data): gives a block that runs on a worker the files of the project's own assets, by name or pattern (models/*.glb). Assets travel with the project on GitHub, so any worker downloads them from EsaSim and no machine has to be online to hold them. Everything a project needs to work (robots, models, textures) belongs in its assets; datasets stay the data it works on, connected to the project.
    • FixedA run that reads a dataset connected from the folder of a machine that is offline no longer waits in the queue: it does not start, and says which machine to turn on. Machines that stopped answering show as offline in the run panel and to AI assistants right away.
    • ChangedChoosing workers for runs, in the project's Compute tab: every worker you may use, with its hardware and what it is doing (a worker someone holds says who and for which project), filters (search, free now, online, GPU, VRAM, RAM, tag, fits this project) and Select all shown. The ones you tick appear in Your selection beside it, where you release them one at a time or all; one working on a task of your run stays until the task ends or you stop the run.
    • ChangedRun in a flow starts at once on your selected workers, like that flow's last run (its block rules and Stop after); the workers chip beside Run opens the run options. With none selected the run panel slides in with nothing ticked, to pick them there: a run no longer takes every free worker by itself.
    • ChangedWorkers added to your selection while a run goes on take its waiting tasks; Release in the run panel lets go of the workers not working on a task, also during a run.
    • ChangedYour selected workers stay yours until you release them: no more release after an idle time, and closing the project (× in the menu) leaves its runs going and its workers selected, so a run can go on for days with the project closed. A workspace admin can still release a worker from its page.
    • ChangedAgent panel: a new message box with a round send button that becomes Stop while the agent works, the attach button and the model inside it; Copy and Edit on your messages (editing one removes what followed it and goes on from the new text), Copy and Retry on the agent's answers; Delete this conversation in the header and a delete button on each past conversation; the panel's width is dragged from its left edge and remembered (double-click for the default).
    • AddedPublic projects: a project's admins can make it public (Settings › Visibility). Everyone signed in finds it under Projects › Public, opens its readme, blueprints and the code of its blocks, runs it on their own workers and takes a copy; its data, runs, results, secrets and team stay private, and only its team changes it.
    • AddedStars: every project has a Star button in its header. Stars rank Projects › Public, and add up for whoever made the projects: your stars show on your profile and next to your name on public projects. Stars come from others, so you cannot star your own. When the project is on GitHub and your GitHub account is connected, a tick box next to the star also stars the repository on GitHub, as you (remembered in your browser).
    • ChangedAn organization is a legal entity, not a plan. Anyone can create one, on any plan: it opens right away on Free, and its Billing page offers Pro (one seat, when one person works for it) or Enterprise (seats for a team), monthly or annual; any organization can buy cloud credits. When a paid plan ends, the organization moves to Free instead of closing, and its members keep their access. Organizations that were waiting for a first Enterprise payment open on Free.
    • AddedThe workspace's plan (Free, Pro, Pro+ for yearly Pro, Enterprise, Enterprise+ for yearly Enterprise) shows at the bottom of the sidebar, above the version, and links to Plan and billing for whoever manages it. The workspace switcher shows each workspace's plan.
    • AddedAgent sessions: each answer of the agent works on copies. The flows, blocks, project settings and assets it changes stay copies until the answer is complete: you see one card with every change (the code and flow differences included) and choose Put in place, which applies all of them at once, or Discard. If the answer crashes, is stopped or is left behind, its copies are deleted and nothing of it reaches the project. Each answer has its own ID (its sub-agents share it): copies of any other answer are deleted on sight.
    • AddedWhile the agent changes a project, the project and the blocks it changes are locked for everyone else (people, other AI assistants, GitHub sync); runs go on as usual. The project page says so, with Open the agent and Stop and discard (for whoever runs it, and the project's admins). A run of a flow the agent changed waits until its changes are in place.
    • ChangedThe agent never changes EsaSim's own blocks: changing one gives your workspace its own copy, which takes its place in the project's flows (the EsaSim block stays as it is). Platform blocks are changed by platform admins only, as before.
    • AddedThe agent goes on when you close the tab. With a model EsaSim calls (an API), the server carries the answer on by itself. With a model your browser calls (Ollama, LM Studio, vLLM), any EsaSim tab you open picks it up, with the panel closed too (one tab at a time), and the Agent button shows a dot while it works.
    • ChangedAdmin › Agent: the daily message limit and the monthly spend limit can be switched off, each with its own tick box.
    • AddedAgent sub-agents: the agent can hand a task that reads a lot (run logs, web pages, files, several flows or blocks) or takes many steps to a sub-agent. The sub-agent starts with a fresh context and the same tools, and gives back only its result, so the agent's own context stays small. Admin › Agent › Sub-agents at a time: 1 (the default) runs one at a time, and the agent waits for its result before doing anything else; more runs that many in parallel (for capable models on APIs); 0 turns them off. In the panel each sub-task is one line that opens on its steps and result; a change it wants still shows its Confirm card, and Stop stops its sub-agents too. Works with models called from your browser (Ollama).
    • ChangedAgent panel: when a request to EsaSim fails during a turn, the panel tries again a few times before it says so.
    • FixedAgent with a model called from your browser (Ollama): every request was refused with "Value looks like object, but can't find closing '}' symbol". EsaSim kept the prepared request and read it back in a way that turned the empty {} of some tool descriptions into [], which Ollama cannot read; the request now goes to the browser exactly as it was prepared. Tool calls in the history go back in the OpenAI form again (arguments as JSON text), which Ollama reads.
    • AddedAgent: long conversations are compacted to fit the model. Once a conversation outgrows Admin › Agent › Context per call (32,000 tokens by default), the outputs of tools in older exchanges are shortened, and then the oldest exchanges go to the model as a short recap (what you asked, what it answered); the panel says when that happens. Set it at or under the context of your models (for Ollama, its OLLAMA_CONTEXT_LENGTH).
    • AddedAgent panel: Resend under each of your messages sends it again (useful after an error); on an earlier message, what came after it goes away, as with Edit.
    • ChangedAgent with a model on your computer: when the browser cannot call it, the panel says whether nothing answers at its address (not running, or local network access blocked) or the server answers but refuses the site (Ollama's OLLAMA_ORIGINS), with what to do.
    • AddedAgent with a model on your own computer: in Admin › AI models, "Called from the person's browser (agent only)" makes the agent's panel call the model's address from the browser (Ollama at http://localhost:11434/v1, LM Studio, vLLM on the local network), so nothing has to be reachable from the internet; EsaSim prepares each request, the browser sends it and brings the answer back, and the tools still run on EsaSim as the person. These models are free and are not offered to the LLM block. Ollama needs OLLAMA_ORIGINS set to the site's address.
    • FixedAgent panel: a message typed before the panel had finished opening could be lost.
    • FixedAdmin › Agent listed only the models offered in the LLM block, so a model kept hidden there (a local model being tried, say) could not serve the agent, and the chat seemed to do nothing. Every saved model can now be ticked for the agent, offered or hidden; and with no model set up the panel says so and the message box is off.
    • AddedAgent, Files & documents skill: attach files in the panel (button or drag and drop, 8 MB each); the agent reads text files, runs Python analyses on the person's selected workers next to the data (charts, tables, any package the worker may install), and makes PDF or Word documents from Markdown, each after a Confirm that shows the code or the text it sends. Files up to 1 MB travel with the run; all of them are also kept in the project's "Agent files" dataset. The runs belong to the project's "Agent analysis" flow, so their code and files stay under Runs and Results, with download links in the chat.
    • AddedLocal models: Ollama, LM Studio and vLLM in Admin › AI models (no key; http allowed for them), for the LLM block and the agent. Admin › Agent › Test the models asks each ticked model a question that needs a tool and says which can run the agent.
    • AddedThe EsaSim agent (off until a platform admin turns it on): an assistant in a panel that slides in from the right of every dashboard page, working with the models of Admin › AI models (Claude, GPT, Gemini, Kimi and any OpenAI-compatible server) through one loop of EsaSim's own. It reads the workspace, changes projects, flows, blocks and files, ranks, selects and releases workers, runs and stops flows, and searches the web, always as the person, and anything that changes something waits for their Confirm on a card that names the project, flow and workers.
    • AddedAdmin › Agent: Off, Admins only (platform admins test it on the live site, not charged) or Everyone (charged to the workspace's credits at the model's price); each skill (workspace, project, runs, compute, web) On, Admins only or Off; the models and the default one; steps per answer, messages per person per day and a monthly cap per workspace; web search by Tavily, Brave or a self-hosted SearXNG with a Try a search button; usage of the last 30 days and Stop all turns. Every confirmed change is in the audit log.
    • AddedWebsite: Aerospace & space, a solution page (/solutions/aerospace) with the questions EsaSim answers for launch, landing and spacecraft control, typical workloads and the booster landing demo; in the Solutions menu, the footer and the home page industries, where the nine tiles sit three by three. The home Aerospace card links to it.
    • AddedGoogle Tag Manager on every page of the site and the dashboard (container in config gtm_id; empty turns it off; not in preview mode).
    • FixedHome page: the logos sit exactly in the middle between the Works with line and the bottom of the dark band, on every screen size.
    • AddedPayments in a Stripe sandbox and live: Admin › Billing has four modes (off, built-in test checkout, Stripe sandbox, Stripe live) and the keys of each Stripe environment side by side (secret, publishable, webhook and connected-accounts webhook secrets), each with Test the connection. A test key is refused where a live one goes, and the reverse. Switching to live asks first.
    • AddedAdmin › Billing › Products and prices: the Stripe price ID behind each plan (base and extra seat, monthly and annual) for the sandbox and for live. Make them in Stripe creates the missing products and prices from the plans' prices (and reuses those it made before); Check reads every ID from Stripe and says whether it is active and matches the plan's amount, currency and interval. Price IDs are no longer on each plan's page.
    • ChangedA workspace's Stripe customer and subscription belong to the environment they were made in: in the other one EsaSim makes a new customer, so sandbox and live never mix. Webhook events are handled with the keys of the environment that sent them. Before going live, End sandbox subscriptions puts test subscribers back on Free, and sandbox money does not count in the monthly total. Existing Stripe keys move by themselves to the environment they belong to (test keys and their price IDs to the sandbox).
    • FixedAdmin › Announcements did not open on MySQL (Something went wrong): its list used a name MySQL reserves.
    • AddedWorker updates the platform can see: each worker is Up to date, Updating, Will update itself, Update by hand, Update failed, or Update did not finish (offered more than 6 hours ago, online since, still on the old version: a failure it did not report). Computing shows it as a badge on each worker; a worker that needs a person shows what went wrong and how to update it by hand on its page and on the Overview.
    • AddedThe oldest worker that may run flows (Admin › Workers and jobs, 0.5.0 by default): older workers get no tasks, and the checks before a run say which workers are left out and whether they will update themselves or need it by hand. Admins also see every worker of the platform by version and update status.
    • AddedAnnouncements: platform admins write messages for the people using EsaSim (Admin › Announcements), as drafts, then published, edited, unpublished or deleted; for everyone or filtered by plan, by role (owners and admins only), by workspace and to workspaces with a worker; Important ones in red; emailed too if wanted. People read them under Messages on their Overview and on /app/messages.
    • AddedA red count next to Overview in the menu: unread messages plus workers that need an update by hand. Opening a message marks it read and lowers the count.
    • FixedCode editor: at full width it went under the dashboard's sidebar. It now reaches the sidebar's edge and follows it when the sidebar is collapsed, opened or resized; dragging its edge stops there too.
    • FixedCode editor: a long line made the editor wider than its panel, so its vertical scrollbar was out of view on the right. The editor now keeps to its panel and both scrollbars always show.
    • AddedCode editor: Copy code copies the whole file shown (backend.py or frontend.js), with the changes not yet applied.
    • ChangedConfirmations are EsaSim dialogs instead of the browser's own pop-up ("esacode.com says…"): the question as a title with what it means under it, a button that says what it does (Stop, Delete, Re-pair…), red for actions that delete or stop something, with the safe button selected so Enter never confirms them by accident. Esc or a click outside cancels.
    • AddedBlueprint editor: every block whose code can be opened has a </> button at its bottom right that opens its source code (amber when the code was changed in this flow).
    • FixedHome page on phones: the page no longer scrolls sideways or cuts text off (the Ship section with its code sample was wider than the screen); the demos, industries and other card lists are rows you swipe; smaller section labels and less empty space.
    • AddedSetting up an account: two things are needed to work in EsaSim, GitHub linked (projects live there) and a worker (runs happen there). While one is missing, a list of the two pops up once per session on the dashboard, with Link and Add and a Step by step that walks through them. New accounts land on the dashboard. The optional ones (a Hugging Face token, two-factor authentication) are on the Overview's Get started card, each marked needed or optional, and in the profile. Each step counts as done when its thing exists, however it was done.
    • AddedA project whose blocks use the Hugging Face token of whoever runs them (text to image, text to video, Hugging Face datasets, Publish to Hugging Face) says so in a popup when someone without a token opens it, once per session: which blocks in which flows and why, where to make a token, and a field to save it to the profile (encrypted) without leaving the project.
    • AddedBlueprint editor: a flow with a run going has a pulsing green dot and a green name on its tab, with the run, its state and its progress in the tab's tooltip; the marks follow the runs every few seconds, and when the running flow's tab is scrolled out of sight the arrow on that side shows the dot. Avatars whose picture cannot be loaded show the initials.
    • ChangedOpening a demo without a worker: the first thing it says is that a worker is needed to run it, with Add a worker, and a message at the bottom right says the same once.
    • AddedMessages at the bottom right of the dashboard: confirmations (saved, linked, sent…) slide in there and go away by themselves; errors and warnings stay at the top of the page.
    • AddedYour GitHub picture is your avatar once GitHub is linked (the menu at the top right, members of an organization); your initials otherwise.
    • ChangedBlueprint editor: Publish shows only to people who can change the flow, and says what it does (makes the draft a numbered version that never changes; runs, endpoints and demo visitors use published versions; Run publishes the draft for you when it changed). A demo's visitors see and run its published version (Version N · what Run uses), never its makers' draft. The View page no longer has its own Connect a 3D mouse button: the 3D view has it.
    • FixedThe checks before a run said No computer is connected; they say No worker is connected. A few more places that said computer for a worker say worker.
    • ChangedOne word for what runs your flows: a worker. The dashboard, the website, the documentation, emails and the AI assistant tools said machine and worker for the same thing; they now say worker (the EsaSim worker, installed on your computer or server), and computer only where the hardware itself is meant (install the worker on your computer, keep the computer awake). Machine blocks are now worker blocks, next to views. The assistant tool list_machines is now list_workers; the old name keeps working. The screenshots in the documentation show the new wording.
    • ChangedA demo opens as a full project, with all its tabs, seen through the workspace of whoever opens it: run it as it is, on your own machines, without copying it and without GitHub. Its Compute, Runs, Results, Data and Analytics show your machines, your runs and your results, never its makers', and its makers never see yours (a run of a demo belongs to the workspace that started it: its machines, sessions, data and credits; the demo's own blocks come with it). The demo itself does not change: Make it my project copies it into your workspace to change it. Settings, Team and API say what belongs to the demo's makers. A project's own runs pages, exports and assistants show only the runs of its workspace.
    • ChangedOpening a demo opens the project itself, for everyone signed in: its readme and its blueprints in the editor, with every block, connection, setting and the code of its blocks, read only (Demo · read only, and Use this demo in the header to take a copy that can be changed and run). Its runs, results, data, team and settings stay with its own people. Before, a demo showed only its readme and a list of its blueprints.
    • FixedPages felt slow. Work done after a page answers (saving a project to GitHub, moving projects, messages) kept the person's session locked, so the next page waited for it: the session is now let go first. A project opened again asks GitHub whether it changed after the page has answered instead of before (the first opening still waits). The editor's block catalog (a few MB with the code of every block) is sent compressed and kept by the browser, which only asks whether it changed.
    • AddedTelegram notifications for the platform admins: Admin › Integrations › Telegram notifications takes a bot token (from @BotFather, kept encrypted) and a chat (yours, a group or a channel), with a choice of events: a new account (and how it came: access invitation, organization invitation or open sign-up), a request for access, a workspace upgrading its plan, a payment (plans and compute credits, test payments marked as such) and, off by default, a paid plan that ends. Each message links to the page in the admin panel. Send a test message checks the setup and says what is wrong (a wrong token, a chat the bot cannot write to); the last result is shown. Messages are sent after the page has answered, so Telegram never slows anyone down.
    • AddedInvite-only access. While it is on (the default), the sign-up page says EsaSim is open by invitation and asks for a request: name, email, company, role and what the person would like to do. Each request is emailed to the platform admins (or to the address set for it) and listed in Admin › Requests under Access, with Approve and invite and Decline. Approving emails the person a link to create their account, valid 14 days, once, for that address only (their email is confirmed by it). Admin › Users switches between Invite only and Open, sets where requests go, invites someone directly and lists the invitations sent. People invited to an organization by its admins can still join. While it is on, the website's Start free buttons say Request access. The sign-in pages carry the new message.
    • ChangedDocumentation reorganised for people starting out: Get started (Getting started, How EsaSim works, Set up a machine), Tutorials, Demo projects, Build, Guides, Run and ship, Machines, Teams and account, Reference. The sidebar keeps the first two open and folds the rest. Getting started is four short steps; How EsaSim works explains five ideas first and the rest later. The CT and image curation guides are now part of their demo pages; the drone landing demo page (there is no such demo: it is a template) and the old Workload presets page are gone, and their addresses lead to the right pages. Text left over from before projects lived on GitHub, from preset jobs and from the cloud roll-out was removed or corrected (Pro: up to 20 machines; EsaSim Cloud in development). Screenshots of the dashboard fill the pages that were waiting for them.
    • FixedAPI tokens page: no longer says the REST API comes in release 0.3, nor shows an example call to an address that does not exist; it says the general REST API is in development and points to API endpoints.
    • AddedDocumentation: code is coloured (Python, JavaScript, JSON, shell and HTTP), and every block of code or command has a copy icon in its corner; the dashboard's code and commands get the same icon where they had no Copy button. New tutorial: A project in code, which builds a project by hand in your own editor (a machine block in Python, a blueprint in JSON, project.json), pushes it to GitHub, imports it, runs it and improves it with git. The assistant tutorials link to it.
    • ChangedHome page: a taller hero with more room between the buttons, the cards and the logos; the hero cards glow blue as they reach the middle of the screen; the light/dark switch sits further from Sign in; smaller logos.
    • ChangedHome page hero: the motto Where physical AI is built., with one short line under it (Build it with your AI assistant. Prove it in simulation. Ship it behind your own app.) and without the three points below the buttons; the logos of the Works with strip are a little smaller and dimmer.
    • ChangedWebsite: the message is Build it. Prove it in simulation. Ship it. The home page follows that path: build with AI assistants, prove in simulation, scale from a laptop to your servers and to EsaSim Cloud (in development, with Request cloud access), ship as an endpoint your app calls or a published policy, and work as a team on your own GitHub with roles, limits and an audit log; two doors, for researchers and small teams and for companies; a call for design partners. The platform overview, compute page, menu, About and footer follow. Contact has two new forms: Cloud access and Design partners (Admin › Requests lists them).
    • ChangedDocumentation brought in line with projects on GitHub, results on machines, published policies, teamwork and endpoints: Getting started (Link GitHub, the project's tabs, where to go next), How EsaSim works (where everything lives; published policies, AI assistants and endpoints as concepts), Results and usage, the demo pages (a copy is saved to your GitHub), the FAQ (own GPUs and cloud, teams, your own app, lock-in), Plans, Blueprints, Build your own blocks and AI assistants. Two new tutorials: Build a study with an AI assistant, and From a blueprint to your app (a picture review built, tested and called from Python and JavaScript). The guide EsaSim gives to assistants says where things live and how to make a flow callable by an app.
    • AddedAPI endpoints: publish a blueprint as an endpoint and your own app, service or CI can run it. A project's new API tab makes one from a published blueprint: its name, the version it runs (always the latest published, or one fixed), the settings a call may set (text, numbers, yes/no, choices of its machine blocks, each with a name), calls an hour and minutes a run. It gets an address (/api/v1/endpoints/<id>) and a key (esf_…, shown once). POST …/runs with {"inputs": {…}, "wait": seconds} starts a run on the project's machines in the name of the endpoint's maker; the answer has its status and, once it ended, every file it made with a link, and small JSON, CSV and text files in the answer itself. GET …/runs/<id> reads it again, …/cancel stops it. The draft never reaches an endpoint; the app sees nothing else of the workspace; every call is a run in Runs and in the audit log. Turn off, New key and Remove on each endpoint. Pro and Enterprise. Docs: API endpoints.
    • ChangedA project has eleven tabs with API: next to the GitHub buttons they take a row of their own below 1500 px.
    • ChangedWebsite: new messaging. EsaSim is about finding problems in simulation before they reach hardware or the field (before you build, before you test, before you ship a change), with field failures as one more scenario of the set instead of the starting point. The home page, platform overview, simulation and About pages say so; the home page is shorter, shows what is available and what is in development in one place instead of a label on every block, and its free plan and first-run texts match the product.
    • AddedWebsite: AI assistants page (Product › AI assistants) and a section on the home page: describe a study, the assistant builds the flow, runs it on your machines, reads the results and keeps improving it; through MCP today, EsaSim's own models and an API for agents in development.
    • FixedWebsite logo strip: every logo is redrawn in one tone (light on the dark band, dark on light pages) from its own pixels, so any file works: white, black or coloured, on a transparent or a white background. Inner detail is kept (white letters inside a shape stay open) where the old one-colour filter filled it in, empty margins are cut, and every logo gets the same visual weight whatever the shape of its file. The strip is titled Works with instead of Powered by.
    • ChangedProjects live on GitHub. Making a project (new, from a template, a demo's copy, an import) needs a linked GitHub account and saves it to a repository as it is made; without one, the page says how to link it. Everyone can still open the demos, which move to GitHub too. The EsaSim server keeps each project's row, its blueprints while they are edited, the history of its runs and small results; its assets are a cache that lets go of those GitHub holds when it is full (the least used first, Admin › Integrations: 2 GB) and brings them back when a page needs them. Assets not on GitHub yet are limited to 4 GB a workspace, an asset to 1.9 GB (the most GitHub keeps in one file), and uploads stop while the server's disk has less than 5 GB free.
    • ChangedProjects made before move to GitHub by themselves, one a minute in the background, with the GitHub account of their maker or of the workspace's owner (a repository of their own when that person chose none); a banner says so and Move it now does it at once. A project whose people have no GitHub linked stays until one of them links it. Admin › Integrations shows how many are where and moves the rest at once. Open it from the hosting is gone.
    • ChangedResults of runs stay on the machines that made them again; only small ones (summaries, previews: up to 5 MB each, 25 MB a run) come to the server, up to 1 GB a workspace. A platform admin can keep every result on the server instead (Admin › Integrations).
    • AddedPublishing trained policies: what the blueprints make is no longer saved to GitHub with every change. Data › Publish a version sends the current files of a policy (or any of the project's data) to GitHub as a release of the project's repository, numbered (walk-policy-v1, v2…), at the commit of the blueprints that made it, with your notes; zips of up to 1.9 GB, nothing kept on the server. Published on GitHub lists the versions for everyone with the repository; Bring into this workspace makes the project's data from one; admins can remove one.
    • AddedWorking together on GitHub, as in any development environment. Merges: when a project changed both in EsaSim and on GitHub (a colleague in another workspace, an edit on GitHub, a merged pull request), the two are merged from the commit both started from, blueprint by blueprint (blocks, connections and each setting), the readme and blocks' code line by line, fields and pictures one by one. Only what was changed two different ways waits for a person, on a page that shows what it was, this version and the other (Choose what to keep); everything else is combined. Before, a project changed on both sides had to take one version whole.
    • AddedBranches and pull requests: the branch menu in a project's header lists main and its branches. Start a branch makes a working copy of the project of your own, saved to its own branch on GitHub (esasim/<login>/<name>); main stays as it is. A branch shows how far it is from main, takes main's changes in with Update from main, and opens a pull request into main that says what changed blueprint by blueprint and asks the project's editors with GitHub linked to review it; its state and reviews show above the tabs. Merge into main merges it in EsaSim as a merge commit, so GitHub shows the pull request merged; one merged on GitHub comes in when main is opened. Delete the branch here and on GitHub after.
    • AddedHistory: a History tab lists the commits of the project (or of the branch), with who made them. A commit shows what it changed: each blueprint drawn with its blocks and connections added, removed and changed, settings before and after, the readme and code line by line; Compare with now, and Restore this version (saved as a new commit).
    • AddedCommits: changes saved by themselves become one commit per burst saying what changed, in the name of who made them, with the others as co-authors. Commit (in the project's header) saves now with a message of your own.
    • ChangedImport from GitHub: choose Work on it together (pull: the project saves back to the repository and changes on either side are merged; a workspace that already has the repository opens its project), Make your own copy (fork: GitHub copies the repository into your account; Update from the original and Pull request to the original), or Just a copy. Copies of a project in other workspaces, branches and forks keep the ids the repository knows its blueprints by, so their commits change only what changed.
    • ChangedGitHub window (saving, updating, checking, importing): the GitHub icon at the top centre, above the centred title; it pulses while the work goes on and turns green when it is done, red when it failed.
    • FixedProject settings: a "Save to" button with a long repository name ran out of the GitHub card; it now wraps inside it.
    • AddedGitHub: a project's cover is now saved with it in the repository's assets folder (assets/cover.svg for a built-in cover, assets/cover.jpg for your own picture; assets/esasim-cover.* if the project has an asset of its own called cover) and shown as a banner at the top of README.md, so the repository's page on GitHub opens with it. Pulling the project back (or importing it into another workspace) brings the cover with it, so the Readme page shows it there too; a new cover replaces the old file at the next save. A readme that already has its own banner picture (pictures/banner, cover or hero, or the cover file itself) gets no second one.
    • ChangedReadme pages (a project's Readme tab and the demos): the cover runs across the top of the readme; the text is set wider and easier to read; the side column has the blueprints as a tidy list (name, number of blocks, what each does), with even spacing between its cards, and moves above the readme on narrow screens.
    • FixedPhones: the app's pages used only part of the screen width (the space the hidden side menu takes on a computer). They now use the whole width.
    • ChangedDocs › Projects › Linking GitHub: which token to make and exactly what to enable on GitHub (fine-grained token on All repositories, Contents and Repository creation on Read and write, nothing else; or a classic token with repo), with a table of the messages Save to GitHub shows and what to change for each. The token hints on the profile and block pages and the error messages say the same, with GitHub's current "+ Add permissions" button.
    • ChangedWebsite: the short line before every small heading label (THE LOOP, WHAT ESASIM ANSWERS…) is now a small hexagon, as in the logo, in the label's colour on light and dark sections.
    • AddedWebsite, industry pages (robotics, autonomous vehicles, drones, manufacturing and logistics, defense, healthcare, marine, research): a first section, "The questions EsaSim answers", with five or six questions people in that industry ask (will the grasp hold on the parts we ship, how many robots does the warehouse need, will it land in a gusty crosswind…) and how EsaSim answers each, linking to the demo that shows it where there is one.
    • Fixed3D view 1.78, rocket launches: touching the main view while the rocket stood on the pad switched its camera to Pad (orbiting the launch pad), which stayed behind at lift-off, so the rocket flew out of the picture, and the view remembered it the next time. A drag on the pad now orbits the booster, which the camera follows into the flight; and at each new flight a camera left on the pad or free goes back to the Director, unless it was picked in the camera menu since the view opened.
    • AddedHome page: an "Aerospace" card (train for flights you cannot rehearse, linking to the booster landing demo; hero-slide-aerospace.mp4 or .jpg) and a "Mission training" card in the scrolling cards (a robot trained for its mission, here the legged robot's warehouse patrol) (hero-slide-patrol.mp4 with its first frame hero-slide-patrol.jpg in assets/images/site), linking to Solutions › Robotics.
    • Fixed3D view 1.77, recorded videos: Record (What I see, in real time) used the browser's MediaRecorder, whose files some players call damaged: MP4s written in fragments with repeated timestamps, an MP4 with sound that Chrome filled with VP9 and Opus (which QuickTime, Windows and phones do not play), and WebMs with no duration. It now encodes frame by frame (WebCodecs, as the replay render does) and writes complete files: MP4 with H.264 at a steady frame rate and its index at the start, with AAC sound where the browser can encode it, or WebM with VP9, Opus sound, its duration and seek index. Browsers without WebCodecs keep MediaRecorder, now with the right file name for what it wrote, never a different video codec for sound, and the duration added to WebM.
    • ChangedWebsite: the top bar spans the whole window, with the logo at the left edge, the menu centred and the theme switch, Sign in and Start free at the right edge. Phones keep the menu button.
    • ChangedHome page: a new headline, "Where physical AI gets built.", above it "Data curation, ML, simulation and deployment in one platform" and below it "From data to real-world deployment, on any hardware, local or cloud." Headlines break into even lines on phones.
    • ChangedHome page: the scrolling cards are larger (up to 720 px wide, from 480) and can show animations: put an MP4 (or WebM) next to a card's picture, under the same name, and it plays in place of the picture, only while on screen; the picture becomes its first frame, and is what people see who ask their system for less motion. IMAGES.md says which format and size to use.
    • AddedAI assistants (MCP), platform admins: an assistant connected by an EsaSim platform admin can change EsaSim's own blocks and the EsaSim library with save_block (the block_id of a built-in or library block; only the fields given change, or the whole definition), add library blocks (library: true), and see and undo changes with a new tool, platform_blocks (list, history, revert, use_release, unpublish, republish). A change is in force at once in every workspace, numbered after the release (1.76+1), kept when a new release is installed, and flagged when the release has a newer version underneath; Admin > Shared blocks lists the changed blocks with a button back to the release's version. Everyone else cannot change these blocks: save_block refuses them and platform_blocks is not offered.
    • AddedDocs: Tutorial: blocks that work together. Write a machine block in Python and a view in JavaScript and connect them, in four tested examples with pictures: a CPU benchmark shown as text, live values while it runs, a Stop button in the view that talks back to the running block, and benchmarks on two machines feeding one comparison. A diagram shows the four routes between blocks (result files, live values, messages, output files).
    • AddedBlock builder: a view's input can be of type Live values (stream), so a view of your own can take a machine block's Live telemetry directly (before, only views made by an AI assistant could). Build your own blocks lists the type.
    • FixedChart 1.2: the values axis is as wide as its longest label, so large numbers (22,000,000) are no longer cut off on the left. Table 1.1: whole numbers of a million or more are written in full (22,106,202) instead of 2.211e+7.
    • FixedWorker 0.11, kept awake with the screen locked: on Linux the worker now also holds off GNOME's automatic suspend when the desktop session starts after the worker (a service starts at boot, you log in later) and after a new login; before, only a session already open when the worker started was held, so the machine suspended at the first idle lock. On Windows it adds a power request (powercfg /requests lists "EsaSim worker"). The worker guide shows the commands to turn automatic sleep off on a machine used as a worker (GNOME, systemd, Windows, Modern Standby, laptop lids) and the one-line update for Windows and Linux.
    • AddedYour machines for a project (sessions): the first run of a project keeps the machines you tick for you, and every later run of any of its flows goes to them, placed by what each block needs. While you keep them nobody else's run goes to them (others see In use), so people never wait behind each other's runs. They stay yours while the blueprint is open, while a run of yours goes on, and for an idle time after (1 h, or 15 min to 8 h), with a warning and Keep before they go, 12 h at most with nobody there, never during a run; Release lets them go at once. The run panel shows them, with Change machines and Release; a button by Run says how many and how long. When a session ends its machines forget the project (worker 0.11).
    • AddedMachines: Who may use it, on each machine's page: everyone in the workspace, or only the people an admin ticks (and whoever paired it). The run panel and runs use only the machines a person may use. The page also says whose session holds the machine, and an admin can release it.
    • AddedWorkers update themselves (from worker 0.11): when the site offers a newer worker, each one stops taking tasks, lets the running ones end, downloads the source, checks its SHA-256, builds it in its folder, checks the new program, puts it in place and restarts. The machine's page says where it is, or what went wrong (the old program then keeps running). Worker settings › Update itself turns it off per machine. Workers before 0.11 need one update by hand.
    • AddedMachines keep nothing (worker 0.11): when a task ends, every result file goes to EsaSim, sent in parts so files of any size up to the limit go, and the task folder is deleted once they are there. Any machine with the right hardware can then take the next block, since nothing the run needs stays on one machine. Limits: 4 GB a file, 10 GB a run, 50 GB a workspace (results_max_*_gb in the server config); a file over them stays on the machine, its folder kept, and the log says so. Workers before 0.11 keep working as before.
    • ChangedSpot (project Spot Mini): the training blueprints (Learn to stand, Learn to walk, Slopes and stairs, Take pushes, Learn the warehouse) read the spot-policy dataset, so a training carries on from the stored policy, not from files an earlier run left on a machine.
    • AddedBlueprints show where a run is: by Run / Stop (and in the console and on the View page) a button says "On Server1 PC", "On 2 machines" or "Waiting for a machine"; it opens the list of the run's machines with the blocks each one runs or ran, their progress, and what still waits for a machine (a click shows the block on the grid). Each block's run badge names its machine too.
    • ChangedThe run panel is simpler: Start is at the top as well as at the bottom (it can no longer end up below the window), the machines a run may use are ticked in one list, each block says where it will run in one line with Change to pick a machine or add rules, and saved profiles show only when there are some (Save these choices as a profile… is at the bottom).
    • FixedGitHub: a save that met another save of the same project (Save to GitHub while a change was being saved by itself) failed with "The branch moved meanwhile". Saves of a project now wait for each other, and one that finds the branch moved is put on top of it.
    • Changed3D view 1.76: views other than the main one (Quality balanced or fast, such as the robot's camera) draw their textures at most 512 px wide, a third of the graphics memory for the warehouse, so a page with several 3D views is less likely to run the browser's graphics out of memory.
    • FixedSaving a project (to GitHub, or Download the project) now takes into its assets the 3D view's files its blueprints draw with (the robot's model, the forklift, the person, the textures, the logo, the soundtrack), so assets/ in the repository and the zip hold every model it uses. Before, they came only when someone ticked them in Data > Assets. One taken out of the assets on purpose is not brought back.
    • Changed3D view 1.75, the warehouse: switching the hall lights off (or on) now does it in every 3D view of the run at once, the robot's camera view included, which goes dark with the hall. The floor's reflections are softer where it is worn, scuffed and marked: a roughness map from the same scuffs and wheel tracks as its colours, so the shine breaks up along the tracks and in the busy areas instead of mirroring everywhere.
    • ChangedAI assistants (MCP): reuse first. The server's instructions, get_started (a new reuse_first part), list_blocks and save_block now ask assistants to build flows from the blocks that exist, to extend a block that almost does the job with a new version rather than write a copy, to write a new block only for what no block does, and to give data to the existing views (the 3D view, charts, tables…) instead of writing new ones. get_started also describes project assets, ctx.assets, and the robot format of the 3D view (any number of joints, trees, joint types, several robots). New tools: list_assets and project_assets.
    • ChangedThe 3D view's description says what it is: one view for every kind of project, drawing what the project gives it (its inputs and its assets), robots of any shape included. The 3D scenes guide has a part on robots and on what the project gives the view.
    • AddedProjects have assets (Data > Assets): the files their views draw with, 3D models, textures, sounds, anything else, in folders. Drop files or folders on it. They are the project's: saved with it to GitHub (assets/, the large ones as release files), in its zip, taken back on import and update, compared by the check, and saved by themselves for a project opened from GitHub. The project gives them to its views (ctx.assets in a view's code). Take the 3D view's own copies into this project copies the models and textures a project uses (Spot, the forklift, the intruder, the flashlight, the logo…) into its assets.
    • Changed3D view 1.74: it draws with what the project gives it: the robot's meshes, the props, the textures, the logo and the soundtrack come from the project's assets, found by name; robot models too when none is wired in. Its own copies serve only projects that have none.
    • Changed3D view 1.73, robots: no limit on the number of joints (it took 12): a robot is posed by j1, j2, … as many as it has, by a list ({"q": […]}) or by the joints' names ({"joints": {"shoulder": 12.5}}), in degrees or radians ("units": "rad"; a model can say "angle_units"). A robot file can be a tree, not only a chain (a joint names its "parent": hands, legs, two arms on one body), with revolute, continuous, prismatic (a lift, a slide) and fixed joints, a "tool" joint and a "base" where it stands. Every robot wired in is shown, each posed by the items that name it ("robot") and placed by a robot object of the scene; the head-up display lists each. The view frames the whole of a tall or wide robot.
    • AddedSettings > Export: Download the project now includes the files its blueprints make (trained policies), and Projects > Import or Update from a zip brings them back into the project's datasets. New: Download results and policies (every run's files with what each run was, and the policies) and Load results, which puts them back into this project or another as imported runs (runs already there are skipped). Zips are made on the server, files of machines fetched first, with each step shown; zips sent back go in parts, past the server's upload limit.
    • AddedProjects open from the hosting or from GitHub (Settings > Opens from). Save to GitHub now checks the repository against the project (blueprints, blocks, readme, pictures, and every zip of its files downloaded and compared) and, when GitHub holds all of it, the project opens from GitHub from then on; demos stay on the hosting. A project opened from GitHub is saved there by itself a few seconds after each change (blueprints, settings, readme, pictures, the blocks it uses, new files its runs make); opening it takes in changes made on GitHub; when it changed both here and there, you choose which to keep; when GitHub cannot be reached, the copy here opens.
    • AddedGitHub: a project saved to GitHub takes the files its blueprints make (every dataset a blueprint writes, such as a robot's trained policies), so the repository holds the whole project. Each goes zipped: into the repository up to 20 MB a zip, while its share stays under 1 GB, and into a release of the repository (esasim-files) when larger. esasim-files.json lists them; unchanged files are not sent again. Importing or updating the project from GitHub brings them back into datasets of the project, and the blueprints point at them. The data the blueprints only read stays in EsaSim.
    • FixedUploads (the assistant's upload_file, files dropped on Project > Data) no longer choose EsaSim storage when the server keeps no files.
    • AddedProject > Data: drop any number of files or whole folders on the page (or choose them) and they go into one of the project's data folders, or into new data made for them on the machine you pick, named after what you dropped. Two files travel at a time, each with its progress; one new version is made for all of them. Files of every kind go, without extension or hidden ones too.
    • AddedAI assistants (MCP): a new tool, upload_file, puts files into a project: into one of its datasets, or one made for the project on the first upload; text as it is, any other file (a trained model, a picture, a zip) as base64, a large file in parts; each upload, or several together, makes a new version of the dataset. It needs Build access and the editor role in the project; files for a machine's folder are written by its worker.
    • PlannedMore data blocks: ROS bag and MCAP readers, frame extraction from videos, detectors, deduplication by embedding; Azure Blob storage.
  2. v1.0Planned

    Cloud GPUs

    • PlannedCloud targets, enabled per provider from the admin panel as capacity is added; blueprint blocks in containers (Python, PyTorch) on EsaSim Cloud.
  3. v0.12.85Nov 10, 2026

    Machines that fit, email you can check, a simpler overview

    • Changed3D view 1.72, the warehouse: the office glass reflects the hall (taken from the hall itself, again when the lights change) with soft glints; the robot's lights come on when the hall's go off, wider, softer, with the light they scatter lighting what is round the spot, and the beams in the air left out of the robot's own camera; the Lights switch acts on every view of the session; fire points (a detailed extinguisher on its bracket under a FIRE POINT sign) and first-aid cabinets on the walls; the EsaSim brand on signs high on three walls, over the office door and printed on some cartons.
    • Changed3D view 1.72, the patrol: what the robot hears and finds is said on the view as it happens (a banner at the top: amber for a sound, blue for something seen, red for an alarm), whether the log is shown or not; recordings and pictures now carry everything drawn over the view (the alerts, the log card, its events and map, the robot's numbers). The camera starts on Director and keeps it: only a real drag hands over to Orbit (a click, a push, a button no longer does), and the camera kept for next time is the one picked.
    • Fixed3D view 1.72: the robot's footsteps were silent in the warehouse.
    • Changed3D view 1.71, the warehouse: a Lights button switches the hall's lights off and on (off: complete darkness but for the robot's own lights; the view remembers it); the robot's lights throw a real torch's beam pattern (a hot centre and soft rings); the intruder wears dark clothes and walks like a person (heel to toe, the knee bending as the weight comes on and folding in the swing, the hips turning and swaying, the arms swinging against the legs, starts and stops eased) and runs leaning in, its arms bent; the robot leaves no footprints in the warehouse (the training grounds keep them).
    • Changed3D view 1.70, the warehouse: the conveyor turns the corner on a curve, its tapered rollers fanning round it; its guard and red pull-cord run along the side facing the hall, not the wall.
    • Changed3D view 1.69, the warehouse: a faint cone of light under every ceiling lamp (soft discs strung down its axis, like the robot's lights); the forklifts' forks worn to bare steel on top and at the tips, scraped along their length, the shanks scuffed through the paint.
    • Changed3D view 1.68, the warehouse patrol: cartons that fall from the racks are drawn where the physics puts them (they tumble, land, can be knocked by the robot and no longer pass through other cartons); spare ones wait out of sight.
    • Changed3D view 1.67: the beams of the robot's lights are a row of soft discs, still and equally spaced along each light's axis, small and brighter at the lamp, wider and fainter out to about 70 cm: a faint cone of light in the air; the moving specks of dust are gone.
    • Changed3D view 1.66, the warehouse: racking like the real thing: orange beams with rounded edges and lighter blue uprights in glossy powder-coated paint that reflects the hall's lamps, galvanised bracing and decks; the floor lines along the racking are yellow paint, chipped, worn and scuffed by tyres. The robot's two lights sit in the small windows either side of its cameras, and the beams in the air are a few faint specks of lit dust that fade within a couple of feet (no cone).
    • Changed3D view 1.65, the warehouse: a row of racking along the west wall (racks along either axis, one or two deep); the conveyor runs along the east and dock walls, with four bays painted on the floor in front of it (a pallet loaded full, one with a few cartons, an empty one, a free bay) and a wheeled recycling bin; the office has a desk with a computer in the middle and three chairs; the robot's charging dock stands on the mezzanine by the office. Bluer uprights, grey decks, less fill light (darker under the shelves). The robot carries two front lights by its cameras: each lights the floor ahead, with a faint beam and a lens flare toward the camera; the blue fan in front of it is gone. No guide marks on the warehouse floor (checkpoints, area names, labels); the training grounds keep theirs.
    • Changed3D view 1.64, the warehouse: more like a real hall: a faint haze the colour of the walls, the walls shaded (darker under the roof, at the foot and in the corners), high-resolution concrete blocks, glossier steel racking reflecting the hall, darker and softer shadows over the whole hall (no edge where they stopped), a weaker glow on bright surfaces. The staging area and the floor pallets carry stacked cartons like the racks; the hanging aisle signs and the pallet truck are gone; the dock doors stand between the wall's columns, without the black bumpers. The racking in more detail: the beams hook onto the uprights by connectors round them, a deck board on every level under the pallets, plain powder-coated beams, rounded yellow guards at the rack ends, scuffed and scraped. The loose cartons on the floor move as the physics moves them. The intruder walks, and runs when it is seen.
    • Changed3D view 1.64: the Free camera of the robot views is walked with the mouse: drag left and right to turn, up and down to go forward and back; right-drag (or Shift-drag) to look up and down and step sideways; the wheel goes forward and back; W A S D or the arrows, Q and E down and up.
    • Fixed3D view 1.64: the fronts of the steel stair treads flickered (the yellow nosing and the tread shared a face).
    • Changed3D view 1.63, the warehouse: a brighter hall like a real distribution centre: a blue-grey epoxy floor with white aisle lines, painted brick walls, grey steel racking with braced frames and orange beams, pallets with fork openings carrying cartons of several sizes stacked by hand (a little out of line, some missing on top; brown, light and white boards, FRAGILE print, labels, tape), yellow guards and numbered signs at the rack ends, a stronger glow on lights and reflections. Two forklifts parked (a model by Kamran Mughal, CC BY 4.0); the intruder is a person model (by Next Stop Willoughby, CC BY 4.0) that walks, and crouches when hiding.
    • Changed3D view 1.63, the patrol: a Log button in the bar shows or hides the mission card, the event list and the map of the hall (off at first; the view remembers it), and the Picture and Record buttons are no longer hidden behind them. The robot's round and its plan are no longer drawn on the floor (the map still shows them). The credit line at the bottom of the robot views is gone (the credits are in the blocks' help). The elevation-map dots around the robot are not drawn in the warehouse (Sensors still shows them on the training grounds).
    • Fixed3D view 1.63: in the warehouse, a training lane (dark asphalt with dashes) was drawn across the hall and up the racking; the hazard stripes on the dock door posts ran the wrong way.
    • AddedAI assistants: a block's code too large for one call can be sent in parts (save_block_part, up to 50 parts, each from a different call if need be), then saved with save_block and code_upload. The parts are joined exactly as sent and kept for a day.
    • ChangedAI assistants: save_block can change a workspace block's definition alone (its settings, help, or the machines it needs) without sending its code again; the new version keeps the code it has. Large blocks (a robot simulation of 200 KB) no longer have to be uploaded whole for a change of settings.
    • AddedBlueprint: next to the run's progress bar (under the flow and on the View page) the percentage is written out, and a clock shows how long the run has been working, ticking each second, and after the run how long it took (it reads 1:02:05 past an hour). Before a machine takes the run it says waiting for a machine.
    • FixedA workspace block (one you or an assistant made) whose outputs go to a dataset on another machine could not send them: the run said The outputs of this block go nowhere else, and the files stayed on the machine that ran it. EsaSim now finds the workspace's own blocks there too.
    • AddedBlocks of a workspace can choose their machines by a setting (hardware_by, as the built-in blocks do): the Quadruped block sends its training (Run on: auto) to a machine with an NVIDIA GPU. The assistant's get_block and save_block show and take it.
    • Added3D view 1.62, the warehouse: aisles cluttered with pallets left on the floor and fallen cartons, a roller conveyor (chrome rollers, cartons riding it, a pull-cord) crossed by a steel step-over bridge, a dispatch platform with steps and a ramp; steel stairs with grating treads, yellow nosings, stringers and handrails. The mission panel shows where a four-legged robot aims its cameras when it looks around with its body.
    • Fixed3D view 1.61: a black layer could flicker over the picture (seen with Spot learning to stand and to walk, and in the warehouse). A pixel drawn as not-a-number, or too bright for the picture's buffer, was spread by the glow (bloom) over squares of the screen or the whole of it, for the frames it was there. Such pixels are now cleaned before the glow, in every 3D view that has one (robots, drones and fleets, rockets, generated scenes, cars). Spot's stand-up replays are now titled learning to stand up.
    • Added3D view 1.60: four-legged robots (Boston Dynamics Spot from MuJoCo Menagerie): its four feet in the footprints, the head-up display and the telemetry window. A warehouse for patrols: a 42 x 25 m hall with docks and roller doors, pallet racking full of goods, staging, a mezzanine office with glass walls, a ramp and stairs, lit by high-bay lamps with shadows over the whole hall and textures with relief (concrete, steel, cardboard, wood, stretch wrap); people, forklifts and fallen cartons; sound rings, the robot's route and field of view, alarm beacons and a siren; a mission panel, an event feed and a map of the hall. In the warehouse the cameras never end up inside the racking.
    • FixedDriving a humanoid robot by hand was hard: what you saw came two to three seconds late, so it kept turning after you let go and you steered against it. The 3D view now plays live frames only as far behind as their arrival needs (often under half a second instead of 1.2 s), the page can read a run's telemetry five times a second (Telemetry block: Read every 0.2 s, as the Playground flow does), the block sends frames ten times a second and eases its commands in and out, the numbers show at once what you ask, and in the playground the camera stays behind the robot (its left is your left) instead of cutting to shots from the front. Left alone, it no longer drifts round: it keeps its heading until told to turn.
    • ChangedBlueprint: choosing a dataset lists the project's own datasets (those its flows read or write, and those its runs used); the workspace's others are one choice away (Other datasets of the workspace).
    • AddedBlocks: a text setting can pick one of the files wired to an input (files_from), narrowed by another setting (by and match). The Humanoid block's Walking policy uses it: the walking policies of the robot chosen, in the datasets wired to Policies, newest first.
    • AddedHumanoid block 10: Ground: Playground, for Walk: an open floor with a sandbox (soft sand the feet sink into), a pool of 10 cm of water that drags at the feet, gravel, stepping stones, two curbs (6 and 10 cm), ice and a few steps, where you drive the robot by hand (forward, back, turn, step aside) with its newest policies. Humanoid training has a fifth flow, 5 · Playground.
    • Added3D view 1.58: a drive pad for Controls (a line drive): buttons held to drive (forward, back, turn left and right, step aside, stop) and the keyboard (W A S D or the arrows, Q E, Space), sending drive = {x, y, turn} to the running block. Humanoid robots: the playground drawn (sand with footprints, water with ripples and splashes, gravel, stepping stones, curbs, steps); the numbers say how it is driven.
    • AddedHumanoid block 9: a square of smooth ice on the circuit (4 x 4 m, friction 0.08, on side 4), where the feet slide; robots learning the circuit start near it now and then, and Walk says when it is on the ice. Push in Walk is now a push by hand on the part of the robot you click.
    • Changed3D view 1.57, humanoid robots: Push is a hand. Click it and it stays on, the pointer an open palm: each click on the robot pushes the part clicked (an arm, the torso, a knee), the way the camera looks, as hard as Push strength says; click Push again or press Esc to stop. A fall now sounds like a footstep, louder. The ice is drawn on the circuit, glassy in a steel frame, and named on the floor.
    • ChangedProjects list their flows in the order of their names everywhere (Blueprint tabs and list, runs, results, the readme made from the flows): number them (1 · …, 2 · …) to set the order; 10 comes after 9.
    • AddedHumanoid block 7: a Robot setting: the Unitree G1 (the default), the Unitree H1 (1.8 m, 19 joints) or the Apptronik Apollo (1.7 m, 32 joints), from MuJoCo Menagerie. Each robot keeps its own policies, named for it (humanoid_h1_walk_…, humanoid_apollo_standup_…; the G1's as before): Continue and Walk use only the chosen robot's and leave the others in the dataset as they are, so switching robot loses nothing. The falls, the standing test, the elevation map and the help to stand up scale with the robot's height and weight.
    • Changed3D view 1.56, humanoid robots: draws the robot the block sends (the G1, the H1 or the Apollo; a run of another robot swaps it), with its own credit, footprints the size of its feet, falls judged for its height, cameras placed for its size, and the telemetry board with all its joints.
    • AddedDocumentation: a Demo projects section, with a page for each demo project to get started (drone landing, text to image, text to video, data curation, CT to 3D anatomy, warehouse fleet, booster landing): what it shows, its flows, what it needs and how to run it, each with a picture; Images and videos from text (models, GPUs, reviewing and keeping the results), Curate an image dataset (the checks, the review grid, Hugging Face), From CT scans to 3D anatomy (reading scans, 3D models, the soft-tissue model), and rocket flights in 3D scenes and rendering. Getting started, Runs and jobs, the FAQ and Build your own blocks now say that work starts from a blueprint, which machine takes each block, and how to rename a setting's choices.
    • ChangedWebsite: the home page shows generative AI, image curation and medical imaging, and demos to start from; Simulation lists the ready-made flows (landing sweep, warehouse fleets, rocket launch and landing, soft-tissue anatomy); Data and curation, Blueprints, the platform overview and Medical and healthcare list what is available now.
    • FixedText to video runs were marked lost after the first video: streaming it live made the worker's report larger than the 256 KB EsaSim took, so the report was refused again and again and the task looked silent. Reports now take as much as the host allows (up to 32 MB), a report that cannot be read still keeps its task alive, and Text to video sends its pieces one at a time, slowly (about 160 KB a second), so even a host that limits requests to a few hundred KB, or a slow uplink, takes every report. Worker 0.10.11 also keeps each report of live data under about 512 KB and, when the host refuses one (413, 403, or three failures in a row), sends it again in smaller parts instead of the same one forever.
    • FixedText to video on Windows: after a few videos the GPU could stop with a CUDA "unspecified launch failure" while the model's layers were copied on a second stream from pinned memory. On Windows the copies now wait their turn (a little slower, steady). If the GPU still stops, the videos made before are kept with their tables, and the log says why and how to make only the rest.
    • FixedA block that fails now ends without Python's clean-up, which after a GPU error crashed the process and buried the block's own message.
    • Changed3D view, cars on a ramp: the stunt's own car (a licensed model) is shipped with the view, so it is drawn without wiring anything; one white line runs down the middle of the ramp and on along the tarmac; the jets' plumes are white puffs of cold air that spin fast as they leave the nozzle and slower as they grow, small on the flanks, large below and behind; no dust. The chase camera stays off the ramp's open side while the car is on it, at its top and falling from it (behind the car it was inside the tower).
    • Added3D view, cars on a ramp: an air-system panel under the numbers: the car from above with its two tanks and their level in %, the two suction fans, and the ten nozzles, each lit while it blows, with its thrust in % and the direction it blows.
    • Fixed3D view, cars on a ramp: the car's windows showed through the jets' plumes; the plumes now hide them.
    • Fixed3D view, cars on a ramp: a stunt run no longer stutters. The run is computed whole before it starts, so it is now sent to the view at once with the moment it starts, and the view plays it on its own clock (with its 3, 2, 1): nothing on the way can hold the car still, and a recording of the view is as smooth.
    • Changed3D view, cars on a ramp: shadows everywhere the car goes (a floodlight from high up whose shadow map follows the car); the car's glass is black; its two headlights; the old drawn car is never shown (only the stunt's own model, or one wired to the view); the red light lines along the run-up light up from the ramp out to the car and follow it; the foot of the ramp and the road no longer flicker against the tarmac.
    • Added3D view, cars on a ramp: a soundtrack that plays in a loop (shipped with the view); the Music button turns it off and the choice is remembered; a recording of the view takes it in, even with the sound effects off.
    • Changed3D view 1.47, cars on a ramp: pictures and recordings show what is over the scene: the 3-2-1, GET READY and the result, and with Sensors on the numbers and the air system panel. Sensors (remembered) now shows or hides the numbers and the air system panel too, besides the laser beams. GET READY shows in every view of the page as soon as Start is pressed in one. The headlights' flares are never cut off by the tarmac; the stage lights at the foot of the ramp throw visible cones of light and flare when you look into them.
    • FixedViews of a run (3D views, charts, gauges) crashed after a while, all at once, with long runs that send large live items (a simulation's replays): once a Telemetry block's Keep the last was reached, the page sent each view the whole stream again on every read, megabytes a second, until the browser ran out of memory. Views now get only the new items, and drop as many old ones as the stream does; the page keeps at most the newest 600 large items of each block and channel; the 3D view frees the old scene's textures when it builds a new one and forgets items long gone.
    • Fixed3D view 1.47, cars on a ramp: the stunt no longer stutters or hangs (nor do its recordings). The reflections render one face of their cube a frame, small, instead of all six at once every third frame; puffs that have faded are no longer drawn (they were still filled, pixel by pixel, at their last size) and a puff by the camera is capped in size on screen; the fixed views (car: chase, car: side, car: telemetry) draw 30 frames a second; a view that lowers its resolution to keep up raises it again only after a long steady spell, so it never seesaws.
    • Changed3D view 1.47, cars on a ramp: the telemetry window keeps the charts of the last run, whole, until the next one starts. The thrusters' plumes are cold air: heavier than the air round them, they sink and spread out flat over the tarmac, growing as they thin out; after a valve shuts the air left in its line keeps bleeding out for a few seconds, a weak plume with a soft hiss and no thrust. The tarmac is darker, and so is the concrete of the ramp and the road (its white line stays white); the flank nozzles show the same high-pressure jet cones and plumes as the ones underneath; the soundtrack is no longer taken from the browser's cache when it changes.
    • Added3D view, cars on a ramp: a telemetry window of its own (camera car: telemetry): instead of the 3D scene the view shows every sensor of the car on charts over the whole run, drawn up to the moment the stunt shows and in step with the other views: speed, vertical speed, height with the floor and roof laser rangefinders, how far off the white line, tilt and nose angle, the gyro's turn rates, the load in g, and the nozzles, fans and air left. It plays no sound and draws no 3D.
    • Changed3D view, cars on a ramp: the red lights along the barrier have red rims and a star-shaped lens flare when you look into them; the car's headlights flare when it faces the camera; its tail light strip is a row of LEDs along the strip's real shape, each with its red glow, so the line of light glows over the bodywork round it seen from behind (brighter when it brakes); the tarmac is asphalt: fine grains with their relief, a little rougher or smoother here and there, faint wear; the car's underside shows its belly plate (seams, rivets, the air tanks' shrouds, the fan grilles); the countdown is large numbers that grow as they fade, with a deep hit instead of beeps.
    • Changed3D view, cars on a ramp: real reflections: a cube camera at the car renders the scene around it a few times a second, and the car's clear-coated paint and glass mirror the ramp, its tower, the lights and the tarmac (not with quality fast). The gas cloud lasts longer. A safe landing on the line ends with CAR LANDED!. Start shows GET READY at once until the countdown. The onboard camera is gone (car: onboard is no longer a camera setting).
    • Changed3D view, cars on a ramp: a follow spot high on a tower keeps the car in a pool of light and throws its shadow (the fill light dimmed, the tarmac darker); the car's two headlights light the ground ahead of it; its brake light shows when it brakes; the suction fans sound like air being sucked in under the skirts, and the motors' whine is softer.
    • Changed3D view, cars on a ramp: sounds: each jet has its own voice, on and off with its valve and placed left or right where it is on the car; the suction fans sound like rushing air; every wheel thumps as it touches down and the touchdown is louder. The panel shows how far off the white line the car is and how askew; a safe landing off the line ends with OFF THE LINE.
    • Fixed3D view, cars on a ramp: when the live data reached the browser late, the view ran out of frames and held the car still in mid-air until more came. It now plays as far behind as the data takes to arrive, so the car always moves as the physics computed it.
    • Added3D view, cars on a ramp: a crash breaks the car (dented where it struck, wheels and panels coming off and tumbling on the tarmac, glass shattering, sparks while it scrapes); the beams of the car's two laser rangefinders (Sensors button); and sound for all of it (Sound button): the motors, tyres, suction fans, the jets and their valves, wind, the countdown, the touchdown and the crash.
    • ChangedDemos: a demo of a project you are a member of opens the project itself, with all its tabs (Data, Blueprint, Runs, Results...), not only its readme. "as others see it", under the card, shows the demo page everyone else gets.
    • AddedMenu: the dot of an open project blinks green while one of its runs is going, so the menu shows at a glance which projects are running. It follows runs as they start and end, without reloading the page.
    • AddedBlueprint: the panel on the right can be widened or narrowed with the mouse: drag its left edge (the arrow keys work too once it has focus). The width is remembered in this browser; double-click the edge for the usual width again.
    • Added3D view: cars on a ramp (esasim.car/1, from the Ramp stunt project): the stunt at night with a crescent ramp on its steel tower, red lights along a barrier mirrored in the tarmac, the car with its wheels turning, steering and riding on their springs, its cold-gas jets with their fog and dust, and broadcast-style cameras (Director, Chase, Orbit, Side, Onboard; car: chase, car: onboard and car: side for fixed views). A GLB or glTF car model wired to the view takes the place of the drawn car; its parts named wheel turn and steer.
    • AddedText to video: LTX-2.3 and LTX-2.5 (19B, by Lightricks), which make the sound with the picture and put it in the MP4; LTX-2.5, distilled to 8 steps, is the best open model in the list. Both are under the LTX-2 Community licence (free under US$10M of yearly revenue); LTX-2.5 is gated and needs a Hugging Face token. Only the parts the pipeline uses are downloaded.
    • ChangedText to video: Wan 2.2 TI2V (5B, 720p) is the default model. LTX-Video 0.9.5 was removed: its videos were too rough (animals with extra legs). Flows that chose it, or saved the earlier names of the models, keep working: a block can now rename a choice of a setting (renamed) and saved flows follow.
    • FixedText to video went to any free machine, then stopped after installing its packages when that machine had no NVIDIA GPU. Its runs now go only to a machine with an NVIDIA GPU (and wait while none is online; the blueprint says so before you run), unless Accelerator is set to CPU. Text to image, Embed images and the fleet blocks do the same when their Accelerator names NVIDIA GPU, Tenstorrent or CPU.
    • FixedEmails sent through the email service (sign-up confirmation, password reset, invitations, notices) could be refused before reaching it, while the admin test went through: web firewalls in front of sendserviceemail.php (ModSecurity's XSS rules) take HTML with style attributes, which every designed email has, for an attack. The designed HTML now goes in base64 (body_b64), with a plain version without attributes in body; update sendserviceemail.php on the email server from the release to send the designed version. A refusal by such a firewall is now named in Admin → Email.
    • FixedSend again (the confirmation email) said the link was sent even when the mail service refused it; it now says when it was not sent.
    • ChangedBlueprint editor: the page you are on, Blocks or View, is shown in blue in the switch at the top left.
    • ChangedHome page: the dark hero carries on under the Powered by strip, down to its line.
    • ChangedStylesheets and scripts are fetched again whenever their file changes, also by an update that keeps the version number, so a partial update shows at once.
    • ChangedOverview: no more New job button; jobs start from a project's blueprint, so the button, the empty state and the Get started step now lead to Projects. Recent jobs show their project and flow and open the project's run page.
    • ChangedAdmin → Email uses the full width like the other admin pages: what is sending and the last week at a glance, the four ways to send as tiles, the email service and SMTP side by side, then the test, what to check when a message does not arrive, and the recent messages.
    • AddedAdmin → Email: the test goes to any address, and can be the confirmation email new accounts get, to check delivery to mailboxes other than your own. Admin → Users: Send the confirmation email again, for an unconfirmed account.
    • AddedBlocks: hardware_by in a block definition narrows the machines a block may run on by the option chosen in one of its settings.
    • FixedRuns: Stop after in the run panel started at 120 minutes whatever the flow asked, so a training block set to run 240 minutes was stopped halfway and lost the policy it had not written yet. The panel now starts from the longest duration a block asks for (its Minutes setting) with a margin, warns when Stop after is shorter, and run_flow and the API use the same default.
    • AddedBlocks: ctx.time_left() says how many seconds remain before the run's time limit stops the block (ctx.max_minutes is the limit), so long blocks can finish in time and keep their outputs. The Humanoid G1 block uses it: learning ends three minutes before the limit and the policy is written.
    • AddedViews can start runs: a view whose block asks for it (Starts runs, or "permissions": ["run"]) calls ctx.run({params}) on a click to run its flow with settings of its own for that run only, such as a prompt, so the View page works like an app. One run at a time, placed like the last run, with the runner role; the settings are checked against the blocks' own and written in the run's log.
    • AddedPrompt view: a prompt box, optional fields, a Generate button and the last prompts. Wire a generating block (Text to image, Text to video, an Agent) into it: Generate runs the flow with the prompt and the pictures, videos or text appear in the same view.
    • ChangedViews: ctx.sources gives the node id and title of each block wired in; ctx.saveState(obj, true) saves at once.
    • FixedAI assistants: an app connected with Read access (as ChatGPT often asks for at first) could not create projects or change flows, and could not say why, because those tools were hidden from it. Every tool is now listed, and those the connection cannot use say which access they need and how to get it. The EsaSim screen where you allow an app now starts on Build.
    • AddedDocumentation: AI assistants (MCP) explains how to connect ChatGPT (Developer mode, Create app, Build access) and how to give a connected app more access.
    • FixedViews opened in the middle of a long run waited for things sent only at its start: the Humanoid training 3D view said Waiting for the robot while the charts moved, because the robot's description had fallen out of the newest items its Telemetry block keeps. A view now also gets the newest item of each kind of every channel (a robot's description, a world's layout) however long ago it came, live and after reopening the page.
    • Changed3D view (1.55): a 3D view with nothing to show no longer plays a sample drone landing. Until a run sends something it shows an empty floor with the esacode logo at the origin and the axes rising from it.
    • Added3D view (1.55): the humanoid hall has the esacode logo and the EsaSim name painted on both long walls, over the circuit and 32 m either side, and the logo painted on the floor in five places: in the middle of the circuit and around it.
    • AddedProjects: My projects and Demos have a search box above the cards. It filters them as you type, by name, description or type; / jumps to it, Esc clears it, and the search stays in the address.
    • AddedDocumentation: Robots: from simulation to real hardware, on training robots, what makes a policy work on the real robot, and the plans for robot descriptions, robot categories and bridge machines that run policies on real devices.
    • ChangedDocumentation: Runs and jobs describes the run panel (the pool, cluster profiles, placing each block, tags, data copied to the machine that runs a block, Stop after); Build your own blocks lists ctx.time_left() and ctx.max_minutes; pages that sent you to Data › Projects, Data › EsaSim library or My computing now point to the project's Results tab, the Library block and Local computing.
    • ChangedWebsite: Compute shows runs spread over several machines with the run panel; Simulation adds humanoid locomotion and training any robot from its description; Robotics adds legged locomotion, recovery skills and the robot description that will connect simulation and real hardware.
    • Added3D view (1.53): a humanoid that falls makes a crash (a heavy thud, the slap of the body and the ring of metal), as loud as the fall is fast; it sounds once per fall, live and in replays.
    • ChangedComputing: the tabs are Local computing (was My computing), Cloud computing, Jobs and Analytics, in that order. Jobs no longer has a New job button: runs start from a project's blueprint.
    • RemovedData: the Projects and EsaSim library tabs. Projects keep their results under each project's Results tab; the library's files are chosen in the Library block of the blueprint editor. Their old addresses open Datasets.
    • AddedRuns: data follows the work. A block whose dataset is in a shared folder of one machine used to run only there, even when the run panel left that machine out (a run then waited for it while the chosen machine sat idle). Now, when the pool, a machine or tag chosen for the block, or its rules leave the data's machine out, EsaSim copies the dataset (up to 2 GB) from that machine to the one that runs the block, which starts once it has arrived; the same when a whole run is sent to another machine. Larger datasets still keep the block on their machine, and the panel says so. The run panel, the run's log and the editor's checks say which happens and why; a file that cannot be copied fails the block with the reason.
    • AddedBlueprint: Run opens a panel that slides in from the right, beside the grid, instead of a dialog. It has a pool of machines to tick, where each block runs (any ticked machine that fits, one machine, or machines with a tag) and rules per block (accelerator, at least so much VRAM or RAM, the same machine as an earlier block, a block's parallel tasks spread out or packed on one machine), with a live line per block saying where its tasks would go right now. Blocks held to a machine by their data say so and stay there.
    • AddedCluster profiles: a pool and its rules saved under a name, for one project or (for admins) the whole workspace, chosen in the run panel; a flow's panel opens on the profile it last ran with. The MCP server's run_flow takes a profile, list_profiles lists them, and list_machines shows each machine's tags, VRAM and RAM.
    • AddedMachines: tags (such as gpu or lab) under Settings on a machine's page, for run profiles to place blocks by.
    • ChangedRuns: the machines check a run's placement when they take a task, so rules hold however tasks are queued; a run whose rules no machine of the pool can meet is refused at the start with the reason, rather than waiting forever.
    • Fixed3D view 1.52, humanoid: the stairs' treads (the circuit's staircase and the practice flights) drew without their top surface, so each step looked hollow from above; they are solid now.
    • Added3D view 1.51, humanoid: the circuit: a lane round a rectangle with rounded corners, a concrete staircase (10 steps up, a landing, 10 down) with yellow nosings and handrails, a square of 64 moving tiles that rise and fall in step with the simulation, and a training yard of four flights (6, 9, 12 and 15 cm risers) inside it; cameras follow the circuit's turns.
    • Added3D view 1.51, humanoid: Sensors shows the elevation map the robot's policy reads, as dots on the ground coloured by height.
    • Fixed3D view 1.51, humanoid: Sound off now silences everything the view plays at once; fixed views (follow, side, front, eyes, depth) play no sound of their own, so only the main view is heard; the motors' whine is about 22 dB quieter.
    • Added3D view 1.50, humanoid: a test course when the block sends one, built from the same numbers as its physics: a square of bumps, a concrete ramp up to a 0.5 m plateau and down again with grooves and yellow-and-black edges, a square of blocks of different heights in steel edging, each named on the floor; the lane runs over the ramp, the cameras ride up and down with the robot and Sensors says what it walks on.
    • Added3D view 1.50, humanoid: Robot's eyes and Depth camera show what the RealSense camera in the G1's head sees and measures (distance in colour, red near to blue far); humanoid: eyes and humanoid: depth fix a view on them.
    • Added3D view 1.50, humanoid: telemetry makes a view a telemetry window: charts of speed and turn (asked and measured), height above the ground, attitude, gyro, accelerometer, the load on each foot and the legs' angles and torques, beside a board of all 29 joints, in step with the walk.
    • Added3D view 1.49: a humanoid robot learning to walk (esasim.humanoid/1, from the Humanoid G1 block). A Unitree G1 (a rigged model by KenzoDkohno22T, CC BY 4.0, shipped with the view), each of its bones placed where the simulation puts the link of the same name, walks down a lane in a test hall: polished concrete that mirrors the lights, ribbed walls, light bars on the ceiling, soft shadows and ambient occlusion, a start line and a marker every 5 m. While it learns, an episode is replayed now and then; with Walk it walks live and is steered from the bar (speed, heading, a push, reset).
    • Added3D view 1.49, humanoid: arrows on the floor show the speed and turn it is asked for and what it does; footprints stay a while and each step lands with a thump (Sound). Sensors shows speed asked and done, the turn, how far off the line it is, the height of its pelvis and the load on each foot. Cameras: Director (cuts between side, front, follow, low and crane shots), Follow, Side, Front, Orbit, Free; humanoid: follow, side and front fix a view for a wall of views.
    • Added3D view 1.48: a resupply drone in a village (esasim.resupply/1, from the Resupply drone block). A Mediterranean hill village built from the block's layout: plastered houses with flat roofs behind parapets, windows with shutters, doors, balconies, awnings and bougainvillea, water tanks, solar heaters and dishes on the roofs; a mosque with its green dome and minaret, a water tower, a telecom mast, olive groves, palms and cypresses, walled yards, parked cars, lanes, paved plazas, street lamps with their wires, hills all round. The light follows the hour of the day (the sun's place and colour, dusk, night with lit windows, street lamps and the moon) and the weather (clear, haze, overcast, rain with wet streets and falling rain, dust, fog), with clouds, shadows over the whole village and ambient occlusion (high quality).
    • Added3D view 1.48, resupply drone: the heavy quadcopter with its rotors (blurred discs as they speed up), nav lights and strobes, a landing light at dusk, the casualty-care kit under it that stays on the ground once released; the dust its rotors blow off the ground; the base (a pad with its lights, a windsock that turns with the wind) and the medic's plaza (an orange marker, a strobe, green smoke drifting downwind, a field tent). Sensors shows the numbers (GNSS: a good fix, jammed, spoofed or caught; how well its cameras navigate; its navigation error; landmark fixes; battery), a map (the way flown, where it thought it was, the jammed area, the landmarks), its 26 range beams and a ring where it thinks it is. Captions say what happens as it happens; GET READY, 3-2-1 and the result show in every view and in recordings. Cameras: Director, Chase, Orbit, Top, Free (village: chase and village: top for fixed views); sounds of the rotors, the wind and the rain.
  4. v0.12.84Nov 10, 2026

    Text to video, and reviewing videos

    • AddedText to video block: open text-to-video models from Hugging Face, small to large (Wan 2.1 1.3B, the default; LTX-Video 0.9.5 2B; Kandinsky 5.0 Video Lite 2B; Wan 2.2 TI2V 5B; HunyuanVideo 1.5 8.3B; Wan 2.2 T2V A14B, the best open model), turn prompts into videos of up to 10 seconds on the machine's NVIDIA GPU: several variants of each prompt (one seed each) or a list of prompts. Models larger than the GPU still run, their layers streamed from the computer's memory group by group, so an 8 GB GPU runs them, more slowly. Each video is an H.264 MP4 small enough to play in the dashboard, with a still, a table of what made it and a summary.
    • AddedVideos stream live, whole: each one is sent as soon as it is made, in pieces of live telemetry, and plays in full in the view while the next one is being made.
    • AddedVideo review view: every video as a card that plays under the pointer, a large player with arrows and keys to watch each one whole, Keep and Remove (K, R, U), filters (to decide, kept, removed), and Save the kept videos into a dataset (as one version, in a folder) or as one zip, with their stills and a table; Save choices gives choices.csv.
    • AddedViews: ctx.saveFiles hands several files at once to the page, which saves them into a dataset as one version or downloads them as a zip.
    • ChangedThe View page sends each view only the live items it does not have yet, instead of its whole live stream each time: much less work when the stream is large.
  5. v0.12.83Nov 10, 2026

    Rideshare payload, interstage camera, launch cloud

    • Changed3D view: smoke and steam puffs are drawn from four 256x256 noise pictures made once when the view starts, stretched and turned on screen, instead of working out the noise for every pixel of every puff in every frame: far less work for the graphics card.
    • Added3D view: the fairing holds a rideshare stack, as on a Transporter flight: a black adapter cone with a silver ring and a scalloped flange, a beige column carrying a ring of small dispensers and satellites in gold and silver foil, solar panels and white boxes, a black scalloped neck, then a cross-shaped upper column with bigger satellites.
    • Changed3D view: the fairing is black inside (carbon composite with white cable runs, bolt holes and gas bottles), and its halves separate as on real flights: pushed apart sideways, tilting open a few tens of degrees and turning slowly, their insides towards the stage as it pulls ahead.
    • Changed3D view: the interstage camera sits on the outside of the interstage, just under its rim, above the grid fins and midway between two of them, looking down along the booster with a fin out on each side, as in the flight footage. The grid fins are darker, titanium darkened by flights.
    • Changed3D view: the launch cloud is a dense tan bank, low and wide, rolling out hundreds of metres to both sides of the pad and lasting a couple of minutes; it keeps its own share of particles, so shorter-lived puffs no longer erase it.
    • Added3D view: at lift-off, ice shaken off the frosted tanks falls away from the rocket (white chips and wisps of frost) for the first hundred metres or so.
    • Fixed3D view: smoke and steam are emitted per second rather than per frame, so a view drawing 30 frames a second shows as much as one drawing 60.
  6. v0.12.82Nov 10, 2026

    Lighter 3D views, a clean stop, smooth live flights

    • Fixed3D view: eight rocket views together could overload the graphics card until the browser switched 3D graphics off. Smoke and steam close to a camera now fade out instead of covering the whole picture hundreds of times over, puffs are no larger on screen than the view, views other than the main one draw 30 frames a second, and every view lowers its resolution while the card cannot keep up (and raises it again once it can).
    • Fixed3D view: when the graphics card is reset, a view pauses and starts again by itself once the card is back; when the browser has switched 3D graphics off, the view says so (restart the browser) instead of retrying.
    • Fixed3D view: stopping a run in the middle of a flight left the rocket hanging with its engines, smoke and sound still going. The scene now holds the moment of the stop and says so, until the next run flies.
    • Fixed3D view: during a live flight the ground could stop and start again while the smoke kept moving: the view ran out of flight data whenever it arrived more than 3 seconds late, then jumped ahead. Views now play as far behind the flight as the data actually arrives late, and the playing clock slows down a little or catches up gently instead of stopping and jumping.
  7. v0.12.81Nov 10, 2026

    Many 3D views on one page

    • Fixed3D view: with many views on the View page, reloading them (a run starting, a change, arranging) could fail with "error creating webgl context": each view kept its graphics context after it was drawn again or reloaded, and the browser allows only a few at once. A view now lets its context go as soon as it is reloaded, closed or drawn again; if the card has none free yet, it waits a moment and starts again.
  8. v0.12.80Nov 10, 2026

    Booster landing: sound in recordings, the camera look in the main view

    • Fixed3D view, seen from far off (the tracking camera): the flame, the engine glow, the thruster jets, the re-entry glow and the landing burn's spread came away from the vehicle and sank below it; they were lowered for the Earth's curve twice.
    • NewRecording what you see now records the sound too (the effects and the sea; the spoken commentary is the browser's own voice and is not recorded). The frame-by-frame replay stays silent.
    • ImprovedWhen the main view looks through an onboard camera or the tracking camera it takes that camera's look too (grain, vignette, glitches, the red dot and its name), on screen and in pictures and videos.
  9. v0.12.79Nov 10, 2026

    Booster landing: tracking camera, entry burn flame, launch cloud

    • FixedTracking camera: it aims at the vehicle as drawn in the same frame (it lagged and let it slip out of the picture), frames the whole vehicle, follows the second stage after separation while it is close enough to see, then the booster.
    • ImprovedEntry burn: the flame shows as a short, bright bulb below the engines, pressed back by the air, and the plasma bell closes right under the engine bells.
    • ImprovedThe launch cloud spreads out from the flame trench over the ground in every direction, rises and drifts off with the wind, thinning as it grows (60 to 120 s).
    • ImprovedFairing separation: the halves are pushed apart and swing over on their bases as the stage leaves them behind, so the second stage camera, looking back, sees their white insides with their outsides facing down.
  10. v0.12.78Nov 10, 2026

    Booster landing: every camera in one menu, onboard views to the main view

    • New3D view (rocket scenes): the camera buttons are now one menu with every camera: Director, Booster, 2nd stage, Ship, Pad, Tracking, Free, and the onboard ones (interstage, engines, grid fin, second stage, drone ship deck). The main view keeps its broadcast overlay, sound and recording while it looks through an onboard camera, so one recording can follow the whole flight from the best place.
    • NewEach onboard view (and the tracking camera) has a Main view button: it shows that camera in the main view at once.
    • NewViews: ctx.peer(topic, data) tells the other views on the page something; they get it with ctx.on("peer", fn).
    • ImprovedRe-entry plasma: one continuous bell, closed in front of the engines, with no ring where two surfaces met.
    • ImprovedThe second stage's nozzle cools to dark within seconds after its engine stops; Booster mission v9 sends the rest of the second stage's path, and its camera keeps flying after the landing, so the engine cut-off (near T+8:30) is seen.
    • ImprovedThe fairing halves are light inside (acoustic blankets), not black.
    • ChangedThe drone ship deck camera gets drops on its lens only at touchdown, when the engine's blast throws spray and steam onto it. Onboard cameras shake only while their own vehicle's engines run.
  11. v0.12.77Nov 10, 2026

    Booster landing: standing on the deck, a closed plasma bell, black legs

    • FixedThe landed booster stood 1.5 m above the deck: the view did not take the mission's deck height (4 m since Booster mission v8) and drew the deck at the old 2.5 m. The feet now stand on it.
    • ImprovedRe-entry: the glowing bell round the booster is closed below the engines (the shock in front of them), so the engine camera sees the plasma too, face on.
    • ImprovedLanding legs black all over (carbon fibre, dark fittings and struts). The clean shapes the folded legs leave on the sooted tank end a little above the legs' tips (they ran up the whole tank).
    • ImprovedThe smoke and steam thrown out over the deck and the sea at landing grow faster and bigger, slow down sooner and last longer, so they read as one cloud.
    • ChangedSound: no crackle (engines, hull slaps or sea hiss); at the drone ship only the low wash of the sea.
  12. v0.12.76Nov 10, 2026

    Booster landing: a steady second-stage camera, a bigger launch cloud

    • Fixed3D view, second stage camera: while a flight played live it jumped back and forth between the second stage and the top of the booster, each time the view reached the newest data a moment before the next part of the second stage's path; the stage is now carried on through such gaps.
    • ImprovedThe cloud at the pad at lift-off billows out faster, grows bigger and lasts longer (45 to 90 s), thinning as it spreads.
  13. v0.12.75Nov 10, 2026

    Booster landing: views fixed, a drone ship like the real ones

    • Fixed3D view: since 0.12.74 views could turn white or black, flicker, or show only part of the picture on some graphics cards (the multisampled half-float buffer). Edges are now smoothed with FXAA on the finished image instead.
    • NewThe drone ship, closer to the real ones: a black hull about 30 m wide with the deck carried out to 52 m on braced wings, dark rails, a bow bulwark, and at the stern the black equipment house with white radomes. Its deck stands 4 m above the calm sea (Booster mission v8; was 2.5 m), and the water is kept under the whole deck as it pitches and rolls, so the swell no longer washes over the pad.
    • ImprovedBooster soot after the burns: darker, and where the four legs lay folded against the tank it stays almost white, in long tapered shapes as on a flown booster.
    • FixedThe engines go dark a few seconds after a burn (they stayed red through the coast after the flip); on the way down the air heats them red again as the speed and the air rise.
    • ImprovedSound: the cold-gas thrusters are a soft, steady hiss while they fire (they were clicks); the engines crackle only in thick air.
    • ChangedBlueprints > View: the bar no longer has its own Stop button (the top bar has it).
  14. v0.12.74Nov 10, 2026

    Booster landing: antialiasing, a steady sea, the sound of the ocean

    • Fixed3D view (rocket scenes): edges were not antialiased, because the glow pass renders into its own buffer; that buffer is now multisampled (4 samples, 2 in the smaller onboard views).
    • FixedThe sea near the drone ship flickered in large patches during the descent: 600 km from the pad the wave and noise calculations ran out of precision. They now work from the nearer of the pad and the ship.
    • NewThe drone ship: the swell slaps against its sides in small bursts of spray, more in a rough sea and as the hull dips; near the ship you hear the ocean (a low wash rising and falling with the waves) and each slap.
  15. v0.12.73Nov 10, 2026

    Booster landing: a real flip, smoke that spreads and thins

    • ImprovedBooster mission (block v7): the flip as the real one flies it. The nitrogen thrusters fire to start the turn, stay quiet while the booster coasts round at a steady 8.6 deg/s, then fire on the other side to stop it; before, they braked for most of the turn, so the jet pointed the way the booster turned. The landing policy is unchanged and needs no new training.
    • Improved3D view: smoke and steam keep going the way they left, grow and thin out as they grow; each puff fades softly at its edge and is lit more evenly, so a cloud reads as one cloud instead of separate balls. The exhaust column after lift-off widens in every direction; the ground cloud at the pad spreads out.
    • ImprovedLaunch pad: less vapour; what pours from the engine bay lands on the launch mount's deck, slides across it and spills over its edges.
    • ChangedCold-gas thrusters: only their jet is drawn (no particles); small corrections are not shown.
  16. v0.12.72Nov 10, 2026

    Booster landing: recordings with the broadcast overlay, a rocking drone ship

    • New3D view: pictures and videos (live recording and the frame-by-frame replay) now include the broadcast overlay: gauges, the mission arc, the clock and the captions, scaled to the size chosen.
    • NewBooster landing: the drone ship rides the swell of the mission's own sea model all the time (it was held still between data frames and after the run), and a landed booster stays standing on the deck and rocks with it. Launch and land now starts with a rougher sea (0.7) for larger waves; the deck stays above the water.
    • NewBooster landing: a burn mark on the deck after touchdown (black soot under the engine, a scorched halo and streaks blown out by the exhaust), shown also when the replay jumps past the landing.
    • NewLaunch pad: cold oxygen vapour from the tanks and the engine bay falls and spreads over the ground instead of rising; water cannons on the launch mount and a flooded flame trench from a few seconds before ignition.
    • ImprovedExhaust plume: soft edges at altitude from five outer shells, each fainter and more broken up than the one inside it. Hot nozzles glow with streaks along the engine's axis. The smoke from the engine bay after landing thins out and stops within a few seconds.
    • FixedBooster landing: the cold-gas thruster puffs during the flip now leave on the side that turns the booster the right way (they pointed along the turn). Onboard cameras shake only from the engines, the airflow and the touchdown, not while the vehicle coasts with its engines off.
  17. v0.12.71Nov 10, 2026

    Choose the demos on the Demos page

    • NewProjects > Demos: platform admins see the projects of their current workspace there, each with Show as a demo, so the first demo is one click away (it can still be chosen from a project's Settings > Demo for everyone). If the database has not been updated for demos yet, the page says so instead of staying empty.
  18. v0.12.70Nov 10, 2026

    Demos for every account, import on the Projects page

    • NewProjects > Demos: complete projects shown to every account. A demo page shows the readme, the blueprints and the workspace blocks they use; Use this demo takes a copy into your workspace (readme, pictures, cover, blueprints and blocks), to change and run on your own machines. The demo itself is never opened, run or changed from outside its workspace, and its data, results, team, keys and choice of datasets and folders never travel; the copy says which blocks need a dataset or a place for their outputs.
    • NewPlatform admins make a project a demo, or stop showing it, under the project's Settings > Demo for everyone, and from the Demos page.
    • ChangedProjects: tabs My projects, Demos, Templates and Blocks. Someone with no projects yet lands on the demos (when there are any); My projects always shows their own.
    • NewProjects > Import: a project from GitHub or from an exported zip, from the top of the Projects pages and from an empty project list.
  19. v0.12.69Nov 9, 2026

    Splashdown, a dry deck, thrusters you can see

    • New3D view, rockets: a booster that goes into the sea throws up a tall column of water and a crown of spray, with mist rising and a ring of spray racing out over the surface; the water falls back and the sea there churns white.
    • Fixed3D view, rockets: the sea no longer washes over the drone ship's deck: round the hull the water stays below the deck as the barge rides the swell.
    • Changed3D view, rockets: the nitrogen thrusters show whenever the flight computer uses them to hold the booster upright (in the physics they always share the work with the grid fins and the engine gimbal), firing in short pulses.
  20. v0.12.68Nov 9, 2026

    Touchdown by contact physics, real explosions, a moving ship

    • NewBooster mission: touchdown is now simulated as a collision. From the moment the first foot touches, the booster is a rigid body on its four legs on the moving deck: each leg is a stiff spring with a crushable core that yields and can fail, with friction on the deck, and the engine skirt and the tank can hit the deck too. The booster settles on its legs and rides the swell, or a leg gives way and it topples and breaks up. The outcome comes from that simulation, and the 3D view follows its frames: the feet stay on the deck and the shock absorbers compress.
    • New3D view, rockets: explosions are a lumpy fireball of soft, noisy puffs released over most of a second, cooling from yellow to orange and red into rising soot, with a blast ring of dust or spray, sparks and debris (no more expanding spheres).
    • New3D view, rockets: where the engine's jet reaches the sea, white steam and spray are thrown out and the water churns white; the foam stays and spreads after.
    • New3D view, rockets: the drone ship heaves, pitches and rolls all the time with the mission's own swell model (the one its physics uses), also during the countdown and after the flight; the swell is larger (about a metre of heave in a moderate sea).
    • New3D view, rockets: the deck camera's lens gets wet in the landing burn: drops that blur the picture behind them, some running down.
    • New3D view, rockets: glossy clear-coated paint on both stages (soot stays matte); heavier brown-black soot after the flight; the legs end in flat pointed tips; the engines' glow fades within seconds after landing; hot nozzles glow in streaks and bands; the second stage's vacuum engine starts with a green flash and a bloom of gas.
    • ChangedBooster mission: a lower, more realistic trajectory: main engine cut-off near 69 km at 2.4 km/s, the booster tops out near 119 km and lands about 650 km downrange. The second stage holds the stack's attitude through separation and only steers once its engine runs. Frost now comes off both stages, only in vacuum after separation, in small flakes.
    • ChangedBooster landing: train goes on from the furthest policy so far (wired from the policies' dataset): the lesson it reached, then its landing rate. A training cut short by the time limit is no longer lost. The mission flies the newest policy that has finished its lessons.
    • Fixed3D view, rockets: the sky in the deck and tracking cameras flickered dark: those cameras were placed after the sky and sea were set up, so for a frame now and then they were judged to be under the sea.
  21. v0.12.67Nov 9, 2026

    Wrecks that go quiet, and the view under the sea

    • Fixed3D view, rockets: after a crash the wreck's clock keeps running when the flight's data stops (the run now ends 6 s after touchdown). The booster goes on sinking and disappears, the fire goes out, and the smoke and steam end; before, they froze at the last moment and smoked forever. The rush of air that sounded like the engines stops at touchdown and stays silent while the last frame is shown.
    • New3D view, rockets: under the sea. With the camera below the surface the water is dark blue and swallows the light within tens of metres, the surface overhead shows the sky only through a bright window straight up, the ship's hull and the wreck fade into the blue, and land and clouds are hidden.
  22. v0.12.66Nov 9, 2026

    Softer plumes, thruster jets, better ice

    • Improved3D view, rockets: high up, the exhaust plume thins out to nothing at its edges, ragged instead of ending in a hard rim (seen best from the onboard cameras during the entry burn).
    • New3D view, rockets: the cold-gas thrusters show their nitrogen jet, a wide, faint, flickering white cone at the top of the booster on the side that fires, opposite to the push. It is longer and wider in vacuum.
    • Improved3D view, rockets: ice flakes in space are larger and fly off the booster in every direction. They move with the booster, so they no longer stall or jump when the flight's data pauses.
    • Fixed3D view, rockets: a dark patch of sea that showed beside the launch site from altitude, where the local coastline and the satellite imagery disagreed.
  23. v0.12.65Nov 9, 2026

    A strongback pad, the EsaSim mark, a chosen voice

    • Improved3D view, rockets: the launch pad is now a strongback pad, as at Vandenberg. A raised concrete deck with yellow railings carries the launch mount and its hold-down clamps. Behind the rocket stands a white strongback: a wide lattice A-frame at the base, a narrow tower above, and clamp arms. Around them are rows of horizontal tanks on saddles, a vertical tank, a slender lightning tower and low white buildings, with their slabs and roads on the ground.
    • Fixed3D view, rockets: the mark on the booster is the EsaSim hexagon with its six bars.
    • New3D view, rockets: a voice menu next to the Commentary button lists the browser's English voices, the most natural first (Edge's neural "Online (Natural)" voices, then other neural ones, then Google's), and remembers the choice. The commentary speaks a little slower and lower.
    • Fixed3D view, rockets: the engine sound stops when the engines stop (also at touchdown), and all sound goes quiet when the view stops updating (the run ended, the tab hidden). Max-Q was called and drawn just after lift-off during a live flight, because the highest pressure so far was taken for the peak; it now counts only once the pressure has clearly fallen. "Supersonic" is called when the Mach number passes 1. The second stage camera no longer jumps back to the booster when the second stage's path ends: the stage carries on along its last velocity.
  24. v0.12.64Nov 9, 2026

    Grid fins, the EsaSim booster and a real launch pad

    • Improved3D view, rockets: grid fins modelled on the cast-titanium ones. Seen face-on they are hexagons, narrower at the root with the corners cut. A thick frame holds a deep lattice of thin blades at 45 degrees, and a solid root web carries the hinge lug and pin.
    • New3D view, rockets: the EsaSim mark and name run up the booster on two opposite sides, and the paint has a little gloss so the sun glints on it.
    • Improved3D view, rockets: light in space. Above the air the sky stops filling the shadows, so the sun is harsh and the booster's own parts (fins, legs, interstage) cast sharp shadows on it, with a faint blue light from the Earth below. The shadows now follow the booster whenever the camera is near it. In space, ice flakes shed from the tanks and engines drift slowly away, glinting in the sun.
    • Improved3D view, rockets: a more real launch pad. The ground around it is textured (scrub, grass, sand, gravel, the crawlerway, service roads, burnt ground north of the flame trench, slabs under the tanks) and takes the shadows, the long shadow of the tower included. The raised concrete hardstand has slabs, joints and exhaust stains. The pad also has a strongback pulled back for launch and a tank farm (a liquid-oxygen sphere and two kerosene tanks).
    • Changed3D view, rockets: with the broadcast overlay, the bar (cameras, sound, commentary) and the controls (Launch, wind) move to the top and show only while the pointer is over the view, and the events box and number tiles give way to the overlay.
    • Fixed3D view, rockets: a booster lost in the sea floats for a moment, then goes under; its fire goes out when it sinks, a little steam rises, and the smoke ends.
  25. v0.12.63Nov 9, 2026

    Sound, a commentator and the whole planet

    • New3D view, rockets: sound effects, all synthesized in the view. You hear the engines' roar, rumble and crackle, the rush of air and the grid fins, the cold-gas thrusters, the legs' pneumatics and lock, the sonic booms as the booster slows below the speed of sound, touchdown and explosions. Sound needs air: it fades with the booster's height and is silent above about 40 km, and it gets quieter with the camera's distance. A Sound button in the bar turns it off.
    • New3D view, rockets: a spoken commentary in the browser's best English voice. It counts down from 10, then calls liftoff, max-Q, MECO, stage separation, second stage ignition, the flip, fairing separation, the entry burn, the landing burn, the legs and the touchdown or the loss. The Commentary button turns it off. Sound and commentary start with the first click in the view (browsers allow sound only then), and only the main view plays them, not the camera views.
    • New3D view, rockets: the whole planet. Zoomed far out, the view shows a globe with NASA's Blue Marble imagery (public domain, NASA Earth Observatory). The oceans glint in the sun, clouds cover the whole Earth, and a glowing rim of atmosphere surrounds it, with no flickering between land and sea. From altitude the real coastline and colours of Florida, the Gulf and the Bahamas appear beyond the launch site, and clouds are softer and sparser from high up.
    • Improved3D view, rockets: landing legs like the real ones. Four tapered carbon-fibre legs with metal edges are hinged at the bottom of the tank and lie flat against it. A three-stage telescoping strut pushes each one out until its level foot pad stands 9 m from the axis and a little below the engines, where the physics has it. The drone ship's deck has EsaSim painted in the middle of the target and along its edge.
    • Changed3D view, rockets: the drone ship deck camera is fixed on a corner of the deck, aimed at the landing target and tilted up, and it rides the ship's roll and pitch. The open ends of both stages (the interstage, the skirt, the engine bells, the fairing) now show their inside instead of disappearing.
  26. v0.12.62Nov 9, 2026

    Rocket flights that look like a launch webcast

    • Improved3D view, rockets: the telemetry overlay now follows the launch webcast layout. Each stage has round speed and altitude dials, grey and ending in red. A wide arc of the flight's events puts now at its top, with what has passed on the left and what is coming on the right, and the mission clock and flight name sit under it. While the booster burns, and through separation, the right corner shows its g-force and its nine engines, lighting the ones that fire: all nine, three for the entry burn, one for the landing. After that it shows the second stage. Everything scales with the view, and during a flight the bar and controls fade away until the pointer moves.
    • Improved3D view, rockets: the Earth seen from altitude. The view now goes through the real thickness of air under the camera: blue straight down, paler towards the horizon. A glowing band of atmosphere sits over the curved limb with black space above, and cloud fields stretch to the horizon in clusters with clear sky between them.
    • Improved3D view, rockets: a less regular sea. Nine wave trains of unrelated lengths come from directions spread around the wind and rise and fall in groups. Ripples are patchy, calm and rough water alternate, whitecaps are scattered, and the foam at the ship's hull is broken.
    • Improved3D view, rockets: in thick air the flame is a long, white-hot jet that turns yellow, then orange; even one engine at its lowest throttle reaches below the legs. The flame lights the legs and the deck. When the plume reaches the deck it throws up rolling smoke and steam. The drone ship's deck has a wide white ring, a yellow ring inside it, old soot marks and yellow edges. The launch tower is grey steel.
    • Fixed3D view, rockets: soot and heat glow are now measured along the whole booster: soot covers the lower half after the entry burn, the way flown boosters look. Before, each part got its own soot, and the interstage glowed brown during the entry burn. The pad's concrete no longer glares under nine engines. The land near the coast no longer flickers through the sea from altitude.
  27. v0.12.61Nov 9, 2026

    A launch broadcast for rocket flights

    • New3D view, rockets: a Director camera, the default, cuts between shots by itself like a launch broadcast: the pad in the countdown, low at lift-off, the long lens from the ground, a chase through max-Q, separation from the side, the second stage climbing away, the booster coasting over the curved Earth, the entry burn close in, the long lens from the ship and the deck for the landing. Dragging the view takes over the camera.
    • New3D view, rockets: a broadcast overlay with speed and altitude gauges for both stages, the mission clock, a timeline of the flight's events and the next one with its countdown. The timeline never gives the landing's outcome away before it happens.
    • New3D view, rockets: the green flash of the igniter at each engine start, two layers of clouds, oxygen venting on the pad, the fairing halves opening away from the second stage, nozzles that glow after a burn, and a more detailed booster (octaweb with nine engines, raceway, weld lines, thruster pods, grid fin actuators, landing leg pistons).
    • Changed3D view, rockets: the booster's plume brightens in thin air and churns when seen from the engine camera; the second stage's vacuum plume is smaller; the coast seen from altitude is irregular and fades into haze instead of ending in a straight line; the engine camera sits a little further out so the landing plume and the ship are in view.
    • Fixed3D view, rockets: the second stage was placed far from the booster (and its views showed a pale fog) when a view joined or jumped in after separation. Going back before a crash now also clears its smoke.
  28. v0.12.60Nov 9, 2026

    Every view of a flight at the same moment

    • Changed3D view, rockets: every view of a run shows the same moment. The views play from the time each piece of data was made on the machine, a few seconds behind it, instead of each keeping its own count, so the main view and the onboard cameras stay together. Training replays follow one schedule that every view works out the same way: each attempt plays in full and its ending stays a few seconds; attempts that arrive meanwhile wait, and only the newest of them plays next.
    • ChangedView page: 3D, camera, image and video views can be made much smaller (down to 2 columns by 3 rows), to tile several cameras.
    • Fixed3D view: the camera buttons of a rocket flight (Booster, Ship, Pad…) raised "Script error." after switching. Errors in a 3D view's animation now show their real message instead of "Script error.".
  29. v0.12.59Nov 9, 2026

    Rocket crashes you can see

    • New3D view, rockets: after touchdown the engine stops, and a crash goes on from the moment of contact. The booster pivots on its base under gravity until it lies on the deck, collapses more the harder it hit, sinks if it came down in the sea, and explodes: at once after a hard impact or in the water, otherwise when its tanks hit the deck. Fireball and flash, burning debris that flies, falls and bounces, sparks, a column of black smoke, spray and steam over water, a fire at the base that burns on. Onboard cameras show SIGNAL LOST.
    • ChangedTraining replays stay on a crash long enough to see it; the result appears at the moment of contact.
  30. v0.12.58Nov 9, 2026

    Rocket launches and landings in the 3D view

    • New3D view: rocket flights (esasim.rocket/1) at Earth scale. The launch pad on the coast, the sea out to the curved horizon with its swell and sun glint, a drone ship that heaves and rolls, the sky darkening with height to black with a blue limb and stars. The booster moves its grid fins and legs as flown; plumes grow and widen as the air thins, with shock diamonds low down; the entry burn wraps the booster in fire, which leaves it sooty; the landing burn splashes over the deck and lights it; steam at lift-off, the exhaust trail, condensation at Mach 1, thruster puffs, smoke after touchdown, bloom.
    • New3D view: buttons to orbit the booster, the second stage, the ship or the pad as they move, a long-lens tracking camera and a free camera (the 3D mouse flies it). The new Camera setting fixes a view on a camera on board (interstage, engines, grid fin, second stage), on the drone ship's deck or on the ground, with the look of a live feed, so several views of one flight sit side by side.
    • ChangedViews wired through a Telemetry block now know which blocks feed it, so a view can prepare for the data before the first item arrives.
  31. v0.12.57Nov 9, 2026

    Stop from the top bar, and room for many flows

    • ChangedBlueprint editor: while a flow runs, the Run button becomes a red Stop button in the same place, on the Blueprint and on the View page, so a run can be stopped from wherever you are.
    • NewFlow tabs: when a project has more flows than the bar can show, arrows appear at both ends to scroll them (the mouse wheel scrolls them too), and the open flow is brought into view when the page opens.
    • ChangedZoom, fit, tidy and note tools now sit on the grid itself, top right; on laptop screens (1360 pixels wide or less) the version picker and Publish leave the top bar, since a run publishes the draft by itself.
  32. v0.12.56Nov 8, 2026

    Your Hugging Face token, in your profile

    • NewProfile > Keys: save your Hugging Face token once (encrypted, never shown again). Every block that takes it (Text to image, Hugging Face dataset, Publish to Hugging Face) uses it when you run a flow, with nothing to paste in each block: a block left without a key of its own uses the token of the person who runs the flow, so each person runs with their own. The profile shows when it was last used; Replace and Remove are there too.
    • ChangedBlueprint editor: such a setting shows the token it will use (Your Hugging Face token …abcd, or none saved yet with a link to the profile); A key for this block only still pastes one into the block, and it comes first. The run log of Text to image says which token it used.
    • NewCustom blocks: a secret setting can say which profile key it takes ("profile_key": "huggingface"); the documentation says how.
  33. v0.12.55Nov 8, 2026

    Images view: a grid, and a viewer with arrows

    • ChangedImages view: only the grid. A click opens the image on top of it, full size, with arrows to go through all of them (also the arrow keys, or a swipe on a touch screen), its place (3 / 20) and name, and a small × (or Esc) to come back to the grid. The images keep their order (image_01, image_02 … also past 99).
    • ChangedImages view: the large live picture on top is kept for live frames that do not each make a file (a camera, a render); pictures that do (Text to image) go straight into the grid. Live picture (auto, on top, in the grid only) changes it.
  34. v0.12.54Nov 8, 2026

    Python packages that keep the machine's PyTorch

    • FixedBlocks: installing a block's Python packages could add a second PyTorch. pip, installing into a package set (--target), did not see what the machine already had and installed every dependency again: accelerate needs torch, so on Windows PyTorch for the CPU came first on the path, the block ran on the CPU and the machine's torchvision broke (Text to image: operator torchvision::nms does not exist). Now pip first works out, against everything installed, what is missing, and only that goes into the set, at the versions it chose; PyTorch is never added as a dependency when the machine has its own. For a package that needs torch, 2 packages instead of 33.
    • FixedBlocks: package sets installed before that hold a PyTorch nobody asked for (added as a dependency) give it up the next time a block starts, so the machine's own PyTorch is used again; the log says so. Runtime 1.7.
  35. v0.12.53Nov 8, 2026

    Text to image: any number of images, and Tenstorrent

    • NewText to image runs on Tenstorrent cards too, through TT-XLA (PyTorch/XLA with Tenstorrent's plugin, pip package pjrt-plugin-tt, installed on the machine as TT-Forge's documentation says): the model computes in bfloat16, its denoiser compiled for the chip by the first image. auto takes a Tenstorrent card, else an NVIDIA GPU, else the CPU; a model the chip's compiler cannot run yet goes on, under auto, with the next device and the log says why.
    • NewText to image: any number of images (up to 100,000; 10 by default, 20 in the demo flows), and Images at once: several images in one pass of the model, faster on a large GPU (the same images as one at a time). If the GPU runs out of memory the block goes on one image at a time. File names take more digits past 99 images, so they keep their order.
  36. v0.12.52Nov 8, 2026

    Text to image: models from small to large

    • NewText to image: models from small to large, all downloaded from Hugging Face the first time: Vega RT and Vega (Segmind, 0.7B, Apache-2.0), SSD-1B (Segmind, 1.3B, Apache-2.0), Stable Diffusion XL 1.0 (3.5B, CreativeML Open RAIL++-M) and FLUX.1 schnell (12B, Apache-2.0, gated: needs a Hugging Face token; for cloud GPUs). A model larger than the GPU still runs, its parts taking turns on the GPU or coming layer by layer; one too large for a CPU, or gated without a token, stops with a message that says what to do.
    • NewText to image: a Summary output, one row per run (model, parameters, steps, size, device, seconds per image, loading time, licence): the summaries of several models join into one table or bar chart.
    • ChangedText to image: only the parts the pipeline lists are downloaded (6.9 GB for SDXL and 34 GB for FLUX, not their whole repositories), never copies for other runtimes (ONNX, OpenVINO); the free disk space is checked first.
  37. v0.12.51Nov 8, 2026

    Text to image: the first generative AI block

    • NewText to image block (AI): a diffusion model downloaded once onto the machine turns a prompt into images, on its NVIDIA GPU or its CPU. One image per seed (the same seed gives the same image), optional variations added to the prompt in turn, or a table of prompts. Models: Segmind Vega (a distilled SDXL, 1024 px, Apache-2.0), Segmind Vega RT (4 steps, Apache-2.0), or any diffusers model on Hugging Face or in a folder, whose licence is read and recorded with every image. Only the files the pipeline needs are downloaded, in half precision (3.3 GB for Vega instead of 13), with the progress shown; images.csv and generation.json record how each image was made.
    • ChangedImages view: live pictures that each make a file gather in the gallery as they arrive (each with its own caption), until the files come at the end of the block.
  38. v0.12.50Nov 8, 2026

    A closed ribcage

    • FixedSoft tissue: the lungs slipped out through the front of the ribcage. Each bone had at most 40 spheres, and the costal cartilages, one structure across the whole front of the chest, were left full of gaps. Each bone now gets as many spheres as it needs to be covered (Spheres per bone: 0, automatic, at most 800), none smaller than 2 mm; the log lists the bones with the most.
    • NewSoft body model: Close the chest wall (on by default). The intercostal muscles are not segmented, so fixed spheres fill the gaps between neighbouring ribs, costal cartilages and sternum; the lungs press out 30 to 45 % less in a test at 3 g, and none goes through. Metaballs shows this wall in muscle red.
    • Changed3D view, soft tissue: only the soft particles look for what they may touch (bones never touch bones), so the many more bone spheres cost little: twice as fast as without this change.
  39. v0.12.49Nov 8, 2026

    Muscles held by the bones, bone and heart surfaces

    • NewSoft body model: muscles are tied to the bones where they meet them, as at their origins and insertions: each muscle sphere that touches a bone, or comes within 6 mm of it, is joined to up to 4 bone spheres by stiff elastic links. The muscles sag about half as much and stay in place face down; the Structures table counts each structure's links to bone, and the log names the muscles held.
    • New3D view, tissue textures: bone gets a light grain and turns darker and yellowish where its surface is hollow or folded (between the processes of a vertebra, at the ends of the ribs, in notches), measured on each bone's own shape when the model opens.
    • Changed3D view, tissue textures: the heart now has the stomach's soft folds in a darker red, with patches of cream-coloured fat; the fine fibre pattern, too noisy, is gone.
  40. v0.12.48Nov 8, 2026

    Damping that damps, a sheen on the skin

    • FixedSoft tissue: organs kept swinging even with Damping at 1. The soft support that holds each organ in its place (the tissue that is not segmented) was almost undamped; it is now critically damped at Damping 1, so the organs settle without swinging back (about 0.1 s after the body is turned over, before about 2 s with motion left). Contacts between organs and with the bones no longer bounce, and the links inside each organ can be damped twice as much.
    • FixedSoft tissue: while the body was turned, the skeleton and the supports jumped once per screen frame, a small jolt each time that kept the tissue trembling (more with more damping). They now move smoothly through each frame: about 5 times less trembling while turning.
    • ChangedSoft body model: soft structures smaller than 1 ml are left out (as in Labels to 3D models): a sliver cut off by the edge of the scan had no surface to show and, almost weightless, rattled; the log names what was left out.
    • New3D view: a white sheen on the skin where the light that follows the camera glances off it, so the body's shape reads at a glance, however see-through the skin is.
  41. v0.12.47Nov 8, 2026

    Tissue textures, metaballs, real masses

    • New3D view: tissue textures. Each tissue has its own surface, made on the graphics card from the model's own coordinates (no texture files, no seams, and it stays on the tissue as it deforms): liver lobules, the spleen's grain, bowel folds, muscle fibres, the heart's fibres and fat, the lung's air sacs, vessel walls, porous bone, lobulated glands. Colour, small bumps and gloss vary under the smooth wet coat. Tissue textures (a setting and a switch in the Parts list) turns them off.
    • New3D view, soft tissue: Metaballs (a setting and a switch in the Parts list) shows the spheres of the soft-body model as they move, each structure in its colour, the anatomy see-through around them; hidden parts hide their spheres.
    • ChangedSoft body model: each structure weighs its density times its real volume (the voxels of its mask), shared by its spheres in proportion to their volumes; the skin weighs a 3 mm layer over the body's outline. Before, the spheres' own volume was used: organs were up to half as heavy as they are, the skin five times heavier. The Structures table gives each volume (ml) and mass (g), and the log the mass of the soft tissue.
    • ChangedSoft body model: the method is credited to Gianluca De Novi, PhD, with a link to the thesis (PDF).
  42. v0.12.46Nov 8, 2026

    Soft tissue: ribs that hold, measured stiffness, a calmer body

    • FixedSoft tissue: organs went through the ribs. Bones get up to 40 spheres each, nearly covering them (ribs too); organs collide with bones even where they touched them in the scan, once they come closer than they were; and the organs' surfaces are kept out of the bones.
    • ChangedSoft body model: liver, spleen, pancreas, kidney, thyroid and muscle stiffness as measured in healthy people by shear-wave elastography (Viceconti et al., World J Radiol 2025; Arda et al., AJR 2011); vessels, airways and heart much stiffer than before.
    • ChangedSoft tissue: a change of gravity, softness or pose eases in over half a second instead of jolting the tissue; less sag and more damping by default.
    • Changed3D view: with 3D mouse moves set to The model, the mouse drag turns the model too (Ctrl: moves it), with or without soft tissue. Anatomy less bright; the skin is matte and shows the body's outline (more opaque at its edges).
  43. v0.12.45Nov 8, 2026

    Soft tissue you can feel: turn it, shake it

    • New3D view, soft tissue: dragging with the mouse turns the body around its centre (with Ctrl it moves it), so the organs feel gravity from the new side and lag behind a quick turn or a shake; before, the mouse turned the camera, which changes nothing for the tissue. The 3D mouse (The model) does the same.
    • ChangedSoft tissue: softer support and less damping by default, so the organs visibly sag and wobble; a Damping slider (low: jelly, high: settles at once). Damping now acts against the body's own motion, not against moving through space, so the tissue keeps its inertia.
    • New3D view: anatomy looks wet, with a clear coat on organs, vessels and muscles that catches the light, and a light that follows the camera.
  44. v0.12.44Nov 8, 2026

    Copy the log

    • NewCopy buttons on the run log, in the blueprint's console (the lines shown, with their time and block) and on the run's Logs page, to paste it elsewhere; they also work where the browser has no clipboard API.
    • FixedSoft body model stopped at once with "SyntaxError: invalid syntax" (0.12.42 and 0.12.43).
  45. v0.12.43Nov 8, 2026

    Soft tissue: surfaces slide on the iso-surface

    • Changed3D view, soft tissue: the vertices of each structure's surface no longer only follow its spheres: they slide back onto their own level of the spheres' field (the iso-surface of the metaballs), as in De Novi's method, so stretched and squeezed organs keep a smooth, rounded shape.
  46. v0.12.42Nov 8, 2026

    Soft tissue under gravity

    • NewSoft body model (block): segmented anatomy as a soft-tissue model, following the metaball method of G. De Novi (PhD thesis, University of Bologna, 2011): a tree of spheres per structure (medial axis approximation), particles joined by elastic links with damping, the skeleton fixed, and a skin layer from the body's outline in the CT that contains the organs; tissue stiffness and density by class, changeable with a table.
    • New3D view: with a soft-body model, the anatomy moves under gravity as the body is turned and moved (with inertia), structures push each other where they meet, and Pull drags an organ; Gravity, Softness, Pause and Reset under Soft tissue. The pose of the scan (lying on the back) can count as at rest.
  47. v0.12.41Nov 8, 2026

    3D view: Parts list folds into a button

    • New3D view: the Parts list folds into a small button (– in its corner) to leave the anatomy free, and opens again from it; it stays as it was left.
    • Fixed3D view: "Waiting for a scene" stayed over 3D files after they had been shown.
  48. v0.12.40Nov 8, 2026

    3D view: one model at a time, without the floor, held with the 3D mouse

    • New3D view, Models: several 3D files one at a time, with a list in the corner to choose which (the choice is remembered), instead of side by side.
    • New3D view, Show the floor: off, the models float at the centre of the view, with no ground or grid.
    • New3D view, 3D mouse moves The model: tilt and twist the cap and the model turns around its centre, push it and the model moves, pull it and it comes closer; the camera stays. Fit (or the 3D mouse's left button) turns it back.
  49. v0.12.39Nov 8, 2026

    From a CT scan to 3D anatomy

    • NewRead medical images (block): CT and MR scans as NIfTI, NRRD, MHA or DICOM series, with their geometry checked (size, spacing, orientation, missing slices), DICOM converted to NIfTI, and a picture of three slices through each, the anatomy coloured over them when labels are connected. Only technical DICOM tags reach the table, never a patient's.
    • NewLabels to 3D models (block): label maps or masks become a clean, checked 3D model per structure: one coloured, grouped GLB scene per case for the 3D view (compact, so it opens in the browser) and STL files for 3D printing, with a table of volumes and which models are ready to print.
    • New3D view: files whose models have names get a Parts list (show or hide each part or group, find one by name), names when pointing at a model, and a plane to cut through them.
    • NewDownload files: zips on servers that send parts of files are read in place, so only the files kept are downloaded (a few cases of a 24 GB dataset); Case file and Cases take whole case folders, at random or by name; Also keeps files such as meta.csv.
  50. v0.12.38Nov 8, 2026

    Review images in a grid

    • NewReview grid (view): images as cards with their label, a badge per flag and the reason; filters by decision, flag, label and name; a large view with every detail, and duplicates side by side with the image kept; Keep, Remove or another label for each image, with keys (K, R, L, U, arrows, Enter). Save decisions gives review.csv for the Review input of Curate and split.
    • NewImage previews (block): small previews of the images to look at (the flagged ones, the images they duplicate, a random sample of the rest) with what the check tables say about each, packed a few hundred to a file. The images stay on the machine; only the previews reach EsaSim.
    • ChangedA run keeps up to 25 MB of tables, reports and previews and, apart, 25 MB of pictures and models on EsaSim: many result pictures no longer crowd out the tables a View needs.
  51. v0.12.37Nov 8, 2026

    Readmes with pictures and badges; machines kept awake

    • NewReadme pictures: upload a banner, screenshots and diagrams under a project's Data › Readme pictures and show them with ![what it shows](pictures/name.png). They are saved with the project to GitHub and in exports (pictures/), and come back on import and with templates.
    • NewThe readme template: Write the readme starts from a centred top (banner, title, tagline, badges for type, language, what it runs on and EsaSim) and the usual sections (Overview, Flows, What you need, How to run it, What you get, Data and licences, Notes), filled in from the flows where EsaSim knows the answer, with prompts for the rest.
    • NewReadmes understand what GitHub readmes use: shields.io badges (drawn by EsaSim itself), <div align="center"> to centre, <img> with a width, <br>.
    • NewWorker settings: Keep this machine awake (always, while it runs tasks, or never). With worker 0.10.9 a machine no longer goes to sleep and offline while it waits for tasks; the screen still turns off and locks. The machine's page shows when it last slept and for how long.
    • FixedEmbed images works with transformers 5 (it stopped with "'BaseModelOutputWithPooling' object has no attribute 'float'"), and no longer prints Hugging Face warnings about symlinks on Windows.
    • ChangedImage quality check: Smallest side is 0 (no limit) by default; at 224 it flagged most photos of datasets with small pictures, such as FruitNet.
  52. v0.12.36Nov 8, 2026

    Download files works again

    • FixedDownload files stopped at once with "'list' object is not callable" since Fetch only was added in 0.12.35.
  53. v0.12.35Nov 8, 2026

    Blocks with many result files are no longer taken for lost

    • FixedA block that ended with many result files (such as 1,000 images) could be marked lost: the worker sent its small files to EsaSim one by one after the block ended, without reporting in, for longer than 3 minutes. Each file sent now counts as the worker reporting in, and worker 0.10.8 keeps reporting while it sends them, summaries first, at most 200 files.
    • ImprovedDownload files: Fetch only takes some of the files of a dataset page (such as *.zip and not the .rar copy of the same data).
  54. v0.12.34Nov 8, 2026

    Every project opens on its readme

    • NewReadme: the first tab of every project, and where a project opens. It says what the project does and how to run it (accounts and keys to paste, settings to fill, data, machines, steps), written in Markdown under Settings > Readme. Until you write one, it is made from the project's flows.
    • NewThe readme is the project's README.md on GitHub and in exports, comes back on import and update from GitHub, and travels with project templates. AI assistants can read and write it (get_project, update_project).
  55. v0.12.33Nov 8, 2026

    Embed images uses the GPU

    • FixedEmbed images asked the worker for the plain PyTorch, which on Windows has no CUDA: on an NVIDIA machine it now gets the CUDA build, as the warehouse blocks do.
  56. v0.12.32Nov 8, 2026

    Data curation blocks, and datasets on the Hugging Face Hub

    • NewDownload files: links, Mendeley Data datasets, Zenodo records or GitHub assets, downloaded once into the machine's cache, archives unpacked, a repeatable sample of each folder kept, with a manifest and the licence and credit written next to the files.
    • NewHugging Face dataset and Publish to Hugging Face: read a dataset of the Hugging Face Hub at an exact commit (all or a sample), and publish files as one commit of a dataset there, with a card naming the licence and the credit. Free public storage, browsable by anyone and versioned, so a curated set stays traceable to the data it came from.
    • NewImage quality check (broken, small, blurred, dark, bright, flat images, with the reason), Find duplicates (perceptual hashes, and embeddings for images that show the same thing), Embed images (CLIP or DINOv2 on the CPU, an NVIDIA GPU or Tenstorrent cards, images per second live, zero-shot labels from prompts), Check labels (likely mislabelled images and outliers, from their nearest neighbours), Embedding map, and Curate and split (removes what the checks flagged or a person rejected, balances and splits train and validation, with a before/after report).
  57. v0.12.31Nov 8, 2026

    A bigger block menu, and a block reference on the website

    • NewAdd block opens a large menu that slides in from the left: a tab per category, the blocks with what each does, and a column with the chosen block in full (inputs, outputs, settings, where it runs) instead of a tooltip, with Add to flow and a link to its documentation. Arrow keys and Enter work from the search.
    • FixedA run whose block was stopped (canceled) while the others had finished stayed "queued" for ever; it now shows as canceled, and runs left that way in the last week are settled.
    • NewBlock reference in the documentation (Docs > Reference > Blocks): a page for every built-in and library block, made from its own definition, so it always matches the version you have. The docs search finds blocks too.
  58. v0.12.30Nov 8, 2026

    Several projects at once; warehouses with inbound flow, real stock and a building

    • NewWork on several projects at the same time: each browser tab keeps its own project and workspace, the sidebar lists the projects you opened (close one with ×), and a tab running a flow shows the run's progress in its title, so you can start a long run and go on with something else.
    • NewFleets in the 3D view with inbound flow: receiving stations with a roller conveyor coming in through the wall and the deliveries waiting on it, robots that load them and store them on the shelves, and pack-out desks whose orders leave on a conveyor through the wall. Robots receiving and storing have their own colours.
    • NewReal stock on the shelves: every package on the racks is the run's own; it leaves its slot when a robot picks it and appears when one stores it. Shelf use colours each pick face by how often it was used and the packages by class (A, B, C); the robot you follow names its slot.
    • NewThe hall is a building: walls with a window band and a roof with lights, drawn only from inside, so from outside you look in and from inside you see the whole building. Conveyors go through openings in the walls.
    • NewWarehouse fleet, Fleet-size sweep and Warehouse layouts are built-in blocks (Simulation), so every workspace has them, with their whole code to read and adapt.
    • ImprovedWarehouse fleet: deliveries arrive as well as orders (by default as many packages as the orders take out), the shelves start 70 % full, and every order and package is recorded: when it came, was assigned, stored or picked, shipped, by which robot, in which slot (orders.csv, packages.csv, stock.csv). New figures: stored per hour, putaway time, reaction time, deliveries waiting, shelves full.
    • ImprovedFleet size sweep and Warehouse layouts measure inbound too (stored per hour, putaway time, deliveries waiting), and the layouts compared include receiving on the pack-out wall.
  59. v0.12.29Nov 8, 2026

    Run timeline, incidents and batteries in 3D, charts by name

    • NewRun timeline: a view of how any run went: its values over time with the events marked on them, incidents and their clearing as bands with how long each took, the list of events, and the totals. Click an event to find it on the time line, or save the events as CSV.
    • NewIncidents in the 3D view: a layout can carry incidents (a spill closing an aisle, a robot stopped by a fault); the view shows a turning beacon, the spill or the robot in red, the person who comes to clear it, and how long is left.
    • NewBattery icons over robots that go to charge or are charging (with a bolt), and over every robot with Batteries; the robot followed shows its own.
    • ImprovedThe heat map goes from blue (a little waiting) through yellow and orange to red (a lot), with its scale in the legend.
    • ImprovedFleets: stations at both ends of the hall, desks on the right side, queue lights per station; routes avoid every closed cell.
    • ImprovedChart: a column of names on the horizontal axis gives one bar or point per name (compare layouts, products, machines); seconds into a run show as minutes and seconds instead of a 1970 date.
  60. v0.12.28Nov 8, 2026

    Fleets you can read: loads, unloads and batteries in the 3D view

    • NewFleets in the 3D view show what each robot carries: its tote with the items in it, the item going from the shelf into the tote while it picks and from the tote to the desk while it is unloaded at the station, and a ring on the floor that fills as the pick or the unload goes on.
    • NewBatteries: a robot going to charge or charging shows its battery over it (the ring shows the charge), Batteries shows every robot's, and the robot you follow gets a card with what it does, how far along it is, its tote and its battery. Charging has its own colour in the legend.
    • ImprovedLong rack rows are drawn as several rack units instead of one stretched rack, and the light strips glow less up close. Fleet runs made before still play as they did.
  61. v0.12.27Nov 8, 2026

    The 3D view drives the run: controls, numbers, events, fleets

    • NewControls on the 3D view: the Controls view's lines (button, slider, select, switch, text) in a bar over the scene, plus pick NAME, which sends the place you click on the floor. They send the same commands as the Controls view, and a control follows the live value of the field it is named after.
    • NewNumbers and events on the 3D view: live fields as tiles (orders per hour, time per order, robots busy…) and the texts of an events channel, over any scene.
    • NewFleets in the 3D view: a grid world and its robots, streamed by a block such as Warehouse fleet, drawn as a hall with racks, stations and docks from the 3D files wired in; smooth motion, light strips, routes, a heat map of waiting, follow a robot, a cinematic orbit, and the whole run on the timeline when it ends. The 3D mouse, pictures and recordings work there as in every 3D view.
  62. v0.12.26Nov 7, 2026

    Textured 3D models in the 3D view

    • FixedThe 3D view showed GLB models without their textures (racks, boxes, labels came out plain white): the pictures inside a GLB file now load.
  63. v0.12.25Nov 7, 2026

    A project's data and results, explored inside the project

    • NewProject > Data lists the project's data as folders (listed in the project, read by its blueprints or by its runs), each with the machine it is on, its files, its version and what reads it; the workspace's other datasets are one click away. A folder opens inside the project.
    • NewAdd files (Project > Data): name them, choose the machine folder, drop files or folders: they go straight to that machine and become a dataset of the project, without passing through the Data section.
    • NewProject > Results works like a file explorer: every run is a folder holding Inputs (each dataset version it read, browsable) and Outputs (the files it made), with the path above the files; nothing sends you out of the project.
    • ImprovedFiles open in a panel that slides in from the right, like the code editor: the list stays usable beside it, the file shown is outlined, the panel's width can be dragged and is remembered, Esc closes it. On wide screens the page narrows to make room.
  64. v0.12.24Nov 7, 2026

    The 3D view waits for the robot

    • FixedBefore the first run, a 3D view wired to a robot model (such as xArm 6 model) showed the sample drone scene; it now shows an empty robot cell and says the robot appears when the blueprint runs.
    • ImprovedViews know which blocks are wired into them, so they can say what they will show before a run. Their messages sit on a small panel that stays readable over any picture.
  65. v0.12.23Nov 7, 2026

    Projects from GitHub and zip files, and back

    • NewUpdate from GitHub (a project's Settings): the blueprints in its repository replace their drafts here, new ones are added, and the workspace blocks they use come too: a block that is the same is left alone, one that differs gets a new version, one that is missing is made. Published versions, keys pasted in blocks and blueprints that are only here are kept. Each step shows in the window as it happens.
    • NewExport a project as a zip (Settings > Export): project.json, a README, its blueprints and the workspace blocks they use, nothing else. Update a project from such a zip, or start a new one from a zip or a GitHub repository under Projects > New project > Import a project.
    • ImprovedThe menu shows the version of EsaSim at its foot (when expanded), linked to what changed.
  66. v0.12.22Nov 7, 2026

    Saving to GitHub, step by step

    • NewSave to GitHub opens a window that lists each step as it happens: finding or making the repository, collecting the blueprints and blocks, sending the files, the commit. It ends with the result and a link to it on GitHub; when GitHub refuses something, the step says which permission to change. The same window shows saving a whole workspace from Profile > GitHub.
  67. v0.12.21Nov 7, 2026

    GitHub: the right permissions named

    • FixedWhen GitHub makes a project's repository but refuses its files, the repository stays the project's: the next save writes into it instead of making another one.
    • ImprovedGitHub messages name the permissions GitHub uses today: Repository creation to make repositories, Contents (Read and write) to save files.
  68. v0.12.20Nov 7, 2026

    Shadows around robots, clearer GitHub messages

    • ImprovedThe 3D view shows a robot cell with soft shadows on the table and a darker floor; the shadows now follow the robot also when the view comes back with the camera you left it with.
    • ImprovedWhen GitHub does not let EsaSim make a project's repository, the message says what to change for the kind of token linked (a fine-grained token, a classic token, or an organization).
  69. v0.12.19Nov 7, 2026

    A repository per project, views that stay as you left them, boards you click

    • NewGitHub: a repository for each project, made for you (private) the first time the project is saved, with its blueprints, the workspace blocks they use and a README. Choose it under Profile > GitHub; one repository for everything is still there, and a repository named there that does not exist yet is made too.
    • NewThe Controls view has boards of cells: grid cell 3x3 board.matrix 1=X -1=O shows the board a running block sends and sends the cell you click. show say.text puts the newest words of a block above the controls, and buttons next to each other share a row.
    • ImprovedA blueprint opens on the page it was left on (Blocks or View), and views come back as they were left: the 3D view keeps its camera, the Controls view its choices.
    • FixedViews now get the files a run left on a machine (up to 64 MB): the page has the machine send them when the view needs them. A 3D view showed no robot because its model stayed on the machine.
    • ImprovedThe xArm block tells the arm's controller its limits (reduced mode: top speed of the tool point and of the joints, the safe box as a fence, top acceleration) and restores the controller at the end; its speed is capped at 150 mm/s and its acceleration at 800 mm/s². The board now lies with its top towards the arm by default (rotation 90°).
  70. v0.12.18Nov 7, 2026

    Robots in the 3D view

    • NewThe 3D view shows robots: connect a robot model (esasim.robot/1, such as the one the xArm 6 model block makes) and the live data of the block that moves it. The joint angles it sends pose the robot, smoothly and a little behind real time; a second set poses a see-through twin beside it (the digital twin next to the real machine); and the objects it describes (a table, sheets showing live pictures, cameras with their field of view, the tool) are drawn around it. The camera can be flown with the 3D mouse, and pictures and videos saved, as with any scene.
    • FixedA robot shown live holds its last pose when nothing new arrives, instead of playing its last moves again.
  71. v0.12.17Nov 7, 2026

    Save to GitHub from any tab of a project

    • ImprovedOnce you have chosen a repository in your profile, every tab of a project (the blueprint editor too) has Save to GitHub at the top right: one commit with the project, its blueprints and the workspace blocks they use. It was only in the project's Settings.
  72. v0.12.16Nov 7, 2026

    Optional imports no longer stop a block

    • FixedA block whose code imports a library only when it is there (inside try: … except ImportError or except Exception, such as Tenstorrent's torch_xla on a PC without the cards) failed before it started, because the worker tried to install that library and pip had none for the machine. Such imports are now optional, and a package found only by reading the code (not listed by the block) is installed when pip can: when it cannot, the block runs without it and the log says so.
  73. v0.12.15Nov 7, 2026

    Workers come with PyTorch and the usual packages for machine learning

    • NewWorker 0.10.7: the setup puts PyTorch and the usual packages for machine learning, vision and data in the worker's own Python, so blocks start without a download. With an NVIDIA GPU PyTorch is the CUDA build (on Windows from PyTorch's own index), otherwise the CPU build; a PyTorch already in the system's Python on Linux, such as one for Tenstorrent cards, is kept. Also NumPy, SciPy, pandas, PyArrow, Pillow, OpenCV, scikit-learn, Matplotlib, h5py, ONNX, ONNX Runtime, tqdm, PyYAML and Requests. On Linux and macOS the worker now has its own Python too (a venv in its folder).
    • FixedOn Windows the setup builds the worker before its tests, and if Visual Studio's compiler fails on a test (an "Internal compiler error" that older versions of Visual Studio 2022 sometimes give), it tries again one file at a time and then goes on with a warning instead of stopping. The worker does not need its tests to run.
  74. v0.12.13Nov 7, 2026

    PyTorch with CUDA on Windows, more settings per block

    • NewA block that lists torch[cuda] among its Python packages gets PyTorch built for NVIDIA GPUs on Windows too (from PyTorch's own package index; pip's ordinary PyTorch for Windows runs only on the CPU). On Linux a PyTorch already in the machine's Python is kept, for example one set up for Tenstorrent cards.
    • ImprovedA block can have up to 60 settings (it was 30), and a block with more is refused with a message instead of losing the last ones.
  75. v0.12.12Nov 7, 2026

    Uploads to a machine fixed, GitHub in the profile

    • FixedFiles dropped into a dataset in a machine's storage could wait forever ("writes the files: 0 of N") after the machine was paired again in the same folder: the worker kept the folder list of its earlier pairing, and the dataset could belong to that earlier entry. The settings now always reach a newly paired worker, the new entry takes over the folders, datasets and waiting files of the earlier one with the same path, and folder work waits until the worker has the current folder list. Waiting files are written as soon as the worker runs; nothing needs to be uploaded again.
    • ImprovedAn upload that waits for a machine says why: the machine is not connected (and since when), or it has not taken the files for a minute. Data > New dataset marks folders of machines that are offline.
    • NewGitHub in your profile: link your account once, choose a repository, branch and folder, and keep your blocks (their code) and projects (their blueprints and the blocks they use, without keys) there. Each can be saved by itself (blocks when you save a version, projects when you publish a blueprint), with a button per project, or all of a workspace in one commit.
    • ImprovedThe dialog to save a picture or video from a view has a close button at the top right and Close at the bottom right.
    • ImprovedWorker 0.10.5 forgets the settings of an earlier pairing when it is paired as a new machine.
  76. v0.12.11Nov 7, 2026

    Live data while a run goes on, new views, device blocks

    • NewA Live tab in the run console: every value a machine block sends while it runs (ctx.telemetry, ctx.picture) shows as it arrives, about once a second, filtered by block and channel. A block's Live telemetry output can be wired straight into any view; the Telemetry block is only needed to pick channels or gather several blocks.
    • NewViews: Gauges, Heatmap, Waveform (long signals with zoom, scrolling, an overview, Follow and Play), Sound (audio files, live samples, beeps), Speak (text to speech), Camera (the camera of the computer you use: pictures, videos, frames sent to the blocks) and Controls (buttons, sliders, switches, text and choices). The Chart view adds areas, steps, points, histograms, zoom and a scrolling live mode.
    • NewMessages to running blocks: the Controls and Camera views, and ctx.send in any view, send messages that a running block reads with ctx.messages("channel"), within about a second.
    • NewA Devices category of machine blocks: Camera capture (pictures or video from a camera of the machine, with a live preview), Network (HTTP, TCP, UDP, listening on a port, a live bridge to a device) and xArm (status, home, moves, drawing with a pen, live commands; it starts in dry run and checks every target against a safe box).
    • ImprovedLive values reach the dashboard faster (about every second instead of every three). Worker 0.10.4 is needed for messages and the faster updates: run the download line again in the worker's folder.
  77. v0.12.10Nov 7, 2026

    Plans set by admins, new datasets on machines

    • NewAdmins set the plan of any workspace (Free, Pro, Enterprise), with no payment: their own under Admin > Overview > Your workspaces, anyone's on the user's page or under Organizations, which now lists personal workspaces too.
    • FixedA new dataset in a machine's storage (or another writable folder) said "The last scan failed: the folder does not exist" until files arrived: its folder is simply empty until then. Worker 0.10.3 also makes the folder at once.
  78. v0.12.9Nov 7, 2026

    Re-pair from the list of machines

    • ImprovedRe-pair, in each machine's row under Computing and on its page: it gives one line to paste in the worker's folder on that machine (with tabs for Windows, Linux and macOS), and the page goes back to your machines once it is connected. The machine keeps its settings, shared folders, datasets and history; the full install steps are there too, folded, for a machine where the worker is not installed any more.
  79. v0.12.8Nov 7, 2026

    Pair a machine again

    • NewPair again, on a machine's page (under Settings, and in the message shown while it is not connected): a new pairing code for the same machine, which keeps its name, Worker settings, shared folders, datasets and history. The page shows the commands; on a machine where the worker is already built, only the pairing line is needed, in the worker's folder.
    • FixedThe Data pages could show a machine as online or offline differently from Computing: they now check the machines' last contact the same way. A machine that is not connected says when it was last seen and how to start it.
  80. v0.12.7Nov 7, 2026

    No data files on the EsaSim server

    • ChangedEsaSim keeps no data files on its own server: datasets live in the folders of your machines (each shares its storage), buckets and cloud drives. EsaSim storage is off by default (Admin > Integrations: storage per workspace 0 GB; the update sets it to 0), is no longer offered for new datasets or connections, and uploads to it are refused with what to do instead. Datasets already there can be moved to a machine or deleted.
  81. v0.12.6Nov 7, 2026

    Datasets on your machines by default

    • ImprovedNew dataset: a machine's own storage is chosen first when the workspace has one, and the form says where the files will be kept (EsaSim storage keeps them on the EsaSim server, a folder on a machine keeps them there). A dataset's page says "on the EsaSim server" for EsaSim storage.
    • NewMove to a machine: a dataset kept in EsaSim storage moves into a folder of one of your machines, keeping its name, project and history. The machine's worker writes the files; the copies on the server are deleted once all of them have arrived.
  82. v0.12.5Nov 7, 2026

    A Python of the worker's own

    • FixedCUDA blocks failed on Windows with "Could not build wheels for numba-cuda": the Windows service only sees Pythons installed for all users, here Visual Studio's Python 3.9, for which numba-cuda has no ready-made package. Worker 0.10.2: the build script puts the official Python 3.12 in the worker's folder (python), and the worker uses it for blocks; otherwise it picks the newest Python of the machine. esasim-worker scan shows which.
    • Improvedpip prefers ready-made packages to building from source, and says what to do when it can only build from source; its temporary files go to the worker's data folder (tmp), like those of blocks.
  83. v0.12.4Nov 7, 2026

    Worker 0.10.1

    • FixedWorker 0.10.0 did not finish building on Windows: two of its tests expected the Linux service names (esasim-worker-…) instead of the Windows ones (EsaSimWorker-…). The worker itself was not affected.
  84. v0.12.3Nov 7, 2026

    One folder, one worker

    • NewWorker 0.10.0 keeps everything in the folder it is downloaded into: the build and vcpkg (build, tools), the program, its configuration and log (config) and its data (data: job files, Python packages of blocks and pip's cache, its storage). The service runs the program from that folder; nothing is copied to Program Files or written to ProgramData, /etc, /var/lib, AppData or the user profile, and no setting of the PC is changed. Only Git, CMake and the C++ build tools are installed for the whole machine when missing.
    • NewSeveral workers on one machine: one folder each. The first service is EsaSimWorker (esasim-worker on Linux), the next ones are named after their folder (or --service-name NAME); service status, stop, start and uninstall run in a folder act on that folder's worker.
    • ChangedThe download line runs in the current folder: make the worker's folder, go there, paste the line. Running it again in the same folder updates the worker and restarts its service (Windows, in an administrator PowerShell).
    • ChangedOn Linux and macOS the service runs as the owner of the worker's folder (no system user esasim). On Windows it still runs as Local Service, which may read the folder and change only data and config.
    • ImprovedMachines set up with worker 0.9 or earlier: service install run in the new folder, without a code, takes the old service over, keeps its pairing, moves its data into the folder and removes the copy in Program Files and the configuration in ProgramData.
  85. v0.12.2Nov 7, 2026

    CUDA blocks run on the packages EsaSim installs

    • FixedBlocks using Numba CUDA (from numba import cuda) said "CUDA is unavailable" with the packages EsaSim installed: the package folders were added to Python without running their start-up files, so numba.cuda was Numba's old built-in target instead of numba-cuda, and NVIDIA's library finder did not look in them for the CUDA runtime, NVVM and libdevice. Package folders are now set up like a site-packages folder (and their DLL folders are searched on Windows).
    • Fixednumba-cuda 0.30 does not work with NumPy 2.5 (it fails on import): with numba-cuda, NumPy stays below 2.5. Machines that installed the packages before get a fresh, matching set on the next run.
    • ImprovedBlocks that use Numba print a CUDA check before they start: the Numba, numba-cuda, NumPy and Python in use, the GPUs the task was given, whether the NVIDIA driver answers (and why not) and whether kernels compile.
    • ImprovedThe packages a block needs are installed together in one folder, so pip picks versions that work with each other.
  86. v0.12.1Nov 7, 2026

    Removing a worker removes its data

    • FixedRemoving a worker removes its shared folders and their datasets from EsaSim too (the files on the machine are not touched); the confirmation says how many. Folders and datasets left by workers removed earlier are cleaned up the next time the Data page opens.
    • FixedDeleting a dataset removes its versions, file lists, previews, scans and waiting transfers one by one, whatever its machine, and says why if it cannot; the name to confirm is no longer case-sensitive.
  87. v0.12.0Nov 7, 2026

    Python packages for blocks, storage on every machine, results for AI assistants

    • NewPython packages for blocks: before a block runs, the worker installs the packages it is missing with pip, into its data folder (never the system's Python), and reuses them on later runs. Packages the code imports are found by themselves (numpy, Pillow for PIL, numba and numba-cuda for numba.cuda, OpenCV for cv2 …); a block's definition can list more, with extras and versions. A worker setting turns it off.
    • NewWorker 0.9.0: every machine shares a storage folder of its own with EsaSim (in its data folder, or where esasim-worker storage --path puts it), with an optional size (--max-gb) that uploads cannot exceed. More folders are shared from the machine with esasim-worker share add NAME PATH [--writable]. Set on the machine only, they show in the dashboard under Set on the machine, with the space they use.
    • NewAI assistants (MCP): create projects (empty or from a template); get_run_results lists every file a run made with a download link for each and a zip of all of them; get_result_file returns a file's text, a picture the assistant can see, or any file as base64.
    • FixedDatasets whose machine was removed (or paired again) said "#0 does not share folders": the dataset page now says the machine was removed and gives its folder to another machine; a worker's settings offer the folders of removed machines, a folder listed again at the same path joins its datasets, and removing a worker hands its folders to another worker of the same machine.
    • ImprovedA shared folder the worker cannot find says why under the folder, with what to do when the Windows service cannot open a folder in a user profile or OneDrive.
    • FixedThe blueprint console no longer shows the first lines of a run several times.
  88. v0.11.1Nov 6, 2026

    Steadier 3D mouse, shared folders, email you can check, clearer results

    • Fixed3D mouse: no more jumps. With devices that send the rotation in a report of its own, the rotation dropped to zero between two reports; it now holds. The motion is smoothed (it eases in and stops quickly when you let go), a drag no longer adds leftover momentum when the flight ends, and once you have flown the camera nothing moves it by itself (a new scene, the end of a live landing) until Fit.
    • FixedShared folders: listing a folder in the Worker settings turns on Share folders with EsaSim. A machine paired again (a new worker) is detected: its settings offer to move the folders and their datasets from the old worker, and the dataset page says which worker holds the folder. Messages name the worker, link to its settings and say when it has not picked up new settings yet; the per-folder option is now Writable (uploads, blocks).
    • NewAdmin > Email: the SMTP server, port, encryption, user, password (stored encrypted), sender and certificate name are set in the panel, and Recent messages lists every email EsaSim tried to send with the answer it got. Admin > System shows whether the last one went out. SMTP now uses the authentication the server offers (PLAIN or LOGIN) and explains a refused certificate or a missing STARTTLS.
    • FixedResults: the counts of kinds of files follow the folder and search in view, in run results and datasets; a block's folder has its title in the path; JSON, YAML and Markdown files count as Text and data rather than logs.
    • FixedRun logs: each line is tagged with its task as in the task filter (Landing sweep · 1/2, 3D scene, Render), and the line saying where a task was assigned names its block (it said "Task 4 of 4" for a run of five tasks).
    • ImprovedResults tab: a wider list of runs, with who started each run, its duration, size and inputs; drag its edge to widen it (remembered in your browser).
  89. v0.11.0Nov 6, 2026

    3D scenes with models and trajectories, rendering on your machines

    • New3D scene block: one row per object with its model (a shape, or a GLB, glTF, OBJ, STL or PLY file) and its trajectory: a table of positions over time with optional roll, pitch and yaw or a quaternion (CSV, TSV, JSON, JSON lines, filtered with #column=value), an object of a simulated run (scene:drone), a fixed position, or live positions. Its scene feeds the 3D view and the Render block alike.
    • NewRender block: renders a scene on a machine into PNG or JPEG frames and an MP4, WebM or GIF video, with Blender (Cycles, on the GPU when there is one) when it is installed or with a built-in renderer in Python. Cameras follow, orbit, fixed and top; one run or all; frames can go to a dataset as they are made.
    • NewLive pictures: the Render block sends a small copy of its latest frame while it works, and the Images view shows pictures streamed through a Telemetry block, the newest on top, with its number and progress.
    • NewTemplate: 3D scene, rendered on a machine (Landing sweep, 3D scene, 3D view, Render, live frames and the video); the Drone landing study project includes it.
    • NewTable settings: blocks can have a setting made of rows with named columns (text, number, choice, colour), edited as cards with suggestions from what is connected. The block builder makes them, and AI assistants see their columns.
    • ImprovedThe 3D view reads orientations (quaternions), fixed positions, scales and the arrow shape from scenes, and sizes models by model_size.
    • ImprovedBlueprint notes: no dark frame inside a note while you write; the text cursor shows where you type.
    • ImprovedDocumentation: a new page, 3D scenes and rendering, and updates for the console, results, table settings, AI assistants and the FAQ.
    • FixedIn the Landing sweep's scenes and live 3D, a drone that has landed sits on the pad's deck instead of inside it.
    • FixedThe Images view no longer covers itself with a dark layer before a picture is enlarged.
  90. v0.10.1Nov 6, 2026

    Fly with the 3D mouse, logos in light mode, Windows build

    • ImprovedThe 3D mouse flies the camera on all six axes: x, y and z move it in its own frame (sideways, forward and back, up and down), pitch, roll and yaw turn it around its own axes. It keeps its roll until a mouse drag, Fit or the right button (which levels the horizon). A setting switches to moving the scene instead.
    • FixedThe logos of the home page show in light mode too: they are drawn as dark silhouettes on light pages and light ones on dark pages, whatever the colours of the logo files.
    • FixedBuilding the worker on Windows: the build goes to a short folder outside the source (%LOCALAPPDATA%\EsaSim\build), so it no longer stops at the 260-character path limit; the download line starts in your user folder so updates replace the same copy, and the script warns about nested copies and OneDrive.
  91. v0.10.0Nov 6, 2026

    Blocks of your own, AI assistants, a console for every flow

    • NewProjects > Blocks: the workspace's own blocks in one place, with their ports, settings, code, versions and the flows that use them; make a block from Hello world or from a copy of a built-in one, on its own page or from the block menu (Make a block). Download any version as a zip.
    • NewPorts declare their formats (file extensions) and what they carry; the editor warns when the formats of a connection do not match. Each block's code starts with a header EsaSim writes from its definition: block, version, workspace, author, ports with types and formats, settings.
    • NewShare a block with every EsaSim workspace: workspace admins send a version for review, the EsaSim team audits its code under Admin > Shared blocks, and approved blocks appear in everyone's block menu, credited to their workspace.
    • NewSave a block to GitHub: link your account (or a fine-grained token), choose a repository, a branch and a folder, and each version goes in as one commit with block.json, its code and a README; optionally every new version.
    • NewAI assistants (MCP): connect Claude, ChatGPT, Cursor or Claude Code to a workspace. They read projects, flows, blocks, runs, logs, results and datasets, build flows and blocks, and run them, with the access you choose (read, build, run) and within your role. Sign in with OAuth from the app, or use a token from Account > AI assistants.
    • NewA console at the bottom of the blueprint editor: the flow's problems as you edit, checks of the machines and data before a run (accelerators, worker versions, offline or busy machines), the errors of the run, and its log live, by block, with filters. It folds, and its top edge drags to make it taller.
    • New3D view: fly the camera with a 3Dconnexion SpaceMouse (Chrome, Edge, Opera); save pictures (PNG, JPEG, WebP) and record videos, either what you see in real time or the replay rendered frame by frame (MP4, WebM or PNG frames), at up to 4K, then download them or keep them in a dataset.
    • ImprovedProject tabs in a new order: Data, Blueprint, Compute, Runs, Results, Analytics, Team, Settings. Runs lists every run with its tasks and logs; Results shows, run by run, what it read and what it made, with the file viewers. Opening a run no longer leads to Compute.
    • ImprovedThe code editor scrolls with visible scrollbars, and its panel can be widened by dragging its edge or set to the whole width; the block builder has a full-screen mode and a movable split.
    • FixedSecret settings of machine blocks (API keys) now reach their code as environment variables, as the block builder says.
  92. v0.9.0Nov 6, 2026

    Connect your data, upload it, see it

    • NewConnections, under Data: EsaSim storage on the server for each workspace, S3-compatible buckets (Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, MinIO, Google Cloud Storage), Google Drive, Dropbox and OneDrive, next to the folders your machines share. Keys and sign-ins are stored encrypted. Platform admins register the cloud drive apps and set the storage per workspace under Admin > Integrations.
    • NewUpload files and whole folders to a dataset in the browser (drag and drop, in parts, up to 20 GB a file), download one file or a selection as a zip, and delete files; each change makes a new version. For a folder on a machine, its worker writes, sends and deletes the files.
    • NewA file browser for datasets, run results and the EsaSim library: folders, a grid of pictures or a list, search and kinds, and a viewer for each kind of file: images with zoom and a strip of pictures, video, audio, PDF, sortable CSV tables, JSON trees, Markdown, text and logs with find, and 3D models and point clouds; arrow keys go to the next file.
    • NewOutputs go to: any block that runs on a machine can send its result files to a dataset in any connection, as they are created or when it ends, copied or moved; the dataset gets a new version whose source is the run.
    • NewFlows read datasets kept in EsaSim storage, buckets and cloud drives: the machine that runs the next block downloads them first, so any machine can use them.
    • ImprovedRuns open inside their project, under Runs & results, with a tab Inputs and results that shows the dataset versions the run read next to the files it made. Going back from a file no longer leads to Computing.
    • ImprovedJobs on your machines can ask for several GPUs again when a machine has a large enough group of GPUs.
    • ImprovedWorker 0.8.0: transfers for uploads, downloads and deletions in shared folders; results of tasks fetched for viewing; datasets downloaded before a block starts; outputs sent as they are made; downloads of any size straight to disk; image previews up to 8 MB.
  93. v0.8.1Nov 6, 2026

    Every accelerator, and machines with several GPUs

    • NewWorker 0.7.0 finds GPUs through Vulkan too, so AMD and Intel cards work on Windows and on Linux without ROCm, with their real memory size; Apple GPUs are found through Metal; on Windows the memory of cards over 4 GB is read correctly. esasim-worker scan, and the machine's page, list what each accelerator still needs (a driver, ROCm, CANN, tt-smi, the NVIDIA Container Toolkit). On Linux, setup.sh installs the Vulkan loader, the Mesa Vulkan drivers and pciutils.
    • NewSharing the accelerators, in Worker settings: all tasks together, one GPU per task, or groups you choose (an 8-GPU machine as 1 + 3 + 4). Each task takes one free group whole and sees only its accelerators, with the machine's Python and in Docker. Jobs on your machines can ask for as many GPUs as the largest group, and only go to a machine when such a group is free.
    • NewSpace for job files, in Worker settings: a limit in GB, and at the limit either wait or delete the oldest job folders (never a running job or a recent one). The machine's page shows the space used.
    • NewSeveral workers on one machine: esasim-worker --instance NAME gives each its own configuration, data folder, log and service; the machine's page warns when two of them may use the same GPU.
    • ImprovedComputing lists each machine with its CPU threads, RAM, accelerators and VRAM, and the storage it can still use; the machine cards of a project show the same. Without a data folder in the settings, a worker started by hand keeps its job files in a data folder next to the program.
    • ImprovedProjects: the open project stays open, with its name in the menu, while you visit other pages, until you close it; opening a project shows its Blueprint, a new project starts on Settings, and Settings is the last tab.
    • ImprovedBlueprint editor: Add block is a blue button in the top left corner of the grid that stays in place while the grid moves.
    • FixedSome tab bars showed a vertical scroll bar at some display scales.
  94. v0.8.0Nov 6, 2026

    The View page and the EsaSim library

    • NewThe blueprint editor has two pages: Blocks, to place and wire blocks, and View, where every view of the flow (charts, 3D view, tables, metrics, images, video, text, your own) appears by itself as soon as it is on the grid. Move views by their title, resize them from the corner, or Arrange them; the layout is saved with the flow. The views show a run, live while it runs, or sample data before the first one.
    • NewEsaSim library: free test data for every workspace under Data > EsaSim library, with starter collections (3D models, landing camera pictures and a video, flight logs and results). Pictures and videos play in the page, logs and tables show their first lines, models and point clouds turn in a 3D preview. Platform admins add collections and upload files of any size from Admin > EsaSim library.
    • NewLibrary block: choose files of the library for a flow. Views load them (a model can take the place of the drone in a 3D scene, with Model for); machines download them before their block starts.
    • NewData > Projects: the results of every project you can open, as folders by flow and run, following your role in each project.
    • NewLive 3D: the 3D view moves the bodies a block streams (for example {"drone": [x, y, z]}) smoothly and at real speed while the run goes on, with trails, the head-up display and the follow camera, then switches to the replay when the run ends. The Landing sweep streams one landing live (Live 3D), and the Drone landing study template wires it.
    • ImprovedThe block menu of the editor opens from Add block (or A) over the grid and closes once a block is added, so the grid has the whole width.
    • ImprovedFor platform staff, the Workspace / Platform admin switch is in the top bar, next to the account menu.
    • NewBlock builder templates: start a new block from a Hello world machine block or view, or from the code of a shipped block of any category. Views get their size on the View page.
    • ImprovedNotes on a blueprint show who wrote them and who changed them last.
    • ImprovedThe code panel of a view switches between Code and Preview, each with the whole width, instead of splitting it.
    • ImprovedJobs moved under Computing; a project's tab Runs & results lists its runs with their flow and who started them.
    • ImprovedThe folded menu shows the small logo instead of a letter: assets/images/logo-small.png, else the white logo, else the favicon.
    • ImprovedThe 3D view shows point clouds (PLY without faces) as points, places several models side by side, frames small models closely and hides the timeline when there is nothing to play.
    • ImprovedWebsite and documentation: a Blueprints product page; the Data and curation page shows what is available now; the home, overview, simulation, compute, drones, research, security and pricing pages describe blueprints, data and the library, with screenshots of the product; new guide The EsaSim library, and a first flow in Getting started.
    • ImprovedWorker 0.6.1: installing the service, and service status, print how to stop, start and remove it (new service stop and service start); run in a window, it says that Ctrl+C stops it. The machine page and the downloads page show the stop command too. On Windows the build no longer stops at the tests, and dataset subfolders written with a backslash are checked for ".." too.
  95. v0.7.0Nov 6, 2026

    Data, your own blocks and templates

    • NewData: machines share folders with EsaSim, and datasets are indexed where they are (file list, SHA-256 checksums, image sizes, log lines, table columns, image previews). Versions are kept when the folder changes; each dataset page has its versions, a file browser by kind with previews, and lineage: the run that made a version, the datasets it came from and the runs that read it.
    • NewData blocks: Dataset (read a fixed version in place; the blocks it feeds go to that machine), Select files (keep what a table chooses, such as an Agent's keep labels) and Save as dataset (a new version, with lineage).
    • NewYour own blocks: a block builder in the editor (kind, ports, settings, icon, code with Verify), or Save as my block from a block whose code you changed. They appear in every project of the workspace and are versioned.
    • NewTemplates: save a project (type, cover, flows, optionally its machines) or a flow as a template of the workspace; new projects and flows start from them. Projects can have your own types, such as Drone swarms.
    • NewBlocks can run in Docker, one container per block with the image you choose, instead of the machine's Python.
    • ImprovedThe Blueprint tab opens the editor inside the project page, with the project's flows as tabs; the left menu has icons and folds to a narrow rail; the page header is one thin row with the tabs.
    • ImprovedWorker 0.6.0: the data role (shared folders, scans, previews), datasets read in place, Save as dataset, and the Docker block runner.
  96. v0.6.0Nov 6, 2026

    Blueprints

    • NewBlueprint editor in every project: flows of blocks wired on a snapping grid, with a block menu (icons and descriptions), typed connections, alignment guides, tidy, undo, copy and paste, notes, a minimap and numbered versions. A project can hold several flows; four templates to start from.
    • NewBlocks are modular: each is a folder with its description and code. Machine blocks are Python and run on your machines through the worker; views are JavaScript and run in the browser in a sandboxed frame. A code panel edits a block's code in the flow and verifies it.
    • NewFirst blocks: Files on a machine, Filter table, Merge, Landing sweep, Accelerator benchmark, Python script, LLM, Agent, Telemetry, and the views Chart, 3D view, Table, Metrics, Images, Video and Text.
    • NewRun a flow from the editor: the plan, the machines with their availability, then each block's state on the grid, live telemetry and the views filling while it runs. Parallel blocks spread over several machines and are combined.
    • New3D view for replays and simulations: physically based materials, soft shadows, sky lighting, a timeline, runs, trails, a camera that keeps the action in frame or rides behind it, and glTF, OBJ, STL and PLY models.
    • NewLLM block: EsaSim models billed per token from your credits, Anthropic, OpenAI, Google, Mistral, xAI and DeepSeek with your own key (stored encrypted, sent only to the machine running the block), or any OpenAI-compatible server.
    • NewAgent block: reviews files, images, logs and table rows in a loop with the model you connect, using skills you allow, and records a label, a confidence and its reasoning for each item. Prompts are settings; the harness is code you can change.
    • ImprovedWorker 0.5.0 runs blueprint blocks with the machine's Python, reports their live telemetry, and has a new setting, Run code from projects.
  97. v0.5.2Nov 6, 2026

    Runs start inside the project

    • NewNew run opens inside the project: pick what to run, set it up, and choose where among the machines the project may use, each showing whether it is available, busy (with its free slots and the runs it is working on), paused or offline. Automatic picks any machine that fits.
    • NewThe Compute tab shows the project's machines and what they are doing right now.
    • ImprovedSwitching workspace moved from the left menu to the account menu at the top right.
  98. v0.5.1Nov 6, 2026

    Project spaces

    • NewProjects are cards with a cover image, a type, their runs and GPU-hours; a project being worked on shows what is running. Create one with a name, description, type, cover (eight built-in or your own picture) and the colleagues to invite.
    • NewEach project opens into its space with tabs: Settings, Data, Team, Blueprint, Compute, Results and Analytics.
    • NewRoles per project: Observer, Runner, Editor and Admin. Invite anyone by email, inside or outside the organization; people outside see only that project, under “Shared with you”.
    • NewCompute per project: choose which machines and servers its runs may use, and whether EsaSim Cloud is allowed. Machines outside the list never receive its tasks.
    • ImprovedResults moved into each project: live telemetry of running jobs, the latest runs and the result files.
  99. v0.5.0Nov 6, 2026

    New dashboard layout

    • NewA thin bar at the top with your name and workspace: its menu holds Profile, Organizations, Security, API tokens, billing and Sign out; light and dark are two icons next to it.
    • NewComputing in the menu, with three tabs: My computing (your machines and servers), Cloud computing (credits) and Analytics (usage).
    • NewTeam in the menu: members and teams of the organization; in a personal workspace, how to create an organization.
    • ImprovedOrganizations you belong to, and creating a new one, are in your profile. The page header is slimmer.
  100. v0.4.4Nov 6, 2026

    Back to your workers once a machine connects

    • ImprovedWhile “Connect the machine” is open, the page waits for the machine and goes back to the workers list as soon as it has paired, with the new machine highlighted.
    • ImprovedOne package: the site zip includes the current EsaSim worker (downloads/esasim-worker-src.tar.gz), so uploading the site also updates the worker the install commands download.
  101. v0.4.3Nov 6, 2026

    Download, build and pair from one page

    • New“Connect the machine” shows, for Windows, Linux and macOS, the line that downloads and builds the worker and the line that pairs it with the code filled in. Your system is selected automatically.
    • NewThe site serves the worker's source code itself (downloads/esasim-worker-src.tar.gz, with its SHA-256 on the downloads page); when a public repository is set in core/content/worker.php the commands use git clone.
  102. v0.4.2Nov 6, 2026

    Build, then paste the pairing command

    • ImprovedWith EsaSim worker 0.4.1 the build leaves the program in the source folder, so the pairing command shown under “Add a machine” works right after the build, in the same window.
    • ImprovedThe pairing command asks for administrator rights itself (Windows prompt, or sudo on Linux and macOS) instead of failing in a normal PowerShell.
  103. v0.4.1Nov 6, 2026

    Worker documentation

    • ImprovedDownloads and the “Set up a machine” guide describe the EsaSim worker 0.4: download and build, pair, run, for Windows, Linux and macOS, plus Worker settings, file locations, updating, uninstalling and troubleshooting.
    • ImprovedThe other guides and product pages use the new names (your machines, shared GPU servers, EsaSim Cloud) and say what runs today.
    • FixedThe install commands under “Add a machine” point to the program where the build puts it.
  104. v0.4.0Nov 5, 2026

    Machines you set up from the dashboard

    • NewThe EsaSim worker installs as a service on Windows, Linux and macOS with one command, starts with the machine and runs without anyone logged in (EsaSim worker 0.4).
    • NewWorker settings on each machine's page: tasks at the same time, which GPUs jobs may use, which presets it runs, working hours, pause and the data folder. The machine applies them within 30 seconds and the page shows when they are applied, or why not.
    • Improved“Add a machine” shows the install command for each system. Clearer names: your machines, shared GPU servers and EsaSim Cloud.
  105. v0.3.0Nov 5, 2026

    Parallel jobs on many workers

    • NewJobs are split into tasks that run in parallel on all your matching workers, and a combine step merges their results when they are done (EsaSim worker 0.3).
    • NewWorkers can run several tasks at once (slots), and you can leave the worker choice to EsaSim ("Any online worker").
    • NewLanding sweep (parallel demo): a built-in preset that simulates drone landings under wind on many workers and reports where the controller fails.
    • NewJob pages list every task with its worker, progress and attempts; logs can be filtered by task.
    • ImprovedA task whose worker disappears goes back in the queue for another worker once before it is marked lost.
  106. v0.2.13Nov 5, 2026

    Open job results in the dashboard

    • NewWorkers (0.2.2) upload small result files (text, data, images up to 5 MB). Open them in the job's Outputs tab or download them; large files stay on the worker.
    • ImprovedThe benchmark preset is called Accelerator benchmark everywhere, and the new-job page describes how local jobs run.
  107. v0.2.12Nov 5, 2026

    Workers run jobs

    • NewLocal workers (EsaSim worker 0.2) pick up jobs, stream logs and progress, stop when you cancel, and report results and output files.
    • NewJobs whose worker stops reporting for 3 minutes are marked lost instead of staying "running".
    • ImprovedJob pages refresh themselves while the job runs. The accelerator benchmark also runs on CPU-only machines.
  108. v0.2.11Nov 4, 2026

    Worker API

    • NewWorker API v1 for the EsaSim worker 0.1: pairing, heartbeat and hardware inventory.
    • NewWorker pages show the scanned machine: OS, CPU, memory, free disk, Docker, each accelerator with its driver, and live CPU and GPU use.
    • ImprovedWorkers are shown offline when their heartbeats stop.
  109. v0.2.10Nov 4, 2026

    Simpler theme switch

    • ImprovedThe theme switch has two buttons, light and dark. Until you pick one the site follows your device; your choice is saved on your account.
    • ImprovedThe blog is off for now.
    • ImprovedFooter, invoices and legal pages name esacode, LLC.
  110. v0.2.9Nov 4, 2026

    Clean addresses after the host fix

    • ImprovedOnce the host forwards every request, old /esacode.com/… addresses redirect to the clean ones.
  111. v0.2.8Nov 4, 2026

    Sign-in fix

    • FixedSign-in no longer fails with "Session expired" when the browser still holds a session cookie from an earlier version.
    • FixedSessions are kept in EsaSim's own storage folder, and pages are never cached by the host.
    • Improved"Powered by" sits under the logos.
  112. v0.2.7Nov 4, 2026

    Works when the site sits in a folder of another site

    • FixedOn hosts where the main site only forwards existing files to the EsaSim folder, links go through the folder so every page opens. Clean addresses come back by themselves once the host forwards everything.
  113. v0.2.6Nov 4, 2026

    Fix for hosts that add their folder to every address

    • FixedPages no longer redirect in a loop on hosts that add the site folder (/esacode.com) to every request.
    • Newesasim-check.php: a server check page that shows how the host passes requests to EsaSim.
    • ImprovedWebsite images are JPG; "Powered by" logos are larger and shown without boxes.
  114. v0.2.5Nov 4, 2026

    Links on every host, new home strip

    • FixedMenu and page links work on hosts that ignore the .htaccess rewrite rules: the site checks itself and switches to /index.php/… addresses when needed.
    • ImprovedHome page: a shorter hero and a row of image cards that scrolls right to left and fades out at the edges.
    • ImprovedThe "Powered by" logos use the same scrolling row.
    • ImprovedThe website menu and footer live in one file, core/content/navigation.php.
  115. v0.2.4Nov 4, 2026

    Industries, new solution pages and address fix

    • NewSolution pages for defense and security, medical and healthcare, and marine and subsea.
    • NewHome page: industries grid and two more carousel slides (autonomy, subsea).
    • ImprovedThe product name is written EsaSim everywhere.
    • FixedOn hosts that report the account folder in the script path, addresses like /esacode.com/... now redirect to the clean address and styles load again.
  116. v0.2.3Nov 4, 2026

    Multi-vendor hardware and prepaid cloud credits

    • NewWorkers and cloud classes for NVIDIA, AMD, Intel, Huawei Ascend and Tenstorrent; each preset states the hardware it supports.
    • NewPrepaid cloud credits: buy up front, jobs reserve their maximum cost, are charged per second and return unused time.
    • NewAdmin: cloud offers, platform fee, provider prepaid balances and a coverage check, credit grants.
    • FixedLinks no longer add the hosting folder name to the address on some hosts.
  117. v0.2.2Nov 4, 2026

    Themes, wider dashboard and a new home page

    • NewLight, dark and automatic themes for the website and dashboard, saved per person.
    • NewAll colours and fonts in one theme file, selectable in the admin panel.
    • NewHome page carousel with a shorter headline.
    • NewDashboard pages use the full width; forms and settings are centred.
    • NewPlatform admins switch between the admin panel and their workspace in one click, with a setup checklist.
    • NewAutomatic database upgrades when new files are uploaded.
  118. v0.2.1Nov 4, 2026

    Safer setup and the email service

    • SecurityThe installer asks for a one-time code that only someone with FTP access can read.
    • SecurityPreview mode can no longer start once the platform is installed.
    • NewAdmin recovery: reset an admin password or rebuild config.php with a fresh setup code.
    • NewEmail through an HTTPS email service, with a settings page and a test button in the admin panel.
  119. v0.2.0Nov 4, 2026

    Website, plans and the job launcher

    • NewPublic website with product pages, blog and changelog.
    • NewDocumentation covering getting started, workers, compute units, jobs, organizations, security, billing and API tokens.
    • NewPricing with Free, Pro and Enterprise plans and monthly or annual billing.
    • NewBilling through Stripe: upgrade from Free to Pro, and create an Enterprise organization with seats.
    • NewEnterprise owners can add or remove seats, switch between monthly and annual billing, and cancel at the end of the paid period.
    • NewInvoices and payment method management through the Stripe customer portal.
    • NewProjects to group related jobs.
    • NewJob launcher with presets: GPU benchmark, Isaac Sim scenario sweep, Isaac Lab RL training, MuJoCo simulation and data curation.
    • NewJob queue with statuses and cancel, clone and rerun actions.
    • NewWorker registration with pairing codes for local workers and install tokens for servers.
    • NewCompute units for servers, with GPU, RAM, disk and CPU core allocation and a warning when a unit spans PCIe groups.
    • NewUsage page with GPU-hours by day, member and worker.
    • NewPersonal API tokens for Pro and Enterprise with scopes, expiry and revocation.
    • NewPlatform admin tools for billing and for handling requests.
  120. v0.1.0Nov 4, 2026

    Accounts and organizations

    • NewAccounts with email confirmation and password reset.
    • SecurityTwo-factor authentication with authenticator apps (TOTP).
    • SecuritySigned-in device list with session revocation.
    • SecurityPasswords hashed with Argon2id and CSRF protection on every form.
    • NewOrganizations with email invitations that expire after 7 days.
    • NewRoles: owner, admin, billing manager, member and viewer.
    • NewTeams and per-member feature permissions and GPU limits.
    • SecurityAudit log of administrative and security events with CSV export.
    • NewPlatform admin area.
    • NewInstaller for setting up the platform on a web server.