Skip to content

Kitewell 0.27.1 — Public beta

Pre-release
Pre-release

Choose a tag to compare

@yohamta0 yohamta0 released this 17 Nov 01:47

Kitewell 0.27.1 is a beta update, with the Dagu 2.27.0 engine.

What's in this release

  • Kitewell starts when it is opened again soon after quitting or after an
    update, rather than stopping at "Kitewell could not start". It waits
    for the previous background service to finish shutting down, then
    starts the new one.

It also brings everything in 0.27.0:

  • The chat is one conversation per project. Kitewell builds, checks, and
    changes workflows in it directly, so what you add next, such as a site,
    a budget, or another condition, goes straight into the work.
  • Kitewell reads your Google Calendar events. When a workflow needs
    Google Calendar, it asks you on a card in the chat to sign in, then
    goes on with what you asked.
  • A workflow's steps on a website share one browser: each starts on the
    page the one before left, still signed in.
  • A list whose pages a Next button turns is read in one step, across
    every page.
  • Rows a site or a sheet gives, such as listings or orders, are kept or
    left out by their values as written, such as 4,280万円, 徒歩4分, or
    昭和58年5月.
  • Conditions you give, such as a budget or a distance, are kept as the
    workflow's settings, so changing one later changes only that value.
  • After a change, Kitewell's check runs again only the steps that
    changed, and every change is checked before it is saved.
  • Kitewell starts a saved workflow only when you ask it to.
  • When you skip a question, Kitewell asks for the site, file, account, or
    model the work needs rather than picking one.
  • Opening the API library, mail accounts, sheets, or knowledge during
    first-run setup no longer fails.
  • Alerts read in the language you read Kitewell in: email, Slack, Teams,
    PagerDuty, webhooks, and Mac notifications, with their titles, counts,
    times, and reasons.
  • Starting a workflow that is already running or queued says so and what
    to do, in your language.
  • The chat answers in the language you write in, even when this computer
    is set to another, and keeps that language in its titles and status.
  • The chat's Thinking shows a model's reasoning from its first word, such
    as DeepSeek's on OpenRouter, which lost its opening words.
  • A chat step that failed says what it could not do, such as "Could not
    read workflow “Daily report”".
  • A notice already showing stays above a dialog that opens.
  • A count of one reads in the singular, such as "1 row" and "1 active".
  • Japanese and Chinese set a name directly against the word after it,
    without a space.
  • Chinese, Korean, French, and German use one word for this computer
    throughout.
  • In the view a connected AI app shows, each run a sheet made names its
    row, such as "Competitor prices, row 3: Giant magnet".
  • Actions in a table row, such as 編集 and 失効させる, keep their label on
    one line.

Upgrading

Nothing to do. Kitewell 0.26.1 and 0.27.0 update themselves to 0.27.1 at a
quiet moment, and running workflows go on across the restart. From 0.26.1,
messages from earlier chat threads no longer show; the rest of the
conversation stays. If Kitewell 0.27.0 shows "Kitewell could not start",
choose Try again.