The release log
What's new at the dock.
Every release, honestly logged. If a pill on this page says Fixed, there was a bug. That is how honest state works.
-
Workspaces on the web: teams, roles and client groups
- ReDock Web now has workspaces: a team with its own sites, plan and people, so an agency is not one login shared around
- Everybody keeps a personal workspace, and your desktop app and its plan carry on exactly as before
- Invite people by email with a role: Owner, Admin, Member or Viewer, and change or remove them at any time
- A viewer can look at every site and press nothing; a member works on them; an admin connects sites and approves AI apps
- Invitation links work once, for seven days, and only for the address you sent them to
- Removing somebody disconnects their AI apps from that workspace in the same moment
- Approve an AI app into one workspace: it reaches that workspace’s sites and no others
- Client groups file a workspace’s sites under the client they belong to
- Every action is recorded with the person’s name and the role they held at the time
- A workspace switcher sits at the top of ReDock Web, and each workspace carries its own plan and site allowance
- ReDock Web installs ReDock Blocks on a live site when you pair it, so the design tools work there without uploading a plugin by hand
- ReDock Web: if that install fails, the site’s row says why and offers an Install ReDock Blocks button plus the plugin zip to upload yourself
- ReDock Web brings back a missing or outdated ReDock Blocks on the next design call, the way the desktop app does
- ReDock Web hands you the ReDock Connect plugin: a Download button on the first-run page and the pair page, on any plan
- ReDock Web spells out the three steps after the download: upload it, activate it, then press Add a client key
- A site can now hold several ReDock connections at once, so the desktop app and ReDock Web no longer knock each other off
- ReDock Web: a site’s own page now has buttons, update a plugin, switch it on or off, change the theme, run a scheduled job, clear caches
- Every button asks the site the same way your AI does, so the change is recorded under your name and shows what it checked afterwards
- Updating a plugin and switching a theme ask you to confirm first, naming the site and exactly what changes
- ReDock Web tells you before you press that it cannot put an old plugin version back, because WordPress only installs the current one
- Switching a theme offers a one-press way back to the theme the site was wearing
- ReDock Web will not switch off ReDock Connect or ReDock Blocks from this page, and says why
- Settings → ReDock Connect lists every connected client with its fingerprint, when it was added and when it last called, each with its own Revoke
- The Connection tab shows which client this computer is and who else is connected, and can revoke any of them
- Disconnecting a site now revokes this computer’s key on the live site too, and leaves every other client working
- Revoking a site in ReDock Web now ends its key on the site as well, instead of leaving it valid there
- Asking a connected site what tables are in its database now works, instead of failing with a database error
- A site’s page in ReDock Web now says whether a theme update is waiting, and which version
- ReDock Web reads a site’s plugins and themes in one go, so its page loads with one less round trip to the site
- Your AI can read a live site’s own system information: WordPress, PHP, database, server, theme, plugins, users, disk and cron
- An AI that puts a heading’s text where Gutenberg’s own schema says it lives no longer writes an empty page: the text is folded in on both doors
- A block with no text anywhere is refused by name instead of being written empty and reported as done
- A page or post write that lost text after the save now says so, names the revision it created and hands back the fresh token
- Every option write keeps its previous value: the result, the audit row and the undo carry it, on the app and on ReDock Web
- One undo per answer: tools that used to say “no undo” beside an undo hint now put the call that reverses them in the undo itself
- New verb set_post_status (draft, publish, private, pending, trash) so “publish it” has a verb; publishing and trashing ask for confirm
- The AI’s instructions are generated from the live tool list on both doors, with one shared source of sentences; the web door now says “read it back”
- The served skill ends with a verb index of every tool by family, so nothing on the endpoint goes untaught under the instructions’ size cap
- The AI is told to ask before publishing, changing the front page or switching the theme when nobody asked for that
- ReDock Web creates pages and posts through ReDock Blocks when the site has it, so every core block composes; the thin path stays as the fallback
- ReDock Web gains update_plugins, activate_theme and search_replace, the same bodies the app runs on a connected site
- ReDock Blocks 1.5.2 reads a node’s text from attributes.content and the read shape too, takes a button’s content as its label, and adds set-post-status
- Your plan on the dashboard links straight to the ReDock Connect download when the plan includes ReDock Web
- ReDock Web gives every connected site its own page: WordPress, PHP, database, server, disk, theme, plugins, people, cron and who is connected
- Anything a site’s host will not report says so in words on that page, instead of showing a dash or a zero that reads as a real answer
- A site that is offline still has a page: what ReDock Web already knew, the time it knew it, and what the site said
- A site on an older ReDock Connect keeps its page and is told which version brings the rest
- The site page lists the AI apps that can reach it and the last changes they made
- Your sites list now links each row to that page and shows its ReDock Blocks version
- Check on a site row now confirms ReDock Blocks as well, so a plugin you uploaded yourself is recognised without installing anything
- Settings → ReDock Connect now shows this site’s own MCP address, ready to copy, so an AI app can be pointed at one site
- One press on that page connects a site to ReDock Web: it mints the key, shows it once, and opens the page that takes it
- An AI app given a site’s address reaches that site and no other, and asking it for a different site is refused by name
- Approving an AI app through a site’s address covers that site alone, and shows up as its own entry you can end on its own
- ReDock Web heads each site with the site’s own name and icon, with its address underneath, instead of a domain in monospace
- Give any connected site a nickname, like Client: Simply Agile, and it shows on that site’s page and on your sites list
- A site’s page in ReDock Web now lives at its own domain, so the address bar says the site you are looking at
- Update ReDock Connect on a live site with one press from ReDock Web: it installs over the connection and your pairing keeps working
- If that update cannot be applied the site keeps the plugin it has, and ReDock Web says in the site’s own words why
- A pattern with sub-patterns inside it now lands as real, editable blocks instead of placeholders you cannot type into
- Inserting a pattern says how many blocks it became and checks they reached the page, instead of trusting that it worked
- Reading a page back no longer calls an ordinary heading or list “rendered at view time”, which used to mislead the AI about its own writing
- Checking a page for a phrase now matches it whether or not WordPress curled the quotes or turned – into a dash, and says it did
- Asking for only part of a page is refused with a plain reason when the mode cannot return one, instead of answering nothing
- A page created a moment ago now reports when it was last changed, instead of a date that reads as never
- A long job like installing a plugin can no longer outlive its own connection and lose its answer after doing the work
- Installing or switching a plugin on or off now hands back the exact call that undoes it
- ReDock Blocks 1.5.3 resolves patterns made of other patterns, reports what an insert became, and answers a real last-changed time
- Windows: two WordPress sites now get their own PHP ports, so both serve while both are running
- Windows: the helpers ReDock runs no longer open command windows, and closing one can no longer stop a site
- Windows: the app says File Explorer, not Finder, and shows a Windows example path when you import a folder
- Making an n8n site no longer holds the app while n8n installs itself: the site appears and its row shows the progress
- The n8n setup line quotes how long the first run took on this computer, instead of promising minutes
-
Connected sites get themes, updates and search-and-replace; Windows fixes
- ReDock now says “this computer” instead of “this Mac” everywhere, so the words are true on Windows too
- Connected sites: switch or install a theme, apply a plugin update, run a search-and-replace (dry run first, with undo), export and import content
- ReDock Connect 1.7.0 for connected sites; the site’s Connection tab offers the update and says which tools wait for it
- Connected sites: writing a critical option asks for confirmation, and database writes keep the safety checks the tool promises
- Getting a single block type’s details works again on every site
- Refreshing caches on a connected site no longer fails; a page cache it cannot reach is named instead
- Running a scheduled task on a connected site now refuses a task nobody scheduled instead of reporting that it ran
- Connectors: point the AI at any remote MCP server on the internet, sign in when it asks, tick the tools it may use, and the agent calls them
- ReDock Web is now part of a plan: your plan says whether you get it and how many live WordPress sites you can connect
- ReDock Web tells you how many site slots you have left before you go and fetch a key, and says which plan would give you more
- Back up, deploy and verify can be stopped; a busy agent says so; one page lists external access
- Shared sites: give a person their own internet access to a plugin’s MCP server and revoke just theirs later (off by default)
- Connect a plugin’s own MCP server to the AI: you see its full tool list first and tick exactly what it may use
- The AI can ship a git-deploy site: redeploy it, roll it back, and publish its static build to your own Cloudflare account
- The AI can back a site up before it changes it, and restore or duplicate it from a backup (restoring over a site needs the same switch as deleting one)
- Connect Claude Code to ReDock and it can create, start and stop sites too (deleting needs a switch in Settings)
- A connected AI app can install a runtime and give a site a domain or a public link (removals need the same switch as deleting a site)
- A backup, restore or duplicate the AI started shows on the Backups card and can be stopped
- The local Gemma model now runs on Windows
- Windows: WordPress sites start cleanly, the site’s own AI works, imported folders keep their name, and a new site’s first backup gets enough time
- A plugin that prints after WordPress’s own command output can no longer empty a site’s plugin list or corrupt its theme name
- Choose where models download, on the download screen or in Settings
- A model on a drive that isn’t connected says so instead of downloading again
- The model picker names the chip that answered, and can always use the processor instead
- A model download that fails now says why, and checks the disk before it starts
-
ReDock runs on Windows
- 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
-
Gemini finishes real work; a Test button for every provider
- 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.
-
emdash: a modern CMS in one step
- 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
.testaddress 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
claudestarts 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.
- 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
-
A new site needs one thing: a name
- 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.
-
Gemini works, and the database tools open again
- 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.
-
Pick your model from what your provider actually serves
- 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.
-
Lives alongside Local, Herd, Valet and MAMP
- 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.
-
Sites open in every browser, and the setup check says why not
- 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.testis, 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.
- 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
-
Buttons say what they do; the debug log; AI permissions
- 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.
-
Errors report themselves
- Errors now report themselves. When something breaks, ReDock sends a scrubbed description of what happened so it can be fixed without you having to describe it, six fields, no file paths, no secrets, no way back to you. Settings › AI and privacy has the switch and says exactly what is sent.
- Fixed: creating a WordPress site could die at twenty seconds and vanish. The readiness check now understands WordPress’s own move to https, and a slow check leaves the site in your list with a note about what to try, it never deletes what it just made.
-
Every field issue from the first fresh-machine install, closed
- A new WordPress site never serves the installer as itself any more: it is installed first, then served, and “Ready” waits for a real
/wp-admin/answer. - Connected (remote) WordPress sites: 62 agent tools now work remotely, up from 47, and every one of the 109 site tools is accounted for in writing.
- The shared site’s wp-admin door works on the public link: one-click login is minted for the host the site is actually shared at.
- Database screens answer in two seconds when an engine is down, and say so honestly instead of spinning.
- Site names are capped at 63 characters with a live counter; repeated connection chatter in the Logs tab folds into one line; follow-scroll stays locked while you read.
- The curl credential for remote sites travels over stdin only, never a temporary file (a macOS 26 fix).
- A new WordPress site never serves the installer as itself any more: it is installed first, then served, and “Ready” waits for a real
-
The restructure: one calm window, six themes, honest everywhere
- The app is reorganised around eleven screens (Home, Sites, Create, Agent, Studio, Sharing, Activity, System, Extensions, Settings and the design storybook), each answering “what is this, what state is it in, what do I do next” at a glance.
- Six themes (Harbor, Marina, Bridge, Operator, Fairweather, Regatta) with one accent and one primary action per screen.
- Honest state became law: status reads only through the pill vocabulary; every error carries its fix; the first-run setup is a numbered manifest of exactly what changes on your Mac.
- The agent’s receipts, the activity ledger and the Studio (docs kits, video, images) moved into the restructure unchanged in behaviour, friendlier in words.
-
Plugin clones survive bad connections
- Network git operations abort a transfer that goes silent for 30 seconds instead of waiting forever, and a plugin clone retries once on a fresh connection, never after an authentication failure.
- The real error is logged and a half-finished clone is cleaned up, so no phantom rows.
- Earlier in the same week (0.2.5): the keychain token lookup and git spawns are bounded, and every git operation is logged.
-
The blank-window fix
- 0.2.0 could open to a black window when one screen read a field off a share record that did not exist. Fixed in three layers: the read itself, an error boundary under every screen so a crash always shows words and two exits, and a packaged-app smoke test that now gates every release.
- Sharing (0.2.0): named
*.redock.xyzlinks, quick links, custom domains with a two-record walkthrough, live visit counts, and stop-sharing that never stops the site.