Setting it up is one thing. Running it is what makes it yours.
Memory, secrets, data, and the daily loop — how to actually run and own your agent.
Narration
A three minute plain-words narration.
The core promise
“Setting it up is one thing. Running it is what makes it yours.”
How it knows you
The memory keys behind your agent.
Behind the scenes, the agent keeps a set of stored facts: your age, location, what you’re into, what you’re working toward, what gets in the way, and what is off limits. These are called memory keys.
They make it personal. When it writes your morning message, it reads these keys to tailor every word. That is why the setup questions matter.
They let you steer it. Change the stored fact about what is getting in the way, and it changes what it suggests. You are not stuck with the setup answers.
Off limits is honoured silently. Name a topic or person it should not raise, and it just does not. You never have to repeat yourself.
Guard your secrets
The dot env file, and the key rule.
Some services need a key to let your agent in — Jina, OpenRouter, the delivery bot. These keys live in a hidden file on your machine called the dot env file.
Never put a key in the chat. No key in a public file, either.
Guard it like a password. It opens your account and your credit.
If a key leaks, rotate it. Do not just delete it. Get a fresh one from the service and swap it in.
Where your data lives
What local-first really protects.
STAYS HOME
On your device
Memory. Your plans. Your voice audio. The model, if you run it locally. These never leave your machine.
CROSSES
Over the network
A web search goes out to Jina. Cloud-model thinking goes to OpenRouter. Delivering a message to your phone goes through Telegram.
Make the choice informedPrivacy matters most? Run the model locally and keep more at home. Want a stronger brain on a modest machine? Use the cloud and accept that your words travel. Neither is wrong — it is a trade-off you now understand.
The daily loop
The engine that runs it.
Three scheduled jobs, called cron jobs, fire at set times: the Morning Minute at six, the Check-In after school, the Planning Session before bed. Each job wakes in its own fresh session.
What fires each morning: it reads the plan and your stored facts, picks the day’s essential, writes the briefing, calls the voice, uploads it, and delivers it to your phone.
Why it remembers you: it reads those memory keys fresh each run. That is why every morning is a little different and always feels personal.
You control the schedule: pause it, resume it, change the time or days, without breaking anything.
Three ideas people mix up
Skills, tools, and personality.
SkillsThe playbooks you teach it — like “help me revise for history.”
ToolsThe capabilities it already has — search, files, terminal.
PersonalityThe character it speaks as.
Keep it moving
Running is not set-and-forget.
The essentials pivot as you grow. The weekly live session keeps it human. The stored facts can change as you change. It adapts because you are meant to keep it moving with you.
Running itKnow how it remembers you. Guard your keys. Understand where your data lives. Learn the daily loop. Do that, and you are not just using the agent. You are running it, and it is yours. Return to the overview →