Queues: ten tasks and go to sleep|INEMA.CLUB-PRO

Course · step 3 of From chat to agent · 7 lessons

Queues: send ten tasks, go to sleep, and check the results in the morning

An agent in chat does one thing at a time, and only while you watch. In this course, you’ll set up your queue: decide what goes in, understand a simple queue, install inemaccbot, add gates before the important steps, and learn to review the batch the next day.

Start lesson 1 Back to the training overview
Office at night with a laptop showing a list of completed tasks and a phone beside it.
  • 7lessons
  • 7hands-on exercises
  • 1real queue night
  • 2videos

The lessons

In the order you’ll do them: first understand and decide, then install, send, add gates, and review. Prerequisite: steps 1 (terminal) and 2 (your Jarvis) of the training.

  1. Lesson 1 · 12 minFrom chat to queue: why save tasksIn chat, the agent does one thing at a time and only while the window is open. A durable queue stores each request, runs one at a time, resumes after a crash, and separates what worked from what failed.
  2. Lesson 2 · 15 minWhat goes to the queue (and what stays with you)Not every task should go to the queue. Before installing anything, you run your list through three questions and get a table: runs on its own, runs with a gate, or stays with you.
  3. Lesson 3 · 20 minA Homegrown Queue in 30 LinesBefore the bot, you’ll see the whole idea in a short script from the jornada-agentes repository: four folders, one task at a time, resume after Ctrl+C, and failures kept separate with the reason.
  4. Lesson 4 · 20 minInstall inemaccbot until /ping respondsinemaccbot is a Telegram gateway with a durable queue: you send a request from your phone, and your computer (or a VPS) runs it as an agent. In this lesson, you install the bot, pair it with your chat, and set it up to run as a service.
  5. Lesson 5 · 18 minTen tasks and go to sleepWith the bot running, your paper queue becomes messages. Each line is a skill with an input; the bot puts each request in the right queue, runs it within that skill’s limits, and lets you know in the chat when it’s done.
  6. Lesson 6 · 18 minWhere the gates go: stop before what mattersA flow is a task with several stages, with the state saved at each one. The gate is the stage that ends and pauses: the bot shows you what it did and waits for you. Approving, correcting, or rejecting is when you manage the work instead of doing it yourself.
  7. Lesson 7 · 18 minThe next day: review, measure, and create the new ruleThe overnight queue is only worthwhile if the morning is short. Read the report in the chat, check each result against what you expected, note how many were right on the first try, and turn the task that failed most into a new rule.

Who it’s for

  1. 1People who already use an agent in the terminal (step 1) and have an assistant with rules (step 2).
  2. 2People who repeat the same tasks every week: transcribe, summarize, draft, generate video.
  3. 3People who want to leave the computer working overnight without worrying about losing what it did.

What you’ll be able to do

  1. 1Sort your tasks into: goes in the queue, needs a gate, stays with you.
  2. 2Run a simple queue and see how it resumes after an interruption.
  3. 3Install inemaccbot until /ping responds in your Telegram.
  4. 4Send a batch one night, approve it at the gate, and measure in the morning how many came out right on the first try.
  5. 5Turn the task that failed most into a new rule.