INEMA Series · 4 sequences

From Chat to Agent Creator

The terminal, your Jarvis, queues, and automated social media. One step at a time, with exercises that tell you when you’re done.

From Chat to Agent Creator: learn fast in 4 sequences — OSWork, Jarvis, queues, and social media
In brief

This repository brings together the exercises from the INEMA series “From Chat to Agent Creator.” It has four sequences, in order: use an agent in the terminal, build a personal assistant on Telegram, put tasks in a queue that runs on its own, and automate social media with your approval. It’s for people who already use AI chat and want it to work independently. Each exercise has a “Done when” criterion to show you when you’re finished. You need a computer, a terminal, and Claude Code or Codex.

What it is

Four steps to move beyond chat

In chat, you’re the driver the whole time: ask, copy, paste, adjust. An agent reads your files, carries out tasks, and keeps working while you do something else. The shift is about changing where you work: from chat to the system.

From Chat to Agent Creator: terminal, AGENTS.md, your Jarvis, durable queue, human approval gate, and automated social media

🪜 Order matters

Without sequence 1, the others won’t hold up. Start with folders and the terminal, then the assistant, then the queue, and only then social media.

⚙️ No magic

Nothing renders while you sleep if the system isn’t running correctly. Without a queue and an approval gate, social media automation just means posting mistakes faster.

✅ Done when

Each exercise ends with a criterion you can check: the page opens, git status doesn’t show .env, the bot remembers you.

The 4 sequences

The whole journey, in order

Each sequence builds on the previous one. Follow them in order, and move on only when you’ve completed the exercises in that stage.

1 · OSWork: terminal→ 2 · Jarvis: INTELECTO→ 3 · Queues: inemaccbot→ 4 · Automated social media
1

💻 From chat to the terminal

Folders, AGENTS.md, Claude Code or Codex working inside the folder, Git as a safety net, and secrets in .env.

2

🤖 Your Jarvis

INTELECTO: a personal assistant in Python on Telegram, with memory and the personality you define. Cloud model (OpenRouter) or local (Ollama).

3

📥 Agent queues

inemaccbot: a Telegram bot with a durable SQLite queue, recovery after a crash, agent skills, and workflows that pause at a gate for your approval.

4

📣 Automated social media

r7e (a reel in 7 steps), promoavatar, and xviral (finviral, saudeviral, advviral): sourced numbers, your face, and regular publishing.

Exercises · step by step

Exercises for each sequence

These are extra exercises to do alongside the courses. Each one has an estimated time and a "Done when" criterion. Open the file on GitHub and follow the order.

1

Sequence 1 — From chat to the terminal (OSWork)

Goal: get an agent working inside one of your folders.

  • E1Your first folder in the terminal
  • E2The employee handbook: AGENTS.md
  • E3Your first task
  • E4The safety net: Git
  • E5Secrets don't belong in the text
  • E6The agent reads your files
2

Sequence 2 — Build your Jarvis (INTELECTO)

Goal: your own assistant that talks through Telegram, remembers conversations, and has your personality.

  • E1Design your Jarvis before installing
  • E2The bot on Telegram
  • E3Install
  • E4Memory test
  • E5Cloud or local
  • E6A real routine
git clone https://github.com/inematds/intelecto.git
cd intelecto
./start.sh   # the assistant asks for the Telegram token, model, and personality
3

Sequence 3 — Agent queues (inemaccbot)

Goal: send several tasks, step away, and find the work done, with a gate where you need to be involved.

  • E1The queue on paper
  • E2A homegrown queue in 30 lines
  • E3Install inemaccbot
  • E4Ten tasks, then go to sleep
  • E5The gate
4

Sequence 4 — Social media on autopilot

Goal: your niche channel publishing regularly, with numbers, sources, and your face, while you approve what matters.

  • E1A reel in 7 steps, on paper
  • E2The top 5 in your niche
  • E3The source-backed foundation
  • E4A 60-second script with the source on screen
  • E5The schedule
  • E6The gate before publishing
Tool · homegrown queue

A task queue in 30 lines

Before using inemaccbot, understand the idea with ferramentas/fila-caseira.sh from this repository. Each file in entrada/ becomes a task; the response goes to feito/; any task that errors goes to falhou/. Running it again picks up only what remains.

entrada/→ rodando/→ feito/ or falhou/
git clone https://github.com/inematds/jornada-agentes.git
cd jornada-agentes
mkdir -p fila/entrada
echo "Summarize what a task queue is in 5 lines." > fila/entrada/01.md
echo "List 3 risks of leaving an agent running on its own." > fila/entrada/02.md
./ferramentas/fila-caseira.sh fila          # default engine: claude
./ferramentas/fila-caseira.sh fila codex    # or Codex, through your subscription

Resuming: if a run stops or you press Ctrl+C, the task in rodando/ returns to entrada/ on the next run. It’s the same idea as inemaccbot’s durable queue, in pocket size. View the script

Series videos

Five videos, one for each step

An opening video covering the entire journey, plus one video for each sequence. They are in production and will be published on the INEMA FTD channel. The scripts are already in the repository.

Get started today

Start with sequence 1

The courses, guides, and projects for each sequence are on INEMA.CLUB, open and free. Move beyond chat and start creating your own agents.