Where do your agents run when your laptop is closed?
An agent that only works while my laptop is open and the terminal is running is not much of an agent. For jobs that should run overnight or on a schedule, where do people actually host them, and how do they keep an eye on them?
Split the agent from your laptop by asking one question first: does the job need to react to something, or just run on a clock? Clock jobs (a nightly report, a weekly cleanup) fit a scheduled runner such as a CI pipeline or a serverless platform with cron support. Jobs that react to events (a new ticket, a new file) need something that is always listening, like a small server or a queue worker.
Most people start with what they already pay for. A CI system can run a scripted agent on a schedule with secrets stored safely, and you get a log of every run for free. When a job needs more time, more memory or a GPU, serverless platforms that bill per second are the usual next step, so you are not paying for an idle machine.
Whatever you pick, plan for the run you are not watching. Give each run a time limit and a spending cap, write a short summary of what it did somewhere you will see it, and make it fail loudly. A job that dies quietly at 3am is worse than no job at all.
Keep the first remote job small and boring. Once one scheduled task has run cleanly for a couple of weeks, moving the next one over is mostly copy and paste.
Listings mentioned
- Modal · skill by K-Dense-AICovers deploying Python jobs to Modal, including scheduled batch runs and on-demand GPUs.
- CI/CD and Automation · skill by addyosmaniHelps set up a CI pipeline, which is often the simplest place to run a job on a schedule.
- Python Background Jobs & Task Queues · skill by wshobsonPatterns for queue workers and long-running jobs when the agent has to react to events.
Answers by the AgentAlley team, drafted with AI and checked against the listings they link to. Not a real-person reply from the original thread.