每个版本的记录。

Kitewell 0.22.3 is a beta update.

What’s in this release

• The project picker no longer says a project is starting long after it started. It read the other projects’ states only when the window opened, so after an update restarted them they kept saying Starting…. The menu now reads them each time it opens.
• The picker marks only projects that do not run: Paused, or Not in plan. A running project, and one starting or stopping, has no label.
• The box that narrows a long project list is lighter.

Upgrading

Nothing to do. Kitewell 0.22.2 and 0.22.1 update themselves to 0.22.3 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.22.2 is a beta update.

What’s in this release

• The project picker says in words how each project stands: Paused, Starting…, Needs attention, or Not in plan, with nothing beside a project that is running. It used to mark them with circles that some fonts drew as specks, so a project starting looked like a stray dot.
• The picker works from the keyboard as a menu does: arrow keys, Home, End, Enter, Escape, and a letter to jump to a project. With six or more projects, a box at the top narrows the list as you type. A project that starts or pauses while the menu is open no longer closes it.
• Manage projects is at the foot of the picker’s menu, in place of the small link below it.

Upgrading

Nothing to do. Kitewell 0.22.1 and 0.21.0 update themselves to 0.22.2 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.22.1 is a beta update.

What’s in this release

• Project settings → Screen steps picks the model that reads the screen for a project’s desktop steps: Kitewell vision, which is included, or one of your own API models. Before saving your model, Kitewell checks that it reads a test screenshot, and says why when it cannot. The choice syncs with the project, and a workflow or step that names its own model keeps it. An API model’s page in Agents & models offers Use for screen steps, and deleting that model returns desktop steps to Kitewell vision. A computer without the chosen model’s key says so before the workflow runs.
• Desktop automations work on every plan. On the free plan, Kitewell vision reads the screen within your workspace’s credits.
• The assistant learns an app from its window’s buttons, fields, and labels, as 0.21.0 described. That needed the engine in this release; with the engine 0.21.0 bundled, the assistant could not look at the app at all.
• A check of a desktop workflow never presses a button that saves, sends, deletes, or confirms, in Japanese or English, even when the model working the screen tries to. Desktop steps that run after one the check only shows are shown too, instead of failing on the form the save would have closed.
• Checks of desktop workflows take minutes, not half an hour. A look at an app closes what it opened, even when it fails; a check waits 30 seconds for a window instead of five minutes; and a model lost on the screen stops after 20 actions, and the assistant is told to try a model with a computer-use tool.
• Checks blame the assistant’s draft less often for what is not its fault. “Do not press 保存” no longer turns the step that fills in the form into one the check only shows, and a step that reads a shown step’s output no longer fails the check. The assistant is told why a step was only shown.
• The assistant keeps its place through long builds. Your answers on question cards, and your leave to work the screen, open sites, or upload files, hold for the whole conversation, and work that goes on by itself knows the draft is its own. It used to ask the same questions again ten minutes in and explore the app a second time.
• An address you type into a question card opens in the browser like one written in the chat. The assistant used to refuse it as a guess and ask again.
• Trying one step on its own no longer replaces the assistant’s draft.
• Desktop workflows the assistant writes fail less. It reads each step of a loop item that failed, opens a combo box or pop-up to read its choices, and is warned before a check when a step asks its model about a value the model never sees.
• An imported API’s field that takes a number or null is sent as null when its value is empty, instead of the request being refused.
• When the window’s page stops, it loads again instead of staying blank, and Quit and Restart to Update no longer ask to discard changes nobody made.
• The bundled engine is now Dagu 2.25.1. Desktop steps stay inside the app they work in and pick a list’s option by name, and a recorded act replays only on the rows it fits. OpenRouter failures sent with a 200 status are retried.

Plans

