YOU

YOU is an open source prototype for a personal context layer: a private, inspectable memory of the people, plans, preferences, routines, and commitments in your life. It can help an assistant make useful suggestions while showing why it believes something and how certain it is. The last agent you’ll ever need is the product ambition: YOU stays with you while underlying models can change.

The model is replaceable. The memory belongs to the user. The long term goal is a portable context service that any authorized harness can use through a scoped HTTP API or MCP adapter.

Prototype status: The app is an interactive frontend with fictional seed data. Changes are saved in this browser's localStorage. It has no real connectors, authentication, live AI, device telemetry, ticket purchases, or production MCP server. The simulated Ask YOU answers use seeded facts and respect available/private memory settings.

Explore the demo

Open the interactive YOU demo · Follow the 90-second walkthrough

The public demo starts with Alex, a fictional persona, and invented people and events. It does not import contacts, read your computer, or connect to your accounts. Anything you type into the demo stays in that browser's local storage unless you choose to export it. Use fictional details when sharing screenshots or feedback.

Screenshots

Fictional sample data, captured from the running prototype:

Try it locally

Requires Node.js 22.13+.

npm ci
npm run dev

Open the local URL printed by the development server. npm run build makes a production build.

What works in the demo

• A first-run experience that selects possible sources and an assistant harness, creates a personal engram, and saves routine preferences. All connection and scheduling choices are simulated.
• A calm suggestion feed for check-ins, plans, relationships, and open commitments.
• A memory browser with known, inferred, unknown, and needs review states, confidence, provenance, and verification dates.
• People profiles, a relationship map, a sample timeline, and source explanations.
• Manual memories, important dates, and reminders; profile editing; dismissing and handling suggestions.
• A simulated Ask YOU view that answers from visible sample memory and says when it does not know.
• Connection placeholders, per-memory availability, local export, and demo reset.

Product principles

1. The user owns the engram. Context is portable and exportable.
2. Every claim has a state and source. An inference is never silently promoted to a fact.
3. Agents receive minimum necessary context. Access is scoped, revocable, and auditable.
4. Sensitive observations invite conversation. A busy calendar may justify a gentle question, not a conclusion about someone's wellbeing.
5. Suggestions remain optional. YOU can be quiet, and users can correct, dismiss, or exclude information.
6. Connectors require permission. No impersonation, fake accounts, or covert collection.

Repository map

app/page.tsx              Interactive prototype
app/api/protocol/route.ts  Read-only discovery of the proposed protocol
data/demo.ts              Fictional people, memories, insights, events, connectors
lib/context-contract.ts   Model-neutral fact, evidence, grant, and scope types
docs/ARCHITECTURE.md      Roadmap for a real local-first service and MCP/API
docs/LAUNCH.md            Honest launch copy and outreach plan

Next implementation milestones

1. Split the browser demo state into a local encrypted datastore with migrations and an import/export format.
2. Build a consented import pipeline: connector → raw event → identity candidate → fact candidate → user review → graph update. Keep raw source and extracted fact separate.
3. Add an HTTP API with user authentication, scope grants, query logs, and an MCP adapter. The same service should work with Claude, OpenAI, Codex, local models, and custom agents.
4. Validate identity matching and inference with uncertainty tests, provenance checks, and correction propagation.
5. Add official connectors where permitted. Device activity and local event discovery need platform-specific feasibility work; they are not connected here.

See the architecture for the proposed data model and boundaries.

Contributing and security

Please read CONTRIBUTING.md and SECURITY.md before sending a change involving personal data or a connector. This project uses the MIT license.