Lesson 3 · 20 min
Before 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.
Start lesson
Goal: run the homegrown queue, interrupt it halfway through, and explain why the second run doesn’t redo what’s already done.
Each request is a .md file that moves between folders.
Scroll down: each step below lights up its part of the diagram.
Each .md file is a request, written the way you’d write it in chat. The order follows the file names.
The script moves the file here before calling the agent. If you press Ctrl+C or the computer crashes, it stays here, which makes it possible to resume.
It worked (exit code 0 and a non-empty response): the final file contains the request, a line with ---, and the agent’s response.
It failed or the response was empty: the file goes here with the exit code and what the agent printed. The queue moves on to the next task.
At startup, the script returns anything left in rodando/ to entrada/. Anything already in feito/ is never redone.
Click each folder. The key is rodando/: the task only leaves that folder when it finishes, moving to feito/ or falhou/.
Run it, interrupt it halfway through with the Ctrl+C button, then run it again.
Illustrative browser simulation: the tasks don’t actually run. The failure is intentional, to show the falhou/ folder.
It’s in ferramentas/fila-caseira.sh in the jornada-agentes repository. Both engines run through your subscription.
git clone https://github.com/inematds/jornada-agentes.git cd jornada-agentes mkdir -p fila/entrada echo "Summarize in 5 lines what a task queue is." > 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
mkdir -p "$PASTA/entrada" "$PASTA/rodando" "$PASTA/feito" "$PASTA/falhou"
# resume: anything left in "rodando" (crash, Ctrl+C) goes back to the queue
for f in "$PASTA"/rodando/*.md; do [ -e "$f" ] && mv "$f" "$PASTA/entrada/"; done
for f in "$PASTA"/entrada/*.md; do
[ -e "$f" ] || { echo "empty queue"; break; }
nome=$(basename "$f")
mv "$f" "$PASTA/rodando/$nome" # picks up the task (only one at a time)
saida=$(claude -p "$(cat "$PASTA/rodando/$nome")" < /dev/null 2>&1); rc=$?
if [ $rc -eq 0 ] && [ -n "$saida" ]; then
# request + --- + response go to feito/
else
# request + ERROR (rc) + output go to falhou/
fi
done→ 01.md feito → 02.md feito entrada: 0 · feito: 2 · falhou: 0
rodando/ to entrada/.rodando/ before calling the agent.feito/. Otherwise: falhou/ with the exit code.Use two tasks from your queue on paper (lesson 2).
Create two or three tasks in fila/entrada and run fila-caseira.sh. In a second run, interrupt with Ctrl+C while a task is in rodando/, check the folder, and run it again.
Done when: the tasks are in fila/feito with their responses, and you saw the queue continue where it left off after Ctrl+C.
The explanation appears after your answer.
Question 1 of 3
You interrupted the queue in the middle of a task. What happens when you run it again?skill
Question 2 of 3
Why does the script move the file to rodando/ BEFORE calling the agent?
Question 3 of 3
The agent responded, but the response was empty. Where does the task go?
Choose an option. The explanation appears after you try.