From December 1, 2026, the free plan holds no projects or workflows. Signing in to Dagu Cloud starts a 14-day trial of Kitewell Team, and running with nobody signed in needs Kitewell Team or its trial. What a plan no longer holds stays to open, read, and export. Until then nothing changes. From three days before a trial ends, the plan banner says when it ends and links to subscribe.

Upgrading

Nothing to do. Kitewell 0.21.0 and 0.20.2 update themselves to 0.22.1 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.21.0 is a beta update.

What’s in this release

• The assistant tries a desktop workflow on the screen before proposing it. Once you allow it on a card, once a conversation, a check opens the app and clicks and types in it for real, up to just before anything would be saved or sent. A loop of desktop steps runs its first item only, and Kitewell then closes what the check left open without saving. Until you allow it, desktop steps are only shown. While a step waits for you to stop using the mouse or keyboard, the chat says so instead of reading as working.
• The assistant learns an app in seconds before writing its steps. It brings the app to the front and reads the window’s buttons, fields, and labels from the system, with no model and no screenshot leaving your Mac. It clicks only what opens a menu, a form, or a list, never what saves, sends, deletes, or confirms. Building a desktop workflow used to take minutes before anything was proposed.
• Asked to work an app on your Mac, such as “the sales app Depot”, the assistant works the app instead of asking for its web address. A question that asks for an address also takes your own words, such as “it’s an app on this Mac”, instead of only a full https:// address.
• Desktop steps never work Kitewell’s pages open in a browser. They could click into them, press a workflow’s Run, and open tabs.
• Files and folders in the task picker: list a folder, copy, move, or delete a file, make a folder, read or write a text file, and zip or unzip, each as a short form. Folders on the way are created, deleting what is already gone succeeds, and a written file replaces the old one. A listing hands the files it finds to a loop.
• The menu bar’s list of runs waiting for you has an Ignore submenu. An ignored run leaves the list and the count, and stays off after a restart until it waits on something new. You can still answer it in Kitewell.
• Running a sheet’s rows by hand starts the rows the workflow accepts, as a schedule already did. Rows whose inputs the workflow refuses end at once with the reason, and the sheet says how many could not start. A manual run used to start nothing when any chosen row was refused.
• A sheet linked to a workbook no longer says finished rows are waiting to be written after they were, nor that the workbook changed since its rows were read when the change was Kitewell’s own write. The workbook panel shows the file’s path from your home folder, as ~/..., and the check boxes clear once the rows you picked start.
• On a wide window, the browser the assistant works sits beside the conversation, as tall as the window, instead of a strip above it.
• Workflows the assistant writes fail less. A loop that types each row of a list into a web form replays instead of asking the model again for every row. A dollar or euro column in a sheet reads as a number, so 79.02 no longer fails after rows of whole-dollar totals.
• The assistant no longer offers to complete a task waiting for you without the decision its form requires. It asks you for the decision first; the card used to fail with “missing properties” after you had said yes.
• A link to a project made after the window opened, from the chat or an MCP client, opens the project instead of saying it is no longer on this device.
• The assistant keeps your request and your language in view through long work that goes on by itself.
• The bundled engine is now Dagu 2.24.0. Desktop steps also replay in macOS sheets and in focused combo boxes.

Upgrading

Nothing to do. Kitewell 0.20.2 and 0.20.1 update themselves to 0.21.0 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.20.2 is a beta update.

What’s in this release

