Khushin Patel
Kapers / V1 foundation / in development

A personal assistant that makes the next action inspectable.

Kapers is an Apple-oriented assistant where natural input becomes a proposal, explicit approval becomes an accountable result, and Undo remains part of the record.

Kapers native Today prototype showing the next commitment.
Current direction

Proposal. Approval. Receipt. Undo.

Kapers was formerly Kris. The product is now presented under its own name, separate from this personal site.

It is designed around clear, bounded actions in the Apple ecosystem. The foundation is still in development; this is a product direction, not a claim that every integration is finished.

Interaction model

Nothing important happens in the background.

The system should show its intent, the user should approve the change, and the result should be recorded.

01 / proposal

Natural input is converted into a specific, reviewable action.

02 / approval

Approval is an explicit and visible decision, not an implication of typing.

03 / receipt

A receipt follows a confirmed result; Undo preserves a way back.