Use what we built, or build your own on the same parts.
Yapture provides a ready-made app plus clients, a market, and a studio. The same parser, list engine, and permissions can support a product with a completely different shape.
- Title
- Bring medication list
- Priority
- high
- Assignee
- alex
- Workspace
- care
- Due
- friday
Every client retains the line you wrote and its parsed fields.
Different interfaces, same tasks and lists.
These entries correspond to real repositories. Their status labels describe release evidence, not ambition.
Yapture App
Manage tasks, notes, events, goals, and routines in the first-party web workspace.
Built from: Script · Lists · Actions · Workspaces
Yapture for Chrome
Select text on a page and turn it into a task from the popup, side panel, or new tab.
Built from: Script · Lists · Archives · Plugins
Yapture Desktop
Use a native window with tasks, notes, calendar, macros, and notifications on your desktop.
Built from: Script · Lists · Macros · AI actions
Yapture for Slack
Create and complete tasks through Slack slash commands and Block Kit buttons.
Built from: Script · Tasks API · Actions
Yapture for Discord
Add tasks from Discord with slash commands, embeds, and approval buttons.
Built from: Script · Tasks API · Signed actions
GP.Family
Coordinate medication, appointments, and family tasks in a care-focused interface.
Built from: @yapture/nlp · @yapture/script-ui · List primitives
A care app should look like care — not like a task manager.
GP.Family uses Yapture's parser and list engine beneath a care-focused interface. It owns roles, sensitive-data policy, documents, and the entire look — while keeping the same tasks and priorities any Yapture client can read.
Read the implementation case study →Care roles, documents, sensitive-data policy, and the complete care experience.
Tasks, priorities, assignees, due dates, and list permissions — readable by any client.
Four ways to add to the ecosystem.
See how the parts become an outcome.
Recipes show the boundary: Yapture carries tasks and coordination; the host owns the domain expertise and consent.
Your lists. Your interface.
Build on the same parts the first-party app uses.