Product updates

What's New

Latest record · v2.2.0 · Public & live

A public, privacy-safe explanation of what changed, why it matters, and where to find it.

This page is public and static. It never reads vault data, imported records, memories, notes, or private research artifacts.

v2.2.0Public & live

Bring the AI you already use, and let it read the record

You can approve a narrow, revocable connection for the AI you already use, and give it the actual scanned record to read rather than only its title. This is running on the live site. No assistant has yet completed a whole connection here, so we still name none as working.

Created

  • Created real file delivery, so your AI can read the scan instead of only its title.

  • Created a connection permission you approve, narrow, and take back at any time.

  • Created a clear separation between storing a file and letting an AI read it.

Fixed

  • Fixed a Memories tab that could only ever be filled by an import.

Upgraded

  • Upgraded saving so a whole source's worth of records lands in one approval.

What to check

  • Open a person, go to Memories, and upload a scan or photograph.
  • Confirm it arrives private, unreviewed, and not allowed for AI use.
  • Mark it reviewed with usable rights, allow AI use, and confirm a connected AI receives the file itself.
  • Confirm an item that only holds a link elsewhere reports honestly that it cannot be delivered.
  • Open Settings, AI connections, and confirm approving, narrowing, and revoking behave as described.
v2.1.0Public & live

Begin with one private family connection

A newcomer can now create two people and their known relationship directly in a private workspace, with clear evidence boundaries and an optional chosen-AI handoff.

Created

  • Created a direct private first start with one person and one known relationship.

Fixed

  • Fixed the empty workspace so its primary action begins with family, not a provider or AI.

Upgraded

  • Made the starting statement and its missing evidence visible after save.

  • Kept the chosen-AI handoff off by default and created it only after an explicit choice.

What to check

  • Open an empty signed-in workspace and choose Add your first connection.
  • Review two people, explicit living or deceased states, and the relationship before saving.
  • Confirm People and the person workspace retain the connected record and its needs-a-source cue.
  • Confirm Queue stays empty unless Ask your chosen AI is explicitly selected.
v2.0.2In review

Queue leads back to the work your AI saved

A completed chosen-AI handoff now gives newcomers a safe path from the Queue result into the private person and story records preserved in their workspace.

Created

  • Created an Open saved work bridge for completed Queue handoffs.

Fixed

  • Fixed Queue completion guidance so a chosen AI returns usable Family History paths.

Upgraded

  • Upgraded live workflow proof with exact synthetic-fixture cleanup guards.

What to check

  • Complete a marked Queue directive through a sanctioned chosen-AI connection and confirm Saved in your workspace offers the person and private story actions.
  • Open both actions and confirm they stay inside the signed-in owner's Family History workspace.
  • Confirm external or opaque result references never become Queue navigation links.
v2.0.1Public & live

A useful first step in an empty workspace

Newcomers now see the two working ways to begin and reach the current OAuth MCP setup from the signed-in workspace and Queue.

Created

  • Fixed the empty dashboard so its first actions work before any family records exist.

Fixed

  • Fixed signed-in AI wayfinding so normal setup leads to the current OAuth MCP guide.

  • Fixed the legacy API console's browser hydration error.

Upgraded

  • Added a first-screen reminder that imports, research, and publishing remain person-controlled.

What to check

  • Sign into an empty workspace and confirm the first actions are Bring in a capture and Connect your AI.
  • Open Your Queue and use See setup to reach /ai without creating a directive.
  • Open Your AI in app navigation and confirm it leads to current OAuth MCP setup, not the legacy key console.
v2.0.0Public & live

One clear home for family-history work

The product, workspace, AI connection, and normal public address now share one enduring identity: Assist With Family History.

Created

  • Created a clearer research-to-story front door and practical FAQ.

Fixed

  • Made assistwithfamilyhistory.com the normal product and sign-in destination.

Upgraded

  • Unified the public site, signed-in workspace, Queue, extension, metadata, and guides under Assist With Family History.

What to check

  • Open assistwithfamilyhistory.com on desktop and phone and confirm the Assist With Family History identity, research-to-story promise, FAQ, and current-status language are clear.
  • Open assistwithfamilyhistory.com/app while signed out, complete the normal sign-in journey, and confirm the workspace stays on the Family History address.
  • Confirm /ai, /ai.txt, /llms.txt, /mcp discovery, and the anonymous OAuth challenge all use the Family History resource address.
v1.1.1Backend live

Your AI can preserve the research trail

A first private, stateless connection now gives compatible AI clients a durable Family History work surface while keeping the person, evidence, and publication boundaries in charge.

Created

  • Created a private chosen-AI workspace connection for real research-to-story work.

  • Created human and agent setup guides with honest Current, Partial, and Later boundaries.

Fixed

  • Fixed new Queue directives so they can wait for the bounded OAuth chosen-AI identity.

Upgraded

  • Upgraded AI saves with provenance, replay protection, stale-edit checks, and human publication gates.

  • Upgraded chosen-AI privacy with server-selected tenancy and bounded living-person context.

What to check

  • Read /ai on desktop or phone and confirm the setup and Partial boundaries are clear.
  • If you have a sanctioned compatible client, confirm all twelve tools appear before saving anything. Fresh-device email verification and immediate JWT revocation remain Partial.
v0.1.0Public & live

Initial release-log baseline

This started the public, privacy-safe release log under the product's former Discover Their Stories name.

Created

  • Created the What's New page and its durable release-note source.

Fixed

  • Fixed the missing /updates route.

Upgraded

  • Upgraded route checks and quiet navigation to protect the release log.