a personal agent that runs continuously on a server and is reachable wherever i already am, over whatsapp or telegram. it holds memory across every conversation rather than starting fresh each time, which is the single thing that decides whether an assistant becomes useful or gets abandoned.
it reads my mail, my recovery and sleep from whoop, my activity from strava, and my orders, so it has the context without being told it. a separate orchestrating agent decides what to actually do with a request, and codex handles the work that is really code.
i have rebuilt it five times over several years. each rewrite kept the same question and threw away the answer.
five attempts
- 01
jarvis v0
the first attempt. scripted commands, no memory, and it forgot everything the moment it closed. it taught me the problem was never the interface.
speech in and speech out, on google's speech api and gtts. it could open applications, tell me the weather, play something on spotify and read my calendar.
- 02
eclipse
enhanced cognitive linguistic interactive personal support engine. python, nlp and mysql. the first version with a real store behind it, and the first that could answer a question about last week.
flask, mysql and llama 3.1, with a login and a chat history in a side panel. still speech to text and back, but now it remembered who was talking.
- 03
eclipse obsidian
moved onto a vps behind a custom pwa, running on cerebras at roughly three thousand tokens a second. a github hook ingested my obsidian journal every night at 2am, so my second brain and the agent were finally the same thing.
faiss and sentence transformers over my notes. cerebras for the main model with openai as the backup. redis for sessions, sqlite for long term memory. fastapi on a digitalocean vps behind nginx, next.js on vercel, github actions to deploy. similar questions were answered from a five minute cache.
- 04
eclipsn
rebuilt around a knowledge graph instead of a flat store, with gmail and whoop feeding it. the graph made connections between things i had never explicitly linked.
split in three: a next.js front, a node gateway that owned the gmail oauth, and a python brain on fastapi and langchain. postgres with pgvector underneath. gmail was read only, and its tokens were encrypted with aes-256-gcm.
- 05
eclipse
the current one. always on, reachable over whatsapp and telegram, with an orchestrating agent above it and a memory layer underneath.
what it is plugged into
- telegram
- whoop
- strava
- gmail
- memory layer
- codex
- orchestrating agent
- backed by open source hermes
