Day 6 — Agents in your pocket

Create your bot with BotFather

In Telegram, find @BotFather — Telegram's official bot for making bots (blue checkmark). Send it:

/newbotBotFather: Alright, a new bot. How are we going to call it?Aigerim's AgentBotFather: Good. Now let's choose a username… must end in "bot".aigerim_agent_botBotFather: Done! Use this token to access the HTTP API:7712345678:AAH-example-token-keep-it-secret

The token is a key to your bot. Treat it like a password: never post it, never leave it in a project folder. Copy it somewhere private for the next step.

Step done when: BotFather congratulated you and the token is copied.

Hand the key to Hermes and start the gateway

On your laptop, inside WSL (Windows) or Terminal (Mac):

hermes gateway setupPaste your Telegram bot token: [paste]…setup asks for / detects your Telegram user id…hermes gateway startGateway running. Message your bot on Telegram.

Step done when: you text “hello” from your phone and Hermes answers in Telegram.

Send real work — text and voice

Try these from your phone, one at a time:

What do you remember about my main project? Short bullets.

Read spec.md in my my-tool folder and suggest one improvement.

🎤 (voice note) Summarize what we decided about my project this week.

Voice notes are transcribed automatically — dictating a task while walking is a genuinely different way of working. Everything you learned this week now works from anywhere your phone works.

Step done when: all three answers arrived, including the voice one.

Give Hermes deploy power (one-time setup, at the laptop)

Hermes can edit your site's files — but publishing went through drag-and-drop until now. Netlify has a command-line tool for exactly this. Tell Hermes:

Install the Netlify CLI and log it into my Netlify account (run netlify login — I'll approve in the browser). Then link my my-site folder to my existing Netlify site and prove it works: make no changes, just run a production deploy from that folder (netlify deploy --prod --dir=.) and give me the live URL.

Step done when: Hermes reports a successful production deploy and the live URL opens.

The finale: change your live site by voice

Close the laptop lid — no, really, leave it running but closed (see the box below) or just step away from it. Open Telegram on your phone and send a voice note:

In my my-site folder: change the accent color to deep orange, and add a line to the footer that says "updated by voice". Then deploy to Netlify production and tell me when it's live.

Wait for the reply. Then open your app icon on the home screen — the one you installed on Day 3 — and pull to refresh.

✦ You spoke into your phone, and real software on the real internet changed — visible in your own app, laptop untouched. That's the promise from week 1, delivered.

Step done when: the voice-ordered change is visible in the home-screen app on your phone.

Decide your own away-rules (optional, recommended)

Some people love that the phone can change production; some want the phone limited to reading and planning. Both are valid — what matters is that it's a decision, not an accident. Pick one and save it:

Standing rule, save to memory: from Telegram you may read, plan, and answer — but never change or deploy files until I confirm from the laptop.

— or —

Standing rule, save to memory: from Telegram you may edit and deploy my-site freely, but always send me what changed and the live URL; for any OTHER folder, ask before changing files.

Step done when: Hermes confirms your rule and shows it saved in memory.