• Renewing a client certificate keeps its sites. Replace… on a certificate under Browser in Device settings takes its renewal and keeps the sites it opens. Adding the renewal as a new certificate used to be refused, because the old one still held those sites. When a site renews your certificate through the browser, Kitewell finds the renewal in your keychain, says so in the expiry notice, and opens Replace… with it chosen. A run that failed because a site’s certificate expired offers the replacement right where it says so.
• When the assistant opens a site whose certificate has expired, it asks you for the renewal on its certificate card and opens the site again once the renewal is in place.
• The assistant reads more of the pages you point it to. A site that asks for a client certificate, or whose certificate comes from your organization’s own authority, no longer ends in a TLS error: the assistant says which certificate opens it, or opens it in its browser, which presents this Mac’s certificates. Intranet pages go to that browser too, so a workflow for an intranet portal is built from the page itself rather than from your description alone.
• On an IPv6-only network, the assistant’s page reader and MCP event delivery now reach public sites that have only IPv4 addresses. They refused every such site.
• The assistant keeps working until the work is done. It used to stop after 24 actions in a row, on a reply cut short, and after a failed call to the model, and wait for you to press Continue. It now goes on by itself, trying again after a short wait when a call fails, until the work is done, needs you, or has gone on for 30 minutes, and then says so.
• The assistant fixes the right step of a long workflow. It reads that step on its own, with the loop it runs in, instead of paging through the whole definition.
• Workflows the assistant writes no longer fail on two mistakes. A step in a loop that read its item as ${item.name}, which the loop leaves as written, now reads ${foreach.item.name}. A browser step told to find a row by a variable, such as “the row whose date is %date%”, gets the date itself, since the browser’s model sees only the variable’s name. A secret stays hidden. What cannot be fixed this way is named when the workflow is checked, before it runs.

Upgrading

Nothing to do. Kitewell 0.20.1 and 0.20.0 update themselves to 0.20.2 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.20.1 is a beta update.

What’s in this release

• Desktop steps leave Kitewell’s own windows alone. A run started while the Kitewell window was in front maximized that window as if it were the app the workflow works in, and a step could have clicked in it. Kitewell now tells its engine that its windows are never to be resized, brought forward, or acted on.
• The assistant keeps answering in the language you write in during a long conversation. Once its own notes and long work pushed your last message out of what it reads, it could answer in English.
• The assistant and MCP clients now read a long workflow’s whole definition, page by page. The end of a long workflow’s YAML used to be cut off, so the assistant could not change a step it could not see.

Upgrading

Nothing to do. Kitewell 0.20.0 and 0.19.0 update themselves to 0.20.1 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.20.0 is a beta update.

What’s in this release

• Desktop steps on a Mac now work with an app’s buttons, fields, lists, and checkboxes through macOS Accessibility, as on Windows. A step Kitewell learned replays by finding the same control again instead of clicking a spot on the screen, so a moved window, another display, or a title that changes with the document still replays without asking the model. Dropdown options are chosen by name, and controls in apps built on Electron are found too.
• A desktop step that meets a screen your workflow did not expect stops there. It no longer brings its window forward over an unanswered dialog; the run says what the dialog asks instead.
• A desktop step can answer a screen an app shows only sometimes, such as 「入力内容をクリアします。よろしいですか？」 after a reset, whenever it comes up, and runs where it never appears wait nothing for it. A part only some runs need, such as a second contact, can depend on the run’s inputs, decided without the model, so one workflow covers every case. A check can also tell whether a button or field is grayed out. Kitewell writes desktop workflows this way, with a step per screen and checks before anything is submitted, so a failed run can be retried from the step that failed.
• Desktop steps are steadier. They read and act only once the window stops changing, which keeps apps that rebuild their window from crashing mid-step; look again while no window is in front; bring a window that is behind another forward before clicking it; and scroll reliably. When you use the mouse or keyboard during a step, it waits for you to stop and then returns to the app it was working in. A checkbox a pinned step sets is left checked or unchecked as recorded, rather than clicked.
• Google Calendar is built into the API library. Connecting it takes one click: Kitewell adds the connection and opens Google’s sign-in, and the connection names the Google account that signed in. It reads your calendars and when you are busy; reading events comes once Google completes its review of Kitewell’s access. Disconnecting a Gmail mailbox no longer ends a calendar connection of the same Google account.
• A Google sign-in for an API connection now stays connected. It used to end after an hour.
• API specifications converted from Google’s API documents import as expected: their actions are no longer marked unsupported, and each is named by what it does instead of by its path.
• A run you open in Runs & logs while it runs is now followed: the view selects the running step, keeps its output at the newest line, and scrolls the diagram and step table to it. A step waiting for you comes first, and a finished run lands on the failed step’s errors or the step that ran last. Anything you do there hands the view back to you; Follow live turns following on again.
• A change the assistant proposes to a workflow shows its diff right in the proposal card, with long stretches of unchanged lines folded.
• When the assistant works a website, it asks once per site rather than once per host, so a sign-in that moves between www., accounts., and app. of one site asks once.
• An alert for a run that stopped because the included model’s credits ran out now says so, instead of only naming the step that failed.

