The steps for hooking five work tasks onto one small PC
With one always-on small desktop serving as a dedicated machine for agent work, the process of hooking up five repetitive tasks using nothing but a single commercial coding agent is shown screen by screen. Worth borrowing as a skeleton are the split between scheduled runs that go every morning and event-driven runs that wake only when a message arrives, and the rule that services with no official integration are plugged in directly via MCP. The most practical piece is an approval gate that, rather than sending email automatically, only goes as far as saving a draft so that a person presses the final button; it also confirms that the automation settings stay in natural language rather than code, so the person in charge can edit them directly. On the other hand, it connects full access to bank accounts and email as is, and never once deals with failure handling, logging or separation of permissions, so this is material from which to take only the operating patterns and discard the security setup.
Key points
- Splits scheduled and event-driven runs according to the nature of each task
- Email goes only as far as a draft, with a person stepping in just before sending
- Services not on the integrations list are connected directly via MCP
- Least privilege, failure handling and logging are not covered at all
This is a note: my own write-up after reading several sources. It has no source link; events checked against a source are kept as records.