Skip to content
New — orchestrate a team of Mel agents from your terminal. Learn more

Status

Is Mel working right now?

This page asks Mel's hosted AI service one question and prints the answer with the time it was asked. That is a reading taken at a moment, not an uptime report — we keep no availability history, so we publish none.

AnsweringMel relay

The Mel relay is the hosted service the Mel agent sends model calls through. It answered our check in 753 ms at Aug 25, 2026, 23:08 UTC.

One check, at most once a minute, and only while someone is reading this page. Nothing here is watching between your visits.

Current release
v0.1.30

What the download service is publishing right now. Download or read what changed.

Our changelog's newest entry is v0.1.32. When these two differ, the download service is the one that decides what you get.

This website
You're reading it

That is the only claim this page can honestly make about itself. It is served by the same host as the rest of openmel.dev, so if that host has an outage this page goes down with it and cannot report it.

Latest changes

v0.1.32LatestAugust 2026 (beta channel)
  • Long sessions no longer hit a wall. A malformed reply from one AI provider could get saved into a conversation, after which every model refused it forever with a misleading 'provider outage' message — while new sessions worked. The server now repairs such conversations automatically on every request (existing stuck conversations start working again with no action needed), the malformed shape can no longer be saved in the first place, and the error message for genuinely unserveable requests now tells the truth.
  • Conversations that outgrow a model's context window now compact automatically and continue — a quiet one-line notice instead of an error. Very long sessions are the point of Mel; now the seams show it.

Before that: v0.1.31, v0.1.30. Every release.

What this page does not tell you

  • No uptime percentage, and no history. We don't collect a public availability series, so there is no honest number to put here. A figure with decimals that nothing measured is worse than silence.
  • No incident log. When something goes wrong we write it up in the changelog of the release that fixes it, in plain words, including the releases that did harm.
  • Nothing about Mel on your machine. The terminal, your command blocks, and any CLI coding agent you run inside Mel execute locally and never touch the service checked above. A bad reading here does not stop them; only the Mel agent's hosted models depend on it.
  • Nothing you should read as an alert. This is a page you visit, not a monitor that watches for you. If Mel is failing for you, tell us — that still reaches a person faster than this page will.