echOS

why echos exists

The friction of capturing a thought is usually enough to kill it. You're walking, an idea hits, and by the time you've opened an app and figured out where to put it, it's gone — or worse, it's in a pile you'll never look at again.

EchOS is a personal AI knowledge system that tries to remove that friction entirely. You send a message to Telegram — text, voice, URL, photo — and it figures out the rest: transcribing, categorising, tagging, indexing. No forms. No schemas. No dashboards.

It started as a personal tool built for one. It stays that way.

what's inside

• A Telegram bot as the primary interface — talk to your notes the way you'd talk to a person
• Hybrid full-text and semantic search with temporal decay, so "what did I save about memory management?" actually works
• Plain .md files in ~/echos/knowledge — open the folder in Obsidian and everything is right there, always
• A writing mode that reads your notes for source material and drafts in your voice, not generic AI prose
• An MCP server so Claude Code, Cursor, and other AI tools can read your knowledge base
• A plugin system for capturing YouTube transcripts, articles, and anything else you want to pipe in
• A Homebrew tap and a one-liner installer for macOS and Linux

It runs on your own server. Your notes never leave your machine except for the AI API calls you configure yourself.

the core loop

You:    Save this → [pastes article URL]
EchOS:  Saved. "How Rust handles memory safety" — tagged rust, programming.
        I pulled the key points if you want a summary.

You:    What do I know about memory management?
EchOS:  Found 7 notes. The Rust piece you just saved, two older ones on
        GC pauses, a voice note from last Tuesday where you were ranting
        about malloc...

You:    Write a short post about it — my style, technical but readable.
EchOS:  [drafts a post grounded in your actual notes, in your voice]

No subscription. No sync fees. No vendor deciding what to do with your thinking.