Upgrading

Nothing to do. Kitewell 0.19.0 updates itself to 0.20.0 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.19.1 is a beta update for Windows. The Mac app stays on 0.19.0, which already reads PDFs with PDFKit.

What’s in this release

• A Windows PC now reads PDFs without extra software. Teach from a manual and a hand-over file used to need poppler’s pdftotext on Windows, which most PCs do not have, so Kitewell asked for Word or text instead, after the file had been uploaded. The Windows app now carries PDFium, Chrome’s PDF engine, and reads a PDF with it when pdftotext is not installed, including the fonts Japanese PDFs embed; a 97-page Japanese manual reads in about two seconds. Where pdftotext is installed it is still used, for the layout of tables.

Upgrading

Nothing to do. Kitewell 0.18.4 updates itself to 0.19.1 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.19.0 is a beta update.

What’s in this release

• Knowledge is now What Kitewell knows (覚えていること). Kitewell learns how your team’s work is done as you work with it. Each business rule, way of working, or correction you state in the chat, even in passing, is kept at once in your words, and the chat says what it remembered, with Undo. New work keeps its rules before Kitewell builds it, and Kitewell reads everything it knows for every request. A page it writes after reading a web page or a run’s output waits for your approval instead.
• Teach from a manual gives Kitewell a PDF, Word or Excel file, or text. The file stays on this computer. Kitewell reads it and keeps each piece of work and each rule it sets out as a page of its own. A Mac reads PDFs without extra software; on Windows, reading a PDF needs poppler’s pdftotext, so give Word or text there instead.
• The page lists what Kitewell knows, newest first. Each page shows a short preview, opens to read in full with who Kitewell learned it from, and is edited where it is. Tell Kitewell starts teaching from the chat, and Write one yourself adds a page. What is new since you last looked is marked while you look and counted in the sidebar, including what Kitewell learned from you. A workflow’s own tab lists what Kitewell knows about it.
• Ask Kitewell to do something once, now, such as checking a mailbox, calling an API, or reading a website, and it runs it without saving a workflow. Anything that would change something waits for your approval on a card. Kitewell’s chat can now work a website itself, shown live. One-off runs show as One-off in run lists, can be deleted, and are removed with other runs.
• A question Kitewell asks with options also takes an answer in your own words.
• What Kitewell’s model reads is masked with every secret the project’s engine keeps and the keys Kitewell holds, wherever they appear: run logs, artifacts, results, and their base64 and URL-encoded forms.
• When Kitewell checks a draft, a browser step now runs for real up to its first change, such as signing in and opening a form, so a step that cannot get that far shows in the check. A browser action runs in a check only when its words say it moves or reads; anything else is only shown.
• The Mac menu bar, the Windows tray, dialogs, notifications, and update prompts are now in the language you read Kitewell in, following your system until you choose one. Dates, times, and counts in run lists, queues, and history; a workflow’s schedule and inputs; and default names, time limits, and retries now follow that language too, and the app says workflow instead of DAG outside the YAML editor. A linked sheet’s columns and its results copy are named in a Chinese or Korean sheet’s own language.
• Batches moved under Runs & logs in the sidebar.
• A workflow whose params are written as a map of defaults now gets its params; it used to start with every param empty.
• A license renewed while this computer’s clock runs a few seconds behind is no longer refused.
• A window that loses its sign-in offers Sign in instead of an error that Try again could not clear.
• A sign-in an open browser is still using counts as in use on the sign-ins screen, so it is not forgotten from under it.
• Kitewell ends a turn that keeps repeating one failing call, and no longer rereads its failed calls in later turns.

