Kindred 2.6.0

Kindred 2.6.0

2.5 added email. 2.6 uses it to make signing in simpler, and makes the sign-in with Google or a personal Microsoft account
something an operator can set up in minutes. Try Kindred on two invented families first:
kindred-demo.niklas-heer.workers.dev.

For everyone

• A sign-in code by email, where your server offers it. Choose Email me a sign-in code on the sign-in page and type
  your account's address; a six-digit code arrives, and works once, for 10 minutes, in the browser that asked. It is a way
  back in, for example after losing every device. If your account has two-step codes, they are still asked. You get a security
  notice after each sign-in this way.
• A new passkey straight away. After signing in with a code you can add a passkey on the new device without more proof.

For operators

• Code by email is off by default: switch on the Code by email card in the console's Sign-in tab. It stays unavailable
  until your server sends email (Email tab, which needs KINDRED_ORIGIN). Codes go only to an account's confirmed address,
  at most 3 an hour per account. An operator signed in with a code needs two-step codes to open the console, and a code is never
  an operator's proof. The trade-off: whoever can read a member's mail can get in, unless the account has a password with
  two-step codes (a member needs a password before turning them on).
• Guided single sign-on setup in the Sign-in tab: Add a provider, then pick Google or a personal Microsoft account
  (Outlook.com, Hotmail, Xbox). The wizard gives the exact redirect URL and every value to paste, and links to the right page
  of the provider's console. Test sign-in runs the real sign-in with your own account and creates nothing; once it works,
  you turn the provider on for your relatives (with the Single sign-on card on). Apple is not included.
• Health warnings: Google deletes OAuth clients nobody used for six months, and Microsoft client secrets expire. The
  console warns you before either happens, and the audit records whether a saved provider had been tested.

Upgrading

Back up first. Accounts migrations 0058 and 0059 are new and keep all stored data; 0059 makes the short-lived
oidc_flow table again, so a single sign-on sign-in in progress during the upgrade has to start over. On Node they apply at
start, on Cloudflare mise run deploy applies them before the new Worker goes live.

• Nothing to do: the code by email is off and no provider changes until you act, and there are no new settings.
• To turn the code on, set up email first, then see
  A sign-in code by email. To set up Google or Microsoft, see
  Single sign-on.
• The hosting guides now describe what Kindred emails; they no longer say it sends none.

The full list is in the changelog.

Kindred 2.5.0

Kindred 2.5.0

2.4 made Kindred something you can run for other families. 2.5 adds what running it for years needs: backups that prove
they work, a gentle end for families nobody visits any more, and email, so a forgotten password or an invitation no
longer depends on someone passing a link along. Try Kindred on two invented families first:
kindred-demo.niklas-heer.workers.dev.

For everyone

• Email, if your server sends it. Confirm your address under "Your email" in the account menu; then you can reset a
  forgotten password by email, and you hear about changes to how you sign in (a new passkey, a changed password). Emails
  come in your language, carry no tracking and link only to your Kindred. Notices can be unsubscribed with one click,
  except security notices, breach notices and a family's final notice before deletion.

For stewards

• Invitations by email, with the link still there to copy.
• A quiet family stays safe. If your server's operator turns the lifecycle on and nobody visits for a long time, you are
  warned first; a read-only family comes back with one click, and you can always download a copy before anything is
  deleted.

For operators

• Backups of every family and of the accounts, every night, encrypted, kept 7 days, 4 weeks and 12 months. A weekly
  restore drill proves one restores. The Backups tab restores a family into a new family (for the stewards its backup
  recorded; pictures only when they are all still its stewards) or over itself, and on Cloudflare rolls a family back to
  before an update. Keep KINDRED_BACKUP_KEY (or KINDRED_SECRET) somewhere other than the server: without the key a
  backup cannot be opened. scripts/backup-open.ts opens one offline.
