An agent in the terminal does one thing at a time and only while you're watching. A queue solves that: each request becomes a saved task, picked up one at a time and resumed if the machine goes down. inemaccbot is a Telegram bot with this durable queue, running skills such as transcription, dubbing, explainer videos, courses, and reels. In multi-stage workflows, a human gate makes the bot stop and wait for your approval. This is where you go from doing the work to managing it.
Sequence 3 — Agent queues: inemaccbot works while you sleep
One agent on its own gets lost
It does one thing at a time, and only while you're watching.
It stops, work is lost
If the internet goes down or the machine restarts, the work in progress disappears.
Ten requests collide
Simultaneous requests compete for the same folder and the same agent.
You stuck at the screen
Without a queue, someone has to keep sending the next request.
Durable queue: nothing gets lost
Each request becomes a task saved in a SQLite database.
While it runs, the task sends a heartbeat. If the signal stops because the machine went down or the process froze, the task goes back in the queue and resumes. Before installing the bot, you can see the same idea in 30 lines with this repository's home-built queue:
mkdir -p fila/entrada
echo "Resuma em 5 linhas o que é uma fila de tarefas." > fila/entrada/01.md
echo "Liste 3 riscos de deixar um agente rodando sozinho." > fila/entrada/02.md
./ferramentas/fila-caseira.sh fila # replies in fila/feito/Skills that run as agents
You send the request on Telegram. The default engine is Claude Code, with Codex or OpenCode as alternatives.
Automated, with you in control
Multi-stage workflows, with the state saved at each stage.
The bot writes the copy
The workflow's first stage, without spending anything expensive.
Then it stops at the gate
You read it, make any needed changes, and approve or reject it.
Only then does it continue
Avatar, download, and video run after you say okay.
You define the tasks, gates, and rules. The agents run through the queue, and you decide at the points that matter. From doing the work to managing it.
Exercises in this sequence
Do them in order. Each exercise has a "ready when" criterion: move on only when it is true.
- E1
Map the queue on paper · 15 min
Ready when: 10 tasks are listed, and at least two have a gate.
- E2
A home-built queue in 30 lines · 30 min
Ready when: the tasks are in fila/feito/ and the queue picked up where it left off after Ctrl+C.
- E3
Install inemaccbot · 1 h
Ready when: /ping replies on your Telegram.
- E4
Ten tasks and go to sleep · 1 night
Ready when: you checked every result and noted how many were right the first time.
- E5
The gate · 30 min
Ready when: you rejected or corrected at least one text before approving it.
Courses, projects, and guides
Everything is open and free. Start with the first item on the list.
Build your queue
Once your queue is running, you can automate social media: that's sequence 4.
Open the inemaccbot guide →