Upgrading

Nothing to do. Kitewell 0.18.4 updates itself to 0.19.0 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.18.4 is a beta update.

What’s in this release

• Each project now has its own conversation with the assistant, so a chat about one project no longer carries another’s history or acts on another project. The chat shows the conversation of the project the Kitewell window shows, and picking a project in either moves the other, unless the window holds unsaved work. With two or more projects, a switcher in the chat lists each one with what waits for you there, whether Kitewell is at work there, or new activity. Notifications open their card or thread in its project’s conversation. Deleting the conversation from the chat header covers only that project; Settings deletes every project’s conversation.
• The assistant now checks a draft with live data without asking first. Only steps that read run: browser steps, GET requests, mail searches, model calls, scratch copies of workbooks, and commands that only read. Steps that send or change something, such as a command that writes, an upload, or a browser action that commits something, are not run. While it checks, the chat says how many steps are done, and each proposal says whether it was checked with live data. The card asking to try a workflow, the trial question, and the trial results in the chat are gone.
• On a Mac, the menu bar now lists the runs waiting for you under Waiting for you, each by its workflow and the first line of what it asks. Choosing one opens Kitewell where the run is answered. It lists ten and says how many more wait.
• A human task’s form now reads like a form: choices as options, yes or no as a checkbox, dates as date pickers, and text fields sized to what they hold. A blank optional field is left out, errors name the field’s label, and a form that only asks for one of a few answers shows them as buttons that complete the task. Prompts show as formatted Markdown, and a long one scrolls so the answer stays in reach. Clicking outside a run’s dialog asks to discard changes only once you began an answer.
• When you approve a run on a card in the chat, the card follows the run until it ends, also across a restart. The assistant then reads how it ended and tells you, with one notification.
• Workflows the assistant writes use your language, including step names and what each browser or desktop step is told to do. It does data work between steps in JavaScript steps instead of awk, sed, or text pipelines, which behave differently on Windows and macOS, and it keeps large data, such as a pull request’s diff, in a file instead of a step output, so run lists and sheets do not slow down reading it. It no longer asks for a password or key among its questions; it asks for a secret, whose value it never sees.
• The workflow editor has a JavaScript task, Work out values with JavaScript, for picking, counting, reshaping, or calculating values from earlier results. Its panel shows what the script reads, the script with highlighting and common snippets, and what it returns. A workflow reference typed into the script, which the engine never fills in, is caught and moved into the input in one click. The spreadsheet starters now use it, so their scripts can be changed there.
• Approving a step, completing a task, and running, stopping, or saving a sheet no longer fail with “Kitewell is completing another operation” while a sheet runs; they wait their turn. A sheet keeps going when rows wait for people, and a scheduled time runs every row whose last run has ended instead of being skipped. Stop all also ends rows waiting for an approval or an answer, and Cancel queued rows cancels only the rows queued when you asked. A row taken off its queue shows as cancelled, and a row the engine keeps refusing fails after 15 minutes with its reason.
• A sheet’s run controls say what they do. Rows that failed or were stopped run again together, leaving out rows a person rejected. A row waiting for an approval opens its run to answer it, any row at rest can run on its own, and the run button says when selected rows are left out. A launch Kitewell refuses starts nothing and leaves every choice open, and a row whose run is still going is not started a second time. Conflicts and notices are worded plainly in the page’s language.
• A sheet launched again before its first launch finished shows one gauge for all of its launches, and Stop all and Cancel queued rows act on all of them. The gauge says how many rows ended, its counts open the rows they count, and its time left leaves out rows waiting for people. Runs not started yet show an outlined badge in sheets and run history, so a queued row no longer looks like one at work, and a row waiting for its automatic retry shows as retrying.
• A sheet’s columns can be resized: drag the edge of a column header, use the arrow keys, or double-click to fit. The widths stay on this device. A sheet without columns offers each published value with what it held in a successful run of its workflow; values too long or structured for a cell start unticked, and one control ticks or clears them all.
• The chat header no longer counts cards you cannot reach. Applying a change withdraws an earlier copy of the same change, marking a thread done or deleting a conversation withdraws the cards it left, and choosing the count opens the card that has waited longest.
• In a project synced through Dagu Cloud, a scheduled workflow runs on one device at a time, as mail workflows already did: turning its schedule on claims it, and the device it leaves turns it off. A device waking from sleep or starting after being off holds its schedules until it has taken Dagu Cloud’s changes, then replays only the missed times of schedules it still holds, so a schedule moved to another device does not run on both.
• Kitewell Free now includes a webhook for one workflow. Personal and Team include as many as you need. When a plan lapses, the webhook turned on first keeps working, and the others start nothing until the plan is back.
• In MCP clients that show Kitewell’s run view, such as Claude and ChatGPT, the view can list a project’s activity: runs going now, each waiting run with its step and what it waits for, then the latest finished runs. Starting, retrying, or approving a run draws it live. When the connection may run workflows, a waiting step can be settled in the view itself, with its approval, form, or answer. A browser or desktop step shows its screenshots there.
• The ChatGPT connection now lists each operation as its own tool. ChatGPT does not get the tools that import APIs or answer a browser or desktop step’s question, which is often a sign-in code; Kitewell’s chat, Claude, and other clients keep them.
• The window shows its pages while project engines start instead of waiting for every engine, and each page loads only the translations of its language. Pages no longer sit on “Getting things ready” when several parts of Kitewell read the same runs at once. Switching language now also translates weekday names, missed-schedule policies, run filters, file chips, and workflow sort labels.
• Background checks only look at runs from the last day, so Kitewell stays light with long run histories. A run already found waiting for you stays seen however old it is. Sheets ask the engine about each row less often, and launches of deleted sheets are passed over.
• In a copy of Kitewell that cannot update itself, such as one run outside Applications on a Mac or from a folder on Windows, Check for Updates now says that only Kitewell installed from kitewell.app takes updates and offers to open the download page.
• The bundled engine is now Dagu 2.22.0.