• Lifecycle of quiet families, off by default: warning, read-only, deletion, with your thresholds, a dry run first and
  automatic deletion only after a final notice reached a steward.
• Email in the console's Email tab: Resend, Postmark, Mailgun (EU region) or SMTP on Node, with a test email and
  delivery problems on the Health tab. It needs KINDRED_ORIGIN, so every link in a message points at your server.
  Sending is limited per address, account, network and server, with a reserve for security mail.

Upgrading

Back up first. Accounts migrations 0051 to 0057 are new, all adding tables or columns; on Node they apply at start, on
Cloudflare mise run deploy applies them before the new Worker goes live.

• Nothing changes until you turn it on: the lifecycle is off, email is off until a provider is set, and the backups begin
  with the next daily run (families on D1 bindings are covered by Cloudflare's own Time Travel instead).
• The Node build gains one dependency, nodemailer, for SMTP; the Worker does not include it.

The full list is in the changelog.

Kindred 2.4.1

The Docker image of 2.4.0 did not build: the image left out the processing-agreement template the app renders. 2.4.1 fixes that. It has no database changes, and nothing changes for Cloudflare installs. What 2.4.0 brought is in its release notes.

Kindred 2.4.0

Kindred 2.4.0

2.3.0 let one server host families for other people. 2.4.0 makes that something you can run: Kindred speaks eleven
languages, offers passwords and single sign-on beside passkeys, gives members and operators what data protection asks for,
and lets an operator open sign-up, decide feature by feature what each family may use, watch how the server grows and keep
it up to date. Try it on two invented families first:
kindred-demo.niklas-heer.workers.dev.

For everyone

• Eleven languages. Spanish, French, Italian, Dutch, Polish, Brazilian Portuguese, Japanese and Simplified Chinese join
  English, German and Afrikaans: every page, the words for relatives ("your great-aunt"), plurals, dates, heraldry,
  occupations and the questions of the week. Each language was translated and then reviewed by a second model.
• More ways to sign in, where your server offers them: a username and password with two-step codes (scan the QR code)
  and recovery codes, or single sign-on with Google, Microsoft, Authentik, Keycloak or another OpenID Connect provider. One
  account can have several ways in.
• Your data, your choice. Download everything your account holds, or delete your account, from the account menu.
• New in Kindred shows what each release brought, in your language.

For stewards

• Answer a relative's data request. A copy, a restriction, or erasure of someone everywhere in the family (history,
  pictures, the feed and the assistant's conversations included), with the deadline in view.
• Features your operator manages show as locked, with one sentence saying why and how to reach them.

For operators

• Hosting mode and sign-up: a landing page, and stewards may start a family themselves (Turnstile, terms, a processing
  agreement, 16 or older), within limits per day, network, account and in total, or with sign-up codes; a readiness
  checklist says what is missing first.
• Policies: the Campaign, the assistant, painted portraits, address suggestions and push, each off, left to families,
  or for chosen families only. AI can run on your key with per-family and server-wide monthly budgets, reserved before every
  call. Announcements reach stewards or everyone.
• Sign-in tab: turn passkeys, passwords and single sign-on on or off, add providers, and make a reset link; it refuses to
  lock the last operator out.
• Statistics, Health and Updates: growth and activity as counts (small numbers hidden), the daily jobs and backups, a
  release check after you agree to it, and a one-click Update for copies made with the Deploy button.
• Privacy tab: the record of processing (Art. 30), the subprocessors (also on /legal), a breach register with its
  72-hour clock, a retention job that reports before it deletes, and statements of reasons when you suspend or close a
  family. See docs/gdpr.md and the processing agreement template.

Upgrading

Back up first. This release adds twelve migrations to migrations/accounts (0038, 0040 to 0050), all adding tables or
columns. On Node they are applied when the server starts, after a copy of the accounts database; on Cloudflare,
mise run deploy applies them before the new Worker goes live. To go back to 2.3.0, restore that copy and start the old
version.

Things to know:

• Nothing changes for a single-family install until you change it: passkeys stay the only way in, the mode stays
  "single", every policy stays "each family decides", and the release check stays off until an operator agrees to it.
• KINDRED_SECRET now also protects passwords and recovery codes. Changing it invalidates every password; keep it.
• Copies made with the Deploy button set KINDRED_UPDATE_VIA=github-actions and can update from the console. Others see
  their own update steps.
• From this release on, migrations are additive: the previous release's code keeps working against them.

The full list is in the changelog.

Kindred 2.3.0

Kindred 2.3.0

2.2.0 gave the family a cookbook, a game of one's own and a feed. 2.3.0 makes the feed say what changed, moves the Campaign
onto an invented continent with a board worth coming back to, and lets one Kindred server host families for other people,
run by an operator who never reads their records. Try it on two invented families before installing anything:
kindred-demo.niklas-heer.workers.dev.

What's new for families

• The feed shows the new value. "Ada updated Carl: new phone number +49 30 …, born 3 May 1950 in Graz." A phone number
  or email you can tap, an address that opens the map, the start of a biography, "Phone number removed". Each reader sees
  only what they could see on the person's page now; old values never, and medical, allergy and faith notes are named by
  kind only. See docs/feed.md.
• The Campaign on an invented continent. A new continent each week, with invented names (checked against real places
  and well-known fictional ones) and real terrain: marshes hold few troops, an attack across a river or by sea takes two
  rounds, mountain ridges close a border. The family's houses are your rivals. Marches, battles and conquests are animated,
  and a reign ends with a chronicle and a title. On a phone the turn, Undo and "End the turn" stay at hand.
• One reign a day counts. The first reign you begin each day is the one the family's table ranks; it is kept as you
  play, so you can continue it on another device. More reigns are practice and still show your personal best. Each score
  shows the renown and quiz advantages behind it. See docs/campaign.md.

Hosting families for other people

• The operator. An instance role, separate from every family's roles. The console at /operator lists the families
  (size, storage, stewards, status; never their records), makes a family for someone with a one-time steward invitation
  (the operator is not added), keeps the waiting list from the public request form, handles data requests from relatives
  who never signed up and forwards them to the family's stewards, sets storage caps, can make a family read-only or close
  it, and keeps an audit log. Operators can be told of new requests by push.
• Who may make families: the operators only, any steward (as before, and the default on an existing install), or
  anyone by request. New installs limit each account to five families.
• Legal pages. An Impressum, privacy policy, terms and a report-content contact, written in the console, appear at
  /legal and in a quiet footer. While there are terms, making a family or becoming its steward asks to accept them.
• Families in Durable Objects on Cloudflare. A family gets its own SQLite-backed Durable Object the moment it is made:
  no D1 binding, no redeploy, no limit of bindings, up to 10 GB each, optionally in the EU. Existing D1 families keep
  working. A Deploy to Cloudflare button starts a new install. scripts/import-to-do.ts moves a family in;
  scripts/backup-do.ts lets a steward download one.

See docs/hosting-many-families.md, with a short checklist of what running a server for
other families involves in the EU (not legal advice).

Upgrading

Back up first. This release adds seven migrations:

• migrations/tree 0035 and 0036: the Campaign's rulesets, and the counted reign fixed when it begins. Apply them before
  the new code serves.
• migrations/accounts 0033 to 0037: Durable Object families, the operator, requests, imports, closed families and terms.

On Node they are applied when the server starts, after a copy of each database. On Cloudflare, mise run deploy applies
them before the new Worker goes live. To go back to 2.2.0, restore those copies and start the old version.

Things to know:

• Your earliest account becomes the server's operator. Nothing else changes for a self-hosted family: family_creation
  stays stewards, there is no family limit, and the legal links stay hidden until the operator writes them.
• Earlier Campaign reigns are kept and listed apart (an earlier ruleset); they are not compared with the new ones. A
  reign in progress in an open tab under the old rules is let go with a short message.
• store.treeIds() and store.ensureTree() are async for anyone with code against the store.
• New settings: KINDRED_JURISDICTION, KINDRED_TURNSTILE_SITE_KEY, KINDRED_TURNSTILE_SECRET.

The full list is in the changelog.

Kindred 2.2.0

Kindred 2.2.0

2.1.0 gave the family a reason to come back. 2.2.0 makes that time better spent: a cookbook for the family's recipes, a
game you can play alone in a few minutes and compare with everyone, a feed that tells you what changed, emoji reactions,
seeing who of the family is here with you, a quick game of naming people in old photographs, portraits that can look like
you, quicker editing, and two tours that explain it all. Try it on two invented families before installing anything:
kindred-demo.niklas-heer.workers.dev. The demo offers the grand tour first.

What's new for families

• Recipes and the Cookbook. A recipe has a form of its own: ingredients in rows (type or paste "800 g beef, diced" and
  it sorts itself), numbered steps, servings, times, tags, where it comes from ("Grandma's") and a picture of the dish that
  stays with the recipe and is not in the Gallery. Its page scales the amounts, lets you tick off ingredients, has a
  cooking mode that keeps the screen awake, and prints as one sheet. The Cookbook gathers the family's recipes with search
  and filters. See docs/recipes.md.
• The Campaign, played alone. A reign is twelve turns as your own house on a map made from the family's places, about
  eight minutes. Each turn you place troops, then give up to three orders (choose a province, choose a target, confirm),
  with your exact chance shown before you attack. Forests, highlands and towns change the odds and the levy. Everyone
  plays the same field each week and compares scores in a weekly table, an all-time list and house totals; recording the
  family still raises your renown. The old shared seasons are kept as "Seasons of old". See docs/campaign.md.
• Emoji reactions. A quick row (❤️ 😂 😮 😢 🙏 👏 🕯️) and a palette with search in English, German and Afrikaans.
  The emoji data ships with Kindred; nothing is asked of an outside server. Existing reactions are converted.
• Updates in the feed. "Ada updated Carl: has a new address, new phone number": what changed, never the value, one entry
  per member and day. Changes only editors may read stay with editors. Members can react to and comment on these, and on
  birthdays and anniversaries.
• Here now. Faces in the top bar show who of the family is in Kindred with you and where; a soft halo marks the tree card
  someone else has selected, and the Edit tab says "Anna is editing Carl". When nobody else is there, it says who was last
  here. Members only, and "Show me to others" in the account menu turns it off both ways. See
  docs/roles-and-privacy.md.
• Who is this? Untagged photographs become a two-minute game on Today, the Gallery and Needed. Anyone in the family can
  suggest who is in a picture; someone who may tag photographs confirms it, and the tag says who named them. See
  docs/who-is-this.md.
• Portraits that can look like you. Every hairstyle is redrawn as a shape of its own, with four new short cuts. Hair and
  beard take any colour, and a beard is chosen by coverage, length and cut, with the moustache separately. Existing drawn
  portraits change only in their hair and beard.
• Quicker editing. On the Edit tab each field folds to one line and only the one you are editing opens. The address box
  suggests whole addresses as you type. Search (⌘K, or the search icon on a phone) also finds places and ignores accents.
• Two tours. New members are offered Welcome, a short walk through what matters on the first day. The grand tour
  covers everything in chapters you can skip, pause and continue; some steps wait for you to try the thing, and "Show me"
  does it for you. Both are under Tours in the account menu. See docs/tours.md.

Upgrading

Back up first. This release adds six migrations:

• migrations/tree 0030 to 0034: emoji reactions and feed events (0030 makes the reaction and comment tables again with
  every row and turns each stored reaction into its emoji), recipes, the Campaign's reigns and its weekly field, and
  "Who is this?".
• migrations/accounts 0032: "here now".

On Node they are applied when the server starts, after a copy of each database. On Cloudflare, mise run deploy applies them
before the new Worker goes live. To go back to 2.1.0, restore those copies and start the old version.

Things to know:

• Address suggestions go to komoot's Photon service. The address box sends what is typed, through your server, to
  OpenStreetMap's Photon to suggest addresses. It is on by default; KINDRED_ADDRESS_LOOKUP=off turns it off, and the box
  then suggests only the family's own places and the offline towns. See docs/roles-and-privacy.md.
• The Campaign ranks reigns only with KINDRED_SECRET set (every normal install has it). The old shared season, if one
  was running, is closed on the first visit after the upgrade; its nightly job and push are gone.
• A new daily job, recipes, deletes the pictures of removed recipes after 31 days.
• Portraits: only the hair and beard of drawn portraits change. A stored full beard with the moustache set to "none" now
  shows a shaven upper lip.
• Tour progress is kept in the browser only.

The full list is in the changelog.

Kindred 2.1.0

Kindred 2.1.0

Kindred 2.0.0 was a place to keep a family's tree. 2.1.0 gives the family a reason to come back to it: a Today page with a
feed, a question and a quiz, a slow game, ways to answer each other's memories, and better tools for recording and printing
what you know. You can look at two invented families before installing anything:
kindred-demo.niklas-heer.workers.dev.

What's new for families

• Today and the family feed. Today is the page to open again tomorrow. Contributors write a short message to the
  family, with up to six pictures and the people it is about; everyone reads and reacts. The feed also shows new memories and
  sayings, a day's photographs, people added to the tree and the end of a Campaign season. Beside it: the question of the
  week (sixty curated questions; an answer is saved as a memory), a daily quiz made from the family's records with a streak
  and a monthly table of houses, the week's birthdays and anniversaries, and one nudge from the Needed page. Share-link
  guests get no feed. Stewards can switch the quiz off. See docs/today.md and docs/feed.md.
• The Campaign. A slow game between the family's houses on a map made from the family's places. Well-recorded houses
  raise more troops; everyone gets three orders a day; a season lasts 28 days. It is off until a steward turns it on under
  Games, never changes the family's records and is left out of every export. See docs/campaign.md.
• Reactions and comments. Members answer a memory or a gallery photo with a heart, "I remember this", a laugh, a candle
  or a thank-you; contributors can comment in plain text. The writer can ask for a push about answers (at most one a day).
  See docs/responses.md.
• Life events and sources. Baptisms, schooling, service, moves, burials and custom events appear on the life timeline and
  on a new Events view of the Atlas. A Sources page holds registers, letters and books, and facts cite them; cited facts
  carry a small "sourced" mark. GEDCOM and the Markdown archive carry both, and the assistant can propose and answer from them.
• Change history and What's new. Every change to the family's records is kept with who made it and what it was before,
  and editors can put an earlier name, date, place or biography back. "What's new" summarises what changed since your last
  visit, and members can turn on a weekly push about it. History is kept three years.
• Print: charts and a family book. Ancestor and descendant charts, and a book with a cover, contents, a section for each
  house, every person and a register of names. Your browser prints it, so "Save as PDF" keeps a file. Living people are
  printed by name and place only, unless you switch "Living people in full" on.
• Ask to join. A guest of a share link can ask for an account with a passkey; a steward approves it with a role or
  declines it on the Access page.
• Managing families in the app. Stewards can create a family, change its details and delete it (after exporting it,
  typing its address and confirming with a passkey) on the new Families page.
• View as. A steward can preview the family as a viewer, contributor, editor, a particular member or a link's guest. A bar
  on every page says so, and nothing can be changed while previewing.
• The character editor. Clicking a drawn portrait opens an editor like a game's character creator: ten categories, many
  more skin tones, hair, clothing, headwear and accessories, "Surprise me", ready-made looks, undo and a comparison. Portraits
  you already have do not change.
• Smaller things. A lighter bar (Today, Tree, Chronicle, Gallery, Contacts, More), share links that protect living
  people by default, reading GEDCOM files in older encodings, text that follows the browser's text size, and a faster tree
  and Chronicle. The changelog lists the rest, including security fixes.

Upgrading

Back up first. This release adds fifteen migrations, all of which add columns or tables and change no row you have:

• migrations/accounts 0022 to 0029: which passkey started a session, the per-link "protect living people" switch (off for
  links that exist), "Guests may ask to join" (on for every link) and join requests, passkey confirmation, "since your last
  visit", the "View as" previews, and the push about a new post.
• migrations/tree 0023 to 0029: small gallery copies, life events and sources, the Campaign, change history (empty:
  earlier changes are not in it), reactions and comments, Today and the quiz, and the feed. 0029 rebuilds the reaction and
  comment tables with the rows they had.

On Node they are applied when the server starts, after a copy of each database. On Cloudflare, mise run deploy applies them
before the new Worker goes live (mise run cf:migrate:remote does that step alone). To go back to 2.0.0, restore those copies
and start the old version; an old version will not run on a migrated database.

Things to know:

• New setting KINDRED_TRUSTED_PROXIES: how many reverse proxies stand in front of the Node server (compose.yaml passes
  it on). Set it behind a proxy, otherwise the sign-in, share-link and invitation limits cannot tell visitors apart.
• New setting KINDRED_HISTORY_YEARS: how long the change history is kept (three years by default).
• KINDRED_DEMO=1 runs a public, read-only demo. It refuses to start beside accounts, Access, a guest host, a setup code
  or reminder keys. See "A public demo" in docs/self-host.md.
• The Node server now runs in production mode unless you set NODE_ENV, and the Content-Security-Policy is enforced rather
  than report-only. If you add scripts or embeds in front of Kindred, check them.
• Share links you already made keep their old protection; new links protect living people. The Access page shows and changes it.
• Removing a passkey signs out the devices that used it, and adding or removing one asks for a passkey confirmation.
• A ready-made multi-arch image is published to ghcr.io/niklas-heer/kindred for each tagged version.
• Restoring a D1 export needs one extra line that moves the guard view first; the corrected commands are in
  docs/deploy-cloudflare.md.
• A person's draft open across the upgrade asks once to load the latest version.

The full list, with every fix, is in the changelog.

Kindred 2.0.0

Kindred 2.0.0

Kindred v2 replaces the v1 Markdown archive application on main. It is a shared web app, built with
TanStack Start and React, running on Node 26 with SQLite or Cloudflare Workers with D1 and R2.
The Rust CLI and its binary installation are not the v2 server.

Changes

• Family, Dynasty and Ancestors trees, keyboard navigation, search, lenses and a minimap that draws the whole family as small house shields.
• Houses with arms, heads, heirs, succession laws and country flags. Name-meaning research and arms fit checks;
  new and revised designs can use the check's feedback.
• Atlas, Almanac, contacts, Chronicle, the Needed research list, photographs and albums. AI face suggestions
  become tags only after confirmation.
• Research projects: one question with its documents, pictures, notes, people and places on one timeline.
• Birth, current and further given names, nickname preferences, typed and labelled fields, and biography editing. Every field has
  a visibility level: Personal, Editors or Family. Life shows ages at dated events and a spouse's death or widowhood when the dates support it.
• A full-page profile for each person, images that open large, an exhaustive searchable faith list, favourite colours, and edits that
  save themselves, with fewer taps on a phone.
• Passkeys, invitations and server-enforced viewer, contributor, editor and steward roles. Each installation signs in one way,
  Kindred's own accounts or Cloudflare Access (KINDRED_AUTH).
  Read-only share links for relatives without an account, protected by a password by default.
• A guided tour for new members, counts-only usage statistics that a steward can turn off, and a feedback inbox that
  stays inside the family's own Kindred.
• A chat window you can move, resize and minimize, with tabs, searchable chat history, streamed replies and Stop. Pasted pictures,
  question cards and widgets for people, relationships and timelines. The assistant can propose nearly any edit a person can make, and
  nothing changes without approval. Stewards choose the model per chat and can retry an answer on a stronger one.
• Optional AI through Anthropic, OpenAI and OpenRouter: several connections per family and a provider/model per feature.
  Shared monthly budget, model discovery, optional web search, approval of assistant proposals, drawn avatars and
  painted portraits. Scheduled arms reviews, occupation/story translations and name-meaning collection have separate switches and a run log.
• English, German and Afrikaans; Codex, Paper and Night themes.
• GEDCOM import with preview, GEDCOM and Markdown export, optional Web Push reminders and nightly private GitHub archives.

Moving from v1

This is a migration, not an in-place CLI update. Back up the entire original archive and attachments, then install
and run the v2 server using the Node/Docker guide or Cloudflare guide.

For a Markdown archive, put person notes directly in people/ in a working copy, then run from the v2 checkout:

mise install
npm install
node scripts/import-kindred.ts /path/to/archive data/seed/family.json
node scripts/seed.ts data/seed/family.json

Create the first account to become steward and inspect the result before inviting others. For Cloudflare, configure
and migrate the family binding, then use the documented D1 transfer. An existing GEDCOM file can instead be imported
by a steward through Import and export, with a preview.

The Markdown importer is partial: it does not restore attachments, current names, titles, epithets, parent confidence
or partnership endings. Names are split at the last word, sex is inferred from parent roles, and repeated unions
between the same pair collapse. The note body becomes biography; structured sources and stories are not restored.
Keep the original archive and check the imported people and relationships. Read the full
migration guide and format limits.

v2 edits its databases; it does not sync changes back into a v1 folder. GEDCOM and Markdown exports omit parts of
the record and do not replace backups of accounts, family databases, media and the sealing secret.

Existing v2 installations

Cloudflare Access installs: set KINDRED_AUTH=cloudflare-access before you deploy this version. With
CF_ACCESS_TEAM_DOMAIN or CF_ACCESS_AUD set and no KINDRED_AUTH, every page of the members' site answers 503 and
nobody can sign in until it is set. Installs without Access settings need do nothing.

Back up before upgrading. Node applies SQL migrations when databases open and makes a copy before pending migrations.
On Cloudflare, run mise run cf:migrate:remote before mise run deploy. Keep KINDRED_SECRET unchanged.
Migration 0010 moves AI keys into provider connections and models into feature routes while preserving switches and
budget. Review the routes after upgrading; if separate assistant and portrait OpenRouter keys existed, the existing
family OpenRouter connection takes precedence.

0.1.0 — 2026-09-19

Release Notes

Documentation

• Add Kindred identity and introduce the user experience (de55bd2)

Features

• Establish Kindred Rust project and release foundation (9750771)
• Implement local family archive and evidence-aware exploration (f2eff81)
• Present family relationships as a readable generation tree (9f711cd)
• Derive family graphs from rich person notes (49de472)
• Organize family branches and flag research gaps (d441f29)

Fixes

• Support native Windows checks and isolate web fixtures (6c719eb)

Install kindred 0.1.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/niklas-heer/kindred/releases/download/v0.1.0/kindred-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/niklas-heer/kindred/releases/download/v0.1.0/kindred-installer.ps1 | iex"

Download kindred 0.1.0

File	Platform	Checksum
kindred-aarch64-apple-darwin.tar.xz	Apple Silicon macOS	checksum
kindred-x86_64-apple-darwin.tar.xz	Intel macOS	checksum
kindred-x86_64-pc-windows-msvc.zip	x64 Windows	checksum
kindred-x86_64-unknown-linux-gnu.tar.xz	x64 Linux	checksum