Local companion
It detects installed agents, reads their accessible histories, classifies sessions and serves searches on your machine.
Local-first architecture
Your AI memory lives on your machine, first.
Tramya reads the histories already sitting on your device. The public website does not automatically receive your conversations, your repos, or your files.
Three layers, three control levels
What Tramya sees, and what it does not.
Web dashboard
Once paired, it asks the companion for what it needs. Access is revocable and your local content is never published as a web page.
Optional Cloud vault
Cloud receives a device-side encrypted copy. The recovery key stays with you and must be stored separately.
Transparency
What Tramya can and cannot retrieve.
| Data | Available | Condition |
|---|---|---|
| Visible messages | Yes | Written by the agent or captured with your consent |
| MEMORY.md, CLAUDE.md, AGENTS.md files | Yes | Present and readable in the project scope |
| Tool calls and visible outputs | Depends on the agent | The source must record them |
| Hidden internal reasoning | No | Not exposed by providers |
| AI provider passwords | No | Never needed for local reads |
Privacy and AI memory
Can the Tramya website see my local projects?
Not by default. The paired dashboard talks to your companion; the public site and search engines do not have access to your projects.
Why create an account if data stays local?
The account manages downloads, paired devices, Free / Pro / Cloud entitlements and revocation. Your conversations do not become commercial data because of it.
What if I lose my Cloud recovery key?
In the announced architecture, Tramya cannot recover it for you. Keep it in a password manager or a secure vault.