Upgrading

Nothing to do. Kitewell 0.18.3 updates itself to 0.18.4 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.18.3 is a beta update.

What’s in this release

• Under every live answer, the chat says what Kitewell is doing and for how long: thinking, writing a workflow, trying it, running a step, or waiting for you. A long step no longer looks stuck.
• While the assistant writes a workflow, its diagram grows step by step in the chat. A trial lights up each step as it runs, then shows where it stopped and what each step found as tables, and all of it stays after a reload. Rows the assistant’s browser reads off a page show as a table too.
• When a workflow depends on what a site, a mailbox, or a file gives, the assistant first tries only the steps that read it, so you see real data sooner, then adds the rest.
• The assistant now changes its drafts by editing only the lines that change, and the chat shows each edit as it lands: the step it changes, marked on the diagram, with the lines taken out and put in. Trying a draft again after you allow trials, or proposing what was just tried, no longer rewrites the whole workflow.
• The chat answers at Medium reasoning effort unless you choose another level, so each step takes less time. A level you chose yourself stays as it is.
• The questions the assistant asks you also ask whether to allow trial runs, so the first trial does not wait on a card of its own.
• Every proposed workflow lists what you asked for, with the step that does it and what the trial showed.
• A run started from the chat shows its first report, the values it published, and the files it saved on its card once it ends, also after a reload.
• Results are no longer written into a workbook that Excel for Mac has open. Undo takes back all of a launch’s results at once, and they stay out of the workbook until you write them again or the row runs again.
• The spreadsheet starters run as their cards say, and a new starter merges a folder of branch workbooks into one sheet by column name.
• A kintone connection with OAuth 2.0 sign-in now saves.
• A run’s step table labels how long each step took as its duration.
• MCP clients can change a saved workflow by sending edits to its YAML instead of the whole YAML, and check those edits first.
• The bundled engine is still Dagu 2.21.0.

