Skip to content

Kindred 2.0.0

Choose a tag to compare

@niklas-heer niklas-heer released this 09 Nov 11:35
· 708 commits to main since this release

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.