What changed.
What became real.

The Yapture.com v2 foundation is a from-scratch rewrite built around three product principles: zero-friction starts, plain text as the portable interface, and many clients reading one truth.

The home page now starts with a local anonymous-list sandbox and performs no network request on load. A person can explicitly create a live list, receive its capability once, and then hand that scoped access to an agent. The portability demo uses @yapture/nlp locally so one line can be inspected as text, structured data, task, calendar evidence, or a client handoff without silent persistence.

Agent onboarding is now a first-class developer path rather than buried documentation. Examples use the current kind-discriminated payload contract, and live operations are clearly separated from local previews. Authentication, scopes, and MCP remain subject to the release-status registry rather than marketing copy.

Client concepts are consolidated into the product narrative and labeled by maturity. Unverified clients and distribution paths stay Preview until a reproducible test proves them available.

The Yapture CLI v2 implementation reached an internal architecture milestone. The candidate includes an OAuth 2.0 + PKCE flow, an Ink-powered TUI, and structured JSON output for agent and shell workflows.

The implementation is designed so an interactive TUI and --json automation can share one command surface across authentication, tasks, workspaces, search, and sync.

This entry records code progress, not general availability. Public binaries, installation instructions, authentication hosts, and cross-platform smoke tests still require verification before the CLI moves out of Preview.

Next verification gates: package provenance, signed binaries, authentication smoke tests, and tested install paths.

Dispatch, a Tauri 2 desktop client experiment, reached an internal implementation milestone. Its 420×700 sidebar explores notification aggregation, keyboard-first terminal control, and text expansion in one surface.

The candidate interaction model includes a filterable notification feed, vim-style bulk actions, pane focus, and a commander mode for terminal prompts.

The text-expansion prototype covers form, clipboard, shell-evaluated, and randomized variables, with an importer concept for existing configurations.

This is not a public-beta announcement. Platform support, permissions, signed packages, release links, and deep-link behavior remain unverified until distribution is tested end to end.