ReDock 0.5.0

• ReDock now runs on Windows
• Studio, image generation, narration, emdash, the local model and the Shopify terminal say "Coming soon on Windows"
• First-run setup fits on one screen and says only what it changes
• Gemini's model list leads with one that answers

ReDock 0.4.7

• Fixed: Gemini can now finish real, multi-step work. Google's newer models attach
  a hidden token to every tool call and require it back on the next step; ReDock
  was dropping it, so Gemini tasks failed right after the first action. It is now
  carried through the whole conversation — verified against Google with a live
  two-turn run.
• New: a "Test it" button on every AI provider. One click sends a real request
  (and a real tool round-trip) through the app itself and tells you in plain
  words whether that provider works right now — no more finding out mid-task.
• Better: when a provider fails, you get one plain sentence about what happened
  and what to do — "the model is busy right now, try again" reads very
  differently from a wall of raw error text. The provider's exact words are
  still there behind a click for anyone who wants them.
• Better: setting up a provider is one visible path — pick it, add the key,
  choose a model, test it — and the model list no longer reloads every time you
  open the picker.
• Changed: the GPT suggestion now leads with OpenAI's newest low-cost model.
• Under the hood: the groundwork for ReDock on Windows is complete — the whole
  codebase now compiles for Windows, checked on every future change. Nothing
  changes on your Mac.

ReDock 0.4.6

• New: emdash — a modern CMS you can create in one step, like a WordPress
  site but built on today's tools. Pick "emdash" on the New site screen, choose
  where its content will live (Cloudflare, or one folder that runs anywhere
  Node runs), and ReDock builds it, starts it at your own .test address with
  real HTTPS, and sets its admin up for you.
• New: signing in to a new emdash site. It has no password — its admin uses a
  passkey, your fingerprint or your device — so the site screen makes you a
  one-time sign-in link and opens it; you register the passkey there and
  you’re in.
• New: your own AI can write the content. An emdash site carries its own AI
  connection, and the site screen hands you the one line that connects Claude
  Code to it, with a key that stays hidden until you ask for it. There is also
  an "Open in Terminal here" button, so claude starts in the site’s folder
  where its own guides already are.
• New: the Deploy tab knows what an emdash site is. The Cloudflare flavour says
  it ships to your own Cloudflare account and that the content you write on
  this Mac stays on this Mac; the other says plainly that copying its folder is
  how it moves, and that deploying it from here is not built yet.