Upgrading

Nothing to do. Kitewell 0.18.2 updates itself to 0.18.3 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.18.2 is a beta update.

What’s in this release

• Dagu Cloud now chooses the model behind Kitewell’s included model, so it can move to a newer model without a Kitewell update.
• The included model’s page says that your prompts and the model’s answers are never used for training.
• Reset the conversation in the chat header starts the chat over, after asking once more, without a trip to device settings.
• Deleting a conversation finishes at once; its trial runs are cleaned up afterwards.
• While the engine starts or updates, the project’s status says so instead of offering Start engine.
• Page titles stay readable in a narrow window, as with the chat docked beside the pages.
• The bundled engine is still Dagu 2.21.0.

Upgrading

Nothing to do. Kitewell 0.18.1 updates itself to 0.18.2 at a quiet moment, and running workflows go on across the restart.

Kitewell 0.18.1 is the first public beta for macOS.

Kitewell runs workflows on your own computer: scheduled commands, Docker containers, coding agents and API models, browser and desktop steps, email, HTTP, SSH, and imported APIs, edited as a graph or as YAML. Each project runs on a bundled Dagu engine, kept running after the window closes, and Kitewell can connect to Dagu Cloud for sync, remote MCP, and run status.

What’s in this release

• The bundled engine is Dagu 2.21.0.
• One installer for each kind of Mac: Kitewell-0.18.1-arm64.pkg for a Mac with an Apple chip, and Kitewell-0.18.1-amd64.pkg for one with an Intel processor. Both are signed and notarized by Apple. The installer puts Kitewell in Applications and asks for an administrator password.
• Updates arrive by themselves: Kitewell downloads a new version in the background, checks it against the Kitewell update key, and installs it at a quiet moment or when you choose Restart to Update in the Kitewell menu. Running workflows go on across the restart.

Requirements

• macOS 13 Ventura or later, on an Apple chip or an Intel processor.
• About 3 GB of free disk space for the app and its updates.

Known issues

• This release has Mac installers only. Windows is on Kitewell 0.18.0.

Upgrading

Nothing to do. Kitewell 0.18.1 is the first public release for macOS; earlier Mac builds were private test builds and are not updated from.

Kitewell 0.18.0 is the first public beta for Windows.

Kitewell runs workflows on your own computer: scheduled commands, Docker containers, coding agents and API models, browser and desktop steps, email, HTTP, SSH, and imported APIs, edited as a graph or as YAML. Each project runs on a bundled Dagu engine, kept running after the window closes, and Kitewell can connect to Dagu Cloud for sync, remote MCP, and run status.

What’s in this release

• The bundled engine is Dagu 2.21.0.
• Installing is one download and one click: Kitewell-0.18.0-win-x64-Setup.exe installs Kitewell for the current user, with no wizard and no administrator prompt, and opens it. WebView2 is installed on first launch when the PC lacks it.
• Updates arrive by themselves: Kitewell downloads a new version in the background, checks it against the Kitewell release key, and installs it at the next launch or at a quiet moment. Running workflows go on across the restart.

Requirements

• Windows 10 or Windows 11, x64. ARM PCs run the x64 build under emulation.
• About 1 GB of free disk space for the app and its updates.

Known issues

• Only x64 is shipped; a native ARM build does not exist yet.
• The Mac release of 0.18.0 follows separately.

Upgrading

Nothing to do. Kitewell 0.18.0 is the first public release; earlier builds were private test builds and are not updated from.