E1 · Design your Jarvis
15 minWrite the meu-jarvis.md: name, style, what it should do, what it should never do, and what it needs to remember.
Done when: the file fits on one screen, and someone else could understand who your assistant is.
Lesson 3 · 10 min
A personal assistant written from scratch in Python, kept small on purpose: it talks with you on Telegram, remembers your conversations, and uses a cloud or local model. You stop opening a website to chat: the assistant is yours.
Start lesson
Objective: design, install, and put to work an assistant with memory and a personality you define.
From Telegram to the model and back.
Scroll down: each step below lights up its part of the diagram.
You chat on Telegram, on your phone or computer, like you would with any contact.
The bot is the entry point. You create it with @BotFather using /newbot and store the token only in .env, as you learned in step 1.
INTELECTO receives the message, combines your assistant’s personality with what it remembers about you, and puts together the request for the model. It’s small by design, so you can understand and change it.
The model generates the response. In the cloud (OpenRouter), it’s more powerful and costs money per use; locally (Ollama), it runs on your computer, if it can handle it.
You write in Telegram, INTELECTO combines personality and memory, the model responds, and the response returns to the same chat. It’s all yours, with the token stored in .env.
Want to see other assistant systems ready to install? The Events JARVIS section brings several together.
Click each step.
Before installing, write down who the assistant is: its name, how it speaks, three things it should do every week, three things it should never do, and what it needs to remember about you.
This file answers the installation questions.
Someone else reads the file and understands who your assistant is.
On Telegram, open @BotFather, send /newbot, and choose a name and @username.
Store the token only in .env.
The token doesn’t appear in any file besides .env.
Clone INTELECTO, export your briefing from the comparison page, and ask Claude Code or Codex to build from it and doc/intelecto.md, with tests.
Use the answers in your meu-jarvis.md. The full step-by-step guide is in lesson 4 of the step 2 course.
You send "hi" and it replies with the name and style you chose.
Tell it three facts about yourself one day, then ask about them the next day in a new conversation.
Then turn one weekly task into a standing request and use it five days in a row.
Every morning, when I send "day," list my three priorities based on what I told you yesterday.
Copy the template, fill it in, and only then install.
# My Jarvis ## Name and speaking style Name: How it speaks (formal, direct, humorous): ## What it should do every week 1. 2. 3. ## What it should never do 1. 2. 3. ## What it needs to remember about me - Profession: - Routine: - Preferences:
git clone https://github.com/inematds/intelecto.git cd intelecto/exemplo-jarvis python3 -m unittest discover -s . -p 'test_*.py' -v python3 smoke.py
Run the same question with both and record the results in a table:
The goal is to use your own numbers to know which model to use for what.
Prerequisite: complete sequence 1 (terminal, folders, .env).
Write the meu-jarvis.md: name, style, what it should do, what it should never do, and what it needs to remember.
Done when: the file fits on one screen, and someone else could understand who your assistant is.
Create the bot with @BotFather using /newbot and save the token in .env.
Done when: you have the token, and it doesn’t appear in any file except .env.
Clone INTELECTO, export the briefing, and ask the agent to build your Jarvis with tests (lesson 4 of the step 2 course).
Done when: you send "hi" and it replies with the name and style you chose.
Day 1: tell it three facts about yourself. Day 2, in a new conversation: ask about them.
Done when: it remembers without you repeating yourself.
Ask the same question with a cloud-based model (OpenRouter) and a local one (Ollama). Record the time, quality, and cost.
Done when: you can say which model to use for what, based on your own numbers.
Turn one of the tasks from E1 into a standing request and use it for a week.
Done when: you used it 5 days in a row and noted what to improve.
Full exercises: jornada-agentes/exercicios/02-jarvis.md. The extra challenge (the task list you send before going to bed) is the start of step 3.
INTELECTO on Telegram, with memory and personality.
The explanation appears after your answer.
Question 1 of 3
Why write the meu-jarvis.md before installing?competency
Question 2 of 3
The assistant didn’t remember what you told it yesterday. What’s the first step?
Question 3 of 3
When does a local model (Ollama) make sense?
Choose an answer. The explanation appears after your attempt.