Why Respire
An agent can lose useful context when a conversation, project or device changes. Respire keeps reusable knowledge outside an individual session so that the user can find, review and maintain it.
flowchart LR Work["Start a task"] --> Recall["Find related knowledge"] Recall --> Review["Read and verify"] Review --> Act["Do the work"] Act --> Save["Save useful conclusions"] Save --> Next["Reuse in a later task"]
| Principle | Product behavior |
|---|---|
| Knowledge remains inspectable | Records have identifiers, content and relationships |
| Context can travel | Devices synchronize encrypted records |
| Ownership stays local | Decryption keys remain with the user |
| Interfaces stay simple | CLI, desktop and agent integrations share public behavior |
| Core has a defined boundary | Retrieval and memory policies ship through a binary SDK |
See getting started and architecture for the practical workflow.