• Deploying an emdash site to your own Cloudflare account was run for real on a
  free account, end to end, and three things it taught are now in the app: the
  guided token screen asks for all six permissions a deploy needs (it used to
  ask for three, and a token made from it couldn't create anything); the two
  refusals a free account actually hits — "switch on R2 once in the dashboard"
  and "the plugin sandbox needs a paid plan" — are said in plain words; and
  when the plugin sandbox is refused, the site now really does deploy without
  it instead of failing (the old retry was listening for words Cloudflare
  never says).
• A new emdash site now asks what kind of site it should be: Blog, Portfolio,
  Marketing — emdash's own designed templates — or Minimal, the near-blank
  canvas. Blog is preselected, so a first site looks finished out of the box
  instead of like plain text.
• The New site screen wears real brand marks now: WordPress, n8n, Bun,
  Playwright and emdash each show their official logo in its official colour
  (Bun had been wearing the Node logo), and the emdash tile carries a small
  Cloudflare mark after its name — that flavour ships to your own Cloudflare
  account.
• Fixed, before release: an emdash site whose setup step failed the first time
  can now be finished from its own screen — the Admin card shows Set up
  whenever the admin or its key is missing, and it retries the one known
  first-run hiccup by itself. The Cloudflare flavour also installs its own
  local emulator during Set up (it never needed a Cloudflare account to run on
  your Mac), and the setup server no longer leaves a worker process behind.

ReDock 0.4.5

• New: pick your model from a list of everything your provider actually serves.
  ReDock used to offer three model names it had been built with — which went out
  of date, and hid every other model your key could use. Now it asks the
  provider and shows the answer, with a search box when the list is long. You
  can still type any model id yourself, including one released today, and the
  list has a Refresh next to it. Works for custom endpoints too.
• Fixed: Google's Gemini, properly this time. The previous fix swapped in a model
  name that turned out not to answer at all, so Gemini still failed. The model
  list is now one we tested against Google directly, and it leads with the one
  that actually responds. If you added Gemini before this update, open the model
  picker and choose gemini-3.6-flash — your saved choice is left alone on purpose,
  so it will not change by itself.
• Fixed: two more providers offered a model that does not exist. Adding OpenRouter
  or GPT could hand you a starting model the provider had never heard of, so the
  very first message failed. Every model ReDock suggests has now been checked
  against the provider that serves it.

ReDock 0.4.4

• Fixed: Google's Gemini works now. The app was asking Google for a model name
  that doesn't exist, so every request failed no matter which key you entered —
  it looked like the app was ignoring your input. It asks for a real model now,
  and an already-saved Google setup corrects itself on the next launch.
• Fixed: the built-in database tools (Adminer, phpMyAdmin) and the welcome page
  now work in a browser that looks addresses up on its own, the same way your
  sites already did. Their names are kept in the same list as your sites' —
  they had been left out of it.

ReDock 0.4.3

• If MySQL's main download site stops carrying the version ReDock uses, the
  install now fetches the identical file from MySQL's permanent archive by
  itself — same file, same integrity check, no dead end.
• A new WordPress site needs one thing: a name. The admin login is filled in for
  you (and the email follows the name as you type, until you change it), and
  anything this Mac is missing — PHP, the database — becomes a checked line that
  says "ReDock will set this up for you" and then does, with progress for each
  step. Nothing sends you off to another screen first any more.
• WordPress and ReDock's AI connection are on from the start. A fresh install is
  a working WordPress app rather than three switches you have to find. Both are
  still switches: Settings → Capabilities turns either back off.
• Once local HTTPS is set up on your Mac, ReDock's web server comes up with the
  app — and right after first-run setup, so the first site you open works
  without a restart. Nothing else starts with it: no sites, no PHP, no database.
• When the database won't start, ReDock now tells you what the DATABASE said,
  not just that it couldn't connect. It reads the engine's own log and shows its
  last lines — on the screen where it failed, in that site's log, and in the
  report you can send.
• ReDock sets up the database the first time it is used, and checks that it
  worked. An empty database folder used to fail silently thirty seconds later
  with "connection refused".
• "Check my setup" gained a Database section: which engine, its version, whether
  it is answering, where its files are, whether they have been set up, and — when
  something is wrong — what it said, with a Start button.
• Every "isn't running" message now carries its own fix and stops pointing at the
  wrong thing. Opening a site while the web server is down used to say local
  HTTPS networking was off, and offer a password that could not help; it now says
  the web server isn't running and starts it.
• Every kind of site installs what it needs while it is being created. PHP, Node,
  Python, n8n, Bun, Playwright, Firecrawl, the image server, Video studio and a
  video project all used to stop and send you to the Runtimes screen when the
  thing they run on wasn't installed; now each one names the version it will
  fetch, keeps Create pressable, and installs it as the first step you watch.
  Copying a live WordPress site does the same instead of refusing at the very
  end, and so does asking the AI agent to make you a site.
• ReDock has its own database now. On a Mac with nothing installed it downloads
  MySQL from its makers — once, about 167 MB, and it tells you the size before it
  starts — sets it up, and runs it for you. One database server for all your
  sites, on its own port, with its own files, started when your sites need it and
  stopped with them.
• If you already have a database, ReDock uses that one and says so. Nothing is
  installed, nothing is moved, and your existing sites carry on exactly where
  they are. If the one you have won't start, ReDock shows you what it said and
  offers one button to use its own instead — your database is left untouched.
• Any site can move its data between the two, from its own Database tab. ReDock
  backs the site up first, copies it across, points the site at the new one, and
  leaves the old copy exactly where it was.
• "Check my setup" now lists both, tells you which is which in plain words, and
  says which of your sites are on each.

ReDock 0.4.2

• Your sites now open in browsers that look addresses up on their own. If Chrome,
  Brave or Edge has "Use secure DNS" switched on, it never asks this Mac where
  mysite.test is — it asks Cloudflare, which has never heard of it — so the
  site was dead in that browser while ReDock showed everything green. ReDock now
  writes your site names where those browsers actually look for them.
• Adding, renaming and removing sites keeps that list up to date on its own, with
  no password each time. The one-off "Enable local access" approval now also
  installs a small updater that does it afterwards; run that once and the rest is
  silent.
• ReDock checks the list every time it starts and puts back anything missing —
  sites you made while it was closed, a half-finished rename, a hand edit.
• "Check my setup" gained two sections: whether every site name is in place, and
  how each browser on this Mac looks addresses up. It says in plain words which
  browsers go elsewhere and why your sites still work in them.
• When a name is missing, a slim notice appears under the header on EVERY screen
  rather than only on Home, with a one-press fix. The same is now true of the
  "another app is using the web port" notice.
• Removing ReDock takes the updater and its permission with it, by both the
  in-app removal and the copyable Terminal command.

ReDock 0.4.1

• ReDock now works on a Mac that already runs Local by Flywheel, Herd, Valet,
  MAMP or a Docker stack. It used to show everything green while nothing opened:
  the other app owned port 443, so browsers reached its server instead of yours,
  and every check ReDock made asked its own ports and got a happy answer.
• When another app is holding the port, ReDock says so on Home and in Settings —
  it names the app, says its own web server is fine behind it, and gives you the
  other app's own fix when it knows one.
• One button switches ReDock to its own ports, and your sites open again
  straight away. Their addresses gain the port; nothing about the sites, their
  files or their databases changes, and you can switch back whenever the other
  app is gone.
• ReDock can quit the other app for you when it recognises it, or stop an
  unrecognised program after showing you exactly which one — and when the
  program belongs to the system it says so instead of offering a button that
  would not work.
• There is a switch in Settings → Local HTTPS for people who already know they
  run another local-server app, so the notice never appears.
• If the ports ReDock itself uses are taken, it moves to the next free ones,
  remembers them, and says which ones it is on and who took the old ones.
  Everything follows on its own.
• New in Settings → Advanced: "Check my setup" looks at every door your sites
  depend on and tells you, per site, what a browser opening it would actually
  reach. You can copy the report or send it to ReDock in one press with a short
  reference to quote back.
• A site that another app is answering for says so, instead of "nothing answered
  on the address" — something did answer, it just was not ReDock.
• The AI agent no longer fails on sites when another app holds port 443 — it
  talks to your sites over a path that never leaves this Mac.
• Sites with the AI features switched off no longer report an error about it.
  Nothing was wrong; it was a switch that was off.

ReDock 0.4.0

• Buttons say what they do. "Create WordPress", "Claim the name", "Delete
  images" — instead of a label that grew and shifted as you typed a name into
  the field above it.
• A live site's debug log can be switched on from ReDock and read in its Logs
  tab. ReDock edits the site's wp-config.php for you, keeps a copy of the
  original, and can put it back. The live site needs ReDock Connect 1.5.0 or
  newer — the one-click update on its Connection tab does that.
• The AI agent's screens are split the way you use them: an "AI permissions"
  tab for what the AI may do on a site, and the conversation on its own. Chat
  text can be selected and copied. The message box grows as you type, can be
  resized by hand, and remembers the size you gave it.
• The update banner is a popup now. "What's new" shows the notes for every
  update before you take it, and when you are already on the latest version it
  shows the notes for the version you have.
• Copying a live WordPress site is a different thing now. Instead of dragging
  it down file by file — thousands of separate requests, and a big video that
  died at 490 MB of 500 starting again from zero — the live site packs itself
  into one archive on its own disk, and ReDock brings that down in pieces that
  pick up at the exact byte if your connection drops. On the test site that is
  185 requests down to 52.
• Sites whose ReDock Connect plugin is older still copy exactly as before, and
  the wizard says so rather than leaving you guessing why it is slow. Updating
  the plugin on the live site is the one-click button already on its Connection
  tab.
• Backups are real backups. A backup is now a dated folder holding the site's
  files, its database, and a sheet of checksums that proves both — not just the
  database. ReDock keeps the last five per site and says so on screen before it
  removes the sixth.
• "Back up now" works on any WordPress site, whether or not it came from a live
  one, and a copy pulled from live keeps its archive as the first backup for
  free.
• If a site's media was left on the live site, its backup offers to go and get
  it — on by default, with the size shown before you commit. Turn it off and
  the backup says, in words, that the media is not in it.
• You can restore a backup over the site it came from — after ReDock takes a
  safety backup of what is there now — or turn it into a brand new site and
  leave the original untouched.
• Fixed: database backups could be taken and then refused to restore. That
  affected the old database snapshots too, and both are fixed.
• Refreshing a site from live asks what you want first. Incremental brings down
  only the files that changed — the quick one, and now the default — while Full
  downloads the whole site again for an exact copy. Each says what it costs you:
  Incremental cannot notice a file you deleted on the live site, so that file
  stays on this Mac.
• Fixed: a backup with nowhere to go now says so before it starts. ReDock
  checks there is room first and refuses in plain numbers — how much it needs,
  how much you have — instead of running for twenty minutes, filling the disk
  and leaving you with neither the backup nor the space to try again.
• Fixed: the new-site wizard could tell you to install PHP when PHP was already
  installed. It was showing that the moment it opened — before it had finished
  looking — and if the check failed it never looked again. It now says what it
  is doing, and offers to try again if it could not find out.
• Fixed: the web server no longer restarts itself over and over. ReDock decides
  whether it needs restarting by comparing the configuration it wants against
  the one the running server loaded — and that comparison was moving on its own
  whenever a public share link had come and gone, so the answer was always
  "restart it". In every log we have, the check had never once come back
  "already correct".
• Fixed: a site that is simply slow to answer after starting is no longer
  reported as a broken web server. WordPress can take a few seconds to serve
  its first page; ReDock now says that site had not answered yet, instead of
  telling you to restart a web server that was working the whole time.
• Fixed: ReDock's own health checks no longer fill the web server's log with
  errors. Each check used to hang up as soon as it had its answer, and the web
  server wrote that down as a failure every time. It reads to the end now.
• Fixed: two sites starting at the same moment could be handed the same port,
  and the second one would quietly fail to come up and fall back to serving its
  files instead of running. Ports are now claimed at the instant they are
  chosen.

ReDock 0.3.2

Full Changelog: https://github.com/iPial/ReDock-releases/commits/v0.3.2