Tasks, notes, and events that keep their original sentence.
Everything in Yapture starts as a line of text you can read. The app adds structure — priority, dates, people — without ever hiding what you wrote.
Pick up prescription #!high #+alex #@care due:tomorrow Four terms. Everything builds on them.
One line of work.
A shareable collection of yaps with permissions.
The way you type structure: #!high, due:friday, #+alex.
Any place a list shows up: web, Chrome, Slack, Discord, desktop, an agent.
Works on the train. Syncs at the station.
Changes persist on the device and reconcile when connectivity returns. No data leaves your machine until you choose to share the list.
Inspect the list primitivesLists work offline. Edits save locally with no round-trip.
When connectivity returns, queued changes reconcile automatically.
Every connected client sees the same list. Conflicts resolve deterministically.
Five places to use the same list.
The complete workspace — lists, calendar, goals, routines, and search across everything.
Capture from any page without leaving it. Side panel, quick-add puck, and context menus.
A native window with global shortcuts, the commander, and system-level integrations.
Turn a message into a task where the conversation is. Slash commands and Block Kit controls.
Slash commands, embeds, and modals your server can act on.
Build a system around the goal.
A useful goal is more than a label. Connect it to routines, time you actually have, portable tasks, and a policy for choosing what deserves attention today.
- 01OutcomeThe result and horizon you define.
- 02PracticeRepeatable behavior, not an opaque streak.
- 03AvailabilityLocal windows before calendar connection.
- 04Portable workReadable Script and inspectable structure.
The builder is a local reference recipe. It does not connect a calendar, create account data, or claim a finished routine-management surface.
Name the outcome.
The goal remains a readable sentence. Yapture adds a stable reference and horizon without replacing your language.
#^run-a-comfortable-5kAI that learns how you work — and stays yours when you leave.
Four visible weights coalesce into one policy for the goal you wrote. A deterministic decision layer explains the recommendation. No schedule, reorder, or agent action is executed here.
Your policy. Fully auditable.
POLICY
Complete tempo intervals
Goal impact is the strongest contribution under your policy. Every scored attribute has accepted evidence.
Complete tempo intervals is recommended with score 72 and 96 percent confidence.
AI Control Panel
Drag the sliders to change how tasks are ranked. The list re-sorts in real time.
- #10.82
- #20.75
- #30.62
- #40.58
- #50.50
This model is stored on your device. Export it as JSON anytime — it works without Yapture.
Powered by AIPeople and agents share one list — with different keys.
Account teams and capability-based lists solve different onboarding problems. Both need visible roles, provenance, and an audit path.
Coming soon Read the capability model| Role | Can | Access |
|---|---|---|
| Owner | Create, edit, delete, share, govern | Capability or account |
| Editor | Read, create, edit | Explicit grant |
| Agent | Read, create within scope | Policy + permission |
| Viewer | Read only | Read-only token |
Product truth has a history.
The changelog records features, fixes, and maturity transitions openly.
Site v2 foundation milestone
The site v2 foundation reframes Yapture around zero-friction starts, portable text, and one truth across clients.
CLI v2 implementation milestone
CLI v2 architecture reached an internal milestone; public packaging and distribution remain verification pending.
Dispatch desktop implementation milestone
Dispatch's desktop interaction model reached an internal milestone; public builds and support claims remain verification pending.
Keep the meaning. Change the client.
Write one line. Use it in the full app, a browser extension, Slack, Discord, or your own product.